VOS Startup and Shutdown a system (r282-03)

8/20/2019 VOS Startup and Shutdown a system (r282-03)

1/198

Stratus Computer, Inc.

R282-03

VOS System Administration:

Starting Up and Shutting Down a Module or System


2/198

Notice

The information contained in this document is subject to change without notice.

UNLESS EXPRESSLY SET FORTH IN A WRITTEN AGREEMENT SIGNED BY AN AUTHORIZED REPRESENTATIVE

OF STRATUS COMPUTER, INC., STRATUS MAKES NO WARRANTY OR REPRESENTATION OF ANY KIND WITH

RESPECT TO THE INFORMATION CONTAINED HEREIN, INCLUDING WARRANTY OF MERCHANTABILITY AND

FITNESS FOR A PURPOSE. Stratus Computer, Inc., assumes no responsibility or obligation of any kind for any errors

contained herein or in connection with the furnishing, performance, or use of this document.

Software described in Stratus documents (a) is the property of Stratus Computer, Inc., or the third party, (b) is furnished

only under license, and (c) may be copied or used only as expressly permitted under the terms of the license.

Stratus manuals document all of the subroutines and commands of the user interface. Any other operating-systemcommands and subroutines are intended solely for use by Stratus personnel and are subject to change without warning.

This document is protected by copyright. All rights are reserved. No part of this document may be copied, reproduced, or

translated, either mechanically or electronically, without the prior written consent of Stratus Computer, Inc.

Stratus, the Stratus logo, Continuum, StrataNET, FTX, and SINAP are registered trademarks of Stratus Computer, Inc.

XA, XA/R, StrataLINK, RSN, Continuous Processing, Isis, the Isis logo, Isis Distributed, Isis Distributed Systems, RADIO,

RADIO Cluster, and the SQL/2000 logo are trademarks of Stratus Computer, Inc.

Apple and Macintosh are registered trademarks of Apple Computer, Inc.

IBM PC is a registered trademark of International Business Machines Corporation.

Sun is a registered trademark of Sun Microsystems, Inc.Hewlett-Packard is a trademark of Hewlett-Packard Company.

All other trademarks are the property of their respective owners.

Manual Name: VOS System Administration: Starting Up and Shutting Down a Module or System

Part Number: R282

Revision Number: 03

VOS Release Number: 14.0.0

Printing Date: January 1998

Stratus Computer, Inc.55 Fairbanks Blvd.

Marlboro, Massachusetts 01752

© 1998 by Stratus Computer, Inc. All rights reserved.


3/198

Contents iii

Contents

Preface ix

1. The Continuum-Series System Console 1-1Front Panel Commands 1-1

Recovering a Hung System 1-6

System Messages 1-6Console Controller Messages 1-7

Console and Error-Log Status Messages 1-9Module Status Lights 1-9

Expansion Cabinet Lights 1-9

Unit Status Lights 1-9

2. The XA/R-Series Modular Control Panel 2-1

The Stratus Modular Control Panel 2-2

Control Panel Components 2-2Module Control Unit (MCU) 2-3

Operator Interface Unit (OIU) 2-3Other Control Panel Features 2-3

Status Display 2-3OIU Query and Control Messages 2-4

System Messages 2-5

Module Status Lights 2-7Unit Failure Lights 2-7

Control Panel Buttons 2-7

The Immediate Power Off Button 2-9

3. Starting Up a Module or System 3-1

Automatic Startup 3-1Single Module Startup 3-1

Automatic Startup Functions 3-2Handling Problems with Automatic Startup 3-2


4/198

Contents

iv VOS System Administration: Starting Up and Shutting Down a Module or System (R282)

Manual Startup 3-3

Disk Boot and Tape Boot 3-3The Steps in a Manual Startup from Disk or Tape 3-4

Link Boot 3-9Link Boot Module Requirements 3-9

The Link Boot Source 3-10

The Link Boot Server 3-10The Steps in a Link Boot 3-11

The Operating System Symbol Table 3-12

4. The Module Startup

Command File 4-1

The module_start_up.cm File 4-1Tailoring the module_start_up.cm File 4-2

5. Responding to Status Lights 5-1Module Status Lights 5-1

Expansion Cabinet Lights 5-1

Fault Indicator Lights on Boards 5-3

Board Testing 5-5

Board Failure 5-5System Problem Analysis 5-5

Proper Recovery 5-6

Recovery Procedures 5-7Recovering with Automatic Dump and Reboot 5-7

Recovering with PCP Execution 5-7Recovering a Hung System 5-8

Determining the attempt_auto_recovery Setting 5-8

Changing the attempt_auto_recovery Setting 5-9Continuum-Series Manual Recovery 5-9

Continuum-Series Automatic Recovery 5-10

XA/R-Series Recovery 5-11Recovering from System Initialization Process Failure

during a Boot 5-11

6. Shutting Down and Powering Off 6-1The module_shut_down.cm File 6-1

Planned Shutdowns 6-1

Emergency Shutdown 6-3


5/198

Contents

Contents v

7. Recovering from a Crash 7-1

Rebooting after a Crash 7-1Checking the Module Hardware 7-2

Checking for Disk Salvage and Recovery 7-3

Disk Salvager Errors 7-3Disk Recovery 7-4

Checking the Module Service Processes 7-5Checking for File Recovery 7-6

Understanding File Recovery 7-6

Disk I/O Concepts 7-7Checking for File Consistency 7-8

Checking Transaction-Protected Files 7-8

Checking Other Types of Files 7-9

8. Command Overview 8-1

broadcast 8-2

patch_file 8-4

patch_index 8-7

recreate_index 8-10

shutdown 8-20

test_index 8-26Current Session Requests 8-28

The help Request 8-28

The names Request 8-29The quit Request 8-30

Requests That Establish a Current Index 8-31The look_at Request 8-31

The use Request 8-33

Requests That Display Information 8-35The check Request 8-35

The dump_node Request 8-40The free Request 8-47

The status Request 8-48

Requests That Set Up, Display, and Alter Position 8-49The backward_index Request 8-49

The convert_key Request 8-51

The convert_key_range Request 8-53The forward_index Request 8-56

The locate_record Request 8-58The position Request 8-59


6/198

Contents

vi VOS System Administration: Starting Up and Shutting Down a Module or System (R282)

Buffer Management Requests 8-61

The create_buffer Request 8-61The delete_buffer Request 8-63

The display_buffer Request 8-64The dump_buffer Request 8-65

The fill_buffer Request 8-66

The list_buffers Request 8-67The set_buffer_byte Request 8-68

The set_buffer_length Request 8-69

The set_buffer_longword Request 8-70The set_buffer_text Request 8-71

The set_buffer_word Request 8-72The use_buffer Request 8-73

verify_end_of_file 8-74

verify_index 8-86

Appendix A. Control Panels A-1

The Control Panel for the 10-Slot XA/R Model 20 Module A-1Master Startup Procedure A-4

The LEVEL-7 Interrupt Button A-4

Recovery Procedures for No Activity A-5

Index Index-1


7/198

Figures vii

Figures

Figure 1-1. Continuum-Series Modules (PA-7100 Processor) Front Panel

Commands 1-2

Figure 1-2. Continuum-Series Modules (PA-8000 Processor) Front Panel

Commands 1-3

Figure 2-1. The Modular Control Panel 2-2

Figure 2-2. Control Panel Buttons 2-8Figure 5-1. Main Cabinet and Expansion Cabinet Status Lights 5-2

Figure 5-2. Logic-Chassis Board Lights 5-3Figure A-1. Control Panel for the 10-Slot XA/R Model 20 Module A-1


8/198

viii VOS System Administration: Starting Up and Shutting Down a Module or System (R282)

Tables

Table 5-1. Main Cabinet and Expansion Cabinet Lights 5-2Table 5-2. Logic-Chassis Board Lights 5-4

Table 5-3. Manual Recovery Command Sequence 5-9

Table 5-4. Automatic Recovery Command Sequence 5-10


9/198

Preface ix

Preface

The manual VOS System Administration: Starting Up and Shutting Down a Module or

System (R282) documents the procedures for starting up and shutting down Stratusmodules. It covers VOS Release 14.0.0 information for the following hardwareplatforms:

• all Continuum-series modules

• all XA/R-series modules

This manual is intended for system administrators.

Manual Version

This manual is a revision. Change bars, which appear in the margin, note the specific

changes to text since the previous publication of this manual. Note, however, thatchange bars are not used in new chapters or appendixes.

This revision incorporates the following changes.

• three new commands that help to diagnose and repair corrupted file indexes:

– verify_index

– patch_file

– patch_index

• the test_index command’s check request’s three new arguments:

-verify_record, -verbose, and -repair

• the recreate_index command’s three new arguments: -duplicate_path,

-syserr, and -recovery_macro

• module_shut_down.cm, a new user-supplied command macro that—if present

in the >system directory—will automatically execute prior to system shutdown

when the shutdown command is given


10/198

Preface

x VOS System Administration: Starting Up and Shutting Down a Module or System (R282)

Manual Organization

The manual contains eight chapters and one appendix.

Chapter 1 documents the Stratus system console found on Continuum-seriesmodules.

Chapter 2 documents the Stratus module control panels found on XA/R-seriesmodules.

Chapter 3 describes how to start up a module or system.

Chapter 4 briefly introduces the module startup command file.

Chapter 5 explains how to respond to problem lights on the control panels.

Chapter 6 explains how to shut down and power off a module or system.

Chapter 7 describes the procedures to follow when recovering from a crash.

Chapter 8 documents the commands that manage system availability and that

diagnose and repair file indexes.

Appendix A describes the control panel of the older 10-slot XA/R Model 20 Stratusmodules.

Related Manuals

Refer to the following Stratus manuals for related documentation.

• Introduction to VOS (R001)

• VOS Reference Manual (R002)

• Site Planning Guide (R003)

• VOS Commands Reference Manual (R098)

• VOS System Administration manuals

VOS System Administration: Administering and Customizing a System (R281)

VOS System Administration: Registration and Security (R283)

VOS System Administration: Disk and Tape Administration (R284)

VOS System Administration: Backing Up and Restoring Data (R285)

VOS System Administration: Administering the Spooler Facility (R286)

VOS System Administration: Configuring a System (R287)


11/198

Preface

Preface xi

Notation Conventions

This manual uses the following notation conventions.

• Italics introduces or defines new terms. For example:

The master disk is the name of the member disk from which the module was

booted.

• Boldface emphasizes words in text. For example:

Every module must have a copy of the module_start_up.cm file.

• Monospace represents text that would appear on your terminal’s screen (such ascommands, subroutines, code fragments, and names of files and directories).For example:

change_current_dir (master_disk)>system>doc

• Monospace italic represents terms that are to be replaced by literal values. In thefollowing example, the user must replace the monospace-italic term with a literal

value.

list_users -module module_name

• Monospace bold represents user input in examples and figures that contain bothuser input and system output (which appears in monospace). For example:

display_access_list system_default

%dev#m1>system>acl>system_default

w *.*

Key Mappings for VOS Functions

VOS provides several command-line and display-form functions. Each function ismapped to a particular key or combination of keys on the terminal keyboard. To

perform a function, you press the appropriate key(s) from the command-line or displayform. For an explanation of the command-line and display-form functions, see the

manual Introduction to VOS (R001).

The keys that perform specific VOS functions vary depending on the terminal. Forexample, on a V103 ASCII terminal, you press the and keys simultaneouslyto perform the INTERRUPT function; on a V105 PC/+ 106 terminal, you press the keyon the numeric keypad to perform the INTERRUPT function.

Certain applications may define these keys differently.

Refer to the documentation for the application for thespecific key mappings.


12/198

Preface

xii VOS System Administration: Starting Up and Shutting Down a Module or System (R282)

The following table lists several VOS functions and the keys to which they are mapped

on commonly used Stratus terminals and on an IBM PC ® or compatible PC that isrunning the Stratus PC/Connect-2 software. (If your PC is running another type of

software to connect to a Stratus host computer, the key mappings may be different.)For information about the key mappings for a terminal that is not listed in this table, referto the documentation for that terminal.

Format for Commands and Requests

Stratus manuals use the following format conventions for documenting commands andrequests. (A request is typically a command used within a subsystem, such as

analyze_system). Note that the command and request descriptions do notnecessarily include all of the following sections.

VOS Function

V103

ASCII

V103

EPC

IBM PC or

Compatible

PC

V105

PC/+ 106

V105

ANSI

CANCEL * †

† Numeric-keypad key

* † † or * †

CYCLE - †

CYCLE BACK - - - † -

DISPLAY FORM -†

-†

†

or -†

or-

HELP - - - -

INSERT DEFAULT - - - -

INSERT SAVED

INTERRUPT - - - † -

NO PAUSE - - * † -

† -


13/198

Preface

Preface xiii

nameThe name of the command or request is at the top of the first page of the

description.

Privileged

This notation appears after the name of a command or request that can be issuedonly from a privileged process. (See the online glossary, which is located in the file

>system>doc>glossary.doc, for the definition of privileged process.)

Purpose

Explains briefly what the command or request does.

Display FormShows the form that is displayed when you type the command or request name

followed by -form or when you press the key that performs the DISPLAY FORM function. Each field in the form represents a command or request argument. If an

add_disk Privileged

PurposeThe add_disk command tells the operating system on the currentmodule to recognize the specified logical volume for the duration of

the current bootload.

Display Form

Command Line Form

add_disk disk_name[ module_name ]

Argumentsdisk_name

The name of the logical volume to be recognized for the currentbootload.

. .

.H

AB

C

D

E

F

G

-------------------------- add_disk ------------------------- disk_name:

module_name: current_module

Required

A

B

C

D


14/198

Preface

xiv VOS System Administration: Starting Up and Shutting Down a Module or System (R282)

argument has a default value, that value is displayed in the form. (See the online

glossary for the definition of default value.)

The following table explains the notation used in display forms.

The Notation Used in Display Forms

Command-Line Form

Shows the syntax of the command or request with its arguments. You can displayan online version of the command-line form of a command or request by typing the

command or request name followed by -usage.

The following table explains the notation used in command-line forms. In the table,the term multiple values refers to explicitly stated separate values, such as two or

more object names. Specifying multiple values is not the same as specifying a starname. (See the online glossary for the definition of star name.) When you specify

multiple values, you must separate each value with a space.

The Notation Used in Command-Line Forms

Notation Meaning

Required field with no default value.

The cursor, which indicates the current position on the

screen. For example, the cursor may be positioned on the

first character of a value, as in ll.

current_user

current_module

current_system current_disk

The default value is the current user, module, system, or

disk. The actual name is displayed in the display form of the

command or request.

Notation Meaning

argument_1 Required argument.

argument_1... Required argument for which you can specify multiple values.

Ç È Set of arguments that are mutually exclusive; you must specifyone of these arguments.

[argument_1] Optional argument.[argument_1]... Optional argument for which you can specify multiple values.

a

E

argument_1

argument_2


15/198

Preface

Preface xv

ArgumentsDescribes the command or request arguments. The following table explains the

notation used in argument descriptions.

The Notation Used in Argument Descriptions

The following additional headings may appear in the command or requestdescription: Explanation, Error Messages, Examples, and Related Information.

Explanation

Explains how to use the command or request and provides supplementary

information.

Error MessagesLists common error messages with a short explanation.

¢ £ Set of optional arguments that are mutually exclusive; you canspecify only one of these arguments.

Note: Dots, brackets, and braces are not literal characters; you should not type them.Any list or set of arguments can contain more than two elements. Brackets and braces

are sometimes nested.

Notation Meaning

There are predefined values for this argument. In the display

form, you display these values in sequence by pressing the key

that performs the CYCLE function.

Required You cannot issue the command or request without specifying a

value for this argument.

If an argument is required but has a default value, it is not labeled

Required since you do not need to specify it in the command-line

form. However, in the display form, a required field must have avalue—either the displayed default value or a value that you

specify.

(Privileged) Only a privileged process can specify a value for this argument.

Notation Meaning

argument_1

argument_2

F

G

H


16/198

Preface

xvi VOS System Administration: Starting Up and Shutting Down a Module or System (R282)

Examples

Illustrates uses of the command or request.

Related InformationRefers you to related information (in this manual or other manuals), including

descriptions of commands, subroutines, and requests that you can use with or in

place of this command or request.

Online Documentation

Stratus provides the following types of online documentation.

• The directory >system>doc provides supplemental online documentation. Itcontains the latest information available, including updates and corrections toStratus manuals and a glossary of terms.

• Stratus offers some of its manuals online, via StrataDOC, an online-documentationproduct that consists of online manuals and StrataDOC Viewer, delivered on a

CD-ROM (note that you must order StrataDOC separately). StrataDOC Viewerallows you to access online manuals from an IBM PC or compatible PC, a Sun ® orHewlett-Packard workstation, or an Apple ® Macintosh ® computer. StrataDOC

provides such features as hypertext links and, on the workstations and PCs, textsearch and retrieval across the manual collection. The online and printed versionsof a manual are identical.

If you have StrataDOC, you can view this manual online.

For a complete list of the manuals that are available online, as well as more

information about StrataDOC, contact your Stratus account representative.

For more information about StrataDOC as well as a complete list of the manuals

that are available online, contact your Stratus account representative.

Ordering Manuals

You can order manuals in the following ways.

• If your system is connected to the Remote Service Network (RSN), issue the

maint_request command at the system prompt. Complete the on-screen formwith all of the information necessary to process your manual order.

• Customers in North America can call the Stratus Customer Assistance Center(CAC) at (800) 221-6588 or (800) 828-8513, 24 hours a day, 7 days a week. Allother customers can contact their nearest Stratus sales office, CAC office, or

distributor; see the file cac_phones.doc in the directory >system>doc for CACphone numbers outside the U.S.

Manual orders will be forwarded to Order Administration.


17/198

Preface

Preface xvii

Commenting on This Manual

You can comment on this manual by using the command comment_on_manual or by

completing the customer survey that appears at the end of this manual. To use the

comment_on_manual command, your system must be connected to the RSN. If yoursystem is not connected to the RSN, you must use the customer survey to comment

on this manual.

The comment_on_manual command is documented in the manual VOS SystemAdministration: Administering and Customizing a System (R281) and the VOSCommands Reference Manual (R098). There are two ways you can use this command

to send your comments.

• If your comments are brief, type comment_on_manual, press or , andcomplete the data-entry form that appears on your screen. When you have

completed the form, press .

• If your comments are lengthy, save them in a file before you issue the command.

Type comment_on_manual followed by -form, then press or . Enterthis manual’s part number, R282, then enter the name of your comments file in the

-comments_path field. Press the key that performs the CYCLE function to changethe value of -use_form to no and then press .

If comment_on_manual does not accept the part

number of this manual (which may occur if the manual isnot yet registered in the manual_info.table file), youcan use the mail request of the maint_request

command to send your comments.

Your comments (along with your name) are sent to Stratus over the RSN.

Stratus welcomes any corrections and suggestions for improving this manual.


18/198

Preface

xviii VOS System Administration: Starting Up and Shutting Down a Module or System (R282)


19/198

The Continuum-Series System Console 1-1

Chapter 1

The Continuum-SeriesSystem Console1-

A Continuum-series module does not have a control panel. Instead, a system console

command interface, accessed through a terminal, brings up the commands formerlyavailable only via the control panel buttons and switches on a Stratus module’s front

panel.

The system console is one part of the console controller. The console controllerfunctions as the central controller for the system. It serves as the system’s central

collection point for maintenance and diagnostic information, the information to theRemote Service Network (RSN), and the control point for the system’s power. The

console controller also provides the monitor terminal functionality.

This chapter describes the Stratus system console and includes the following maintopics.

• ‘‘Front Panel Commands”

• ‘‘System Messages”

• ‘‘Module Status Lights”

For information on the modular control panel found on XA/R-series modules, seeChapter 2, ‘‘The XA/R-Series Modular Control Panel.” For information about the control

panel that Stratus supported before the modular control panel, see Appendix A,‘‘Control Panels.”

Front Panel Commands

On previous Stratus modules, the control panel provided the mechanism for a system

administrator to issue basic instructions, such as those used to shut down and start upthe module. On Continuum-series modules, you issue these instructions through the

system console.

Since the system console simulates a control panel command interface, the systemconsole’s main menu is called the front panel .


20/198


1-2 VOS System Administration: Starting Up and Shutting Down a Module or System (R282)

The system console allows you to perform functions such as booting the module,

shutting down the module, killing power to the module, and reporting the state of allsystem indicator lights. Online help is also available via the front panel help command.

To enter the system console front panel, press the key and the key that performsthe BREAK function simultaneously. The console displays a list of commands. The

exact list of commands presented by the system console varies slightly betweenContinuum models. See Figure 1-1 and Figure 1-2.

If the front panel receives no input for 20 seconds, it times out and reverts back todisplaying system messages (“Panel goes to sleep...” message). Press the key and the key that performs the BREAK function simultaneously once again to returnto the front panel display and prompt.

Figure 1-1. Continuum-Series Modules (PA-7100 Processor) Front Panel Commands

Front Panel Commands:

help ......... displays command list.

boot_auto .... begin automatic mode startup.

boot_manual .. begin operator assisted mode startup.

shutdown ..... begin orderly system shutdown.

power_off .... immediately kill power.

restart_cpu .. force CPU into kernel dump/debug mode.

reset_bus .... force reset *ALL* boards.

status ....... report state of system indicator lamps.

history ...... display switch closure history.

quit, q ...... exit the front panel command loop.

. .......... display firmware version.

Front panel ready.


21/198



Figure 1-2. Continuum-Series Modules (PA-8000 Processor) Front Panel Commands

The following commands are available through the system console front panel.

* helpDisplays a list of front panel commands.

* boot_autoIf the system power is off, boot_auto turns the power on and initiates anautoboot. If the power is on, this command just sets the auto flag in the console

controller firmware so that the CPU prom will do an automatic boot the next time itis asked to boot. No further input is required.

* boot_manualIf the system power is off, boot_manual turns the power on and initiates anoperator assisted module startup. If the power is already on, this command justsets the manual flag in the console controller firmware so that the CPU prom will

perform an operator assisted manual boot the next time it is asked to boot.

* shutdownThis command sends a shutdown message to the operating system, causing it toinitiate an orderly shutdown. When the operating system completes its shutdown,it sends a command to the console controller to turn off the system power. (The

console controller remains running on housekeeping power.)

* power_offImmediately kills power to the module. This leaves the console controller running

on housekeeping power.

Front Panel Commands:

help ......... displays command list.

boot_auto .... begin automatic mode startup.

boot_manual .. begin operator assisted mode startup.

shutdown ..... begin orderly system shutdown.

power_off .... immediately kill power.

restart_cpu .. force CPU into kernel dump/debug mode.

reset_bus .... force reset *ALL* boards.

hpmc_reset ... send HPMC to CPU.

status ....... report state of system indicator lamps.

history ...... display switch closure history.

quit, q ...... exit the front panel command loop.

. .......... display firmware version.

Front panel ready.


22/198



Use the POWER_OFF command only when instructed to do

so by the Customer Assistance Center (CAC) or whenthere is an emergency such as a fire. Do not use this

button to initiate a normal shutdown. Issue the SHUTDOWN command for that purpose. If the system is not properlyshut down before it is restarted, its files are left in a state

similar to the state after a system failure.

* restart_cpuCommences a halt and restart of the module, equivalent to the LEVEL-7 button on

some older Stratus modules. It forces the operating system into kerneldump/debug mode.

Initiating a halt and restart may require issuing additionalrecovery commands once the module has restarted. Files

open at the time of a halt might be left in an inconsistentstate. When possible, issue the shutdown operating

system command from a terminal, or the SHUTDOWN control command from the control panel. Use the

RESTART_CPU command only if the module does not

respond to other commands or if requested to by the CAC.

* reset_busThis command sends a reset_bus command to the system. If there is anunbroken CPU board in the system, reset_bus causes a reset to be sent to all

boards on the bus. What kind of reset will occur on each board depends on itsstate. If the board is “broken,” it will force a cold reset. Otherwise, it will force a

warm reset. If there are no viable CPU boards, the command is a no-operation.

On Continuum-series modules using the PA-7100 processor, if reset_bus succeeds, the caches are flushed so that a meaningful memory dump can betaken.

On Continuum-series modules using the PA-8000 processor, if this command

succeeds, the caches are initialized and any dump contents are lost. (This cacheinitialization is required as part of the PA-8000 chip initialization). Therefore, the

following warning has been added to the confirm message for this command.

PA-7100 systems Repeat command to confirm

PA-8000 systems Repeat command to confirm:

Warning this does NOT preserve dump data


23/198

Recovering a Hung System


* hpmc_reset (PA-8000 processor systems only) hpmc_reset sends a high priority machine check (HPMC) to all CPUs on all

CPU/memory boards in the system. This is essentially a high-priority interrupt. Itinvokes an HPMC handler in the console controller prom code that saves context

to RAM memory and flushes the caches to preserve dump information.

This command should be attempted on a Continuum-series module with aPA-8000-based processor after the shutdown and then restart_cpu

commands fail, and before using reset_bus.

* statusReports the status of system indicator lights.

* historyDisplays a history of the last n front panel commands (limited to the boot_auto,

boot_manual, shutdown, power_off, restart_cpu, reset_bus, and

hpmc_reset commands).

* quit, qExits from the system console front panel. As noted previously, the system console

front panel times out automatically if it receives no input for 20 seconds.

* .Displays the version of firmware currently in use.

When your system is having problems, the order in which you attempt these

commands (from mildest to severest: shutdown, restart_cpu, hpmc_reset, and

reset_bus,) can assist or inhibit the CAC’s ability to diagnose problems with your

system. Seek assistance from the CAC if you are in doubt as to the order in which youshould enter them.

For more information on using these system console commands within the context ofactually starting up or shutting down a system, see Chapter 3, ‘‘Starting Up a Moduleor System, ” Chapter 5, ‘‘Responding to Status Lights,” or Chapter 6, ‘‘Shutting Down

and Powering Off.”

Recovering a Hung System

A system is hung if the console controller receives no indication of activity from theoperating system for five minutes. ‘‘Continuum-Series Manual Recovery” in Chapter 5 explains how to return a hung system to operation.

System Messages

The following informational messages may appear when the module is running. These

messages do not require any operator input.


24/198

System Messages


* Booting release_number Specifies the operating system release number being booted. It appears onceduring a boot.

* Salvaging logical_volume_name Specifies the logical volume being salvaged.

* Recovering disk_name Specifies the disk that is recovering.

* module_start_upIndicates the start of processing the module_start_up.cm file. While

module_start_up.cm is running, you will see many messages as it starts

individual system services.

* module_start_up complete Indicates that the module_start_up.cm file has finished processing.

* manual boot readyIndicates that the system has booted as far as the manual boot command level.

* Shutdown request sent to CPUIndicates that the shutdown command has been issued from the system console

front panel and the module is being shut down.

* overseer: Shutdown started by usernameIndicates that the user username has issued a shutdown command from the

operating system and that the module is being shut down.

* PCP - dumpingIndicates that a dump is being created.

* PCP - commandIndicates that the PCP (Primitive Control Program) is capable of acceptingcommand input.

* Creating SymbolsIndicates that the OS symbol table creation is in progress.

* HH:MM module_name Shows the current time and name of the module.* slot_id message

Indicates that there are board or device errors. For slot_id , one of the followingis displayed:

• the affected slot number of the chassis


25/198

System Messages


• one of these component names: Bus, BusA, BusB, Battery, Fan, EvBulk,or OddBulk

For message, one of the following is displayed:

• broken: The board is marked as broken.

• Failure: The board has a failure code.

• missing: The board is marked as missing.

• no devs: This board should have devices attached, but none are known.

• dev err: Some device attached to the controller has an error, is broken, or is

missing.

Console Controller Messages

The following messages may be generated by the console controller.

* CC:System ID does not match CC stored system IDThe console controller has been inserted in a new host; that is, a host where thehost operating system has not yet burned the backplane ID into the console

controller prom.

* CC:System power is off;CC saved power state is off.A newly inserted console controller detects that the host power is off. However,since its stored power state is also off, it did not turn on host power. Use the frontpanel command to turn on the power.

* CC:Deadman timer expired; system restart option not selected.The console controller detected a host failure but the host restart option was notenabled. You will see this message only if your Continuum system’s console

controller was configured with attempt_auto_recovery set to off.

* CC:Host did not respond to initial power on command.The console controller powered on the host either automatically or as a result of apanel command, and the host failed to start.

* CC:Sable Diagnostic Failed.The console controller detected a failure when running the Sable diagnostic

routines. This is an information message only; the console controller continues tooperate if possible. The Sable is the shared memory used for communication

between the console controller and the host.

In addition, when a Continuum-series module’s console controller is configured with

attempt_auto_recovery turned on, the controller sends the following series ofmessages as it proceeds through its protocol of successively more comprehensive

efforts to restart the system. Once one of the efforts succeeds, the console brings up


26/198

Module Status Lights


the operating system and, if possible, generates a dump. The protocol and messages

are slightly different, depending upon the Continuum-series module in use.

A PA-7100-based Continuum system displays the following messages.

*CC: Deadman timer expired; trying level7.

The console controller detected a host failure and is attempting a LEVEL-7 restartof the system equivalent to entering a restart_cpu command on the front panel.If this effort succeeds, a dump will be produced.

* CC: Level 7 failed after deadman timer expired; trying reset.The LEVEL-7 restart attempt failed. The console controller is attempting a systemreset equivalent to entering a reset_bus command on the front panel. If this effort

succeeds, a dump will be attempted.

A PA-8000-based Continuum system displays the following messages.

* CC: Deadman timer expired; trying level7.The console controller detected a host failure and is attempting a LEVEL-7 restartof the system equivalent to entering a restart_cpu command on the front panel.If this effort succeeds, a dump will be produced.

* CC: Level 7 failed after deadman timer expired; trying HPMC.The LEVEL-7 restart attempt failed. The console controller is attempting a systemreset equivalent to entering a hpmc_reset command on the front panel. If thiseffort succeeds, a dump will be produced.

*CC: HPMC failed after deadman timer expired; trying reset.

The hpmc_reset attempt failed. The console controller is attempting a systemreset equivalent to entering a reset_bus command on the front panel. If this effort

succeeds, a dump will be attempted, but it will likely be incomplete.

If the reset_bus restart effort fails, the console controller will automatically powercycle the module.

Console and Error-Log Status Messages

The system console displays the messages that the system continually sends to it

about the operational status of its hardware components. If a status light signals anerror condition, check the system console display for a corresponding error message,

which may give more specific information about the error condition.


A Continuum-series module has three main indicator lights at the top of the module.From left to right, these lights are the system fault indicator (yellow), the cabinet fault


27/198



indicator (yellow), and the system no fault light (green). Each of these three lights iseither on or off; they do not blink. A brief description follows.

• Yellow (first light on the left)—There is a faulty component in the system.

• Yellow (the light in the center)—There is a faulty component in the main cabinet.

• Green—All system components are operating normally.

The lights cycle (repeatedly light one after the other) during system testing. If all

main-cabinet lights are off, there is a power failure.

Expansion Cabinet Lights

Each expansion cabinet has one yellow light at the top of the cabinet. The light is offwhen all the components within that cabinet are operating without fault. The light is on

only when any component within the cabinet is faulty.

Unit Status Lights

Status lights are located on each customer-replaceable unit in your system. Dependingupon the component, there may be one, two, or three status lights.

For more information on status lights, refer to Chapter 5, ‘‘Responding to StatusLights,” and the VOS Continuum 600 and 1200 Series with PA-8000: Operation and

Maintenance Guide (R445) and Continuum Operation and Maintenance: 600 and 1200Series (R396) manuals.


28/198




29/198

The XA/R-Series Modular Control Panel 2-1

Chapter 2

The XA/R-SeriesModular Control Panel2-

Stratus has adopted a standard, modular control panel for all XA/R-series modules.

This standard control panel is fault-isolating and comprises customer-replaceableunits. It is possible to configure the control panel to be fault tolerant, and you can attach

a terminal or modem directly to the control panel via a serial port. The control panelsupports a special set of query and control commands.

This chapter describes the modular control panel. For more information, see Module

Control Panel Guide: Operation and Replacement (R334). The chapter includes thefollowing main topics.

• ‘‘The Stratus Modular Control Panel”

• ‘‘Control Panel Components”

• ‘‘Module Control Unit (MCU)”

• ‘‘Operator Interface Unit (OIU)”

• ‘‘Other Control Panel Features”

• ‘‘Status Display”

• ‘‘OIU Query and Control Messages”

• ‘‘System Messages”

• ‘‘Module Status Lights”

• ‘‘Unit Failure Lights”

• ‘‘Control Panel Buttons”

• ‘‘The Immediate Power Off Button”

The only exception to this standardized module controlpanel is the panel found on the earliest XA/R-series

module, the 10-slot XA/R Model 20. For information aboutthis control panel that Stratus provided before the modularcontrol panel, see Appendix A, ‘‘Control Panels.”


30/198

The Stratus Modular Control Panel


The Stratus Modular Control Panel

The control panel provides the mechanism for a system administrator to issue basic

instructions, such as those used to shut down and start up the module. The panel forXA/R-series (RISC-based) modules is mounted in the top left-hand corner of the maindoor, protected by a small cover plate that slides upward. The module status lights on

the right side of the control panel are visible through the door.

The modular control panel offers many features, including the following:

• configurable fault tolerance

• replacement of components by customers

• communication to the panel via the panel buttons, or via a serial port connected toa terminal or modem

Figure 2-1 shows the modular control panel.

Figure 2-1. The Modular Control Panel

Control Panel Components

The control panel comprises the following:

• two customer-replaceable components

• module status lights

• a door labeled IMMEDIATE POWER OFF/ON, that conceals the two power buttons

The customer-replaceable components are the Module Control Unit (MCU) and theOperator Interface Unit (OIU). System administrators can remove and replace these

OPERATOR INTERFACE UNIT UNIT

FAILURE

UNIT

FAILUREMODULE CONTROL UNIT

ENTERCYCLE

OPERATING

BATTERY

TEST/

PROBLEM

IMMEDIATE

POWER

OFF/ON

Cycle Button Enter Button

Unit Failure Light

Operating Light

Battery Light

Test/Problem Light

Unit Failure Light

LCD

Power Switches DoorAD0494


31/198

Module Control Unit (MCU)


units without special tools. Refer to Module Control Panel Guide: Operation andReplacement (R334) for information about replacing these components.

Module Control Unit (MCU)

The MCU is typically located on the left of the panel, and has a UNIT FAILURE light.

The MCU controls the operating states of the module, sending signals between the

control panel and the module. It is the only unit capable of controlling the signals sentto and received from CPUs in the module. During an MCU failure, the system shouldcontinue to run. The ENTER button on the OIU is not operational during an MCU

failure.

Operator Interface Unit (OIU)

The OIU is typically located in the middle of the control panel. It consists of a liquid

crystal display (LCD), a UNIT FAILURE light, and two buttons, CYCLE and ENTER.These buttons display and select query and control messages. See ‘‘OIU Query andControl Messages” later in this chapter for more information.

Other Control Panel Features

To the right of the customer-replaceable units is the door to the IMMEDIATE POWEROFF/ON buttons and the OPERATING, BATTERY, and TEST/PROBLEM lights. The

power buttons are located behind a door to prevent a user from accidentally pressingone of them. The buttons behind the IMMEDIATE POWER OFF/ON door should

always function, even if the MCU fails. These control panel components are describedin the sections ‘‘Module Status Lights,” and ‘‘Control Panel Buttons,” later in thischapter.

Status Display

The LCD on the OIU displays query and control messages. The LCD also displaysPrimitive Control Program (PCP) messages. These two types of messages are

described in the following sections.


32/198

OIU Query and Control Messages


OIU Query and Control Messages

The OIU query and control messages are displayed and cycled by pressing the CYCLE

button and are issued by pressing the ENTER button. Here is the list of the OIU queryand control messages and message descriptions.

* BLANKThe LCD is blank when the OIU enters an idle state. Once the OIU is in an idlestate, either the date/time and module name or a CPU status message orcommand are displayed by the LCD. From the idle state, you can use the CYCLE

button to cycle through the OIU commands and press the ENTER button toexecute one.

* AUTO BOOTPress the ENTER button to instruct the MCU to boot the module without furtherinput.

* MANUAL BOOTPress the ENTER button to instruct the MCU to boot the module manually.* SHUTDOWN

Press the ENTER button to commence an orderly shutdown of the module. TheMCU will send a SHUTDOWN? query to the LCD. To verify that the shutdown should

be initiated, press the CYCLE button until the YES message appears on the LCD,then press the ENTER button. If you do not press the ENTER button in response

to the YES message within approximately ten seconds, the MCU returns the controlpanel to the idle state.

* RESTARTPress the ENTER button to commence a halt and restart of the module, equivalentto the LEVEL-7 button on some Stratus modules. The MCU sends a HALT &

RESTART? query to the LCD. To verify that the halt and restart should be issued,

press the CYCLE button until the YES message appears on the LCD, then pressthe ENTER button. If you do not press the ENTER button in response to YES withinapproximately ten seconds, the MCU returns the control panel to the idle state.

Initiating a halt and restart may require issuing additionalrecovery commands once the module has restarted. Files

open at the time of a halt may be left in an inconsistentstate. When possible, issue the shutdown operatingsystem command from a terminal, or the SHUTDOWN

control command from the control panel. Use the

RESTART command only if the module does not respondto other commands, or if instructed to do so by the CAC.

* REV?Press the ENTER button to display the current revisions of the MCU board and

PROM code in the control panel.


33/198

System Messages


* YESPress the ENTER button to confirm the SHUTDOWN and HALT & RESTART?

commands from the MCU.

* NOPress the ENTER button to terminate the SHUTDOWN and HALT & RESTART?

commands from the MCU.

When you press the CYCLE button, the query and control message appears on the

LCD for approximately five seconds. If you do not press the ENTER button within thattime, the OIU returns to the idle state. If the module sends a message to the OIU in themiddle of a cycle operation, the OIU retains the state currently appearing on the LCD

until you press the CYCLE button again, or until the time out has elapsed.

If you do not respond to the prompt for the SHUTDOWN or HALT & RESTART? messages within approximately 10 seconds, the MCU treats the lack of response as a

NO.

System Messages

The informational messages appear when the module is running and do not requireany operator input. Following is a list of the system messages.

• Booting release_number

Specifies the operating system release number being booted. It appears once

during a boot.

• Salvaging logical_volume_name

Specifies the logical volume being salvaged.

• Recovering disk_name

Specifies the disk that is recovering.

• module_start_up

Indicates the start of processing the module_start_up.cm file. While

module_start_up.cm is running, you will see many messages as it starts

individual system services.

• module_start_up complete

Indicates that the module_start_up.cm file has finished processing.

• manual boot ready

Indicates that the system has booted as far as the manual boot command level.


34/198

System Messages


• Shutdown request

Indicates that the SHUT DOWN button on the module has been pressed and the

module is being shut down.

• PCP - dumping

Indicates that a dump is being created.

• PCP - command

Indicates that the PCP (Primitive Control Program) is capable of acceptingcommand input.

• Creating Symbols

Indicates that the operating system symbol table creation is in progress.

• HH:MM module_name

Shows the current time and name of the module.

• slot_id message

Indicates that there are board or device errors. For slot_id , one of the followingis displayed:

– the affected slot number of the chassis

– one of these component names: Bus, BusA, BusB, Battery, Fan, EvBulk,

or OddBulk

For message, one of the following is displayed:

– broken: The board is marked as broken.

– failure: The board has a failure code.

– missing: The board is marked as missing.

– no devs: This board should have devices attached, but none are known.

– dev err: Some device attached to the controller has an error, is broken, or ismissing.


35/198




The module status lights (described briefly below) are located to the right of thecustomer-replaceable units and are visible through small openings in the control panel

door.

* OPERATINGDuring module startup, this green light alternates with the amber TEST/PROBLEMlight. Once the module is operating, the green light remains lit.

* BATTERYThis yellow light comes on when power to the module is lost, indicating that the

module is not operating but is maintaining a restartable state on its emergencybatteries. The control panel will not operate when the battery light is on, except for

the IMMEDIATE POWER OFF/ON buttons.

*TEST/PROBLEM

This amber light comes on when a fault is detected during the module’s operation.It also alternates with the green OPERATING light approximately every four

seconds during module startup. If the power-on diagnostic detects a problem, theTEST/PROBLEM light stays on.

Unit Failure Lights

A UNIT FAILURE light is the round amber light located on each customer-replaceableunit. An amber light on either unit means that the unit has failed and that the unit shouldbe replaced. Contact the CAC for a replacement unit.

Since the loss of the MCU suspends operation of the control panel, the amberTEST/PROBLEM light will stay lit until the MCU is removed and replaced. When you

replace the MCU, the UNIT FAILURE light in the replacement MCU will not be lit; theTEST/PROBLEM light will be on or off depending on whether there are other red-lit

boards in the module.

Control Panel Buttons

The control panel has only two visible buttons:

• CYCLE

• ENTER

However, behind the door labelled IMMEDIATE POWER OFF/ON are two additionalbuttons labelled:

• O (red power off)

• | (green power on)


36/198

Control Panel Buttons


Figure 2-2 shows the location of the control panel buttons.

Figure 2-2. Control Panel Buttons

* CYCLEUse this white button to display and cycle through the query and control messages.* ENTER

Use this white button to instruct the MCU to perform the operation displayed on the

LCD. For example, if the AUTOBOOT command is on the status display when theENTER button is pressed, an automatic reboot of the module is initiated.

* OThis red power-off button is located behind the IMMEDIATE POWER OFF/ON

door. Pressing it will initiate an immediate loss of power to the module. Avoidpressing this button; use the shutdown command whenever possible. Consultwith the CAC before pressing this button unless there is an emergency (such as a

fire) that requires an instantaneous power cut.

* 1This green power-on button is located behind the IMMEDIATE POWER OFF/ON

door. Pressing it will initiate an automatic boot; however, if the disk label had the-no_auto_boot flag set, a manual boot is initiated. Avoid pressing this button;use the MANUAL BOOT or AUTO BOOT option instead. Consult the CAC before

pressing this button, unless there is an emergency.

(Power OffRed Button)

(Power OnGreen Button)

OPERATOR INTERFACE UNIT UNIT

FAILURE

ENTERCYCLE

CycleButton

EnterButton

OPERATING

BATTERY

TEST/

PROBLEM

AD0501


37/198

The Immediate Power Off Button


The Immediate Power Off Button

The IMMEDIATE POWER OFF button powers off the module immediately. This buttonis located behind the IMMEDIATE POWER OFF/ON door on the modular control panel.

Never press this button unless instructed to do so by the

Customer Assistance Center (CAC) unless there is anemergency, such as a fire. Do not use this button to initiatea normal shutdown. Issue the shutdown command forthat purpose. If the system is not properly shut down

before it is restarted, its files are left in a state similar tothe state after a system failure.


38/198


39/198

Starting Up a Module or System 3-1

Chapter 3

Starting Up a Module orSystem3-

Startup is the procedure that powers on and boots a module. This chapter explains how

to perform automatic startup and manual startup, and explains what to do when amodule fails. It includes the following main topics.

• ‘‘Automatic Startup”

• ‘‘Manual Startup”• ‘‘Link Boot”

• ‘‘The Operating System Symbol Table”

As indicated in the Preface, this chapter focuses on the instructions pertaining tomodules with the new system console or modular control panel. Instructions pertaining

to 10-slot XA/R Model 20 modules with a different control panel are included asadditional information. Refer to Appendix A, ‘‘Control Panels,” for more information on

this older control panel.

Automatic Startup

This section describes the automatic startup process.

Single Module Startup

To start up a Continuum-series module with the system console, perform the followingsteps.

1. Press the key and the key that performs the BREAK function simultaneously.The console displays a list of commands.

2. Enter the boot_auto command to begin startup.

To start up a module with the modular control panel, perform the following steps.

1. Press the CYCLE button until the AUTOBOOT option is displayed.

2. Press the ENTER button to execute the AUTOBOOT option.


40/198

Automatic Startup


The OPERATING light alternates with the TEST/PROBLEM light approximately every

four seconds until the operating system is started.

Automatic Startup Functions

At automatic startup, the CPU/memory board runs diagnostics and self-tests stored in

a PROM. After these run successfully, the module finds the master disk. The PROMstarts up the master disk and reads a utility program that loads the operating system

from the master disk’s default boot partition.

The operating system initializes all disks and then creates a process that executes the

commands in the file module_start_up.cm. See Chapter 4, ‘‘The Module StartupCommand File,” for more information.

During startup, the TEST/PROBLEM light and OPERATING light blink alternatelyabout every four seconds. When the process TheOverseer is successfully loaded,

the OPERATING light becomes steady. Ordinarily the amber TEST/PROBLEM lightgoes off; however, it stays on if the power-on diagnostic tests detect trouble.

Handling Problems with Automatic Startup

For an automatic startup to proceed normally, the >system directory must contain thefile module_start_up.cm and all the files it references. (See VOS System

Administration: Administering and Customizing a System (R281) for more information.)Following are ways the operating system responds differently to a missing

module_start_up.cm file than it does to the absence of a file the macro references.

• If module_start_up.cm is missing, the operating system sends messagesnoting its absence to the system console’s monitor terminal and the current system

error log. It waits briefly to allow you to see the monitor terminal message, thenstarts an interactive process at command level.

At this point, the operating system has terminated the automatic startup. You arenow at Step 6 of the manual startup procedure described later in this chapter.Follow Step 6 to finish the startup.

• If a configuration table or other file referenced in module_start_up.cm is

missing, the operating system sends messages noting the missing file to thesystem console’s monitor terminal and the current system error log, and attempts

to complete the automatic startup. If it is able to finish, you must now perform amanual startup and re-create the file, as described in VOS System Administration:Configuring a System (R287).

If the operating system cannot complete the automatic startup successfully, ask theCAC for assistance.

The automatic startup may also experience problems if module_start_up.cm or anyof the files it references is present, but defective, in >system. In this case, the


41/198

Manual Startup


operating system’s behavior and your response are the same as when a configurationtable is missing.

See VOS System Administration: Administering and Customizing a System (R281) forfurther information about the system console’s monitor terminal functionality, and

system error logs.

Manual Startup

Manual startup allows you to load the operating system from tape or disk. Theprocedure is interactive and therefore requires a monitor terminal. See VOS System

Administration: Administering and Customizing a System (R281) for more informationabout the system console’s monitor terminal functions.

During a manual startup, the only functioning editing key

is .

Disk Boot and Tape Boot

In most cases, you perform the manual boot from disk. This means that the operating

system is loaded from a boot partition , which is a region of the master disk. See VOSSystem Administration: Disk and Tape Administration (R284) for more information.

Boot from tape only in the following cases:

• if you want to physically reload all the contents of the master disk

• if the master disk has so many irrecoverable errors that you cannot boot from it

In a boot from tape, the operating system is loaded from a boot tape . This is a tape thatcontains a copy of the operating system and a complete copy of the contents of the

master disk. A boot tape is created when the dump_disk command executes on amaster disk. See VOS System Administration: Backing Up and Restoring Data (R285)for specific information. Always have a current boot tape available.

If you rename a boot disk, you must create a new boot tape. When you boot from tape,

the disk name on the boot tape must be the same as the boot disk’s name. If the namesare inconsistent, the operating system prompts you to rename the disk to its formername (the name on the boot tape) so that the tape can reload the disk. See VOS

System Administration: Disk and Tape Administration (R284) for more information onboot disks.

A boot from tape is a relatively standard task except when

a tape drive is not attached to the module that is to bebooted. If you have an XA/R-series module, you mayprefer to perform a link boot , a boot through the


42/198

Manual Startup


StrataLINK communications network. See ‘‘Link Boot”

later in this chapter for details.

The Steps in a Manual Startup from Disk or Tape

The following sections describe the procedure for manual startup from disk or tape for

Stratus modules. Except for Steps 4a and 4b, the steps are the same for disk boot andfor tape boot.

If the manual startup is not successful, call the CAC.

1. To initiate the manual reboot, perform the following steps.

a. On a Continuum-series module with the system console, press the keyand the key that performs the BREAK function simultaneously, and then enterthe boot_manual command. The module status lights cycle while the

computer is starting up. The green no-fault light become steady when thecomputer is running.

b. On a module with the modular control panel, cycle to the MANUAL BOOT command on the LCD and press the ENTER button. The green OPERATING

lights alternate with the amber TEST/PROBLEM lights approximately everyfour seconds while the computer is starting up. The green OPERATING lightsbecome steady when the computer is running.

2. If you manually boot a module from tape, you must first load the tape. If the tape

drive has an ONLINE button on its control panel, you must also press that buttonto put the tape online.

3. The system console’s monitor terminal displays the following question:

Boot from slot?

If you are booting from the master disk, press without entering a number.Otherwise, enter the number of the main chassis slot containing the disk controller,tape controller, or IOP to be used for the manual boot, and press .

If the specified main chassis slot contains an IOP, the terminal displays anadditional prompt:

Enter IOA slot/device in the form ss/dd

To boot from the default device on the IOA associated with the specified IOP, press

without entering any numbers. To boot from the default device on aspecified IOA, enter the adapter slot number and press . To boot from anyother device, enter its adapter slot number and device number, separated by a

slant character (/), and press .

4. The procedure differs, depending on whether you are booting from disk or tape.


43/198

Manual Startup


a. Disk. Because you specified either a disk controller or disk IOA connected toan IOP in Step 3, the terminal displays the following question:

Boot from partition?

To load the operating system from the default boot partition, press without entering a number. To load the operating system from a specificpartition, enter a valid boot partition number from 1 to 8; in this case, pressing

is not necessary.

The boot disk should always be a duplex disk, as described in VOS SystemAdministration: Disk and Tape Administration (R284). If the primary partner ofthe boot disk is not functioning, press the STOP button and repeat Steps 1, 2,

and 3, using the slot number of the secondary partner of the boot disk.

This is the end of the disk description. Skip to Step 5.

b. Tape. Because you specified either a tape controller or a tape IOA connected

to an IOP in Step 3, the operating system asks you questions regardingformatting, initializing, and reloading the master disk. See VOS System

Administration: Disk and Tape Administration (R284) for more information. Youcan choose to reformat or initialize the master disk before you reload it, or you

can answer no to the formatting and initializing questions to go directly to thereloading procedure.

i. The terminal displays the question on formatting first.

Do you want to format disk_name?

The disk_name argument above refers to the uninitialized disk name of

the master disk. The uninitialized disk name describes the disk’s physicallocation within the module. Refer to VOS System Administration: Disk andTape Administration (R284) for more information about uninitialized disk

names.

If you answer yes and the master disk does not already have a valid label,the master disk is formatted. If you answer yes and the master disk

already has a valid label, the operating system asks you to verify that youwant to destroy the master disk’s contents by formatting.

Are you sure? disk_name has a valid label now--

If you answer yes to this question, the master disk is formatted.

If you formatted the master disk, go to Step iii.

Answering no to either the formatting question or the verification question

bypasses the formatting procedure and lets you choose initialization orreloading instead.


44/198

Manual Startup


ii. The terminal displays the initialization question next.

Do you want to initialize disk_name?

The disk_name argument above refers to the uninitialized disk name of

the master disk. The uninitialized disk name describes the disk’s physical

location within the module. Refer to VOS System Administration: Disk andTape Administration (R284) for more information about uninitialized disk

names.

If you answer yes and the master disk does not already have a valid label,the operating system asks you to supply certain initialization data. If you

answer yes and the master disk already has a valid label, the operatingsystem asks you to verify that you want the master disk’s contentsdestroyed by initialization.

Are you sure? disk_name has a valid label now--

If you answer yes to this question, the master disk is initialized.If you answered no, go to Step iv.

iii. If you formatted or initialized the master disk, the operating system then

asks you to supply two values: the type of disk drive and size of its pagingpartition. See the descriptions of the initialize_boot_disk and

display_disk_label commands in VOS System Administration: Diskand Tape Administration (R284) for information about these values. Afteryou supply these values, the terminal displays the question on reloading.

iv. Answering no to either the initialization question or the verification

question bypasses the initializing procedure and skips to the reloadingquestion.

Reload master disk disk_name?

You can answer yes, no, or -u (unattended).

Answer yes if you have a boot tape to work with and you want to reload

the master disk from that boot tape. The operating system is loaded fromthe boot tape along with all files of the master disk.

Make sure the master disk you are reloading is the same size as the

master disk from which the dump image was made. If the new master diskis a different size, the reload will not be performed correctly. Also, makesure that the disk you are reloading uses dynamic bad block remapping.

Dynamic bad block remapping copies bad blocks to good blocks in a sparedisk partition.

While reloading progresses, the operating system prompts you to load anysubsequent tapes needed. You do not need to rewind them.


45/198

Manual Startup


If you answer -u (unattended), the operating system is loaded as if youanswered yes, but you are not prompted to load subsequent tapes. Note

that this option is meaningful only of your tape drive supports

-unattended mode. For additional information about loading tapes with

the -u option, refer to the description of the save command in VOSCommands Reference Manual (R098).

If you answer no, the operating system alone is loaded into memory andthe paging partition from the boot tape. The usual disk boot partitions will

not be reloaded, and other methods of restoring at least one such partitionmust be done before a disk boot can be performed.

5. The system console’s monitor terminal displays the following question:

Enter PCP for manual damage repair (%system#master_disk)?

Unless the CAC tells you to respond to this question with yes, respond with no followed by .

If you respond no, the monitor terminal displays the following question:

Override devices.table parameters with system defaults for

monitor terminal?

Answer no to this question to use the device parameters specified in the

devices.table file for the system console’s monitor terminal.

Answer yes if there is a problem with the devices.table file for the monitor

terminal. This override allows the system to accept data from the monitor terminal.

Correct the devices.tin file from the monitor terminal and re-create thedevices.table file. Reboot the system once the correction is made to the fileand answer no once the reboot process reaches this question again.

When performing a manual boot from an IOP-based device on an XA/R-seriesmodule, you are asked an additional question. (This IOP-related dialogue does not

appear on Continuum-series modules.)

Override IOP configuration?

Answer no to this question to use the normally configured IOP software (as you

would for an automatic boot).

Answer yes if there is a problem with the configured software. You will then beprompted to supply the names of the firmware files to be used for the IOP and for


46/198

Manual Startup


asynchronous channels on communications adapter types 1, 3, and 5, with

questions similar to these.

Default IOP Firmware (iop_type_a.pm)?

Comm adapter types 1/3/5 Firmware file (ioa01_async.pm)?

The default answer for each question is given in parentheses. Press if youwant to use the default; otherwise, specify the name of a file in the directory

>system>firmware to be loaded.

Finally, on all systems, the terminal displays the following message to indicate that

the manual boot is completed:

Overseer.System logged in

ready date/time

You are now at command level; your current directory is

(master_disk)>Overseer. The user name of the process on the systemconsole’s monitor terminal is Overseer.System.

6. If necessary, repair or re-create module_start_up.cm or a configuration table,or repair the command library. See VOS System Administration: Configuring aSystem (R287) for instructions, and finish the startup as described in that manual.

If a previous module startup failed, display the file module_start_up.out,

located in the >Overseer directory, for information about why the startup failed.

If you do not need to repair or re-create files, proceed to Step 7.

7. To complete a normal startup, type the following:

start_logging module_start_up.out

>system>module_start_up

This sequence tells the operating system to execute the commands in the file

module_start_up.cm (described in Chapter 4, ‘‘The Module Startup Command

File”) and to create a log file that records the execution of the commands.

If you log out before executing module_start_up.cm and/or TheOverseer

process is not running, the operating system creates a new login process andpositions you at Step 6.

8. Log out the Overseer process on the system console’s monitor terminal.


47/198

Link Boot


Link Boot

As noted in the previous section, you perform a tape boot when the master disk on themodule to be booted has enough unrecoverable errors to prevent a reliable disk boot

or when you want to physically reload the entire contents of the master disk. In mostcases, a tape boot is a straightforward task; however, if a tape drive is not physically

attached to the module to be booted, the operation can be complicated and timeconsuming. If you have an XA/R-series module, you may want to perform a link boot inthis circumstance.

You cannot perform a link boot on Continuum-seriesmodules.

A link boot of a module is a boot of the module performed via the StrataLINKcommunications network. A boot source, accessible to another module on the same

system, communicates with the module to be booted using a server process called alink boot server (described later in this section) to provide the information needed for

the boot.

The performance of a link boot operation is slightly slower than that of a local boot, buta link boot can be more convenient.

Link Boot Module Requirements

A link boot operation requires two modules.

• The booting module , the module to be booted via the StrataLINK communicationsnetwork.

• The server module , the module to perform the boot. The server module must be onthe same system as the booting module, and must have access to the boot source.

The number of modules on a given system may affect the success of a link boot.StrataLINK traffic density is directly proportional to the total number of modules on a

given system, so the likelihood of an error during a link boot increases as the numberof modules increases. Therefore, the maximum number of modules that can exist on asystem without interfering with a link boot is unique to each case.

1. If you initiate the link boot from a module that is

running VOS Release 11.1 or later, all I101-10 and

I101-11 Link Controllers in the module that wasbooted are capable of transferring 32 bits of data at atime on to and off of the StrataBUS.

2. If you initiate the link boot from a module that isrunning a release of VOS earlier than 11.1, all I101-10

and I101-11 Link Controllers in the module that wasbooted will transfer 16 bits of data at a time on to andoff of the StrataBUS.


48/198

Link Boot


The Link Boot Source

The boot source for the link boot can be a boot tape, an operating system program file,or a boot partition located on any other module on your system. Therefore, whenperforming a link boot from a boot tape, you do not need to be concerned with the

physical location of the tape drive on which the boot tape will be mounted.

When you perform a link boot from tape, you can reformat, reinitialize, and/or reload

the master disk.

The Link Boot Server

A link boot server is a server process that responds to link boot requests from the

booting module by transferring data from the boot source to the booting module. Thelink boot server must be started on the server module. Start the link boot server with

the command link_boot_server.

Only one link boot server is allowed on a system at a time. To ensure this, a link bootserver, when started, checks immediately to see whether there is another link bootserver on the same system by issuing a new link boot request. If it finds a second link

boot server, the first link boot server stops further processing and performs a routinecleanup. If it does not find a second link boot server, it proceeds with the link boot.

See VOS System Administration: Administering and Customizing a System (R281) forthe description of the link_boot_server command.

The Steps in a Link Boot

To boot a module via the StrataLINK communications network, perform the followingsteps in the order shown. Two messages shown below often appear during this

procedure which do not indicate a problem with the link boot.

net interrupt for unassigned link

net_driver: station ## has ring number # configured as ring #

If you see these messages, continue the link boot procedure as if no messages were

displayed.

1. On the server module, invoke a link boot server by entering thelink_boot_server command with a valid boot source option.

2. On the booting module, perform a manual boot as described earlier in the section

‘‘Manual Startup” with the following directions.

a. Supply the main-chassis slot number of a link controller in the booting module

at the following prompt:

Boot from slot?


49/198

Link Boot


b. The following prompts appear only in the boot from link procedure. The valuesdisplayed in parentheses are default values for the booting module. To accept

a value, press at the prompt. To change a value, enter the new valueat the prompt followed by .

Enter system number system_number:

Enter system name system_name:Enter system module number system_module_number:

Enter system module name system_module_name:

Enter net address net_address:

c. At the end of this step, the module is booted but the link boot may not becomplete. However, the link boot server is no longer needed; it will beterminated automatically.


50/198

The Operating System Symbol Table


The Operating System Symbol Table

The operating system symbol table is created each time a new version of the operating

system is booted. If an error occurs and this file is not created during bootload, you willget one of the following messages during the execution of programs that reference thesymbol table file, such as analyze_system and tp_overseer.

• e$corrupted_os_symtab (4214) if the format of the symbol table is unusable

• e$wrong_os_symtab (4215) if the symbol table is not for the current version of

the operating system

• e$cant_open_os_symtab (4216) if the symbol table is not readable or has notbeen created

These messages are returned to the .out file for that process and to the terminal if the

process is run from a terminal. If this occurs, delete the out-of-date symbol table bytyping delete_file (master_disk)>system>os.symtab and create an

updated version with the create_os_symtab command.


51/198

The Module Startup Command File 4-1

Chapter 4

The Module StartupCommand File4-

This chapter documents the module_start_up.cm file and includes an excerpt from

the file. It includes the following main topics.

• ‘‘The module_start_up.cm File”

• ‘‘Tailoring the module_start_up.cm File”

The module_start_up.cm File

The module_start_up.cm file contains commands that the operating system

executes as part of the procedure for starting up a module. It is contained in the

>system directory of the master disk of every module in a system. See VOS SystemAdministration: Administering and Customizing a System (R281) for information about

the >system directory. You may want to store a copy of the module_start_up.cm file in the >system>configuration directory for protection if the >system copy islost.

Some of the functions performed by commands in this file include the following:

• reading the table files that specify the configurations of boards, disks, and devicesconnected to the module

• identifying the modules within a system

• starting system service processes such as TheOverseer, spooler, and networkwatchdog

Some commands, called system process commands , are used mostly in

module_start_up.cm files. For example, you would never issue the operatingsystem command overseer, and you probably would not use the commands

link_server or network_watchdog. The system process commands initiate

service processes for the module.

Every module must have a copy of module_start_up.cm. You cannot start up the

operating system properly without it. If it is missing, refer to VOS SystemAdministration: Configuring a System (R287) for instructions on re-creating it.


52/198

Tailoring the module_start_up.cm File


The sample module_start_up.cm file that is shipped with the installation software

is stored in the directory (master_disk)>system>release_dir.

Tailoring the module_start_up.cm File

This section provides an example of how to construct a single module_start_up.cm file for use in every module of a multimodule system. The purpose of this procedure isto solve the following problems that exist when each module has its own

module_start_up.cm file.

• Whenever you make a change that applies to the whole system, you must make

the same change to copies on every module. You can make the change in onecopy and then copy that file to another location on the same module, but youshould check before copying the updated file to another module. The

module_start_up.cm file for each module probably has commands unique to itsown module, and executing it on another module may not work.

• To have a complete picture of the system’s startup configuration, you must look at

all the files.

The example uses goto and label statements to execute different commands ondifferent modules.

Example

The following excerpt from a module_start_up.cm file replaces several lines of theinstallation file.

The first block of commands starts the spooler and the print queues on module #m1. Itreplaces the lines in the installation file that initialize and start the spooler process. The

second block starts X.25 gateway processes on module #m2. (These processes allowthe system to be part of a wide area network.) It replaces the lines in the installation filethat start the X.25 gateway processes. The last four lines of t

Date post:	07-Aug-2018
Category:	Documents
Upload:	kennycheung
View:	233 times
Download:	0 times

VOS Startup and Shutdown a system (r282-03)

Documents