Compaq ES40 AlphaServer User Interface Guide

PDF

Dokument

Reklamë

AlphaServer ES40

User Interface Guide

Order Number: EK–ES240–UI. A01

This guide is intended for use by managers and operators of

AlphaServer ES40 systems.

Compaq Computer Corporation

First Printing, April 1999

The information in this publication is subject to change without notice.

COMPAQ COMPUTER CORPORATION SHALL NOT BE LIABLE FOR TECHNICAL

OR EDITORIAL ERRORS OR OMISSIONS CONTAINED HEREIN, NOR FOR

INCIDENTAL OR CONSEQUENTIAL DAMAGES RESULTING FROM THE

FURNISHING, PERFORMANCE, OR USE OF THIS MATERIAL. THIS

INFORMATION IS PROVIDED “AS IS” AND COMPAQ COMPUTER CORPORATION

DISCLAIMS ANY WARRANTIES, EXPRESS, IMPLIED OR STATUTORY AND

EXPRESSLY DISCLAIMS THE IMPLIED WARRANTIES OF MERCHANTABILITY,

FITNESS FOR PARTICULAR PURPOSE, GOOD TITLE AND AGAINST

INFRINGEMENT.

This publication contains information protected by copyright. No part of this publication may be photocopied or reproduced in any form without prior written consent from

Compaq Computer Corporation.

The software described in this guide is furnished under a license agreement or nondisclosure agreement. The software may be used or copied only in accordance with the terms of the agreement.

COMPAQ and the Compaq logo are registered in United States Patent and Trademark

Office. Tru64 is a trademark of Compaq Computer Corporation. AlphaServer and

OpenVMS are trademarks of Digital Equipment Corporation. Prestoserve is a trademark of Legato Systems, Inc. UNIX is a registered trademark in the U.S. and other countries, licensed exclusively through X/Open Company Ltd.

Microsoft, Windows, and Windows NT are registered trademarks of Microsoft

Corporation.

Other product names mentioned herein may be the trademarks of their respective companies.

Warning!

This is a Class A product. In a domestic environment this product may cause radio interference in which case the user may be required to take adequate measures.

Achtung!

Dieses ist ein Gerät der Funkstörgrenzwertklasse A. In Wohnbereichen können bei Betrieb dieses Gerätes Rundfunkstörungen auftreten, in welchen Fällen der

Benutzer für entsprechende Gegenmaßnahmen verantwortlich ist.

Attention!

Ceci est un produit de Classe A. Dans un environnement domestique, ce produit risque de créer des interférences radioélectriques, il appartiendra alors à l'utilisateur de prendre les mesures spécifiques appropriées.

FCC Notice:

This equipment generates, uses, and may emit radio frequency energy.

The equipment has been type tested and found to comply with the limits for a Class A digital device pursuant to Part 15 of FCC rules, which are designed to provide reasonable protection against such radio frequency interference.

Operation of this equipment in a residential area may cause interference in which case the user at his own expense will be required to take whatever measures may be required to correct the interference.

Any modifications to this device—unless expressly approved by the manufacturer—can void the user’s authority to operate this equipment under part 15 of the FCC rules.

Preface

Chapter 1 Console Program Overview

1.1

1.2

1.3

Console Overview

Console Terminal

Console Mode

Chapter 2 SRM Console

2.1

2.2

2.3

2.4

2.5

2.6

2.7

2.8

Invoking the SRM Console

SRM Command Overview

Management Tasks Performed from SRM

Getting Help on SRM Commands

Displaying the Logical Configuration

Displaying the Bootable Devices

Displaying the System FRUs

Displaying FRUs with Errors

2.9

Displaying the Memory Configuration

2.10

Displaying the PAL Version

2.11

Displaying the Power Status

2.12

Displaying the SRM Console Version

2.13

Booting Tru64 UNIX or OpenVMS

2.14

Configuring a PCI NVRAM Module

2.15

Configuring RAID Devices

2.16

Testing the System

2.17

Forcing a System Crash Dump

2.18

Resuming Program Execution

2.19

Reading a File

2.20

Initializing the System

2.21

Loading the AlphaBIOS Console

2.22

Creating a Power-Up Script

2.23

Entering the RMC from the Local VGA Monitor

2.24

Setting and Viewing Environment Variables ix

1-2

1-3

1-4

2-25

2-26

2-28

2-29

2-30

2-32

2-34

2-35

2-2

2-4

2-9

2-10

2-12

2-17

2-18

2-21

2-22

2-23

2-24

2-36

2-38

2-40

2-42

2-44 v

2.25

Ensuring Console Security

2.26

Updating Firmware

Chapter 3 AlphaBIOS Console

3.1

3.2

3.3

3.4

3.5

3.6

3.7

3.8

3.9

3.10

3.11

3.12

Starting AlphaBIOS

Keyboard Conventions and Help

Displaying the System Configuration

Defining the System Partition

Setting Up the Hard Disk

Configuring System Parameters

Setting Up a Windows NT Network

Installing Windows NT

Running Utility Programs

Selecting the Version of Windows NT

Changing to the SRM Console

Upgrading Firmware

Chapter 4 RMC Commands

4.1

4.2

4.3

4.4

4.5

4.6

4.7

4.8

4.9

RMC Commands List clear alert clear port disable alert disable remote enable alert enable remote env halt in

4.10

halt out

4.11

hangup

4.12

help or ?

4.13

power off

4.14

power on

4.15

quit

4.16

reset

4.17

send alert

4.18

set alert

4.19

set com1_mode

4.20

set dial

4.21

set escape

4.22

set init

4.23

set logout vi

2-76

2-85

3-2

3-4

3-6

3-20

3-24

3-32

3-38

3-42

3-44

3-50

3-58

3-61

4-13

4-14

4-15

4-16

4-17

4-18

4-19

4-20

4-21

4-22

4-24

4-25

4-26

4-27

4-2

4-4

4-5

4-6

4-7

4-8

4-9

4-10

4-12

4.24

set password

4.25

set user

4.26

status

Figures

3–1 AlphaBIOS Setup Screen

3–2 Help Screen for CMOS Setup

3–3 Navigation Help Screen

3–4 Display System Configuration Screen

3–5 System Board Configuration Screen

3–6 Hard Disk Configuration Information Screen

3–7 PCI Configuration Screen

3–8 Advanced PCI Information Screen

3–9 SCSI Configuration Screen

3–10 Memory Configuration Screen

3–11 Integrated Peripherals Screen

3–12 System Partition Not Defined

3–13 Hard Disk Setup Screen

3–14 Create New Partition Dialog Box

3–15 Delete Partition Dialog Box

3–16 Format Disk Dialog Box

3–17 Standard Formatting

3–18 Standard CMOS Setup Screen

3–19 Advanced CMOS Setup Screen

3–20 Network Setup Screen

3–21 Installing Windows NT

3–22 Utilities Menu

3–23 New Error Frame Was Detected Window

3–24 Run Maintenance Program Dialog Box

3–25 Operating System Selections

3–26 Primary Operating System

3–27 Operating System Selection Setup

3–28 Invoking SRM from AlphaBIOS

Tables

1 Compaq AlphaServer ES40 Documentation

2–1 Summary of SRM Console Commands

2–2 Notation Formats for SRM Console Commands

2–3 Special Characters for SRM Console

2–4 Management Tasks and Related SRM Commands

2–5 Correspondence Between Logical and Physical PCI Slots

4-28

4-29

4-30 x

2-4

2-6

2-7

2-9

2-16

3-16

3-18

3-19

3-20

3-24

3-28

3-29

3-30

3-3

3-4

3-5

3-6

3-8

3-10

3-12

3-14

3-31

3-34

3-36

3-38

3-42

3-44

3-46

3-48

3-50

3-52

3-54

3-58 vii

2–6 Device Naming Conventions

2–7 Bit Assignments for Error Field

2–8 Environment Variable Summary

3–1 CMOS Setup Modes

4–1 Status Command Fields

Examples

2–1 Help (or Man)

2–2 Show Config

2–3 Show Device

2–4 Show Fru

2–5 Show Error

2–6 Show Memory

2–7 Show PAL

2–8 Show Power

2–9 Show Version

2–10 OpenVMS Boot

2–11 Prcache

2–12 Test

2–13 Crash

2–14 Continue

2–15 More

2–16 Init

2–17 AlphaBIOS

2–18 Editing the Nvram Script

2–19 Clearing the Nvram Script

2–20 Entering RMC from a VGA Monitor

2–21 Set envar and Show envar

2–22 Set Password

2–23 Set Secure

2–24 Login

2–25 Clear Password

2-17

2-20

2-46

3-32

4-31

2-28

2-30

2-32

2-34

2-35

2-36

2-38

2-40

2-42

2-10

2-12

2-17

2-18

2-21

2-22

2-23

2-24

2-25

2-26

2-44

2-78

2-80

2-82

2-84 viii

Preface

Intended Audience

This manual is for system managers and operators of Compaq AlphaServer

ES40 systems.

Document Structure

This manual uses a structured documentation design. Topics are organized into small sections, usually consisting of two facing pages. Most topics begin with an abstract that provides an overview of the section, followed by an illustration or example. The facing page contains descriptions, procedures, and syntax definitions.

This manual has four chapters.

•

Chapter 1, Console Program Overview, gives an overview of the console interfaces that underlie the interaction between the server hardware and the supported operating systems.

•

Chapter 2, SRM Console, describes the SRM console interface for systems running Tru64 UNIX or OpenVMS.

•

Chapter 3, AlphaBIOS Console, describes the enhanced BIOS graphical interface for systems running Windows NT.

•

Chapter 4, RMC Commands, describes the command set for the remote management console (RMC).

Documentation Titles

Table 1 Compaq AlphaServer ES40 Documentation

Title

User Documentation Kit

Owner’s Guide

User Interface Guide

Basic Installation

Release Notes

Documentation CD (6 languages)

Maintenance Kit

Service Guide

Service Guide HTML Diskette

Illustrated Parts Breakdown

Loose Piece Items

Rackmount Installation Guide

Rackmount Installation Template

Order Number

QZ-01BAA-GZ

EK-ES240-UG

EK-ES240-UI

EK-ES240-PD

EK-ES240-RN

AG-RF9HA-BE

QZ-01BAB-GZ

EK-ES240-SV

AK-RFXDA-CA

EK-ES240-IP

EK-ES240-RG

EK-ES4RM-TP

Support Resources

Support resources for this system are available on the Internet, including a supported options list, firmware updates, and patches.

http://www.digital.com/alphaserver/technical.html

Chapter 1 Console Program Overview

This chapter gives an overview of the console interfaces that underlie the interaction between the server hardware and the supported operating systems.

There are three console interfaces: SRM, AlphaBIOS, and RMC.

•

SRM supports the Tru64 UNIX and OpenVMS operating systems.

•

AlphaBIOS supports the Windows NT operating system.

•

RMC, the remote management console, allows you to monitor the system either locally or from a remote location.

Console Program Overview 1-1

1.1 Console Overview

The system has a console consisting of firmware programs and an attached terminal. The firmware programs consist of software code that is stored within computer chips called flash ROMs that are located on the system board. The chips can be electronically reprogrammed, allowing you to upgrade the code without installing new chips.

The console programs contain instructions that help the hardware perform its assigned functions. There is a console program for SRM and a console program for AlphaBIOS. The console provides the following services:

•

Initializes, tests, and prepares the system hardware for Alpha system software

•

Bootstraps (loads into memory and starts the execution of) operating system software and performs I/O services during booting and shutdown

•

Controls and monitors the state and state transitions of each processor in a multiprocessor system

•

Provides services to operating system software that simplify system software control of hardware

•

Provides the user interface—SRM, which supports the Tru64 UNIX and

OpenVMS operating systems, and AlphaBIOS, which supports the Windows

NT operating system

A third console program, the remote management console (RMC), is implemented through an independent microprocessor that resides on the system board. The RMC allows you to manage the system either on site or from a remote location.

1-2 Compaq AlphaServer ES40 User Interface Guide

1.2 Console Terminal

The console terminal that displays the SRM user interface can be either a serial terminal (VT320 or higher, or equivalent) or a VGA monitor. Systems running Windows NT require a VGA monitor.

Tower

Pedestal/Rack

PK0225

Console Program Overview 1-3

1.3 Console Mode

When the operating system is halted, the system enters console mode.

In console mode, the system operates under the control of a console program and the commands entered or selected by the operator at the console terminal.

1.3.1 SRM Console

SRM (named for the Alpha System Reference Manual) is a commandline interface that supports the Tru64 UNIX and OpenVMS operating systems.

SRM is a UNIX style shell that provides a set of commands and operators and a script-writing facility. The SRM user interface is used to configure and boot the

UNIX or OpenVMS operating system, test the system hardware (for Windows

NT systems, as well), and run firmware diagnostics. The SRM console is described in Chapter 2.

1.3.2 AlphaBIOS Console

AlphaBIOS is an enhanced BIOS graphical user interface for Compaq

AlphaServer platforms. AlphaBIOS is used to configure and boot the

Windows NT operating system and to run AlphaBIOS-compliant utilities.

One such utility is the RAID standalone configuration utility (RCU). The RCU is used to set up the disk drives and logical units on systems that have the optional StorageWorks RAID Array Subsystem For instructions on using the

RCU, refer to the documentation included in your RAID kit. The AlphaBIOS console is described in Chapter 3.

1-4 Compaq AlphaServer ES40 User Interface Guide

1.3.3 Remote Management Console

The remote management console (RMC) is used for either local or remote system management. Through RMC, you can enter commands that emulate the control panel functions and commands that monitor system environmental conditions. The remote management console also provides configuration and error log functionality.

The RMC is described in Chapter 4 of the Compaq AlphaServer ES40 User’s

Guide. Chapter 4 of this book gives an RMC commands reference.

Console Program Overview 1-5

Chapter 2 SRM Console

The SRM user interface is the command-line interface that allows you to configure and boot the Tru64 UNIX or OpenVMS operating system and verify the configuration of devices (for Windows NT, as well).

This chapter describes typical functions performed from the SRM console and the commands and environment variables used for these functions. Key sections in this chapter are:

•

Invoking the SRM Console

•

SRM Command Overview

•

Displaying System Information

•

Booting the Tru64 UNIX or OpenVMS Operating System

•

Configuring the System

•

Testing the System

•

Forcing a System Crash Dump

•

Reading a File

•

Initializing the System

•

Loading the AlphaBIOS Console

•

Creating a Power-Up Script

•

Entering the RMC from the Local VGA Monitor

•

Setting and Viewing Environment Variables

•

Ensuring Console Security

•

Updating Firmware

SRM Console 2-1

2.1 Invoking the SRM Console

You can invoke the SRM console at power-up or restart, after a system failure, or from RMC. Once you invoke SRM, you enter commands at the console prompt, P00>>>.

Invoking SRM from Tru64 UNIX or OpenVMS

The SRM console is invoked automatically at power-up or after a reset or failure. The auto_action environment variable is set by default to halt, which causes the system to stop in the SRM console.

If the operating system is running, invoke the SRM console by shutting down the operating system. Follow the shutdown procedure described in your operating system documentation.

You can also force entry to the SRM console if the auto_action environment variable is set to boot or reset or if the os_type environment variable is set to

nt. To force entry, press the Halt button on the control panel.

CAUTION: A forced halt interrupts the operating system. Applications that are

running may lose data.

Invoking SRM from Windows NT

The os_type environment variable, which selects the user interface for the system, is set to nt. If you invoke the SRM console from AlphaBIOS, os_type is changed to unix or openvms. The Windows NT system will load the SRM console on each reset until you restore your original setup information.

Invoke SRM from Windows NT as follows:

From the AlphaBIOS Setup screen, select CMOS Setup and press Enter.

In the CMOS Setup screen, press F6. The advanced CMOS Setup screen is displayed.

Select UNIX (SRM) or OpenVMS (SRM) and press F10.

The CMOS Setup screen is displayed. Press F10 to save the change.

2-2 Compaq AlphaServer ES40 User Interface Guide

Press the Reset button to reset the system. The SRM console prompt is displayed.

When you have completed your SRM console session, you can restore your original setup. At the SRM prompt, set os_type to nt and then enter the

init command or press the Reset button. The AlphaBIOS console will then load on each subsequent reset.

You can also force entry to SRM from Windows NT. Press the Halt button, and then reset the system. This method does not change the setup information, and

AlphaBIOS will load and start the next time the system is powered up, reset, or initialized with the Halt button unlatched.

CAUTION: A forced halt interrupts the operating system. Applications that are

running may lose data.

Invoking SRM from RMC

To invoke the SRM console from the remote management console, issue the following commands:

RMC> halt in

RMC> reset

These commands are equivalent to pressing the Halt button on the control panel and then pressing the Reset button. See the Compaq AlphaServer ES40

Owner’s Guide for details on the remote management console. See Chapter 4 of this book for a description of the RMC commands.

To return to operating system mode, unlatch the Halt button or issue the RMC

halt out command, and boot the operating system.

SRM Console 2-3

2.2 SRM Command Overview

Table 2–1 summarizes alphabetically the most frequently used SRM console commands; Table 2–2 gives the command notation formats; and

Table 2–3 shows special characters used on the command line.

Table 2–1 Summary of SRM Console Commands

Command alphabios boot continue crash edit set envar show envar show config

Function

Loads and starts the AlphaBIOS console.

Loads and starts the operating system.

Resumes program execution on the specified processor or on the primary processor if none is specified.

Forces a crash dump at the operating system level.

Invokes the console line editor on a RAM script or on the user power-up script, “nvram,” which is always invoked during the power-up sequence.

Displays information about the specified console command.

help (or man)

command

init more

[filename]

prcache rmc

Resets the SRM console and reinitializes the hardware.

Displays a file one screen at a time.

Initializes and displays the status of the PCI NVRAM.

Invokes the remote management console from the local VGA monitor.

Sets or modifies the value of an environment variable.

Displays the state of the specified environment variable.

Displays the logical configuration at the last system initialization.

2-4 Compaq AlphaServer ES40 User Interface Guide

Command Function show device

Displays a list of controllers and bootable devices in the system.

show error

Reports errors logged in the EEPROMs.

show fru show memory

Displays the physical configuration of all field-replaceable units (FRUs).

Displays information about system memory.

show pal

Displays the versions of UNIX and OpenVMS PALcode.

show power

Displays information about system environmental characteristics, including power supplies, system fans, CPU fans, and temperature.

show version test

Displays the version of the SRM console program installed on the system.

Verifies the configuration of the devices in the system.

NOTE: Commands used to diagnose errors are documented in the Compaq

AlphaServer ES40 Service Guide.

SRM Console 2-5

Table 2–2 Notation Formats for SRM Console Commands

Attribute Conditions

Length

Case

Up to 255 characters, not including the terminating carriage return or any characters deleted as the command is entered.

To enter a command longer than 80 characters, use the backslash character for line continuation (see Table 2–3).

Upper- or lowercase characters can be used for input.

Characters are displayed in the case in which they are entered.

Abbreviation Only by dropping characters from the end of words. You must enter the minimum number of characters to identify the keyword unambiguously. Abbreviation of environment variables is allowed with the show command.

Options You can use command options, to modify the environment, after the command keyword or after any symbol or number in the command. See individual command descriptions for examples.

Numbers

No characters

Most numbers in console commands are in decimal notation.

A command line with no characters is a null command. The console program takes no action and does not issue an error message; it returns the console prompt. The console supports command-line recall and editing.

Spaces or tabs

Multiple adjacent spaces and tabs are compressed and treated as a single space. Leading and trailing spaces are ignored.

2-6 Compaq AlphaServer ES40 User Interface Guide

Table 2–3 Special Characters for SRM Console

Character

Return or

Enter

Backslash (\)

Delete

Ctrl/A

Ctrl/B or up-arrow

Ctrl/C

Left-arrow

Ctrl/E

Ctrl/F or right-arrow

Ctrl/H

Backspace

Ctrl/J

Ctrl/O

Function

Terminates a command line. No action is taken on a command until it is terminated. If no characters are entered and this key is pressed, the console just redisplays the prompt.

Continues a command on the next line. Must be the last character on the line to be continued.

Deletes the previous character.

Toggles between insert and overstrike modes. The default is overstrike.

Recalls previous command or commands. The last 16 commands are stored in the recall buffer.

Terminates the process that is running. Clears Ctrl/S; resumes output suspended by Ctrl/O. When entered as part of a command line, deletes the current line. Ctrl/C has no effect as part of a binary data stream.

Moves the cursor left one position.

Moves the cursor to the end of the line.

Moves the cursor right one position.

Moves the cursor to the beginning of the line.

Deletes ones character.

Deletes the previous word.

Stops output to the console terminal for the current command. Toggles between enable and disable. The output can be reenabled by other means as well: when the console prompts for a command, issues an error message, or enters program mode, or when Ctrl/P is entered.

Continued on next page

SRM Console 2-7

Table 2–3 Special Characters for SRM Console (Continued)

Character

Ctrl/Q

Ctrl/R

Ctrl/S

Ctrl/U

" "

Function

Resumes output to the console terminal that was suspended by Ctrl/S.

Redisplays the current line. Deleted characters are omitted. This command is useful for hardcopy terminals.

Suspends output to the console terminal until Ctrl/Q is entered. Cleared by Ctrl/C.

Deletes the current line.

Wildcarding for commands such as show.

Double quotes enable you to denote a string for environment variable assignment.

Specifies that all text between it and the end of the line is a comment. Control characters are not considered part of a comment.

2-8 Compaq AlphaServer ES40 User Interface Guide

2.3 Management Tasks Performed from SRM

This section lists system management tasks and the related SRM commands.

Table 2–4 Management Tasks and Related SRM Commands

Task

Get help on SRM commands

Start AlphaBIOS from SRM

Display the item indicated (logical configuration, boot devices, FRUs, memory, PALcode version, power supplies and sensors, and SRM version)

Boot OpenVMS or UNIX operating system

Initialize (reset) console firmware

Set and view environment variables

Edit a script

Read a file

Force a crash dump

Resume program execution

Initialize and display status of PCI NVRAM

Run RMC from the local VGA monitor

Verify the devices in the system

Commands

help or man

alphabios show (config, device, error, fru, memory, pal, power, version) boot init set envar show envar edit more crash continue prcache rmc test

SRM Console 2-9

2.4 Getting Help on SRM Commands

The help (or man) command displays basic information about a command.

Example 2–1 Help (or Man)

P00>>> help set

NAME

set

FUNCTION

Set or modify the value of an environment variable.

SYNOPSIS

set <envar> <value>

[-integer] [-string]

where

<envar>={auto_action,bootdef_dev,boot_file,boot_osflags,...}

2-10 Compaq AlphaServer ES40 User Interface Guide

The help (or man) command displays basic information about the use of console commands when the system is in console mode. The syntax is:

help (or man) [command . . . ]

command . . .

Command or topic for which help is requested. The options are:

none

Displays the complete list of commands for which you can receive help.

command_name

Displays information about the console command.

argument_string

(such as “sh”)

Displays information about all commands that begin with that string.

SRM Console 2-11

2.5 Displaying the Logical Configuration

Use the show config command to display the logical configuration of the system.For the physical configuration, see the show fru command

(Section 2.7).

Example 2–2 Show Config

P00>>> show config

Compaq Computer Corporation

Compaq AlphaServer ES40

Firmware

SRM Console: V5.4-5528

ARC Console: 5.68

➊

PALcode: OpenVMS PALcode V1.50-0, Tru64 UNIX PALcode V1.47-5

Serial Rom: V1.5-F

RMC Rom: V1.0

RMC Flash Rom: V1.2

➋

Processors

CPU 0

CPU 1

CPU 2

CPU 3

Alpha 21264-4 500 MHz 4MB Bcache

➌

Core Logic

Cchip

Dchip

Pchip 0

Pchip 1

TIG

DECchip 21272-CA Rev 9(C4)

DECchip 21272-DA Rev 2

DECchip 21272-EA Rev 2

Rev 10

➍

Memory

Array Size Base Address

--------- ---------- ----------------

0 256Mb 0000000060000000

1 512Mb 0000000040000000

2 256Mb 0000000070000000

3 1024Mb 0000000000000000

2048 MB of System Memory

2-12 Compaq AlphaServer ES40 User Interface Guide

➊

Firmware. Version numbers of the SRM console, AlphaBIOS (ARC) console, PALcode, serial ROM, RMC ROM and RMC flash ROM.

➋

Processors. Processors present, processor version and clock speed, and amount of backup cache.

➌

Core logic. Version numbers of the chips on the system board.

➍

Memory. Memory arrays and memory size.

Continued on next page

SRM Console 2-13

Example 2–2 Show Config (Continued)

Slot Option Hose 0, Bus 0, PCI

2/0 NCR 53C896 pke0.7.0.2.0

2/1 NCR 53C896 pkf0.7.0.102.0

SCSI Bus ID 7

➎

4 DEC PowerStorm

7 Acer Labs M1543C Bridge to Bus 1, ISA

15 Acer Labs M1543C IDE dqa.0.0.15.0

dqb.0.1.15.0

dqa0.0.0.15.0

19 Acer Labs M1543C USB

TOSHIBA CD-ROM XM-6302B

Option Hose 0, Bus 1, ISA

Floppy dva0.0.0.1000.0

Slot Option Hose 1, Bus 0, PCI

1 NCR 53C895 pka0.7.0.1.1

SCSI Bus ID 7

dka0.0.0.1.1

dka100.1.0.1.1

RZ2DD-LS

dka200.2.0.1.1

3 NCR 53C810 pkb0.7.0.3.1

dkb0.0.0.3.1

4 DE500-BA Network Con ewa0.0.0.4.1

6 DECchip 21152-AA

RZ1CB-CS

SCSI Bus ID 7

RZ25

00-00-F8-09-90-FF

Bridge to Bus 2, PCI

Slot Option Hose 1, Bus 2, PCI

0 NCR 53C875 pkc0.7.0.2000.1

SCSI Bus ID 7

1 NCR 53C875 pkd0.7.0.2001.1

SCSI Bus ID 7

2 DE500-AA Network Con ewb0.0.0.2002.1

00-06-2B-00-25-5B

P00>>>

2-14 Compaq AlphaServer ES40 User Interface Guide

➎

PCI bus information.

The “Slot” column lists the logical slots seen by the system. These are not the physical slots into which devices are installed. See Table 2–5 for the correspondence between logical slots and physical slots.

The NCR 53C896 on Hose 0, Bus 0 is a dual-channel Ultra2 SCSI multifunction controller. Two controllers reside on the same chip. They are shown as 2/0 and 2/1. The first number is the logical slot, and the second is the function.

The Acer Labs bridge chip, which is located in PCI logical slot 7, has two built-in IDE controllers. The CD-ROM is on the first controller.

NOTE: The naming of devices (for example,dqa.0.0.15.0) follows the

conventions described in Table 2–6.

In Example 2–2, the following devices are present:

Hose 0, Bus 0, PCI

Slot 2/0

Slot 2/1

Slot 4

Slot 7

Slot 15

Slot 19

SCSI controller

VGA controller

PCI to ISA bridge chip

IDE controller and CD-ROM drive

Universal serial bus (USB) controller

Hose 0, Bus 1, ISA

Diskette drive

Hose 1, Bus 0, PCI

Slot 1

Slot 3

Slot 4

Slot 6

SCSI controller and drives

Ethernet controller

PCI-to-PCI bridge chip to Bus 2

Hose 1, Bus 2, PCI

Slot 0

Slot 1

Slot 2

SCSI controller

Ethernet controller

Continued on next page

SRM Console 2-15

Table 2–5 Correspondence Between Logical and Physical PCI Slots

Physical Slot

Logical Slot

PCI 0

Device

PCI 1

Device

NOTE: PCI 0 and PCI 1 correspond to Hose 0 and Hose 1 in the logical

configuration.

2-16 Compaq AlphaServer ES40 User Interface Guide

2.6 Displaying the Bootable Devices

Use the show device command to display the bootable devices. DK =

SCSI drive; DQ = IDE drive; DV = diskette drive; EI or EW = Ethernet controller; PK = SCSI controller.

Example 2–3 Show Device

P00>>> show device dka0.0.0.1.1 DKA0 RZ2DD-LS 0306 dka100.1.0.1.1 DKA100 RZ2DD-LS 0306 dka200.2.0.1.1 DKA200 RZ1CB-CS 0844 dkb0.0.0.3.1 DKB0 RZ25 0900 dqa0.0.0.15.0 DQA0 TOSHIBA CD-ROM XM-6302B 1012 dva0.0.0.1000.0 DVA0 ewa0.0.0.4.1 EWA0 00-00-F8-09-90-FF ewb0.0.0.2002.1 EWB0 00-06-2B-00-25-5B pka0.7.0.1.1 PKA0 SCSI Bus ID 7 pkb0.7.0.3.1 PKB0 SCSI Bus ID 7 pkc0.7.0.2000.1 PKC0 SCSI Bus ID 7 pkd0.7.0.2001.1 PKD0 SCSI Bus ID 7

Table 2–6 Device Naming Conventions

Category Description dq

Driver ID Two-letter designator of port or class driver dk SCSI drive or CD ew Ethernet port dq IDE CD-ROM dr RAID set device du DSSI disk fw mk mu

FDDI device

SCSI tape

DSSI tape dv Diskette drive ei Ethernet port

One-letter designator of storage adapter

(a, b, c…).

pk SCSI port pu DSSI port

Storage adapter

Device unit number

Unique number (MSCP unit number). SCSI unit numbers are forced to 100 X node ID.

Bus node number Bus node ID.

Channel number Used for multi-channel devices.

Logical slot num.

Corresponds to PCI slot number (see Table 2–5).

Hose number 0 — PCI 0

1 — PCI 1

SRM Console 2-17

2.7 Displaying the System FRUs

Use the show fru command to view the physical configuration of FRUs.

Use the show error command to display FRUs with errors.

Example 2–4 Show Fru

➊ ➋ ➌ ➍ ➎ ➏

P00>>> show fru

FRUname E Part# Serial# Misc. Other

SMB0 00 54-25385-01.C03 NI81561341

SMB0.CPU0 00 54-30158-03.A05 NI90260078

SMB0.CPU1 00 54-30158-03.A05 NI90260073

SMB0.CPU2 00 54-30158-03.A05 NI90260056

SMB0.CPU3 00 54-30158-03.A05 NI90260071

SMB0.MMB0 00 54-25582-01.B02 AY90112345

SMB0.MMB0.DIM1 00 54-24941-EA.A01CPQ NI90202001

SMB0.MMB0.DIM2 00 54-24941-EA.A01CPQ NI90200102

SMB0.MMB0.DIM3 00 54-24941-EA.A01CPQ NI90200103

SMB0.MMB0.DIM4 00 54-24941-EA.A01CPQ NI90200104

SMB0.MMB0.DIM5 00 54-24941-EA.A01CPQ NI90202005

SMB0.MMB0.DIM6 00 54-24941-EA.A01CPQ NI90202006

SMB0.MMB1 00 54-25582-01.B02 AY90112301

SMB0.MMB1.DIM1 00 54-25053-BA.A01CPQ NI90112341

SMB0.MMB1.DIM2 00 54-25053-BA.A01CPQ NI90112342

SMB0.MMB1.DIM3 00 54-25053-BA.A01CPQ NI90112343

SMB0.MMB1.DIM4 00 54-25053-BA.A01CPQ NI90112344

SMB0.MMB1.DIM5 00 54-25053-BA.A01CPQ NI90112345

SMB0.MMB1.DIM6 00 54-25053-BA.A01CPQ AY80112346

SMB0.MMB2 00 54-25582-01.B02 AY80012302

SMB0.MMB2.DIM1 00 54-25053-BA.A01CPQ NI90112331

SMB0.MMB2.DIM2 00 54-25053-BA.A01CPQ AY80112332

SMB0.MMB2.DIM3 00 54-25053-BA.A01CPQ AY80112333

SMB0.MMB2.DIM4 00 54-25053-BA.A01CPQ AY80112334

SMB0.MMB2.DIM5 00 54-25053-BA.A01CPQ AY80112335

SMB0.MMB2.DIM6 00 54-25053-BA.A01CPQ AY80112336

SMB0.MMB3 00 54-25582-01.B02 AY90112303

SMB0.MMB3.DIM1 00 54-25053-BA.A01CPQ AY80112341

SMB0.MMB3.DIM2 00 54-25053-BA.A01CPQ AY80112342

SMB0.MMB3.DIM3 00 54-25053-BA.A01CPQ AY80112343

SMB0.MMB3.DIM4 00 54-25053-BA.A01CPQ AY80112344

SMB0.MMB3.DIM5 00 54-25053-BA.A01CPQ AY80112345

SMB0.MMB3.DIM6 00 54-25053-BA.A01CPQ AY80112346

SMB0.CPB0 00 54-30156-01 AY80100999

SMB0.CPB0.PCI4 00 ELSA GLoria Synergy

SMB0.CPB0.PCI5 00 NCR 53C895

SMB0.CPB0.PCIA 00 DE500-BA Network Cont

SMB0.CPB0.SBM0 00 - -

PWR0 00 30-49448-01.A02 2P90700557 API-7850

PWR1 00 30-49448-01.A02 2P90700558 API-7850

2-18 Compaq AlphaServer ES40 User Interface Guide

FAN1 00 70-40073-01 - Fan

FAN2 00 70-40073-01 - Fan

FAN3 00 70-40072-01 - Fan

FAN4 00 70-40071-01 - Fan

FAN5 00 70-40073-02 - Fan

FAN6 00 70-40074-01 - Fan

JIO0 00 54-25575-01 - Junk I/O

OCP0 00 70-33894-0x - OCP

P00>>>

➊

FRUname The FRU name recognized by the SRM console. The name also indicates the location of that FRU in the physical hierarchy.

SMB = system board; CPU = CPUs; MMB = memory motherboard; DIM = DIMMs; CPB = PCI backplane; PCI =

PCI option; SBM = SCSI backplane; PWR = power supply;

FAN = fans; JIO= I/O connector module (junk I/O).

➋

E Error field. Indicates whether the FRU has any errors logged against it. FRUs without errors show 00 (hex). FRUs with errors have a non-zero value that represents a bit mask of possible errors. See Table 2–7.

➌

Part #

➍

➎

➏

Serial #

Misc.

Other

The part number of the FRU in ASCII, either a Compaq part number or a vendor part number.

The serial number. For Compaq FRUs, the serial number has the form XXYWWNNNNN.

XX = manufacturing location code

YWW = year and week

NNNNN = sequence number. For vendor FRUs, the 4-byte sequence number is displayed in hex.

Miscellaneous information about the FRUs. For Compaq

FRUs, a model name, number, or an “a.k.a” name. For vendor

FRUs, the manufacturer's name.

Optional data. For Compaq FRUs, the Compaq part alias number (if one exists). For vendor FRUs, the year and week of manufacture.

Continued on next page

SRM Console 2-19

Table 2–7 Bit Assignments for Error Field

Bit

Bit 0 is 1

Bit 1 is 1

Bit 2 is 1

Bit 3 is 1

Bit 4 is 1

Bit 5 is 1

Bit 6 is 1

Bit 7 is 1

Meaning

Failure

TDD error has been logged

At least one SDD error has been logged

FRU EEPROM is unreadable

Checksum failure on bytes 0-62

Checksum failure on bytes 64-126

Checksum failure on bytes 128-254

FRU’s system serial does not match system’s

NOTE: Contact your service provider if the E (error) field shows any of these

errors.

2-20 Compaq AlphaServer ES40 User Interface Guide

2.8 Displaying FRUs with Errors

The show error command displays FRUs that have errors logged to the serial control bus EEPROMs.

Example 2–5 Show Error

P00>>> show error

SMB0 TDD - Type: 1 Test: 1 SubTest: 1 Error: 1

SMB0

P00>>>

SDD - Type: 4 LastLog: 1 Overwrite: 0

The output of the show error command is based on information logged to the serial control bus EEPROMs. Both the operating system and the ROM-based diagnostics log errors to the EEPROMs. This functionality allows service providers to generate an error log from the console environment.

The syntax is:

show error

If no errors are logged, nothing is displayed and you are returned to the SRM console prompt.

Example 2–5 shows errors reported on the system board (SMB0). Contact your service provider if errors are displayed.

SRM Console 2-21

2.9 Displaying the Memory Configuration

Use the show memory command to view the total memory size and location.

Example 2–6 Show Memory

P00>>> show memory

Array Size Base Address

--------- ---------- ----------------

0 256Mb 0000000060000000

1 512Mb 0000000040000000

2 256Mb 0000000070000000

3 1024Mb 0000000000000000

2048 MB of System Memory

The show memory display corresponds to the memory array configuration shown in the Compaq AlphaServer ES40 Owner’s Guide. The display does not indicate the number of DIMMs or their size. Thus, in Example 2–6, Array 3 could consist of two sets of 128 MB DIMMs (eight DIMMs) or one set of 256 MB

DIMMs (four DIMMs). Either combination provides 1024 MB of memory.

Use the show fru command to display all the DIMMs in the system and their locations.

2-22 Compaq AlphaServer ES40 User Interface Guide

2.10 Displaying the PAL Version

Use the show pal command to display the PALcode version.

Example 2–7 Show PAL

P00>>> show pal pal OpenVMS PALcode V1.50-5, Tru64 UNIX PALcode V1.47-5

P00>>>

The show pal command displays the versions of UNIX and OpenVMS PALcode.

PALcode is the Alpha Privileged Architecture Library code, written to support

Alpha processors. It implements architecturally defined processor behavior.

The syntax is:

show pal

SRM Console 2-23

2.11 Displaying the Power Status

Use the show power command to display the status of power supplies, fans, and system temperature. If you are not able to access SRM, invoke RMC and issue the env command.

Example 2–8 Show Power

P00>>> show power

Status

Power Supply 0 Good

Power Supply 1 Good

Power Supply 2 Not Available

System Fan 1 Good

System Fan 2 Good

System Fan 3 Bad

System Fan 4 Good

System Fan 5 Good

System Fan 6 Good

CPU 0 Temperature Warning

CPU 1 Temperature Good

CPU 2 Temperature Good

CPU 3 Temperature Good

Zone 0 Temperature Good

Zone 1 Temperature Good

Zone 2 Temperature Good

P00>>>

➊

Power supplies. Power supply 2 is not installed.

➋

System fans. Fan 3 is not working.

➌

Temperature sensors on CPUs. CPU 0 is above threshold.

➍

Temperature sensors on PCI backplane.

The syntax is:

show power

➌

➍

➊

➋

2-24 Compaq AlphaServer ES40 User Interface Guide

2.12 Displaying the SRM Console Version

Use the show version command to display the version of the SRM console that is installed.

Example 2–9 Show Version

P00>>> show version version V5.4-5602 Feb 1 1999 14:53:22

P00>>>

The show version command displays the version of the SRM console program that is installed on the system.

The syntax is:

show version

SRM Console 2-25

2.13 Booting Tru64 UNIX or OpenVMS

The boot command boots the UNIX or OpenVMS operating system. You can specify a boot device, operating system-specific boot information

(boot flags), and an Ethernet protocol for network boots. You can also specify whether the boot program should halt and remain in console mode.

Example 2–10 OpenVMS Boot

P00>>> boot dkb0

(boot dkb0.0.0.2.1 -flags 0) block 0 of dkb0.0.0.2.1 is a valid boot block reading 1002 blocks from dkb0.0.0.2.1

bootstrap code read in base = 200000, image_start = 0, image_bytes = 7d400 initializing HWRPB at 2000 initializing page table at 1f2000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code

OpenVMS (TM) Operating System, Version 7.1

The boot command initializes the processor, loads a program image from the specified boot device, and transfers control to that image. If you do not specify a boot device in the command line, the default boot device is used. The default boot device is determined by the value of the bootdef_dev environment variable, described in Section 2.24.2.

If you specify a list of boot devices, a bootstrap is attempted from each device in order. Then control passes to the first successfully booted image. In a list, always enter network devices last, because network bootstraps terminate only if a fatal error occurs or when an image is successfully loaded.

The syntax is:

boot [-file filename] [-flags [value]] [-halt] [-protocols enet_protocol]

[boot_dev]

2-26 Compaq AlphaServer ES40 User Interface Guide

-file

filename

Specifies the name of a file to load into the system. Use the set

boot_file command to set a default boot file (Section 2.24.3).

NOTE: For booting from Ethernet, the filename is limited by

the MOP V3 load protocol to 15 characters. The MOP protocol is used with OpenVMS systems.

-flags

[value]

-halt

-protocols

enet_protocol boot_dev

Provides additional operating system-specific boot information.

In UNIX, specifies boot flags. In OpenVMS, specifies system root number and boot flags. These values are passed to the operating system for interpretation. Preset default boot flag values are 0,0. Use the set boot_osflags command to change the default boot flag values. See Section 2.24.4.

Forces the bootstrap operation to halt and invoke the console program. The console is invoked after the bootstrap image is loaded and page tables and other data structures are set up.

Console device drivers are not shut down. Transfer control to the bootstrap image by entering the continue command.

Specifies the Ethernet protocol to be used for the network boot.

Either mop (for OpenVMS) or bootp (for UNIX) may be specified. Use the set ew*0_protocols or ei*0_protocols command to set a default network boot protocol. See Section

2.24.13.

A device path or list of devices from which the console program attempts to boot, or a saved boot specification in the form of an environment variable. Use the set bootdef_dev command to set a default boot device. See Section 2.24.2.

NOTE: Entering values for boot flags, the boot device name, or Ethernet

protocol on the boot command overrides the current default value for

the current boot request, but does not change the corresponding environment variable. For example, if you have defined a value for

boot_osflags and you specify the -flags argument on the boot

command line, the -flags argument takes precedence for that boot

session.

SRM Console 2-27

2.14 Configuring a PCI NVRAM Module

The prcache command is used to support Tru64 UNIX systems equipped with a Prestoserve PCI NVRAM module.

Example 2–11 Prcache

P00>>> prcache -f

PCI NVRAM Disk Cache: passed

Size: 4MB

PCI Memory Address: 40000000

System ID: 12000000

State: - not valid

Battery Status: good (Charging)

Battery Disconnect Circuit Status: enabled

P00>>> prcache -z

This command will zero the PCI NVRAM Disk Cache

Do you really want to continue [Y/N] ? : y clearing disk cache

P00>>>

-f

-z

-u

The prcache command, with the options listed below, checks PCI NVRAM configuration and battery status, clears data from the NVRAM module, and disables the NVRAM battery disconnect circuit. This command is used only with

UNIX systems. The syntax is:

prcache -{f,z,u}

Checks configuration and battery status.

Clears valid data; writes zeros to memory.

Disables the NVRAM battery disconnect circuit.

2-28 Compaq AlphaServer ES40 User Interface Guide

2.15 Configuring RAID Devices

RAID devices are configured from the AlphaBIOS console.

RAID devices are configured with the RAID standalone configuration utility.

See Chapter 3 for information about running AlphaBIOS utility programs.

SRM Console 2-29

2.16 Testing the System

The test command verifies the configuration of the devices in the system. This command can be used on all supported operating systems:

UNIX, OpenVMS, and Windows NT.

Example 2–12 Test

P00>>> test

Testing the Memory

Testing the DK* Disks(read only)

No DU* Disks available for testing

No DR* Disks available for testing

Testing the DQ* Disks(read only)

Testing the DF* Disks(read only)

No MK* Tapes available for testing

No MU* Tapes available for testing

Testing the DV* Floppy Disks(read only)

Testing the VGA (Alphanumeric Mode only)

Testing the EWA0 Network

Testing the EWB0 Network

P00>>>

The test command also does a quick test on the system speaker. A beep is emitted as the command starts to run.

The tests are run sequentially, and the status of each subsystem test is displayed to the console terminal as the tests progress. If a particular device is not available to test, a message is displayed. The test script does no destructive testing; that is, it does not write to disk drives.

The syntax is:

test [argument]

Use the -lb (loopback) argument for console loopback tests.

To run a complete diagnostic test using the test command, the system configuration must include:

•

A serial loopback connected to the COM2 port (not included)

•

A parallel loopback connected to the parallel port (not included)

2-30 Compaq AlphaServer ES40 User Interface Guide

•

A formatted diskette

•

A formatted CD-ROM

The test script tests devices in the following order:

Memory tests (one pass)

Read-only tests: DK* disks, DR* disks, DQ* disks, DU* disks, MK* tapes,

DV* floppy.

Console loopback tests if -lb argument is specified: COM2 serial port and parallel port.

VGA console tests: These tests are run only if the console environment variable is set to serial. The VGA console test displays rows of the word

compaq.

Network internal loopback tests for EW* networks.

NOTE: No write tests are performed on disk and tape drives. Media must be

installed to test the diskette drive and tape drives.

Testing a Windows NT System

To test a system running Windows NT, invoke the SRM console in one of the following ways and then enter the test command:

•

From the AlphaBIOS console, press the Halt button, and press the Reset button to reset the system.

•

Alternatively, select UNIX (SRM) or OpenVMS (SRM) from the Advanced

CMOS Setup screen and then reset the system.

The second method changes the os_type environment variable to UNIX or

OpenVMS, causing the SRM console to start on each subsequent reset. To restore your original setup for Windows NT, enter the following commands while still in the SRM console:

P00>>> set os_type nt

P00>>> init

SRM Console 2-31

2.17 Forcing a System Crash Dump

The crash command causes a UNIX or OpenVMS operating system that has hung to crash so that you can capture a crash dump to the selected device.

Example 2–13 Crash

P00>>> crash

CPU 0 restarting

DUMP: 19837638 blocks available for dumping.

DUMP: 118178 wanted for a partial compressed dump.

DUMP: Allowing 2060017 of the 2064113 available on 0x800001 device string for dump = SCSI 1 1 0 0 0 0 0.

DUMP.prom: dev SCSI 1 1 0 0 0 0 0, block 2178787

DUMP: Header to 0x800001 at 2064113 (0x1f7ef1) device string for dump = SCSI 1 1 0 0 0 0 0.

DUMP.prom: dev SCSI 1 1 0 0 0 0 0, block 2178787

DUMP: Dump to 0x800001: .......: End 0x800001 device string for dump = SCSI 1 1 0 0 0 0 0.

DUMP.prom: dev SCSI 1 1 0 0 0 0 0, block 2178787

DUMP: Header to 0x800001 at 2064113 (0x1f7ef1) succeeded halted CPU 0 halt code = 5

HALT instruction executed

PC = fffffc0000568704

P00>>>

2-32 Compaq AlphaServer ES40 User Interface Guide

The crash command forces a UNIX or OpenVMS operating system that has stopped responding to crash so that you can capture a crash dump.

The syntax is:

crash

Press the Halt button or use the RMC halt in command to invoke the SRM console, then enter the crash command to restart the primary CPU and force a crash dump to the selected device.

•

See the OpenVMS Alpha System Dump Analyzer Utility Manual for information on how to interpret OpenVMS crash dump files.

•

See the Guide to Kernel Debugging for information on using the Tru64

UNIX Krash Utility.

SRM Console 2-33

2.18 Resuming Program Execution

The continue command resumes the execution of the operating system on the processor you specify or on the primary processor, if none is specified.

Example 2–14 Continue

P00>>> halt

P00>>> continue continuing CPU

Typically, you use the continue command if you inadvertently halt the system and want to resume operating system mode. The continue command is valid under the following circumstances:

•

If you pressed the Halt button on the control panel or entered the RMC halt

in command. You must unlatch the Halt button or enter the RMC halt out command before issuing the continue command.

•

If you used the –halt option with the boot command

•

If you issued a Ctrl/P at the SRM console (OpenVMS systems only)

•

If you do not disturb the machine state after the halt by entering other SRM commands

The syntax is:

continue

2-34 Compaq AlphaServer ES40 User Interface Guide

2.19 Reading a File

The more command displays a file one screen at a time.

Example 2–15 More

P00>>> more el # Display the contents of the

# SRM console’s event log one

# screen at a time.

P00>>> help * | more # Display the contents of

# online help one screen at a time.

The more command is similar to the UNIX more command. It is useful for displaying output that scrolls too quickly to be viewed. For example, when you power up the system, the system startup messages scroll, and the messages are written to an event log. When the P00>>> prompt is displayed, you can use the

more el command to display the contents of the event log file. The syntax is:

more [file...]

File is the name of the file to be displayed.

SRM Console 2-35

2.20 Initializing the System

The init command resets the SRM console firmware and reinitializes the hardware. Example 2–16 shows an abbreviated example.

Example 2–16 Init

P00>>> init

OpenVMS PALcode V1.50-0, Tru64 UNIX PALcode V1.47-5 starting console on CPU 0 initialized idle PCB initializing semaphores initializing heap initial heap 200c0 memory low limit = 152000 heap = 200c0, 17fc0 initializing driver structures initializing idle process PID initializing file system initializing hardware initializing timer data structures lowering IPL

CPU 0 speed is 2.00 ns (500MHz) create dead_eater create poll create timer create powerup access NVRAM

Memory size 2048 MB testing memory

...

probe I/O subsystem probing hose 1, PCI probing PCI-to-PCI bridge, bus 2 bus 0, slot 1 -- pka -- NCR 53C895 bus 0, slot 3 -- pkb -- NCR 53C810 bus 0, slot 4 -- ewa -- DE500-BA Network Controller bus 2, slot 0 -- pkc -- NCR 53C875 bus 2, slot 1 -- pkd -- NCR 53C875 bus 2, slot 2 -- ewb -- DE500-AA Network Controller probing hose 0, PCI probing PCI-to-ISA bridge, bus 1 bus 0, slot 2, function 0 -- pke -- NCR 53C896 bus 0, slot 2, function 1 -- pkf -- NCR 53C896 bus 0, slot 4 -- vga -- DEC PowerStorm bus 0, slot 15 -- dqa -- Acer Labs M1543C IDE bus 0, slot 15 -- dqb -- Acer Labs M1543C IDE starting drivers entering idle loop

2-36 Compaq AlphaServer ES40 User Interface Guide

initializing keyboard starting console on CPU 1 initialized idle PCB initializing idle process PID lowering IPL

CPU 1 speed is 2.00 ns (500MHz) create powerup

Memory Testing and Configuration Status

Array Size Base Address

--------- ---------- ----------------

0 256Mb 0000000060000000

1 512Mb 0000000040000000

2 256Mb 0000000070000000

3 1024Mb 0000000000000000

2048 MB of System Memory

Testing the System

Testing the Disks (read only)

Testing the Network initializing GCT/FRU at offset 1a0000

AlphaServer ES40 Console V5.4-5528, built on Feb 1 1999 at 01:43:35

P00>>>

The init command restarts the SRM console and reinitializes the hardware.

This command is similar to performing a reset, but a reset causes full start-up diagnostics to be performed, whereas init performs only the SRM diagnostics.

The syntax is:

init

After you use the init command, the system stops in the SRM console because the auto_action environment variable is set by default to halt. To cause the system to boot automatically after issuing the init command, set the

auto_action environment variable to boot or restart.

New values for the following environment variables take effect only after you reset the system by pressing the Reset button or issuing the init command:

auto_action console cpu_enabled os_type pk*0_fast pk*0_host_id pk*0_soft_term

SRM Console 2-37

2.21 Loading the AlphaBIOS Console

The alphabios command loads and starts the AlphaBIOS console.

AlphaBIOS-based utilities, such as the RAID configuration utility, are run from AlphaBIOS.

Example 2–17 AlphaBIOS

P00>>> alphabios -g

Loading Arc Firmware From Flash resetting all I/O buses

Arc Firmware Loaded

2-38 Compaq AlphaServer ES40 User Interface Guide

The syntax is:

alphabios

Options

-g

Starts AlphaBIOS on a VGA port. Use this option if the console environment variable is set to serial, but you want AlphaBIOS to come up on the VGA monitor.

To return to the SRM console, do one of the following:

If you are running UNIX or OpenVMS (the os_type environment variable is set to unix or openvms), reset the system by pressing the Reset button.

If you are running Windows NT (the os_type environment variable is set to

nt), press the Halt button and reset the system. Alternatively, select UNIX

console (SRM) or OpenVMS console (SRM) from the Advanced CMOS

Setup screen and then reset the system.

SRM Console 2-39

2.22 Creating a Power-Up Script

The system comes with a script (set of commands) named “nvram” that is stored in EEROM. Nvram is a user-created power-up script that is always invoked during the power-up sequence. Use the SRM edit command to create or alter the nvram script.

Example 2–18 Editing the Nvram Script

P00>>> edit nvram editing ‘nvram’

0 bytes read in

*10 set mopv3_boot 1

*exit

17 bytes written out to nvram

P00>>>

Example 2–19 Clearing the Nvram Script

P00>>> edit nvram editing ‘nvram’

20 bytes read in

*10

*exit

0 bytes written out to nvram

P00>>>

2-40 Compaq AlphaServer ES40 User Interface Guide

You can create an nvram script to include any commands you want the system to execute at power-up. You create and edit the nvram script using the SRM edit command. With edit, lines may be added, overwritten, or deleted. To clear the script, enter line numbers without any text. This deletes the lines.

In Example 2–18 an environment variable called “mop3_boot” is created and set to 1 on each power-up. By default, MOP boots send four MOP V4 requests before defaulting to MOP V3. This user-created environment variable forces the

SRM console to bypass MOP V4 requests. This speeds up MOP booting on networks with MOP V3 software.

The syntax is:

edit file

The file is the name of the file to be edited.

The editing commands are:

help list

Displays the brief help file.

Lists the current file prefixed with line numbers.

renumber

Renumbers the lines of the file in increments of 10.

exit quit

Leaves the editor and closes the file, saving all changes.

Leaves the editor and closes the file without saving changes.

nn nn text

Deletes line number nn.

Adds or overwrites line number nn with the specified text.

CAUTION: Use caution when editing the nvram script. It is possible to disable

the system by including an inappropriate command. For example, if you include the init command in the script, the system will go into an endless loop.

To correct this error, press the Halt button or issue the RMC halt

in command, then power up or reset the system. When the P00>>> prompt is displayed, edit the nvram script to remove the illegal command.

SRM Console 2-41

2.23 Entering the RMC from the Local VGA Monitor

Use the rmc command to enter the remote management console from a

VGA monitor connected to the system. All RMC commands are available and all output is redirected to the VGA monitor.

Example 2–20 Entering RMC from a VGA Monitor

Failing Connection

P00>>> rmc

Unable to allocate COM1. Currently in use by: shell

To connect to the Remote Management Console from the graphics interface the “console” environment variable must be set to “graphics,” and the serial interface cannot be in use by another console program.

RMC>

Successful Connection

P00>>> rmc

You are about to connect to the Remote Management Console.

Use the RMC reset command or press the front panel reset button to disconnect and to reload the SRM console.

Do you really want to continue? [y/(n)] y

Please enter the escape sequence to connect to the Remote

Management Console.

Exiting from the Graphics Interface

RMC> reset

2-42 Compaq AlphaServer ES40 User Interface Guide

The rmc command allows you to invoke the remote management console (RMC) from a VGA monitor connected to the VGA port. The syntax is:

rmc

After entering the rmc command, type the default escape sequence to connect to the RMC. The default escape sequence is:

^[^[rmc

This sequence is equivalent to Ctrl/left bracket, Ctrl/left bracket, rmc. On some keyboards, the escape key functions like the Ctrl/left bracket combination.

The console environment variable must be set to graphics, and the serial interface cannot be in use by another console program. Once you have connected to RMC, the serial interface is disabled. See Example 2–20 for an example of an unsuccessful connection and a successful connection.

To exit RMC, enter the RMC reset command or press the Reset button on the control panel. The reset disconnects the RMC session, resets hardware, and reloads the SRM console from the flash ROM.

See the Compaq AlphaServer ES40 Owner’s Guide for complete information about RMC. See Chapter 4 in this book for a description of the RMC command set.

SRM Console 2-43

2.24 Setting and Viewing Environment Variables

Use the set envar and show envar commands to set and view environment variables.

Example 2–21 Set envar and Show envar

P00>>> set bootdef_dev dkb0

P00>>> show bootdef_dev

Bootdef_dev dkb0

Environment variables pass configuration information between the console and the operating system. Their settings determine how the system powers up, boots the operating system, and operates. Environment variables are set or changed with the set envar command. Their values are viewed with the show

envar command.

2-44 Compaq AlphaServer ES40 User Interface Guide

set envar

The set command sets or modifies the value of an environment variable. It can also be used to create a new environment variable if the name used is unique.

set envar value

envar

The name of the environment variable to be modified. See

Table 2–8 for a list of environment variables

value

The new value of the environment variable.

New values for the following environment variables take effect only after you reset the system by pressing the Reset button or by issuing the init command.

auto_action console cpu_enabled os_type pk*0_fast pk*0_host_id pk*0_soft_term show envar

The show envar command displays the current value (or setting) of an environment variable. The syntax is:

show envar

envar

The name of the environment variable to be displayed. The

show* command displays all environment variables.

Table 2–8 summarizes the SRM environment variables. These environment variables are described in the following pages.

Continued on next page

SRM Console 2-45

Table 2–8 Environment Variable Summary

Environment

Variable auto_action bootdef_dev boot_file boot_osflags com1_baud com2_baud

com1_flow or

com2_flow com1_mode

Function

Specifies the console’s action at power-up, a failure, or a reset.

Specifies the default boot device string.

Specifies the default file name to be used for booting when no file name is specified by the boot command.

Specifies the default operating system boot flags.

Sets the baud rate of the internal COM1 serial interface.

Sets the default baud rate of the COM2 serial port.

Specifies the flow control on the serial ports.

com1_modem or

com2_modem console cpu_enabled

ei*0_inet_init or

ew*0_inet_init

ei*0_mode or

ew*0_mode

ei*0_protocols or

ew*0_protocols kbd_hardware_ type

Specifies the COM1 data flow paths so that data either flows through the RMC or bypasses it.

Specifies to the operating system whether or not a modem is present.

Specifies the device on which power-up output is displayed (serial terminal or VGA monitor).

Enables or disables a specific secondary CPU.

Determines whether the interface's internal Internet database is initialized from nvram or from a network server (by using the bootp protocol).

Specifies the connection type of the default Ethernet controller.

Specifies network protocols for booting over the

Ethernet controller.

Specifies the default console keyboard type.

2-46 Compaq AlphaServer ES40 User Interface Guide

Environment

Variable language memory_test ocp_text os_type password pci_parity pk*0_fast pk*0_host_id pk*0_soft_term tt_allow_login

Function

Specifies the console keyboard layout.

Specifies the extent to which memory will be tested.

Overrides the default OCP display text with userspecified text.

Specifies the operating system and sets the appropriate console interface.

Sets a console password. Required for placing the

SRM into secure mode.

Disables or enables parity checking on the PCI bus.

Enables fast SCSI mode.

Specifies the default value for a controller host bus node ID.

Enables or disables SCSI terminators on systems that use the QLogic ISP1020 SCSI controller.

Enables or disables login to the SRM console firmware on other console ports.

SRM Console 2-47

2.24.1 auto_action

The auto_action environment variable specifies the action the console takes any time the system powers up, fails, or resets. The value of auto_action takes effect only after you reset the system by pressing the

Reset button or by issuing the init command.

The default setting for auto_action is halt. With this setting, the system stops in the SRM console after being initialized. To cause the operating system to boot automatically after initialization, set the auto_action environment variable to boot or restart.

•

When auto_action is set to boot, the system boots from the default boot device specified by the value of the bootdef_dev environment variable.

•

When auto_action is set to restart, the system boots from whatever device it booted from before the shutdown/reset or failure.

NOTE: After you set the auto_action environment variable, it is recommended

that you set the boot device and operating system flags as well, using

the set bootdef_dev and set boot_osflags commands.

The syntax is:

set auto_action value

The options for value are:

halt boot restart

The system remains in console mode after power-up or a system crash.

The operating system boots automatically after the SRM init command is issued or the Reset button is pressed.

The operating system boots automatically after the SRM init command is issued or the Reset button is pressed, and it also reboots after an operating system crash.

2-48 Compaq AlphaServer ES40 User Interface Guide

Examples

In the following example, the operator sets the auto_action environment variable to restart. The device specified with the bootdef_dev environment variable is dka0. When UNIX is shut down and rebooted, the system will reboot from dka0.

P00>>> show auto_action auto_action halt

P00>>> set auto_action restart

P00>>> init

P00>>> show auto_action auto_action restart

P00>>> show bootdef_dev bootdef_dev dka0

P00>>> boot

...

(Log into UNIX and shutdown/reboot)

#shutdown -r now

...

console will boot from dka0

In the following example, auto_action is set to restart, but UNIX is booted from a device other than the device set with bootdef_dev. When UNIX is shut down and rebooted, the system reboots from the specified device.

P00>>> boot dka100

(Log into UNIX and shutdown/reboot)

#shutdown -r now

...

console will boot from dka100

SRM Console 2-49

2.24.2 bootdef_dev

The bootdef_dev environment variable specifies one or more devices from which to boot the operating system. When more than one device is specified, the system searches in the order listed and boots from the first device with operating system software.

Enter the show bootdef_dev command to display the current default boot device. Enter the show device command for a list of all devices in the system.

The syntax is:

set bootdef_dev boot_device

boot_device

The name of the device on which the system software has been loaded. To specify more than one device, separate the names with commas.

Example

In this example, two boot devices are specified. The system will try booting from dkb0 and if unsuccessful, will boot from dka0.

P00>>> set bootdef_dev dkb0, dka0

NOTE: When you set the bootdef_dev environment variable, it is

recommended that you set the operating system boot parameters as well,

using the set boot_osflags command.

2-50 Compaq AlphaServer ES40 User Interface Guide

2.24.3 boot_file

The boot_file environment variable specifies the default file name to be

used for booting when no file name is specified by the boot command.

The factory default value is null.

The syntax is:

set boot_file filename

Example

In this example, a boot file is specified for booting OpenVMS from the

InfoServer. APB_0712 is the file name of the APB program used for the initial system load (ISL) boot program.

P00>>> set boot_file apb_0712

P00>>> boot

SRM Console 2-51

2.24.4 boot_osflags

The boot_osflags environment variable sets the default boot flags and, for OpenVMS, a root number.

Boot flags contain information used by the operating system to determine some aspects of a system bootstrap. Under normal circumstances, you can use the default boot flag settings.

To change the boot flags for the current boot only, use the flags_value argument with the boot command.

The syntax is:

set boot_osflags flags_value

The flags_value argument is specific to the operating system.

UNIX Systems

UNIX systems take a single ASCII character as the flags_value argument.

Load operating system software from the specified boot device (autoboot).

Boot to multiuser mode.

Prompt for the name of a file to load and other options (boot interactively).

Boot to single-user mode.

Stop in single-user mode. Boots /vmunix to single-user mode and stops at the # (root) prompt.

D Full dump; implies “s” as well. By default, if UNIX crashes, it completes a partial memory dump. Specifying “D” forces a full dump at system crash.

2-52 Compaq AlphaServer ES40 User Interface Guide

OpenVMS Systems

OpenVMS systems require an ordered pair as the flags_value argument:

root_number and boot_flags.

root_number Directory number of the system disk on which OpenVMS files are located. For example: boot_flags

root_number Root Directory

0 (default) [SYS0.SYSEXE]

[SYS1.SYSEXE]

[SYS2.SYSEXE]

3 [SYS3.SYSEXE]

The hexadecimal value of the bit number or numbers set. To specify multiple boot flags, add the flag values (logical OR).

For example, the flag value 10080 executes both the 80 and

10000 flag settings. See the following table.

Flags_Value Bit Number Meaning

100

10000

20000

Bootstrap conversationally (enables you to modify SYSGEN parameters in SYSBOOT).

Map XDELTA to a running system.

Stop at initial system breakpoint.

Perform diagnostic bootstrap.

Stop at the bootstrap breakpoints.

Omit header from secondary bootstrap image.

Prompt for the name of the secondary bootstrap file.

Halt before secondary bootstrap.

Display debug messages during booting.

Display user messages during booting.

Continued on next page

SRM Console 2-53

Examples

In the following UNIX example, the boot flags are set to autoboot the system to multiuser mode when you enter the boot command.

P00>>> set boot_osflags a

In the following OpenVMS example, root_number is set to 2 and boot_flags is set to 1. With this setting, the system will boot from root directory SYS2.SYSEXE

to the SYSBOOT prompt when you enter the boot command.

P00>>> set boot_osflags 2,1

In the following OpenVMS example, root_number is set to 0 and boot_flags is set to 80. With this setting, the operator will be prompted for the name of the secondary bootstrap file when the boot command is entered.

P00>>> set boot_osflags 0,80

2-54 Compaq AlphaServer ES40 User Interface Guide

2.24.5 **com*_baud**

The default baud rate for the system is 9600. The com*_baud commands set the baud rate for COM1 and COM2.

com1_baud

The com1_baud environment variable sets the baud rate for the internal

COM1 serial interface.

com2_baud

The com2_baud environment variable sets the baud rate to match that of the device connected to the COM2 port.

The syntax is:

set com*_baud baud_value

baud_value

The new baud rate. A list of possible values is displayed by entering the command without a value.

Example

The following example shows the supported baud rate values.

P00>>> set com2_baud

57600

38400

19200

9600

7200

4800

3600

2400

2000

1800

SRM Console 2-55

2.24.6 **com*_flow**

The com1_flow and com2_flow environment variables set the flow control on the COM1 and COM2 serial ports, respectively.

The syntax is:

set com*_flow flow_value

flow_value

Defined values are:

none—No data flows in or out of the serial ports. Use this setting for devices that do not recognize XON/XOFF or that would be confused by these signals.

software—Use XON/XOFF(default). This is the setting for a standard serial terminal.

hardware—Use modem signals CTS/RTS. Use this setting if you are connecting a modem to a serial port.

Example

P00>>> set com1_flow hardware

2-56 Compaq AlphaServer ES40 User Interface Guide

2.24.7 com1_mode

The set com1_mode command specifies the COM1 data flow paths, so that data either flows through the RMC or bypasses it. You can also set com1_mode from the RMC.

By default all data passes through the RMC. Data and control signals flow from the system COM1 port, through the RMC, and to the active external port, either the COM1 serial port (MMJ) or the 9-pin modem port. If a modem is connected, the data goes to the modem. This mode is called through mode.

You can enter the RMC from either the MMJ port or the modem port. Only one session can be active at a time.

For modem connection, you can use the set com1_mode command to allow data to partially or completely bypass the RMC. The bypass modes are snoop mode, soft bypass mode, and firm bypass mode. These modes disable the local channel from sending characters to the system COM1 port.

You can also set the RMC to local mode, in which only the local channel can communicate with the system COM1 port. Local mode disables the modem from sending characters to the system COM1 port, but you can still enter the

RMC.

The syntax is set com1_mode value

value

through snoop soft_bypass firm_bypass local

Defined values are:

All data passes through RMC and is filtered for the RMC escape sequence. This is the default.

Data partially bypasses RMC, but RMC taps into the data lines and listens passively for the RMC escape sequence.

Data bypasses RMC, but RMC switches automatically into snoop mode if loss of carrier occurs.

Data bypasses RMC. RMC remote management features are disabled.

Changes the focus of the COM1 traffic to the local RMC COM1 port if

RMC is currently in one of the bypass modes or if RMC is in through mode with an active remote session.

Example

P00>>> set com1_mode snoop

SRM Console 2-57

2.24.8 **com*_modem**

The com1_modem and com2_modem environment variables are used to tell the operating system whether a modem is present on the COM1 or

COM2 ports, respectively. From the settings of these variables, the operating system determines whether the port should assert a signal

DTR.

The syntax is:

set com*_modem modem_value

modem_value

Defined values are: on—Modem is present.

off—Modem is not present (default value).

If you attach a modem to the COM1 or COM2 port, set the modem_value to on.

This setting tells the operating system to assert a DTR (data terminal ready) signal to let the modem know that there is hardware attached. The modem responds with a DSR (data set ready) signal.

Example

P00>>> set com1_modem on

2-58 Compaq AlphaServer ES40 User Interface Guide

2.24.9 console

The console terminal can be either a VGA monitor or a serial terminal.

The console environment variable specifies which type of console is

used.

The syntax is:

set console output_device

The options for output_device are:

graphics (default)

serial

The console terminal is a VGA monitor or a device connected to the VGA port.

The console terminal is the device connected to the

COM1 port.

The value of console takes effect only after you reset the system by pressing the Reset button or by issuing the init command.

Example

P00>>> show console console graphics

P00>>> set console serial

P00>>> init

P00>>> show console console serial

P00>>>

SRM Console 2-59

2.24.10 cpu_enabled

The cpu_enabled environment variable sets a bit mask that enables or disables specific CPUs on a multiprocessor system.

Disabling a CPU may be necessary if a number of errors are reported on a specific CPU. These errors might be displayed during power-up or might be displayed with the show fru or show config command.

Disabled CPUs are prevented from running the console or the operating system.

Bit 0 of the mask corresponds to CPU 0, bit 1 to CPU 1, and so on. A zero in the bit mask prevents the corresponding CPU from running; a one allows it to run.

The bit mask is expressed as a hexadecimal value.

The value of cpu_enabled takes effect only after you reset the system by pressing the Reset button or by issuing the init command.

The cpu_enabled environment variable is typically used in benchmark testing.

NOTE: The primary CPU cannot be disabled. The primary CPU is the lowest

numbered working CPU.

2-60 Compaq AlphaServer ES40 User Interface Guide

The syntax is:

set cpu_enabled hex_digit

The hex_digit values are shown in the table.

Hex_Digit Value

Binary Equivalent

CPU enable 3210 (bit)

0000

0001

0010

0011

0100

0101

0110

0111

1000

1001

1010

1011

1100

1101

1110

1111

Enabled CPUs

No CPUs (CPU 0 still comes up)

CPU 0

CPU 1

CPU 0,1

CPU 2

CPU 0,2

CPU 1,2

CPU 0,1,2

CPU 3

CPU 0,3

CPU 1,3

CPU 0,1,3

CPU 2,3

CPU 0,2,3

CPU 1,2,3

CPU 0,1,2,3

Example

In the following example, CPU 0 and CPU 1 are enabled, and CPU 2 and CPU 3 are disabled.

P00>>> set cpu_enabled 3

SRM Console 2-61

2.24.11 **ei0_inet_init or ew0_inet_init**

The ei*0_inet_init or ew*0_inet_init environment variable determines whether the interface’s internal Internet database is initialized from nvram or from a network server (through the bootp protocol). Legal values are nvram and bootp. The default value is bootp. Set this environment variable if you are booting UNIX from a RIS server.

To list the network devices on your system, enter the show device command.

The Ethernet controllers start with the letters “ei” or “ew,” for example, ewa0.

The third letter is the adapter ID for the specific Ethernet controller. Replace the asterisk (*) with the adapter ID letter when using this command.

The syntax is:

set ei*0_inet_init value or

set ew*0_inet_init value

The value is one of the following:

nvram

Initializes the internal Internet database from nvram.

bootp

Initializes the internal Internet database from a network server through the bootp protocol.

Example

P00>>> set ewa0_inet_init bootp

2-62 Compaq AlphaServer ES40 User Interface Guide

2.24.12 **ei0_mode or ew0_mode**

The ei*0_mode or ew*0_mode environment variable sets an Ethernet controller to run an AUI, ThinWire, or twisted-pair Ethernet network.

For the fast setting, the device defaults to fast.

To list the network devices on your system, enter the show device command.

The Ethernet controllers start with the letters “ei” or “ew,” for example, ewa0.

The third letter is the adapter ID for the specific Ethernet controller. Replace the asterisk (*) with the adapter ID letter when entering the command.

The syntax is:

set ei*0_mode value or

set ew*0_mode value

The options for value are:

aui bnc fast

Fastfd full

Device type is AUI.

Device type is ThinWire.

Device type is fast 100BaseT.

Device type is fast full duplex 100BaseT.

Device type is full duplex twisted-pair.

twisted-pair

Device type is 10BaseT (twisted-pair).

Example

P00>>> set ewa0_mode t

P00>>> show ewa0_mode ewa0_mode twisted-pair

SRM Console 2-63

2.24.13

**ei0_protocols or ew0_protocols**

The ei*0_protocols or ew*0_protocols environment variable sets network protocols for booting and other functions.

To list the network devices on your system, enter the show device command.

The Ethernet controllers start with the letters “ei” or “ew,” for example, ewa0.

The third letter is the adapter ID for the specific Ethernet controller. Replace the asterisk (*) with the adapter ID letter when entering the command.

The syntax is:

set ei*0_protocols protocol_value or

set ew*0_protocols protocol_value

The options for protocol_value are:

mop (default) Sets the network protocol to mop (Maintenance Operations

Protocol), the setting typically used with the OpenVMS operating system.

bootp

Sets the network protocol to bootp, the setting typically used with the UNIX operating system.

bootp,mop

When both are listed, the system attempts to use the mop protocol first, regardless of which is listed first. If not successful, it then attempts the bootp protocol.

Example

P00>>> show device

ewa0.0.0.1001.0 EWA0 08-00-2B-3E-BC-B5 ewb0.0.0.12.0 EWB0 00-00-C0-33-E0-0D ewc0.0.0.13.0 EWC0 08-00-2B-E6-4B-F3

P00>>> set ewa0_protocols bootp

P00>>> show ewa0_protocols ewa0_protocols bootp

2-64 Compaq AlphaServer ES40 User Interface Guide

2.24.14 kbd_hardware_type

The kbd_hardware_type environment variable sets the keyboard hardware type as either PCXAL or LK411 and enables the system to interpret the terminal keyboard layout correctly.

The syntax is:

set kbd_hardware_type keyboard_type

The options for keyboard_type are:

pcxal (default) Selects the 102-type keyboard layout.

lk411

Selects the LK411 keyboard layout.

Example

P00>>> set kbd_hardware_type lk411

P00>>>

SRM Console 2-65

2.24.15 language

The language environment variable specifies the keyboard layout, which depends on the language. The setting of the language environment variable must match the language of the keyboard variant.

The factory keyboard setting is 36 English (American).

The value of language takes effect only after you reset the system by pressing the Reset button or issuing the init command.

The syntax is:

set language language_code

The options for language_code are:

No language

Dansk (Danish)

Deutsch (German)

Deutsch (Swiss)

English (American)

English (British/Irish)

Español (Spanish)

Français (French)

Français (Canadian)

Français (Suisse

Romande)

Italiano (Italian)

Nederlands (Netherlands)

Norsk (Norwegian)

Portugues (Portuguese)

Suomi (Finnish)

Svenska (Swedish)

Belgisch-Nederlands (Dutch)

Japanese (JIS)

Japanese (ANSI)

Example

P00>>> set language 3A

2-66 Compaq AlphaServer ES40 User Interface Guide

2.24.16 memory_test

The memory_test environment variable determines the extent of memory testing on the next reset. You can set this variable for systems running UNIX.

The syntax is:

set memory_test value

The options for value are:

full (default)

partial none

Specifies that the full memory test will be run. Systems using the OpenVMS operating system must run the full memory test.

Specifies that the first 256 MB of memory will be tested.

Specifies that memory will not be tested. (However, tests are always run on the first 32 MB.)

Example

With the following setting, the first 256 MB of memory are tested when a system running UNIX is reset.

P00>>> set memory_test partial

SRM Console 2-67

2.24.17 ocp_text

The ocp_text environment variable specifies a message to be displayed on the control panel display after self-tests and diagnostics have been completed. It is useful to set this environment variable if you have a number of systems and you want to identify each system by a node name.

The syntax is:

set ocp_text message

The message is the message you want to be displayed, typically the network node name you have defined for the system. The message can be up to 16 characters and must be entered in quotation marks.

Example:

P00>>> set ocp_text “Node Alpha1”

P00>>>

2-68 Compaq AlphaServer ES40 User Interface Guide

2.24.18 os_type

The os_type environment variable specifies the default operating system. This variable is set at the factory to the setting for the operating system you purchased. Use this command to change the factory default setting.

The value of os_type takes effect only after you reset the system by pressing the Reset button or by issuing the init command.

The syntax is:

set os_type os_type

The options for os_type are:

unix vms nt

Sets the default to UNIX. The SRM firmware is started during power-up or reset.

Sets the default to OpenVMS. The SRM firmware is started during power-up or reset.

Sets the default to Windows NT. The SRM firmware is started, and it loads and starts the AlphaBIOS firmware during power-up or reset. (If the Halt button was pressed, or the RMC halt in command was issued, this option is overridden.)

Example

In this example, the default operating system is set to Windows NT. After the system is initialized, the AlphaBIOS console is loaded and the Windows NT boot menu is displayed.

P00>>> set os_type nt

P00>>> init

SRM Console 2-69

2.24.19 pci_parity

The pci_parity environment variable disables or enables parity checking on the PCI bus.

Some PCI devices do not implement PCI parity checking, and some have a parity-generating scheme in which the parity is sometimes incorrect or is not fully compliant with the PCI specification. A side effect of this behavior is that superfluous PCI parity errors are reported by the host PCI bridge. In such cases, the device can be used as long as parity is not checked; disabling PCI parity checking prevents false parity errors that can cause system problems.

The syntax is:

set pci_parity value

The options for value are:

on (default)

off

Enables PCI parity checking.

Disables PCI parity checking.

Example

P00>>> set pci_parity off

P00>>> show pci_parity pci parity off

2-70 Compaq AlphaServer ES40 User Interface Guide

2.24.20 **pk*0_fast**

The pk*0_fast environment variable enables fast SCSI to perform in either standard or fast mode.

If the system has at least one fast SCSI device, set the default controller speed to fast SCSI (1). Devices on a controller that connects to both standard and fast

SCSI devices will perform at the appropriate rate for the device. If the system has no fast SCSI devices, set the default controller speed to standard SCSI (0).

If a fast SCSI device is on a controller set to standard, it will perform in standard mode.

To list the controllers on your system, enter the show device command. SCSI controllers begin with the letters “pk,” for example, pka0. The third letter is the adapter ID for the specific SCSI controller. Replace the asterisk with the adapter ID letter when entering the set pk*0_fast command.

The value of set pk*0_fast takes effect only after you reset the system by pressing the Reset button or by issuing the init command.

The syntax is:

set pk*0_fast scsi_speed

The options for scsi_speed are:

1 (default)

The controller is in standard SCSI mode.

The controller is in fast SCSI mode.

Example

P00>>> set pkb0_fast 1

P00>>> init

P00>>> show pkb0_fast

P00>>> pkb0_fast 1

SRM Console 2-71

2.24.21 **pk*0_host_id**

The pk*0_host_id environment variable sets the controller host bus node ID to a value between 0 and 7.

Each SCSI bus in the system requires a controller. Buses can support up to eight devices; however, the eighth device must be a controller. Each device on the bus, including the controller, must have a unique ID, which is a number between 0 and 7. This is the bus node ID number.

On each bus, the default bus node ID for the controller is set to 7. You do not need to change the controller bus node ID unless you place two or more controllers on the same bus.

To list the controllers on your system, enter the show device command. SCSI controllers begin with the letters “pk” (for example, pka0). The third letter is the adapter ID for the controller. Replace the asterisk with the adapter ID letter when entering the set pk*0_host_id command.

The value of pk*0_host_id takes effect only after you reset the system by pressing the Reset button or by issuing the init command.

The syntax is:

set pk*_host_id scsi_node_id

The value for scsi_node_id is the bus node ID, a number from 0 to 7.

Example

In this example, the default bus node ID for a SCSI controller with an adapter

ID of “b” is set to bus node ID 6.

P00>>> set pkb0_host_id 6

P00>>> init

P00>>> show pkb0_host_id pkb0_host_id 6

2-72 Compaq AlphaServer ES40 User Interface Guide

2.24.22 **pk*0_soft_term**

The pk*0_soft_term environment variable enables or disables SCSI terminators for optional SCSI controllers. This environment variable applies to systems that use the QLogic SCSI controller, though it does not affect the onboard controller.

The QLogic ISP1020 SCSI controller implements the 16-bit wide SCSI bus. The

QLogic module has two terminators, one for the low eight bits and one for the high eight bits.

The value of pk*0_soft_term takes effect only after you reset the system by pressing the Reset button or by issuing the init command.

The syntax is:

set pk*0_soft_term value

The options for value are:

off low high

on (default)

diff

Disables termination of all 16 bits.

Enables low eight bits and disables high eight bits.

Enables high eight bits and disables low eight bits.

Enables all 16 bits.

Places the bus in differential mode.

Continued on next page

SRM Console 2-73

Examples

In this example, both terminators are disabled.

P00>>> set pkb0_soft_term off

P00>>> init

P00>>> show pkb0_soft_term pkb0_soft_term off

In this example, the terminator for the high 8 bits is enabled.

P00>>> set pkb0_soft_term high

P00>>> init

P00>>> show pkb0_soft_term pkb0_soft_term high

2-74 Compaq AlphaServer ES40 User Interface Guide

2.24.23 tt_allow_login

The tt_allow_login environment variable enables or disables login to the SRM console firmware on alternative console ports. “Login” refers to pressing the Return or Enter key to activate the console device.

If the console environment variable is set to serial, the primary console device is the terminal connected through the COM1 port. The set tt_allow_login 1 command lets you activate a console device through COM2 or a VGA monitor.

The set tt_allow_login 0 command disables console activation through alternative ports. You might want to disable console access to COM2 as a system security measure or if you want to use COM2 as an “application only” port.

The syntax is:

set tt_allow_login value

The options for value are:

Disables login through the COM2 port or the VGA monitor.

1 (default) Enables login through the COM2 port or the VGA monitor.

Example

In the following example, the primary console device is set to the terminal connected through the COM1 port. Then the set tt_allow_login 0 command is used to disable logins through either the COM2 port or a VGA monitor.

P00>>> set console serial

P00>>> init

P00>> set tt_allow_login 0

SRM Console 2-75

2.25 Ensuring Console Security

The SRM console firmware has console security features intended to prevent unauthorized personnel from modifying the system parameters or otherwise tampering with the system from the console.

The security features include a secure mode and commands to set console security.

2.25.1 Overview of Secure Mode

The SRM console has two modes, user mode and secure mode.

•

User mode allows you to use all SRM console commands. User mode is the default mode.

•

Secure mode allows you to use only the boot and continue commands. The

boot command cannot take command-line parameters when the console is in secure mode. The console boots the operating system using the environment variables stored in NVRAM (boot_file, bootdef_dev,

boot_flags).

2-76 Compaq AlphaServer ES40 User Interface Guide

Secure Function Commands

•

The set password and set secure commands are used to set secure mode.

•

The clear password command is used to exit secure mode and return to user mode. All the SRM console commands are available and the console is no longer secure.

•

The login command turns off console security for the current console session. Once you enter the login command in secure mode, you can enter any SRM command as usual. However, the system automatically returns to secure mode when you enter the boot or continue command or when you reset the system.

NOTE: The security features work only if access to the system hardware is

denied to unauthorized personnel. Be sure the system is available only to authorized personnel.

SRM Console 2-77

2.25.2 Setting the Console Password

Set the console password with the set password command. A password is required for operating the system in secure mode.

Example 2–22 Set Password

P00>>> set password

Please enter the password:

Please enter the password again:

P00>>>

➊

P00>>> set password

Please enter the password:

Please enter the password again:

Now enter the old password:

P00>>>

P00>>> set password

Please enter the password:

Password length must be between 15 and 30 characters

P00>>>

➋

➌

2-78 Compaq AlphaServer ES40 User Interface Guide

➊

Setting a password. If a password has not been set and the set password command is issued, the console prompts for a password and verification.

The password and verification are not echoed.

➋

Changing a password. If a password has been set and the set password command is issued, the console prompts for the new password and verification, then prompts for the old password. The password is not changed if the validation password entered does not match the existing password stored in

NVRAM.

➌

The password length must be between 15 and 30 alphanumeric characters.

Any characters entered after the 30th character are not stored.

The set password command sets the console password for the first time or changes an existing password. It is necessary to set the password only if the system is going to operate in secure mode.

The syntax is:

set password

SRM Console 2-79

2.25.3 Setting the Console to Secure Mode

To set the console to secure mode, first set the password. Then enter the set secure command. The system immediately enters secure mode.

Example 2–23 Set Secure

P00>>> set secure

Console is secure. Please login.

P00>>> b dkb0

Console is secure - parameters are not allowed.

P00>>> login

Please enter the password:

P00>>> b dkb0

(boot dkb0.0.0.3.1)

➊

➋

➊

The console is put into secure mode, and then the operator attempts to boot the operating system with command-line parameters. A message is displayed indicating that boot parameters are not allowed when the system is in secure mode.

➋

The login command is entered to turn off security features for the current console session. After successfully logging in, the operator enters a boot command with command-line parameters.

2-80 Compaq AlphaServer ES40 User Interface Guide

The set secure command enables secure mode. If no password has been set, you are prompted to set the password. Once you set a password and enter the

set secure command, secure mode is in effect immediately and only the

continue, boot (using the stored parameters), and login commands can be performed.

The syntax is:

set secure

SRM Console 2-81

2.25.4 Turning Off Security During a Console Session

The login command turns off the security features, enabling access to all SRM console commands during the current console session. The

system automatically returns to secure mode as soon as the boot or

continue command is entered or when the system is reset.

Example 2–24 Login

P00>>> login

Secure not set. Please set the password.

P00>>> set password

Please enter the password:

Please enter the password again:

P00>>> login

Please enter the password.

P00>>> show boot*

➊

➋

➌

➊

The login command is entered, but the system is not in secure mode. A password must be set.

➋

A password is set.

➌

The login command is entered. After the password is entered, console security is turned off for the current session and the operator can enter commands.

2-82 Compaq AlphaServer ES40 User Interface Guide

When you enter the login command, you are prompted for the current system password. If a password has not been set, a message is displayed indicating that there is no password in NVRAM. If a password has been set, this prompt is displayed:

Please enter the password:

If the password entered matches the password in NVRAM, when the prompt is redisplayed the console is no longer in secure mode and all console commands can be performed during the current console session.

If You Forget the Password

If you forget the current password, use the login command in conjunction with the control panel Halt button to clear the password, as follows:

Enter the login command:

P00>>> login

When prompted for the password, press the Halt button to the latched position and then press the Return (or Enter) key.

Press the Halt button to release the halt. The password is now cleared and the console cannot be put into secure mode unless you set a new password.

SRM Console 2-83

2.25.5 Returning to User Mode

The clear password command clears the password environment variable, setting it to zero. Once the password is cleared, you are returned to user mode.

Example 2–25 Clear Password

P00>>> clear password

Please enter the password:

➊

Console is secure

P00>>> clear password

Please enter the password:

➋

Password successfully cleared.

P00>>>

➊

The wrong password is entered. The system remains in secure mode.

➋

The password is successfully cleared.

The clear password command is used to exit secure mode and return to user mode. To use clear password, you must know the current password. Once you clear the password, the console is no longer secure.

To clear the password without knowing the current password, you must use the

login command in conjunction with the Halt button, as described in Section

2.25.4.

2-84 Compaq AlphaServer ES40 User Interface Guide

2.26 Updating Firmware

System firmware is typically updated whenever the operating system is updated. You might also need to update firmware if you add I/O device controllers and adapters; if enhancements are made to the firmware; or if the serial ROM or RMC firmware should ever become corrupted.

Procedures for updating the SRM firmware are described in the Compaq

AlphaServer Owner’s Guide.

SRM Console 2-85

Chapter 3 AlphaBIOS Console

AlphaBIOS is the enhanced BIOS graphical interface for AlphaServer platforms. AlphaBIOS supports the Microsoft Windows NT operating system on

Alpha systems. From AlphaBIOS you can install and boot Windows NT, display the system configuration, perform setup tasks, run utility programs, and update

AlphaBIOS firmware.

This chapter explains how to perform these system management tasks from the

AlphaBIOS menus.

Sections in this chapter are:

•

Starting AlphaBIOS

•

Keyboard Conventions and Help

•

Displaying the System Configuration

•

Defining the System Partition

•

Setting Up the Hard Disk

•

Configuring System Parameters

•

Setting Up a Windows NT Network

•

Installing Windows NT

•

Running Utility Programs

•

Selecting the Version of Windows NT

•

Changing to the SRM Console

•

Upgrading Firmware

AlphaBIOS Console 3-1

3.1 Starting AlphaBIOS

When you initialize the system, a startup screen displays information about the system and processors. Memory is tested and the system initializes the SCSI devices. When initialization is complete, a boot screen is displayed.

AlphaBIOS 5.68

Alpha Processor and System Information:

System: AlphaServer ES40

Processor: Alpha 21264, 500 MHz

Memory: 256 MB

Alpha Processor(s) Status:

Processor 0 Running

Processors 1, 2, 3 Ready

SCSI Controller Initialization...

Initialize ATAPI #0...

Device: CD-ROM SCSI ID:0 TOSHIBA CD-ROM XM62028 1110

F2=Setup PAUSE=Pause Display ESC=Bypass Network Init

PKO950

AlphaBIOS 5.68

Please select the operating system to start:

Windows NT Server 4.00

Use and to move the highlight to your choice.

Press Enter to choose.

AlphaServer

Press <F2> to enter SETUP

PK0949

3-2 Compaq AlphaServer ES40 User Interface Guide

Before booting the operating system, you need to define the system partitions and perform other configuration tasks from AlphaBIOS Setup (Figure 3–1). To enter AlphaBIOS Setup, press F2 from the boot menu. Use the arrow keys to select the menu item you want and press Enter. (Refer to Section 3.2 for information on navigating the AlphaBIOS screens.)

Figure 3–1 AlphaBIOS Setup Screen

AlphaBIOS Setup

Display System Configuration...

AlphaBIOS Upgrade...

Hard Disk Setup...

CMOS Setup...

Network Setup...

Install Windows NT

Utilities

About AlphaBIOS...

Press ENTER to partition or format hard disks.

ESC=Exit

PK0905

AlphaBIOS Console 3-3

3.2 Keyboard Conventions and Help

AlphaBIOS uses Windows keyboard conventions for navigating the interface and selecting items. The valid keystrokes are listed in the keyboard help screens.

Figure 3–2 Help Screen for CMOS Setup

Help: CMOS Setup F1=Key Help

F3 Change color scheme.

F6 Enter Advanced CMOS Setup.

F7 Set factory default CMOS settings.

ESC Exit CMOS Setup and discard any changes.

F10 Exit CMOS Setup and save changes,

including changes from Advanced CMOS Setup.

ENTER=Continue

PK-0724-96

Two levels of keyboard help are available. The first level, reached by pressing

F1 once, explains the keystrokes available for the specific part of AlphaBIOS currently displayed. Figure 3–2 is an example of the help displayed by pressing

F1 once, in this case from the CMOS Setup screen.

The second level of keyboard help, reached by pressing F1 from the first help screen, explains the keystrokes available for navigating the entire interface (see

Figure 3–3).

3-4 Compaq AlphaServer ES40 User Interface Guide

Figure 3–3 Navigation Help Screen

AlphaBIOS Setup F1=Help

Help: Action Keys

TAB Move highlight forward between fields of a dialog.

SHIFT+TAB Move highlight backward between fields of a dialog.

Move highlight within a menu, or cycle through available field

values in a dialog window.

ALT+ Drop down a menu of choices from a drop-down listbox. A

drop-down listbox can be recognized by the symbol.

HOME Move to the beginning of a text entry field.

END Move to the end of a text entry field.

Move to the left or right in a text entry field.

ESC Discard changes and/or backup to previous screen.

ENTER=Continue

PK-0725-96

AlphaBIOS Console 3-5

3.3 Displaying the System Configuration

Use the Display System Configuration screen to view information about the system’s installed processor, memory, attached devices, and option boards.

NOTE: You cannot configure the system from this screen.

Figure 3–4 Display System Configuration Screen

Display System Configuration

Systemboard Configuration

Hard Disk Configuration

PCI Configuration

SCSI Configuration

Memory Configuration

Integrated Peripherals

System Type: AlphaServer ES40

Processor: Digital Alpha 21264, Revision 4.0 (4 Processors)

Speed: 500 MHz

Cache: 4 MB

Memory: 2048 MB

Floppy Drive A: 3.5" 1.44 MB

Floppy Drive B: None

Keyboard: U.S. 101-key keyboard

AlphaBIOS Version: 5.68

ESC=Exit

PK0902

3-6 Compaq AlphaServer ES40 User Interface Guide

To display the system configuration

Select Display System Configuration from the AlphaBIOS Setup screen, and press Enter.

In the Display System Configuration screen, use the arrow keys to select the configuration category you want to see.

From this screen, you can view configuration information about these system components:

•

System board

•

Hard disk

•

PCI devices

•

SCSI devices

•

Memory

•

Integrated peripherals

The sections that follow explain the display for each component.

AlphaBIOS Console 3-7

3.3.1 System Board Configuration Display

Figure 3–5 System Board Configuration Screen

Display System Configuration F1=Help

Systemboard Configuration

Hard Disk Configuration

PCI Configuration

SCSI Configuration

Memory Configuration

Integrated Peripherals

System Type: AlphaServer ES40

Processor: Digital Alpha 21264, Revision 4.0 (2 Processors)

Speed: 500 MHz

Cache: 4 MB

Memory: 512 MB

Floppy Drive A: 3.5" 1.44 MB

Floppy Drive B: None

Keyboard: U.S. 101-key keyboard

AlphaBIOS Version: 5.68

ESC=Exit

PK0917

3-8 Compaq AlphaServer ES40 User Interface Guide

➊

System type — The model number of the system.

➋

Processor — The model and revision level of the processor chip. The revision level can help technical support personnel in troubleshooting.

➌

Speed — The speed of the processor.

➍

Cache — The amount, in kilobytes, of static RAM cache memory.

➎

Memory — The amount, in megabytes, of main memory in the system.

➏

Floppy drives — Size and capacity of diskette drives.

➐

Keyboard — Language and type of keyboard.

➑

Firmware version — The version of AlphaBIOS that is currently running.

AlphaBIOS Console 3-9

3.3.2 Hard Disk Configuration Display

Figure 3–6 Hard Disk Configuration Information Screen

Display System Configuration

Systemboard Configuration

Hard Disk Configuration

PCI Configuration

SCSI Configuration

Memory Configuration

Integrated Peripherals

2 2

1 4

1 5

Disk 0 NCRC8xx #0, SCSI ID 0 4091 MB

DEC RZ1CB-CS (C) DEC0844

Disk 1 NCRC8xx #0, SCSI ID 1 4091 MB

DEC RZ1CB-CS (C) DEC0844

Partition 1 4091 MB NTFS

Disk 2 NCRC8xx #0, SCSI ID 2 4091 MB

DEC RZ1CB-CS (C) DEC0844

Partition 1 4091 MB NTFS

ENTER=Select ESC=Exit

PK0916

NOTE: This screen is for information only; it cannot be edited. To make

changes to the hard disk setup, use the Hard Disk Setup screen (Section

3.5).

3-10 Compaq AlphaServer ES40 User Interface Guide

➊

Physical disk ID — Based on the SCSI ID. The disk with the lowest SCSI

ID is disk 0, the disk with the next lowest SCSI ID is disk 1, and so on.

➋

Controller — The brand and model of SCSI chip used on the SCSI controller.

➌

Controller number — Based on how many SCSI controllers of a particular type are installed in the system. The first controller of a type is always numbered 0.

➍

SCSI ID number — A unique number you assign to each SCSI device installed in the system. The SCSI ID is usually set with jumpers or a thumb wheel attached to the drive housing.

➎

Size — The raw capacity of the drive. Formatting the drive with different file systems (for example, FAT and NTFS) can result in different usable sizes because of the differences in how storage is managed under those file systems.

➏

Partition number — Within a single drive, partition numbers are assigned in sequential order: 1, 2, 3, and so on. The partitions populate the drive from the innermost cylinders to the outermost cylinders. If you have a large hard disk (over 800 MB) and plan to use the FAT file system, it is useful to break the disk into several smaller partitions because the FAT file system uses disk space more efficiently at smaller partition sizes.

Partition size is not a concern for the NTFS file system, as NTFS uses disk space efficiently at all partition sizes.

➐

Partition size — The raw (unformatted) storage capacity of the partition.

Storage space will differ based on the file system with which the partition is formatted.

➑

Partition format — The file system (if any) used on a partition. This field displays FAT, NTFS, or unknown (if the partition is unformatted).

AlphaBIOS Console 3-11

3.3.3 PCI Configuration Display

Figure 3–7 PCI Configuration Screen

Display System Configuration F1=Help

Systemboard Configuration

Hard Disk Configuration

PCI Configuration

SCSI Configuration

Memory Configuration

1 2

3 4

Device Name Device Type Revision Physical Slot

DIGITAL PBXGB VGA 34 Slot-1 HwBus0

AcerLabs PCI-ISA ISA bridge 195 Embedded HwBus-0

AcerLabs IDE M5229 IDE 193 Embedded HwBus-0

AcerLabs USB M5237 USB 3 Embedded HwBus-0

DIGITAL 21152 PCI bridge 2 Slot-1 HwBus-0

NCR875 SCSI 4 Slot-1 HwBus-0

Intel 82558 NIC Ethernet 5 Slot-1 HwBus-0

ENTER=Select ESC=Exit

PK0918

3-12 Compaq AlphaServer ES40 User Interface Guide

➊

Device name — The name and model of the device as recorded in the device’s firmware. The device ID may also be displayed.

➋

Device type — The function of the device in the system.

➌

Revision — The number of times the device has been updated by the manufacturer.

➍

Physical slot — The PCI slot number to which the device is physically attached. The ISA bridge, IDE, and USB are integrated (embedded) on the system board.

To display the Advanced PCI Information screen

You can find additional detail about any of the PCI devices listed in the

Advanced PCI Information screen.

Press Enter to enable selection in the device list.

Use the arrow keys to select the device for which you want additional detail.

Press Enter to display the detail.

Press Escape to return to the table of PCI devices.

The Advanced PCI Information screen is shown in Figure 3–8.

AlphaBIOS Console 3-13

Figure 3–8 Advanced PCI Information Screen

Advanced PCI Information

1 2 3

Bus Number=0, Device Number=7, Function Number=0

Configuration Space:

Vendor ID 00 1011

Device ID 02 000d

Command 04 0147

Status 06 C280

Revision ID 08 22

Prog. I/F 09 00

Sub Class Code 0a 00

Class Code 0b 03

Cache Line Size 0c 00

Latency Timer 0d 20

Header Type 0e 00

BIST 0f 00

Base Address 0 10 02000008

ENTER=Continue

PK0944

3-14 Compaq AlphaServer ES40 User Interface Guide

➊

Bus number — The logical PCI bus number.

➋

Device number — The PCI bus device number.

➌

Function number — The number assigned to a particular function on a multifunction device. For example, a combination Ethernet/SCSI controller would be listed twice, with the first function listed as 0 and the second as 1.

➍

Configuration space— The information in the selected device’s PCI configuration space.

AlphaBIOS Console 3-15

3.3.4 SCSI Configuration Display

Figure 3–9 SCSI Configuration Screen

Display System Configuration

Systemboard Configuration

Hard Disk Configuration

PCI Configuration

SCSI Configuration

Memory Configuration

Integrated Peripherals

ATAPI #0

LSI STORAGE #0

LSI STORAGE #1

ATAPI #0, SCSI ID 255, SCSI Bus 0

2 3

4 5

SCSI ID Device Size Description

0 CD-ROM TOSHIBA CD-ROM XM-6202B 1110

PK0919

3-16 Compaq AlphaServer ES40 User Interface Guide

➊

SCSI controller information — The physical characteristics of the selected

SCSI controller, including:

Controller — Brand and model of SCSI chip used on the SCSI controller.

Controller number — Based on the number of SCSI controllers of a particular type in the system. The first controller of a type is always numbered 0.

SCSI ID number — A unique number assigned to the SCSI controller.

The standard scheme is for controllers to be SCSI ID 7.

SCSI bus number — Indicates if the controller is first or second in the system. The first controller is tied to SCSI bus 0, and the second to SCSI bus 1.

➋

SCSI ID — A unique number you assign to each SCSI device in the system. The SCSI ID is usually set with jumpers or a thumb wheel attached to the drive housing.

➌

Device type — Hard disk, CD-ROM, scanner, or other type of device.

➍

Size — The raw capacity of the drive. Formatting the drive with different file systems (for example, FAT and NTFS) can result in different usable sizes because of differences in the way those file systems manage storage.

This field is left blank if it is not applicable to a device (for example, a scanner).

➎

Description — The name and model of the device as recorded in the device’s firmware.

AlphaBIOS Console 3-17

3.3.5 Memory Configuration Display

Figure 3–10 Memory Configuration Screen

Display System Configuration F1=Help

Systemboard Configuration

Hard Disk Configuration

PCI Configuration

SCSI Configuration

Memory Configuration

Integrated Peripherals

System Memory Configuration

Bank 0: 128 MB (32 MB Per DIMM) -- Starting Address = 0x00000000

Bank 1: 128 MB (32 MB Per DIMM) -- Starting Address = 0x10000000

Bank 2: 0 MB

Bank 3: 0 MB

ESC=Exit

PK0920

➊

Memory Bank — A group of DIMMs. You can calculate the number of

DIMMs per bank by dividing the number of megabytes per DIMM within a bank into the total memory installed in the bank. In the example, Bank 0 has 128 MB of memory installed, and each DIMM slot in the bank contains

32 MB of memory. Therefore, Bank 0 contains four DIMMs.

➋

Installed Memory — The amount of memory, in megabytes, installed in a bank of DIMM slots.

➌

Memory per DIMM — The amount of memory, in megabytes, contained in each DIMM within a bank of DIMM slots.

3-18 Compaq AlphaServer ES40 User Interface Guide

3.3.6 Integrated Peripherals Display

Figure 3–11 Integrated Peripherals Screen

Display System Configuration

Systemboard Configuration

Hard Disk Configuration

PCI Configuration

SCSI Configuration

Memory Configuration

Integrated Peripherals

Integrated Peripheral State

3 4

Serial Port 1: Enabled as COM1: 3F8, IRQ4

Serial Port 2: Enabled as COM2: 2F8, IRQ3

Parallel Port 1: Enabled as LPT1 3BC, IRQ7

ESC=Exit

PK0921

➊

Device type — The type and configuration of built-in peripherals.

➋

MS DOS name — Shows if the device is enabled, and if it is enabled, the addressable MS-DOS name for the device.

➌

Port address — The physical memory location from and to which data travels as it is received into the device, and sent from the device, respectively.

➍

Interrupt — The interrupt request line (IRQ) used by the device to get the

CPU’s attention.

AlphaBIOS Console 3-19

3.4 Defining the System Partition

Before you install Windows NT, a system partition must be defined. On an Alpha system, a system partition is set by AlphaBIOS when you install Windows NT for the first time.

If you are installing Windows NT for the first time, AlphaBIOS determines that a system partition has not been defined when you select Install Windows NT in the AlphaBIOS Setup screen (see Figure 3–12).

Figure 3–12 System Partition Not Defined

AlphaBIOS Setup

Display System Configuration

Upgrade AlphaBIOS

Hard Disk Setup...

CMOS Se

Network

Install

No System Partition

You must designate a FAT disk partition as a System

Utiliti

About A

Partition. Windows NT will use the System Partition to store system specific startup files.

Please select a partition as the System Partition.

System Partition: Disk 0, Partition 1

ENTER=Continue E Disk 0, Partition 1

Disk 0, Partition 2

Disk 1, Partition 1

Disk 1, Partition 2

PK0925

3-20 Compaq AlphaServer ES40 User Interface Guide

3.4.1 Purpose of the System Partition

The system partition has two purposes: First, it tells the Windows NT installation program where to place the OS Loader and hardware support files. Second, on subsequent restarts of Windows NT, the system partition definition tells AlphaBIOS where the OSLOADER.EXE

file is so that it can successfully hand off control to the OS Loader and continue the boot process.

The system partition can be the same disk partition into which Windows NT is installed, or it can be a different partition on that disk. Usually, but not necessarily, Windows NT is installed into an NTFS partition. However, it is a requirement that the system partition be a FAT partition and that it be on the same disk with the partition containing Windows NT. The size of the system partition can be as small as 6 MB.

AlphaBIOS Console 3-21

3.4.2 How AlphaBIOS Works with System Partitions

If you have previously installed Windows NT on your system, a system partition will have already been defined and Windows NT will know where to place the OS loader and hardware support files. However, if you are installing Windows NT for the first time, AlphaBIOS will determine that a system partition has not been defined when you select

Install Windows NT in the AlphaBIOS Setup screen.

AlphaBIOS searches for all FAT partitions on the system. If only one FAT partition exists, AlphaBIOS designates that FAT partition as the system partition and continues with the Windows NT installation. If more than one

FAT partition exists on your system, AlphaBIOS displays the list of FAT partitions from which you can choose the system partition (see Figure 3–12).

After you choose the system partition, the installation process continues.

3-22 Compaq AlphaServer ES40 User Interface Guide

3.4.3 Partition Arrangement on First Hard Disk

The recommended hard disk partition arrangement on the first hard disk in your system is 6 megabytes less than the total size of the drive on partition 1 and the remaining 6 megabytes on partition 2.

Partition 1 holds the operating system and application/data files. It is recommended that Partition 1 be drive C, which therefore becomes the larger drive. An express hard disk setup (Section 3.5.1) automatically creates the first partition as drive C, thereby ensuring that the default drive has sufficient space for installing additional applications.

Partition 2 holds only the boot files. It is recommended that Partition 2 be drive

D, which therefore becomes the smaller partition. An express hard disk setup automatically creates the second partition as drive D. Although Windows NT requires that a boot partition be formatted with the FAT file system, the

Windows NT file system (NTFS) provides advantages over FAT, such as additional security and more efficient use of disk space. By keeping the FAT boot partition small, the maximum amount of space is left available for use as an NTFS partition.

AlphaBIOS Console 3-23

3.5 Setting Up the Hard Disk

You can perform either an express or a custom hard disk setup. An express setup creates the recommended partition arrangement on the first hard disk, disk 0. Express hard disk setup is described in Section

3.5.1. Custom hard disk setup is described in Section 3.5.2.

Figure 3–13 Hard Disk Setup Screen

Hard Disk Setup

1 2

Disk 0 NCRC8xx #0, SCSI ID 0 4091 MB

Partition 1 4085 MB FAT

Disk 1 NCRC8XX #0, SCSI ID 1 4091 MB

Partition 1 4091 MB NTFS

Disk 2 NCRC8XX #0, SCSI ID 2 4091 MB

Partition 1 4091 MB NTFS

INSERT =New DEL=Delete F6 =Format F7 =Express ESC=Exit

PK0940

➊

Physical disk ID — Based on the SCSI ID. The disk with the lowest SCSI

ID is disk 0, the disk with the next lowest SCSI ID is disk 1, and so on.

➋

Controller — Brand and model of SCSI chip used on the SCSI controller.

➌

Controller number — Based on how many SCSI controllers of a particular type are installed in the system. The first controller of a type is always numbered 0.

➍

SCSI ID number — A unique number you assign to each SCSI device in the system. This is usually done with jumpers or a thumb wheel attached to the drive housing.

3-24 Compaq AlphaServer ES40 User Interface Guide

➎

Size — The raw capacity of the drive. Formatting the drive with different file systems (for example, FAT and NTFS) may result in different usable sizes because of the differences in how storage is managed under those file systems.

➏

Partition number — Within a single drive, partition numbers are assigned in sequential order: 1, 2, 3, and so on. The partitions populate the drive from the innermost cylinders to the outermost. If you have a large hard disk (over 800 MB) and plan to use the FAT file system, it is a good idea to break the disk into several smaller partitions because the FAT file system uses disk space more efficiently at smaller partition sizes. This is not a concern for the NTFS file system, since it uses disk space very efficiently at all partition sizes.

➐

Partition size — The raw (unformatted) storage capacity of the partition.

Storage space will differ based on the file system with which the partition is formatted.

➑

Partition format — The file system (if any) used on a partition. This field displays FAT, NTFS, or unknown (if the partition is unformatted).

➒

Disk setup options

Insert partition (Insert key) — Use this option to create new partitions.

Before creating a new partition, be sure to select an unpartitioned space.

Pressing the Insert key while an already partitioned space is selected causes an informational error to be displayed.

Delete partition (Delete key) — Use this option to delete existing partitions. Before deleting a partition, be sure any data you want to save on the partition has been backed up. Deleting a partition deletes all data on that partition but leaves the rest of the disk unaffected. Pressing the

Delete key while an unpartitioned space is selected displays an informational error.

Format partition (F6 key) — Format a partitioned space with the FAT file system.

Express setup (F7 key) — Create the default recommended partition arrangement for Windows NT on disk 0.

Exit (Escape key) — Return to the AlphaBIOS Setup screen.

AlphaBIOS Console 3-25

3.5.1 Express Hard Disk Setup

An express hard disk setup creates the recommended partition arrangement on the first hard disk (disk 0). It does not, however, format the large partition with NTFS. You can do the NTFS formatting during Windows NT installation.

NOTE: Because Windows NT 4.0 does not allow installation to partitions

greater that 4095 MB, express hard disk setup creates a maximum primary partition size of 4095 MB even if more space is available. The primary partition is the partition onto which the Windows NT files are copied during installation.

The hard disk with the lowest SCSI ID number is seen as disk 0 by

AlphaBIOS.

CAUTION: If you have any needed information on your disk, be sure to back

up your disk before using express setup.

Changes to the hard disk configuration are immediate; the changes are made as soon as they are entered. Unintended data loss could occur, so use care when changing your hard disk arrangement.

3-26 Compaq AlphaServer ES40 User Interface Guide

To perform an express hard disk setup

Back up any needed information from your disk.

Start AlphaBIOS Setup, select Hard Disk Setup, and press Enter.

Press F7 to enter Express Setup.

Press F10 to continue with the setup.

AlphaBIOS Console 3-27

3.5.2 Custom Hard Disk Setup

Use the Create Partition and Delete Partition options to create a custom hard disk partition arrangement or otherwise manually manage your hard disk partitions.

Figure 3–14 Create New Partition Dialog Box

Hard Disk Setup

Disk 0 NCRC8xx #0, SCSI ID 0 4091 MB

Partition 1 200 MB

Unused 3891 MB

Create new partition, Disk 0 Partition 2

Disk 1 NCRC810 #0, SCSI ID 5 1001 MB

Partition 1 995 MB

Partition 2 6 MB

Available space: 4091 MB

ENTER=Continue ESC=Cancel

PK0945

CAUTION: Changes to the hard disk configuration are immediate; the changes

are made as soon as they are entered. Unintended data loss could occur, so use care when changing your hard disk arrangement.

3-28 Compaq AlphaServer ES40 User Interface Guide

To create a partition

Start AlphaBIOS Setup and select Hard Disk Setup. Press Enter.

Select the disk on which to create the partition.

If one or more partitions already exist on the disk, select the unpartitioned space.

Press Insert. A dialog box is displayed, similar to Figure 3–14.

Type the size of the partition to create and press Enter.

To delete a partition

Start AlphaBIOS and select Hard Disk Setup. Press Enter.

Select the partition to be deleted (see

➊

in Figure 3–15).

Press Delete. A dialog box is displayed (see

➋

Press F10 to confirm the deletion.

Figure 3–15 Delete Partition Dialog Box

Hard Disk Setup

Disk 0 NCRC8xx #0, SCSI ID 0 4091 MB

Partition 1 4085 MB NTFS

Partition 2 6 MB FAT

Disk 1 NCRC8xx #0, SCSI ID 5 4091 MB

Delete Disk 1, Partition 1

The delete operation will destroy all data on partition 1 of disk 1.

Press F10 to continue. Press ESC to cancel.

F10=Continue ESC=Cancel

PK0946

AlphaBIOS Console 3-29

3.5.3 Formatting a FAT Partition

AlphaBIOS can format partitions with the FAT file system. Use

Windows NT to format a partition using NTFS.

Figure 3–16 Format Disk Dialog Box

Hard Disk Setup F1=Help

Disk 0 NCR8Cxx #0, SCSI ID 0 4091 MB

Partition 1 200 MB FAT

Disk 1 NCRC810 #0, SCSI ID 5 1001 MB

Partition 1 995 MB NTFS

Format Method: Standard Format

Standard Format

Quick Format

ENTER=Continue ESC=Cancel

PK0947

3-30 Compaq AlphaServer ES40 User Interface Guide

To format a FAT partition

Start AlphaBIOS Setup and select Hard Disk Setup. Press Enter.

Select the partition to be formatted (see

➊

in Figure 3–16).

Press F6. A dialog box is displayed, asking whether to perform a quick or standard format (see

➋

). If you select Quick Format, the formatting is completed immediately, but no bad sectors are mapped. If you select

Standard Format, a dialog box similar to that in Figure 3–17 is displayed while the drive is formatted, showing the progress of the formatting.

Standard formatting maps bad sectors.

Select a format method and press Enter.

Figure 3–17 Standard Formatting

Hard Disk Setup F1=Help

Disk 0 NCRC8xx #0, SCSI ID 0 4091 MB

Partition 1 4085 MB FAT

Partition 2 6 MB Unrecognized

Disk 1 NCRC8xx #0, SCSI ID 5 4091 MB

Partition 1 4085 MB NTFS

Partition 2 6 MB FAT

Disk 0, Partition 2 6 MB

Formatting...

25%

ESC=Cancel

PK0948

AlphaBIOS Console 3-31

3.6 Configuring System Parameters

CMOS Setup is used to configure several system parameters. CMOS

Setup has two modes: Standard CMOS Setup is used to configure basic system parameters; Advanced CMOS Setup is used for system-specific parameters and password protection.

Table 3–1 lists the tasks that can be performed in the two CMOS Setup modes.

Table 3–1 CMOS Setup Modes

Standard CMOS Setup

Enable/disable Auto Start

Set date and time

Configure floppies

Configure keyboard

Advanced CMOS Setup

Set length of memory test

Enable/disable PCI parity

Enable/disable password protection

Enable/disable SCSI BIOS

3-32 Compaq AlphaServer ES40 User Interface Guide

To enter standard CMOS setup:

Start AlphaBIOS Setup, select CMOS Setup, and press Enter.

To enter advanced CMOS setup

Start AlphaBIOS Setup, select CMOS Setup, and press Enter.

In the CMOS Setup screen, press F6.

AlphaBIOS Console 3-33

3.6.1 Standard CMOS Setup

Figure 3–18 Standard CMOS Setup Screen

CMOS Setup F1=Help

Time: 13:22:27

Floppy Drive A: 3.5" 1.44 MB

Floppy Drive B: None

Keyboard: U.S. 101-key keyboard

Auto Start: Enabled

Auto Start Count: 30 Seconds

Press or to modify date fields. Date modifications will take effect immediately.

F3=Color F6=Advanced F7=Defaults ESC=Discard Changes F10=Save Changes

PK0926

➊

Date and time — When setting the time, use the 24-hour format. For example, 10:00 p.m. is 22:00:00.

➋

Floppy drive — The ES40 system supports a 3.5 inch, 1.44 MB drive.

3-34 Compaq AlphaServer ES40 User Interface Guide

➌

Keyboard — The keyboard setting makes it possible to use most language keyboards. To ensure correct character mappings, the language of your keyboard, Windows NT, and the keyboard language selection in CMOS

Setup should all match.

➍

Auto start and auto start count — The Auto Start setting determines whether the primary operating system is automatically started after the system is reset or power-cycled. The Auto Start Count setting is the amount of time the Boot screen is displayed before the default system is automatically started. This delay gives you the opportunity, after resetting or power-cycling the system, to select another version of Windows NT to start or to enter AlphaBIOS Setup.

➎

Standard CMOS Setup options

Color (F3 key) — Repeatedly cycles through the available AlphaBIOS color schemes.

Advanced (F6 key) — Displays the Advanced CMOS Setup screen.

Defaults (F7 key) — Restores the default Standard CMOS Setup values without affecting the Advanced CMOS Setup values.

Discard changes (Escape key) — Restores the settings in effect when you started CMOS Setup. This option also discards changes made in Advanced

CMOS Setup.

Save changes (F10) — Saves changes made in both the standard and advanced modes of CMOS Setup.

AlphaBIOS Console 3-35

3.6.2 Advanced CMOS Setup

Figure 3–19 Advanced CMOS Setup Screen

Advanced CMOS Setup F1=Help

PCI Parity Checking: Disabled

Power-up Memory Test: Partial

AlphaBIOS Password Option: Disabled

SCSI BIOS Emulation: Enabled For All

Console Selection: Windows NT Console (AlphaBIOS)

Press or to enable or disable detection of PCI bus parity errors. Some non-compliant PCI option boards do not work properly with PCI parity checking enabled.

ESC=Discard Changes F10=Save Changes

PK0903

➊

PCI parity checking — Enables and disables settings for PCI parity checking, which ensures data integrity across the PCI bus. Because some third-party PCI options do not correctly implement PCI parity generation, the default is Disabled.

➋

Power-up memory test — Enables and disables settings for the power-up memory test. When enabled, the power-up memory test verifies the integrity of main system memory. The three memory test settings are:

Disabled

Partial

Full

No memory test performed by AlphaBIOS

Tests up to first 256 MB

Tests all of the memory.

3-36 Compaq AlphaServer ES40 User Interface Guide

➌

Password setup — Enables and disables settings for password setup.

Password protection provides two levels of security for your system: setup, which requires a password to start AlphaBIOS Setup, and startup, which requires a password before the system initializes. Startup protection provides more comprehensive protection than setup protection because the system cannot be used at all until the correct password is entered.

➍

SCSI BIOS Emulation — You can use any SCSI controller with your Alpha system if the controller has its own onboard BIOS. When you enable this option, the SCSI controller’s BIOS is initialized with its default settings at boot time. If the controller has a BIOS-based setup utility, you are prompted to press a key combination to run the utility. The utility allows you to change the adapter's default settings. The key combination varies with the manufacturer.

This option is generally left enabled, but if you do not have a SCSI BIOS– based adapter installed in your system, you can disable this feature to speed up boot time.

➎

Console selection — Switches from AlphaBIOS to SRM firmware. If you select OpenVMS (SRM) or UNIX (SRM), the next time you reset your system, the SRM firmware will be loaded instead of AlphaBIOS. This menu selection changes the setting of the os_type environment variable in the SRM console.

➏

Advanced CMOS Setup options

Discard changes (Escape key) —Restores those settings in effect when you started Advanced CMOS Setup. This does not discard changes made to

Standard CMOS Setup.

Save Changes (F10 key) — Saves changes made in Advanced CMOS Setup.

When exiting CMOS Setup, you must also save your changes at the

Standard CMOS Setup screen for the changes to be stored permanently.

AlphaBIOS Console 3-37

3.7 Setting Up a Windows NT Network

You can install versions of Windows NT or upgrade AlphaBIOS over the network. An AlphaBIOS server and AlphaBIOS client must be set up before you can use the network feature.

The Network Setup screen (Figure 3–20) displays the configuration of a selected network. Each installed DC21x4 network adapter corresponds to a network.

You can change settings and save them for each network shown. Some changes are effective immediately; others require a reboot to take effect.

Figure 3–20 Network Setup Screen

Network 0

Select Network:

Network 1

Network Setup F1=Help

Local IP: 16 .64 .48 .76 TFTP Server IP: 10 .0 .0 .1

Gateway IP: 16 .64 .48 .1 Subnet Mask: 255.255.255.0

TFTP Directory:

Press or to select a network. Properties of the selected network will appear immediately.

ESC=Discard Changes F10=Save Changes

PK0923

3-38 Compaq AlphaServer ES40 User Interface Guide

Select network—Each network adapter in your system is assigned a number, starting at zero. Settings of multiple adapters are stored separately.

Network—Network enable/disable toggle. If a network was not initialized at startup, reboot to initialize and enable it. If a network was initialized at startup, you can disable and re-enable it without a reboot.

IP Address Source—Permits you to choose a source for an IP address. There are three possible sources: DHCP (Domain Host Configuration Protocol),

BOOTP, and STATIC. STATIC requires you to enter all the needed information on the network screen. If you make a change to BOOTP or

DHCP and save it, a request message is issued immediately to the BOOTP and DHCP servers.

Status—Displays the network initialization status, including the status of adapter initialization and the call to the BOOTP or DHCP server. The possible messages are:

Adapter initialized—BOOTP/DHCP succeeded

Adapter initialized—BOOTP failed

Adapter initialized—DHCP failed

Adapter initialized—Using local settings

Adapter is not initialized (Network bypassed or disabled)

Adapter initialization failed

Adapter—The network adapter model.

Ethernet Address—The physical address of the network card connecting the system to the currently selected network.

Lease Time—Length of current lease. The time for which the DHCP server has leased the IP address to the AlphaBIOS client. N/A if the IP address source is BOOTP or STATIC or if a call to a DHCP server failed.

Lease Starts—Date and time when the lease was granted. N/A if the IP address source is BOOTP or STATIC or if a call to a DHCP server failed.

Local IP—IP address of the system that is displaying the Network Setup screen.

Continued on next page

AlphaBIOS Console 3-39

TFTP Server IP—TCP/IP address of your TFTP server. If the TFTP server is on a different subnet from the client, a subnet mask and a router IP address must be provided.

Gateway IP—IP address of the router connecting the two subnets. This field is used when your system resides in a subnet different from the

DHCP server.

NOTE: Your router must have BOOTP/DHCP relay support to enable a

router to forward DHCP packets from one subnet to another.

Subnet Mask—Subnet assigned to your network segment by the network administrator. If the TFTP server is on a different subnet from the client, a subnet mask and a router IP address must be provided, either by the user or by a BOOTP or DHCP server.

TFTP Directory—Many TFTP software installation routines require that you specify a fully qualified path, including initial and final backslashes, to the TFTP program files and the files to be transferred. These fields can be left blank if you installed your TFTP server software into a directory that is included in your Windows NT User path.

For a DHCP client that uses the MS-DHCP server, since the SP1 DHCP server does not provide a TFTP directory (in Boot file name field), you must enter it manually and save it for the current run.

3-40 Compaq AlphaServer ES40 User Interface Guide

3.7.1 Saving AlphaBIOS Network Settings

IP addresses assigned using DHCP are not saved in the client’s nonvolatile memory.

•

To use IP addresses saved in the client’s nonvolatile memory, select

STATIC in the IP address source field, enter the TFTP Server IP address manually, and press F10. This procedure works for the current run.

•

To save the TFTP server IP address in nonvolatile memory for the next run, select STATIC in the IP address source field, press F10, enter the TFTP server IP address, press F10, and select DHCP in the IP Address Source field.

When BOOTP is used as the IP address source, a successful call overwrites all

IP addresses saved in nonvolatile memory for as long as the TFTP server is responding.

AlphaBIOS Console 3-41

3.8 Installing Windows NT

Install Windows NT from CD-ROM. Up to three versions of the operating system can be installed in the system.

Figure 3–21 Installing Windows NT

AlphaBIOS Setup

Display System Configuration...

AlphaBIOS Upgrade...

Hard Disk Setup...

CMOS Setup...

Network Setup...

Install Windows NT

Utilities

About AlphaBIOS...

Press ENTER to install or upgrade Windows NT from CD-ROM.

ESC=Exit

PK0922

3-42 Compaq AlphaServer ES40 User Interface Guide

Windows NT Boot Process

AlphaBIOS boots Windows NT in two stages. During the first stage the system reads the OS Loader program, OSLOADER.EXE, from a disk. The OS Loader program must be located on a partition formatted with the FAT file system. An express hard disk setup (step 2 in the procedure that follows) creates the recommended partition arrangement on the first hard disk. See Section 3.5 for details on formatting partitions.

Once the OS Loader program executes, it uses the services provided by

AlphaBIOS to load the operating system components. After the operating system is loaded, the OS Loader starts execution of the operating system.

Installing Windows NT from CD-ROM

If Windows NT was installed at the factory, Windows NT setup will start automatically the first time the system powers up. If it was not installed, or if you are installing another version, install it from the CD-ROM drive attached to your system.

NOTE: Steps 1 and 2 in the following procedure are necessary only when you

are first setting up your system. On subsequent installations and upgrades, begin at step 3.

Use CMOS Setup to set the system date and time: start AlphaBIOS Setup, select CMOS Setup, and press Enter.

Perform an express hard disk setup: return to the main AlphaBIOS Setup screen, select Hard Disk Setup, and press Enter.

Put the Windows NT CD into the CD-ROM drive.

Start AlphaBIOS Setup, select Install Windows NT, and press Enter.

Follow the prompts to complete the installation. For more information on installing Windows NT, refer to the Installation Guide in your Windows NT software package.

AlphaBIOS Console 3-43

3.9 Running Utility Programs

AlphaBIOS offers several utility programs that you can access from the

Utilities menu in AlphaBIOS Setup.

Figure 3–22 Utilities Menu

AlphaBIOS Setup F1=Help

Display System Configuration...

Upgrade AlphaBIOS

Hard Disk Setup...

CMOS Setup...

Install Windows NT

Utilities

About AlphaBIOS...

Display Error Frames...

OS Selection Setup...

Run Maintenance Program...

Press ENTER to display Hardware Error Report frames.

ESC=Exit

PK0954

3-44 Compaq AlphaServer ES40 User Interface Guide

The Utilities menu lets you display error frames, set up your operating system selections, and run maintenance programs.

•

Section 3.9.1 briefly describes the AlphaBIOS Display Error Frame function.

•

To run a maintenance program, such as the RAID configuration utility, see

Section 3.9.2.

•

To set up operating system selections, see Section 3.10.2.

AlphaBIOS Console 3-45

3.9.1 Displaying Error Frames

The Display Error Frames selection of the Utilities menu allows you to view hardware error reports. These reports are generated if a fatal error or double error halt occurs.

Figure 3–23 New Error Frame Was Detected Window

AlphaBIOS 5.68

Alpha Processor and System Information:

New Error Frame was detected

AlphaBIOS has detected a new hardware error report in the error frame sector of the flash ROM in this system. If the Alpha hardware error logging service is installed, then you will be able to see this report in the system event log after the system is booted.

0568

1.2d

This report frame can also be examined from AlphaBIOS:

Press F2 to enter the main AlphaBIOS Setup screen, then select Utilities, and then select Display Error Frames.

This window will be closed in 25 sec.

SPACE =Confirm ESC=Stop Count Down

AlphaServer

PK0955

3-46 Compaq AlphaServer ES40 User Interface Guide

When a fatal error or double error halt occurs, AlphaBIOS can display an error frame. The next time you boot the system after a fatal error or double error halt, AlphaBIOS displays a warning message just after initialization has been completed and just before the Boot menu is displayed. An example is shown in

Figure 3–23. The warning message is closed after 30 seconds. To keep the warning message window open, press the ESC key while the window is displayed.

To display the error frame, enter AlphaBIOS Setup and select the Utilities menu.

From the Utilities menu, select Display Error Frames….

The AlphaBIOS error frame feature is intended for use by service providers.

See the Compaq AlphaServer ES40 Service Guide for more information.

AlphaBIOS Console 3-47

3.9.2 Running a Maintenance Program

Maintenance programs are run from the Utilities menu. Enter the name of the program to be run. Enter the location if you do not specify the path with the program name. Figure 3–24 shows the program name entry for the RAID configuration utility.

Figure 3–24 Run Maintenance Program Dialog Box

AlphaBIOS Setup

Display System Configuration...

Upgrade AlphaBIOS

Hard Disk Setup...

CMOS S

Networ

Instal

Utilit

About

1 1

Run Maintenance Program

Program Name: ra200rcu.exe

ENTER=Execute

CD:

Disk 0, Partition 1

Disk 0, Partition 2

Disk 1, Partition 1

PK0927

3-48 Compaq AlphaServer ES40 User Interface Guide

Maintenance programs can be run from either a VGA monitor or a serial terminal. If you have a serial terminal, See Chapter 2 of the Compaq

AlphaServer ES40 Owner’s Guide for directions.

If your system has a RAID controller installed, and you change your system configuration (for example, by adding another RAID drive), you will have to run a RAID configuration utility. As you modify your system, you might be required to run other types of maintenance programs as well.

➊

Program name — The program to be run. It must be an executable program with an .EXE filename extension. However, when entering the program name, it is not necessary to type the extension. The executable program for the RAID configuration utility is RA200RCU.EXE.

Programs run from AlphaBIOS must be written as ARC compatible images.

➋

Location — The location from which the program in the Program Name field will be run if no path is entered along with the program name. To display a list of all available disks and partitions, press the Alt and down arrow keys at the same time. Once the list is displayed, use the arrow keys to cycle through the selections.

AlphaBIOS Console 3-49

3.10 Selecting the Version of Windows NT

Up to three versions of Windows NT can reside on the system at one time. It is necessary to select the version that will be started.

Figure 3–25 Operating System Selections

Operating System Selection Setup

Windows NT Server 4.0

Primary Operating System

Boot Name: Windows NT Server 4.0

Boot File: Disk 0, Partition 2 \os\winnt40\osloader.exe

OS Path: Disk 0, Partition 1 \WINNT40

OS Options:

INSERT=New F6=Edit F8=Primary ESC=Discard Changes

DEL=Delete F7=Copy F9=Validate F10=Save Changes

PK0941a

NOTE: The “operating system selection” refers to selecting a version of Windows

NT.

3-50 Compaq AlphaServer ES40 User Interface Guide

Each operating system selection is a set of information for a version of

Windows NT. It describes the disk and partition containing the OS Loader file,

OSLOADER.EXE, associated with a particular operating system installation, as well as the path to the operating system itself. In addition, the operating system selection contains any options passed to the operating system during boot.

By default, one operating system selection is displayed on the AlphaBIOS Boot screen for each operating system installed on the system. It is not normally necessary to modify operating system selections, because the Windows NT installation creates and modifies operating system selections as needed.

Figure 3–25 shows how operating system selections appear.

AlphaBIOS Console 3-51

3.10.1 Designating a Primary Operating System

Each time you install a separate version of Windows NT, a new operating system selection is created.

Figure 3–26 Primary Operating System

AlphaBIOS Version 5.xx

Please select the operating system to start:

Windows NT Server 5.00

Windows NT Server 4.00

Use and to move the highlight to your choice.

Press Enter to choose.

CMOS Setup

Date: Friday, Mar 5 1999

Time: 11:26:22

Floppy Drive A: 3.5" 1.44 MB

Floppy Drive B: None

Keyboard: U.S. 101-key keyboard

Auto Start: Enabled

Auto Start Count: 30 Seconds

Operating System Selection Setup

Windows NT Server 5.00

Windows NT Server 4.00

Primary Operating System

PK0904

3-52 Compaq AlphaServer ES40 User Interface Guide

Three versions of Windows NT can reside on the system at the same time. This can be useful for testing the compatibility of applications across different versions of Windows NT.

Although you can start any of the installed versions of Windows NT, one of them must be the primary operating system. The version of Windows NT you select as the primary operating system starts automatically if the Auto Start option is enabled in AlphaBIOS.

Figure 3–26 illustrates the relationship between multiple installations of the operating system, Auto Start, and the primary operating system.

➊

The primary operating system is listed first on the Boot screen.

➋

The primary operating system starts automatically if the Auto Start option is enabled in CMOS Setup.

➌

The primary operating system can be selected in the Operating System

Selection Setup screen.

To designate a new primary operating system

From the AlphaBIOS Setup screen, select Utilities. In the selection box that is displayed, choose OS Selection Setup.

The Operating System Selection Setup screen is displayed. Select the primary operating system from the list.

AlphaBIOS Console 3-53

3.10.2 Setting Up Operating System Selections

The process of setting up your operating system selections is similar to using an editor. You can make changes to your operating system selections and then either save your changes or exit without saving.

Figure 3–27 Operating System Selection Setup

Operating System Selection Setup

Windows NT Server 4.0

Primary Operating System

Boot Name: Windows NT Server 4.0

Boot File: Disk 0, Partition 2 \os\winnt40\osloader.exe

OS Path: Disk 0, Partition 1 \WINNT40

OS Options:

INSERT=New F6=Edit F8=Primary ESC=Discard Changes

DEL=Delete F7=Copy F9=Validate F10=Save Changes

PK0941

AlphaBIOS boots Windows NT in two stages. During the first stage the system reads the OS Loader program, OSLOADER.EXE, from a disk. The selection for the operating system describes the path where AlphaBIOS will find the OS

Loader program. The OS Loader program must be located on a partition formatted with the FAT file system. See Section 3.5 for information on formatting partitions.

Once the OS Loader program executes, it uses the services provided by

AlphaBIOS to load the operating system components. After the operating system is loaded, the OS Loader starts execution of the operating system.

3-54 Compaq AlphaServer ES40 User Interface Guide

➊

Primary operating system — The OS that appears first on the AlphaBIOS

Boot screen. It is also the version of the OS that starts automatically if

Auto Start is enabled. Any of the operating system selections can be the primary operating system.

➋

Boot name — Each boot name is associated with an operating system selection. Windows NT setup automatically creates a boot name each time you install the operating system. You can modify the boot name at any time without affecting the rest of the operating system selection. The boot name must have at least one character.

➌

Boot file — Describes the disk, partition, path, and name of the file that

AlphaBIOS passes control to during the process of starting the operating system. This setting is created along with the operating system selection during Windows NT setup, and it is usually not modified by the user.

However, this setting can be modified if necessary. For example, a developer testing different versions of OSLOADER.EXE can store the different versions in different locations and modify this line to start the operating system with the different versions as needed.

During Operating System Selection Setup, you can select the disk and partition for the location of the boot file from a list of choices presented in a list box. To open a list of values for the field, press the Alt and down arrow keys together. When you select a boot file location and name, AlphaBIOS searches for the specified program on the specified partition. If the search fails, a warning is displayed, saying that the file does not exist. You can continue with the changes or cancel the operation and fix the problem.

Because the boot file must be located in a FAT partition, only FAT partitions are available as the boot partition within the list box.

➍

OS path — Describes the disk, partition, and path to the operating system root directory for an operating system selection.

During Operating System Selection Setup, you can select the disk and partition for the location of the boot file from a list of choices presented in a list box. To open a list of possible values for the field, press the Alt and down arrow keys at the same time. When you select or enter an OS path,

AlphaBIOS searches for the directory. If the search fails, a warning is displayed, saying that the directory does not exist. You can continue with the changes or cancel the operation and fix the problem.

Continued on next page

AlphaBIOS Console 3-55

➎

OS options — Lists the startup parameters passed to the operating system for an operating system selection. One example of a startup parameter is whether to start the operating system in debug mode. By default, Windows

NT does not add any entries to this field. This field can be modified.

➏

Operating System Selection Setup options — You can use the options listed at the bottom of the screen to edit operating system selections. When you edit an OS selection, the fields of the OS selection are validated when you exit the OS Selection Setup screen. Depending on the option you choose, one of the following dialog boxes will display.

New OS selection (Insert key) — Displays the Insert New Operating

System Selection dialog box, with default values for the new OS selection already filled in. You can change these values as necessary.

Delete OS selection (Delete key) — Tags the currently selected OS selection for deletion. Although the OS selection is removed from the screen, it is not deleted until you save changes.

You can also delete all of your OS selections at once by pressing the

Control and Delete keys at the same time while in the Operating System

Selection Setup screen.

NOTE: If you delete all the OS selections, a dialog box is displayed

informing you that no OS selections exist and offering three options. You can create a new OS selection, exit without saving changes, or exit and save changes

Edit OS selection (F6 key) — Edit all values of an OS selection by selecting the OS selection to edit and pressing F6. A dialog box displays with current information. You can then edit the OS selection fields.

Copy OS selection (F7 key) — Create a new OS selection by using an existing OS selection as a template. To do so, select the OS selection you want to copy and press F7. A dialog box displays with the values of your

OS selection. You can then edit the OS selection fields. If you do not make any changes, a duplicate copy of the OS selection you copied is made.

Primary operating system (F8 key) — Sets the selected OS selection as the primary operating system. When you make an OS selection primary, it is displayed first on the Operating System Selection Setup screen with the text “Primary Operating System.” In addition, the primary operating system is displayed first on the AlphaBIOS Boot screen and is automatically started if Auto Start is enabled.

3-56 Compaq AlphaServer ES40 User Interface Guide

Validate OS selection (F9 key) — Validates the fields in the currently selected OS selection. The validation routine checks that the OS loader file and OS directory fields contain valid paths and that the OSLOADER.EXE

file exists in the directory specified. At the end of the validation, a dialog box is displayed describing the results of the validation. An error in an OS selection causes the validation routine to display a dialog box describing the component of the OS selection that is in error. You can choose to edit the OS selection to correct the error or delete the OS selection altogether.

You can also validate all OS selections at once by pressing the Control and

F9 keys at the same time. All OS selections are validated in the order they are listed on screen.

Discard changes (Escape key) — Returns to the AlphaBIOS Setup screen without saving changes.

Save changes (F10 key) — Saves changes and returns to the AlphaBIOS

Setup screen.

Operating System Selection Setup Errors

•

No hard drives were found connected to your computer

This message means that AlphaBIOS could not locate a hard drive. Setup cannot proceed. For possible causes and remedies, see Section 3.4.

•

Internal error occurred

This message means that a disk was found, but an error was detected in communicating with the disk. Setup cannot proceed. For possible causes and remedies, see Section 3.4.

•

No Partitions on Disk

If hard disk 0 does not have any partitions defined, when you start OS Selection

Setup, you are prompted whether to perform an express disk setup. Express disk setup automatically creates the default disk partition arrangement on hard disk 0.

AlphaBIOS Console 3-57

3.11 Changing to the SRM Console

Under some circumstances, you might need to use SRM commands. To invoke the SRM console, press the Halt button on the control panel and reset the system; or, select UNIX (SRM) or OpenVMS (SRM) from the

Advanced CMOS Setup screen and reset the system.

Figure 3–28 Invoking SRM from AlphaBIOS

Advanced CMOS Setup F1=Help

PCI Parity Checking: Disabled

Power-up Memory Test: Partial

AlphaBIOS Password Option: Disabled

Console Selection: Digital UNIX Console (SRM)

Windows NT Console (AlphaBIOS)

OpenVMS Console (SRM)

Digital UNIX Console (SRM)

Press or to select the firmware console that will be presented the next time the system is power-cycled.

ESC=Discard Changes F10=Save Changes

PK0924

3-58 Compaq AlphaServer ES40 User Interface Guide

Use one of the following methods to change from AlphaBIOS to SRM. The method you choose depends on which console you want to start on subsequent resets.

From Advanced CMOS Setup

When you invoke the SRM console from AlphaBIOS, the os_type environment variable is changed to UNIX or OpenVMS. The system will load the SRM console on each reset until you restore your original setup information by changing os_type to NT.

Select CMOS Setup and press Enter.

In the CMOS Setup screen press F6. The Advanced CMOS Setup screen is displayed.

Select UNIX (SRM) or OpenVMS (SRM) and press F10.

The CMOS Setup screen is displayed. Press F10 to save the change.

Reset the system.

When you have completed your SRM console session, you can restore your original setup. At the SRM prompt, set os_type to nt and then enter the

init command or press the Reset button. The AlphaBIOS console will then load on each subsequent reset.

From the Control Panel

You can force entry to SRM from Windows NT. Press the Halt button and then reset the system. This method does not change the setup information, and

AlphaBIOS will load and start the next time the system is powered up, reset, or initialized with the Halt button unlatched.

CAUTION: A forced halt interrupts the operating system. Applications that are

running may lose data.

Returning to AlphaBIOS

To return to the AlphaBIOS console, issue the alphabios command at the SRM console prompt.

Continued on next page

AlphaBIOS Console 3-59

The SRM commands listed below are used with Windows NT systems. See

Chapter 2 for more information.

test

Verifies all the devices in the system. There is no comparable AlphaBIOS selection for this function.

set os_type nt

Sets the operating system type to NT so that the

AlphaBIOS console is invoked at a power-up or reset.

set console

Sets the display device. Must be set to graphics if a VGA monitor is attached to the VGA port.

rmc

Invokes the remote management console from a VGA monitor connected to the system.

3-60 Compaq AlphaServer ES40 User Interface Guide

3.12 Upgrading Firmware

As new versions of Windows NT are released, it might be necessary to upgrade AlphaBIOS to the latest version. Additionally, as improvements are made to AlphaBIOS, it might be desirable to upgrade to take advantage of new AlphaBIOS features.

You can upgrade AlphaBIOS from the Alpha Systems Firmware Update CD-

ROM (issued quarterly) or over a Windows NT network. See Chapter 6 of the

Compaq AlphaServer ES40 Owner’s Guide.

AlphaBIOS Console 3-61

Chapter 4 RMC Commands

This chapter describes the command set for the remote management console

(RMC). The operation of the RMC is described in the Compaq AlphaServer

ES40 Owner’s Guide.

RMC Commands 4-1

4.1 RMC Commands List

From the remote management console command-line interface, you can issue commands to monitor the system (voltages, temperatures, and fans), and manipulate it (reset, power on/off, halt) remotely or locally.

clear {alert, port} deposit disable {alert, remote} dump enable {alert, remote} env halt {in, out} hangup

help or ?

power {on, off} quit reset send alert set {alert, com1_mode, dial, escape, init, logout, password, user} status

NOTE: The deposit and dump commands are reserved for service providers.

4-2 Compaq AlphaServer ES40 User Interface Guide

Command Conventions

Observe the following conventions for entering RMC commands:

•

Enter enough characters to distinguish the command.

NOTE: The reset and quit commands are exceptions. You must enter the

entire word for these commands to work.

•

For commands consisting of two words, enter the entire first word and at least one letter of the second word. For example, you can enter disable a for disable alert.

•

For commands that have parameters, you are prompted for the parameter.

•

Use the Backspace key to erase input.

•

If you enter a nonexistent command or a command that does not follow conventions, the following message is displayed:

*** ERROR - unknown command ***

•

If you enter a string that exceeds 14 characters, the following message is displayed:

*** ERROR - overflow ***

RMC Commands 4-3

4.2 clear alert

The clear alert command clears the current alert condition and causes the RMC to stop paging the remote system operator.

If the alert is not cleared, the RMC continues to page the remote operator every

30 minutes if the dial-out alert feature is enabled.

The clear alert command clears the current alert so that the RMC can capture a new alert. The last alert is stored until a new event overwrites it. The Alert

Pending field of the status command becomes NO after the alert is cleared.

RMC> clear alert

RMC>

4-4 Compaq AlphaServer ES40 User Interface Guide

4.3 clear port

The clear port command clears any “stuck” conditions on the system’s

COM1 port.

The clear port command attempts to free the port by resetting all UARTs controlled by the RMC if the port is currently locked by an application program, without resetting the entire system.

RMC> clear port

RMC>

NOTE: This command also causes the modem to disconnect.

RMC Commands 4-5

4.4 disable alert

The disable alert command disables the RMC from paging a remote system operator.

Monitoring continues and alerts are still logged in the Last Alert field of the

status command, but alerts are not sent to the remote operator.

RMC> disable alert

RMC>

4-6 Compaq AlphaServer ES40 User Interface Guide

4.5 disable remote

The disable remote command disables remote access to the RMC modem port and disables automatic dial-out.

RMC> disable remote

RMC>

RMC Commands 4-7

4.6 enable alert

The enable alert command enables the RMC to page a remote system operator.

Before you can enter the enable alert command, you must configure remote dial-in and call-out, set an RMC password, and enable remote access to the

RMC modem port. See the Compaq AlphaServer ES40 Owner’s Guide for the complete set-up procedure.

RMC> set dial

Dial String: ATXDT9,15085553333

RMC> set alert

Alert String: ,,,,,,5085553332#;

RMC> enable alert

RMC>

If the enable alert command fails, the following error message is displayed:

*** ERROR - enable failed ***

Issue the status command to see if the Remote Access field is set to Enabled.

4-8 Compaq AlphaServer ES40 User Interface Guide

4.7 enable remote

The enable remote command enables remote access to the RMC modem port by configuring the modem with the setting stored in the initialization string.

This command also allows the RMC to automatically dial the pager number set with the set dial command upon detection of alert conditions.

Before you can enter the enable remote command, you must configure remote dial-in by setting an RMC password and initialization string. See the Compaq

AlphaServer ES40 Owner’s Guide for the complete set-up procedure.

RMC> set password

RMC Password: ****

Verification: ****

RMC> set init

Init String: AT&F0E0V0X0S0=2

RMC> enable remote

If the enable remote command fails, the following error message is displayed:

*** ERROR - enable failed ***

Check that the modem is connected and that you have set the initialization string correctly.

RMC Commands 4-9

4.8 env

The env command displays the system environmental status, including power supplies, voltages, fans, and temperatures. If a fault has occurred, the reading blinks.

RMC>env

System Hardware Monitor

Temperature (warnings at 45.0°C, power-off at 50.0°C)

CPU0: 26.0°C CPU1: 26.0°C CPU2: 27.0°C CPU3: 26.0°C

Zone0: 29.0°C Zone1: 30.0°C Zone2: 31.0°C

Fan RPM

Fan1: 2295 Fan2: 2295 Fan3: 2205

Fan4: 2235 Fan5: OFF Fan6: 2518

Power Supply(OK, FAIL, OFF, '----' means not present)

PS0 : OK PS1 : OK PS2 : ----

CPU0: OK CPU1: OK CPU2: OK CPU3: OK

CPU CORE voltage

CPU0: +2.192V CPU1: +2.192V CPU2: +2.192V CPU3: +2.192V

CPU IO voltage

CPU0: +1.488V CPU1: +1.488V CPU2: +1.488V CPU3: +1.488V

Bulk voltage

+3.3V Bulk: +3.328V +5V Bulk: +5.076V +12V Bulk: +12.096V

Vterm: +1.824V Cterm: +2.000V -12V Bulk: -12.480V

➎

➏

➊

➋

➌

➍

4-10 Compaq AlphaServer ES40 User Interface Guide

➊

CPU temperature. In this example four CPUs are present.

➋ Temperature of PCI backplane: Zone 0 includes PCI slots 1–3, Zone 1 includes PCI slots 7–10, and Zone 2 includes PCI slots 4–6.

➌

Fan RPM. With the exception of Fan 5, all fans are powered as long as the system is powered on. Fan 5 is OFF unless Fan 6 fails.

➍

The normal power supply status is either OK (system is powered on) or

OFF (system is powered off or the power supply cord is not plugged in).

FAIL indicates a problem with a supply.

➎

CPU CORE voltage and CPU I/O voltage. In a good system, the core voltage for all CPUs should be the same, and the I/O voltage for all CPUs should be the same.

➏

Bulk power supply voltage.

RMC Commands 4-11

4.9 halt in

The halt in command is equivalent to pressing the Halt button on the control panel.

The halt in command halts the managed system. When the halt in command is issued, the terminal exits RMC and returns to the server’s COM1 port.

Toggling the Power button on the operator control panel overrides the halt in condition.

RMC> halt in

Returning to COM port

NOTE: The halt in command does not halt systems running Windows NT.

However, if you power up after the halt in command has been issued, the system stops in the SRM console. To load AlphaBIOS, issue the

halt out command before powering up.

4-12 Compaq AlphaServer ES40 User Interface Guide

4.10 halt out

The halt out command is equivalent to releasing the Halt button on the control panel.

The halt out command releases a halt. The terminal exits RMC and returns to the server’s COM1 port.

RMC> halt out

Returning to COM port

You cannot use halt out to release a halt if the Halt button on the operator control panel is latched in. If you issue the command, the following message is displayed:

RMC> halt out

Halt button is IN

RMC Commands 4-13

4.11 hangup

The hangup command terminates the modem session.

If you do not issue the hangup command, the session is disconnected automatically after a period of idle time set by the set logout command. The default is 20 minutes.

RMC> hangup

RMC>

4-14 Compaq AlphaServer ES40 User Interface Guide

4.12 help or ?

The help or ? command displays the RMC command set.

RMC> help clear {alert, port} deposit disable {alert, remote} dump enable {alert, remote} env halt {in, out} hangup help or ?

power {off, on} quit reset send alert set {alert, com1_mode, dial, escape, init, logout, password, user} status

RMC Commands 4-15

4.13 power off

The power off command is equivalent to turning off the system power from the operator control panel.

If the system is already powered off, this command has no effect. You can override the power off command either by issuing a power on command or by toggling the Power button on the operator control panel.

RMC> power off

RMC>

4-16 Compaq AlphaServer ES40 User Interface Guide

4.14 power on

The power on command is equivalent to turning on the system power from the operator control panel.

If the system is already powered on, this command has no effect. After the

power on command is issued, the terminal exits RMC and reconnects to the server’s COM1 port.

RMC> power on

Returning to COM port

The power on command does not turn on the system if the Power button on the operator control panel is in the OFF position. If you issue the command, the following message is displayed:

RMC> power on

Power button is OFF

RMC Commands 4-17

4.15 quit

The quit command exits RMC and returns the terminal to the server’s

COM1 port.

You must enter the entire word for the command to take effect.

RMC> quit

Returning to COM port

4-18 Compaq AlphaServer ES40 User Interface Guide

4.16 reset

The reset command is equivalent to pushing the Reset button on the operator control panel.

The reset command restarts the system. The terminal exits RMC and reconnects to the server’s COM1 port. You must enter the entire word for the command to take effect.

RMC>reset

Returning to COM port

RMC Commands 4-19

4.17 send alert

The send alert command forces an alert condition.

This command is used to test the setup of the dial-out alert function. It is issued from the local terminal.

As long as no one connects to the modem and there is no alert pending, the alert will be sent to the pager immediately.

If the pager does not receive the alert, re-check your setup.

RMC> send alert

Alert detected!

4-20 Compaq AlphaServer ES40 User Interface Guide

4.18 set alert

The set alert command sets the alert string that is transmitted through the modem when an alert condition is detected.

Set the alert string to the phone number of the modem connected to the remote system. The alert string is appended after the dial string, and the combined string is sent to the modem.

The alert string consists of the following elements:

,,,,,, Each comma (,) provides a 2-second delay. In this example, a delay of 12 seconds is set to allow the paging service to answer.

;

5085553332# A call-back number for the paging service. The alert string must be terminated by the pound (#) character.

A semicolon (;) must be used to terminate the entire string.

The example shown below is generic. Because paging services vary, be sure to listen to the options provided by the paging service to determine the appropriate delay and the menu options.

RMC> set alert

Alert String: ,,,,,,5085553332#;

RMC>

RMC Commands 4-21

4.19 set com1_mode

The set com1_mode command specifies the COM1 data flow paths, so that data either passes through the RMC or bypasses it.

You can enter the RMC from either the MMJ port or the modem port. Only one session can be active at a time.

For modem connection, you can set the com1_mode environment variable to allow data to partially or completely bypass the RMC. The bypass modes are snoop mode, soft bypass mode, and firm bypass mode. These modes disable the local channel from sending characters to the system COM1 port. If the

com1_mode value has been set to soft_bypass or firm_bypass, and the system is turned off, the mode reverts to snoop.

•

In snoop mode, you can type an escape sequence to enter the RMC. RMC mode provides a command-line interface for issuing commands to monitor and control the system.

•

In soft bypass mode, you cannot enter the RMC. But if an alert condition or loss of carrier occurs, the RMC switches into snoop mode. From snoop mode you can enter RMC.

•

In firm bypass mode you cannot enter the RMC. To enter, reset the

com1_mode environment variable from the SRM console, as described in

Chapter 2, then set up the RMC again from the local terminal.

RMC.

NOTE: You can always enter the RMC locally regardless of the current mode.

4-22 Compaq AlphaServer ES40 User Interface Guide

You can set com1_mode to one of the following values:

through snoop soft_bypass firm_bypass local

All data passes through RMC and is filtered for the escape sequence. This is the default.

Data partially bypasses RMC, but RMC taps into the data lines and listens passively for the escape sequence.

Data bypasses RMC, but RMC switches automatically into snoop mode if loss of carrier occurs.

Data bypasses RMC. RMC remote management features are disabled.

Changes the focus of the COM1 traffic to the local MMJ port if

RMC is currently in one of the bypass modes or is in through mode with an active remote session.

Example

RMC> set com1_mode

Com1_mode (THROUGH, SNOOP, SOFT_BYPASS, FIRM_BYPASS, LOCAL): local

RMC Commands 4-23

4.20 set dial

The set dial command sets the string to be used by the RMC to dial out when an alert condition occurs.

The dial string must be in the correct format for the attached modem. If a paging service is to be contacted, the string must include the appropriate modem commands to dial the number. The dial string is case sensitive. The

RMC automatically converts all alphabetic characters to uppercase.

The dial string consists of the following elements:

ATXDT

15085553333

AT = Attention.

X = Forces the modem to dial “blindly” (not seek the dial tone). Enter this character if the dial-out line modifies its dial tone when used for services such as voice mail.

D = Dial

T = Tone (for touch-tone)

The number for an outside line (in this example, 9). Enter the number for an outside line if your system requires it.

, = Pause for 2 seconds.

Phone number of the paging service.

RMC> set dial

Dial String: ATXDT9,15085553333

RMC>

4-24 Compaq AlphaServer ES40 User Interface Guide

4.21 set escape

The set escape command sets a new escape sequence for invoking RMC.

The escape sequence can be any character string, not to exceed 14 characters. A typical sequence consists of two or more control characters. It is recommended that control characters be used in preference to ASCII characters. Use the

status command to verify the escape sequence.

Be sure to record the new escape sequence. If you forget the escape sequence, you must reset the RMC to the factory defaults. See the Compaq AlphaServer

ES40 Owner’s Guide for information on setting the RMC to the factory defaults.

The following example consists of two instances of the Esc key and the letters

“FUN.” The “F” is not displayed when you set the sequence because it is preceded by the escape character. Enter the status command to see the new escape sequence.

RMC> set escape

Escape Sequence: un

RMC> status

Escape Sequence: ^[^[FUN

RMC Commands 4-25

4.22 set init

The set init command sets the modem initialization string.

The initialization string is limited to 31 characters and can be modified depending on the type of modem used. The following modems require the initialization strings shown here.

Modem

Motorola 3400 Lifestyle 28.8

AT &T Dataport 14.4/FAX

Hayes Smartmodem Optima 288

V-34/V.FC + FAX

Initialization String

AT&F0E0V0X0S0=2

AT&FE0V0X0S0=2

RMC> set init

Init String: AT&F0E0V0X0S0=2

RMC>

Because the modem commands disallow mixed cases, the RMC automatically converts all alphabetic characters entered in the init string to uppercase.

The RMC automatically configures the modem’s flow control according to the setting of the SRM com1_flow environment variable. The RMC also enables the modem carrier detect feature to monitor the modem connectivity.

4-26 Compaq AlphaServer ES40 User Interface Guide

4.23 set logout

The set logout command sets the amount of time before the RMC terminates an inactive modem

connection.

The default is 20 minutes.

The settings are in tens of minutes, 0–9. The zero (0) setting disables logout.

With logout disabled, the RMC never disconnects the idle modem session.

The following example sets the logout timer to 30 minutes.

RMC> set logout

Logout Time (0-9 tens of minutes): 3

RMC Commands 4-27

4.24 set password

The set password command allows you to set or change the password that is prompted for at the beginning of a modem session.

A password must be set to enable access through a modem. The string cannot exceed 14 characters. For security, the password is not echoed on the screen.

When prompted for verification, type the password again. If you mistype, reenter the set password command.

RMC> set pass

RMC Password: ****

Verification: ****

*** ERROR - Verification failed, password is not set ***

RMC> set pass

RMC Password: ****

Verification: ****

4-28 Compaq AlphaServer ES40 User Interface Guide

4.25 set user

The set user command allows you to set a user string to be displayed in the status command.

You may want to make notes regarding the system. The string is limited to 63 characters and is displayed in the User String field when you enter the status command.

In this example, the operator leaves a reminder that a power supply needs to be replaced.

RMC> set user

User String: need to replace P/S

RMC> status

PLATFORM STATUS

User String: need to replace P/S

RMC Commands 4-29

4.26 status

The status command displays the system status and the current RMC settings.

Table 4–1 describes each field of the status command output.

RMC> status

PLATFORM STATUS

On-Chip Firmware Revision: V1.0

Flash Firmware Revision: V1.2

Server Power: ON

System Halt: Deasserted

RMC Power Control: ON

Escape Sequence: ^[^[RMC

Remote Access: Enabled

RMC Password: set

Alert Enable: Disabled

Alert Pending: YES

Init String: AT&F0E0V0X0S0=2

Dial String: ATXDT9,15085553333

Alert String: ,,,,,,5085553332#;

Com1_mode: THROUGH

Last Alert: PS1 failed

Logout Timer: 20 minutes

User String: need to replace PS

4-30 Compaq AlphaServer ES40 User Interface Guide

Table 4–1 Status Command Fields

Field

On-Chip Firmware

Revision:

Flash Firmware

Revision:

Server Power:

Meaning

Revision of RMC firmware on the microcontroller.

Revision of RMC firmware in flash ROM.

System Halt:

RMC Power Control:

Escape Sequence:

Remote Access:

RMC Password:

Alert Enable:

Alert Pending:

Init String:

Dial String:

Alert String:

Com1_mode:

Last Alert:

Logout Timer:

User String:

ON = System is on.

OFF = System is off.

Asserted = System has been halted.

Deasserted = Halt has been released.

ON= System has powered on from RMC.

OFF = System has powered off from RMC.

Current escape sequence for access to RMC console.

Enabled = Modem for remote access is enabled.

Disabled = Modem for remote access is disabled.

Set = Password set for modem access.

Not set = No password set for modem access.

Enabled = Dial-out enabled for sending alerts.

Disabled = Dial-out disabled for sending alerts.

YES = Alert has been triggered.

NO = No alert has been triggered.

Initialization string that was set for modem.

Pager string to be dialed when an alert occurs.

Identifies the system that triggered the alert to the paging service. Usually the phone number of the monitored system.

Identifies the current COM1 mode.

Type of alert (for example, power supply 1 failed).

The amount of time before the RMC terminates an inactive modem connection. The default is 20 minutes.

Notes supplied by user.

RMC Commands 4-31

Index

Advanced CMOS setup mode, 3-32

Advanced CMOS setup screen, 3-36

Advanced PCI Information screen, 3-13, 3-14 alphabios command (SRM), 2-38

AlphaBIOS console, 3-1 checking PCI parity, 3-36 defined, 1-4 displaying error frames, 3-46 displaying hard disk configuration, 3-10 displaying integrated peripherals, 3-19 displaying memory configuration, 3-18 displaying PCI configuration, 3-12 displaying SCSI configuration, 3-16 displaying system board configuration, 3-8 displaying system configuration, 3-6 first-level help, 3-4 key conventions, 3-4 loading, 2-38 maintenance programs, 3-48 navigation, 3-5 setting date and time, 3-34 setting keyboard language, 3-35 setting password, 3-37 setup screen, 3-3 starting, 3-2 switching to SRM, 3-37, 3-58 upgrading, 3-61

Utilities menu, 3-44

Auto Start and primary operating system, 3-53

Auto Start setting, Windows NT, 3-35 auto_action environment variable, 2-2, 2-48 auto_action environment variable, SRM, 2-37

Autoboot, 2-48

Baud rate, setting, 2-55 boot command (SRM), 2-26

Boot devices, specifying, 2-50

Boot file, specifying, 2-51

Boot flags

OpenVMS, 2-53

Tru64 UNIX, 2-52

Boot process, Windows NT, 3-43, 3-54 boot_file environment variable, 2-51 boot_osflags environment variable, 2-52

Bootable devices, displaying, 2-17 bootdef_dev environment variable, 2-50 bootp protocol, 2-64

Bus node ID, SCSI, 2-72

clear alert command (RMC), 4-4 clear password command (SRM), 2-84 clear port command (RMC), 4-5

Clearing SRM password, 2-84

COM ports, baud rate, 2-55 com*_baud environment variable, 2-55 com*_flow environment variable, 2-56 com*_modem environment variable, 2-58 com1_baud environment variable, 2-55 com1_flow environment variable, 2-56 com1_mode environment variable, 2-57 com1_modem environment variable, 2-58 com2_baud environment variable, 2-55 com2_flow environment variable, 2-56 com2_modem environment variable, 2-58

Command conventions, RMC, 4-3

Index-1

Command syntax, SRM console, 2-6

Configuring parameters, AlphaBIOS, 3-32

Console commands list (SRM), 2-4

Console device, activating, 2-75 console environment variable, 2-59

Console mode, 1-4

Console password, 2-78 clearing, 2-84

Console program, 1-2

Console terminal, 1-3

Console tests, 2-31

Console, specifying, 2-59, 3-37

Control panel message, 2-68

Controllers, SCSI, 2-72

CPU, enabling, 2-60 cpu_enabled environment variable, 2-60 crash command (SRM), 2-32

Crash dump, 2-32

Create New Partition dialog box, 3-28

Custom hard disk setup, 3-28

Date, setting in AlphaBIOS, 3-34

Delete Partition dialog box, 3-29

Device naming, 2-17

Devices, verifying, 2-30

DHCP address source, 3-39

Diagnostic tests, 2-30 disable alert command (RMC), 4-6 disable remote command (RMC), 4-7

Disk partition creating in AlphaBIOS, 3-29 deleting in AlphaBIOS, 3-29

Display System Configuration screen, 3-6

Displaying error frames, 3-46

Displaying logical configuration, 2-12

DTR, asserting, 2-58

edit command (SRM), 2-41 ei*0_inet_init environment variable, 2-62 ei*0_mode environment variable, 2-63 ei*0_protocols environment variable, 2-64 enable alert command (RMC), 4-8 enable remote command (RMC), 4-9

Index-2

env command (RMC), 4-10

Environment variables initializing, 2-45 summary, 2-46

Error frames, displaying, 3-46

Escape sequence, RMC, 2-43

Ethernet controllers, 2-63

Ethernet settings, 2-63

Event log, displaying, 2-35 ew*0_inet_init environment variable, 2-62 ew*0_mode environment variable, 2-63 ew*0_protocols environment variable, 2-64

Express hard disk setup, 3-26

Fans, status of, 2-24

Fast SCSI, 2-71

FAT partitions, 3-21 formatting, 3-30 quick format, 3-31 standard format, 3-31

File, displaying, 2-35

Firmware updating, 3-61 updating, 2-85

Floppy drive type, 3-34

Format Disk dialog box, 3-30

Formatting FAT partitions, 3-31 with NTFS, 3-30

FRUs, displaying, 2-18

FRUs, displaying errors, 2-21

Halt button, with login command, 2-83 halt in command (RMC), 4-12 halt out command (RMC), 4-13 hangup command (RMC), 4-14

Hard disk

Create Partition option, 3-28

Delete Partition option, 3-28 setup for Windows NT, 3-24

Hard Disk Configuration display, 3-10

Hard Disk Setup screen, 3-24

Hardware, initializing, 2-36 help command (SRM), 2-10 help or ? command (RMC), 4-15

init command (SRM), 2-36

Initializing the system, 2-36

Installing Windows NT, 3-42 from CD-ROM, 3-43

Integrated Peripherals screen, 3-19

Internet database, initializing, 2-62

kbd_hardware_type environ. variable, 2-65

Key conventions, AlphaBIOS, 3-4

Keyboard language variants, 2-66 setting language, AlphaBIOS, 3-35

Keyboard type, setting, 2-65

language environment variable, 2-66 login command (SRM), 2-82

Loopback tests, 2-31

Maintenance programs, 3-44, 3-48 man command (SRM), 2-10

Memory configuration screen, 3-18

Memory test

AlphaBIOS, 3-36

SRM, 2-67

Memory, displaying, 2-22 memory_test environment variable, 2-67

MOP protocol, 2-64

MOP V3 software, 2-41 more command (SRM), 2-35

Network settings, saving, 3-41

Network Setup screen, 3-38

No System Partition screen, 3-20

NTFS, formatting with, 3-30

Nvram script, 2-40

ocp_text environment variable, 2-68

Operating System Selection screen, 3-50

Operating System Selection Setup screen, 3-

Operating system, specifying, 2-69

OS Loader, 3-43, 3-54 os_type environment variable, 2-69, 3-37

PALcode version, displaying, 2-23

Parameters, configuring in AlphaBIOS, 3-32

Parity checking, 2-70

Password, setting AlphaBIOS, 3-37

Password, setting SRM, 2-78

PCI configuration screen, 3-12

PCI devices, viewing, 3-13

PCI NVRAM module, configuring, 2-28

PCI options, slot numbers, 2-16

PCI parity, 2-70

PCI parity checking, 3-36 pci_parity environment variable, 2-70 pk*0_fast environment variable, 2-71 pk*0_host_id environment variable, 2-72 pk*0_soft_term environment variable, 2-73 power off command (RMC), 4-16 power on command (RMC), 4-17

Power status, displaying, 2-24

Power-up memory test

AlphaBIOS, 3-36

SRM, 2-67

Power-up script, creating, 2-40 prcache command (SRM), 2-28

Primary operating system, designating, 3-52

Processor, enabling, 2-60

Program, resuming, 2-34

QLogic controller, 2-73 quit command (RMC), 4-18

RAID configuration, 3-49

Index-3

RAID devices, configuring, 2-29

Reading a file, 2-35 reset command (RMC), 2-43, 4-19

Resetting firmware, 2-36

RMC command conventions, 4-3 defined, 1-5 escape sequence, 2-43 rmc command (SRM), 2-42

RMC commands clear alert, 4-4 clear port, 4-5 disable alert, 4-6 disable remote, 4-7 enable alert, 4-8 enable remote, 4-9 env, 4-10 halt in, 4-12 halt out, 4-13 hangup, 4-14 help or ?, 4-15 list of, 4-2 power off, 4-16 power on, 4-17 quit, 4-18 reset, 2-43, 4-19 send alert, 4-20 set alert, 4-21 set com1_mode, 4-22 set dial, 4-24 set escape, 4-25 set init, 4-26 set logout, 4-27 set password, 4-28 set user, 4-29 status, 4-30

SCSI BIOS emulation, 3-37

SCSI configuration screen, 3-16

SCSI controller IDs, 2-72

SCSI devices, speed of, 2-71

SCSI terminators, enabling, 2-73

Secure function commands, 2-77

Secure mode, setting SRM to, 2-80

Security features, turning off, 2-82

Security, SRM console, 2-76

Index-4

send alert command (RMC), 4-20

Serial ports determining presence of modem on, 2-58 flow control, 2-56 set alert command (RMC), 4-21 set com1_mode command (RMC), 4-22 set command (SRM), 2-44, 2-45 set dial command (RMC), 4-24 set escape command (RMC), 4-25 set init command (RMC), 4-26 set logout command (RMC), 4-27 set password command (RMC), 4-28 set password command (SRM), 2-78 set secure command (SRM), 2-80 set user command (RMC), 4-29

Setup errors, Windows NT, 3-57

Setup screen, AlphaBIOS, 3-3 show command (SRM), 2-44, 2-45 show config command (SRM), 2-12 show device command (SRM), 2-17 show error command (SRM), 2-21 show fru command (SRM), 2-18 show memory command (SRM), 2-22 show pal command (SRM), 2-23 show power command (SRM), 2-24 show version command (SRM), 2-25

Special characters, SRM console, 2-7

SRM console command syntax, 2-6 defined, 1-4 device naming conventions, 2-17 displaying system configuration, 2-12 finding help, 2-10 invoking, 2-2 invoking from AlphaBIOS, 3-58 invoking from RMC, 2-3 invoking from Tru64 UNIX or OpenVMS,

2-2 invoking from Windows NT, 2-2 loading AlphaBIOS, 2-38 reading a file, 2-35 resetting firmware, 2-36 security, 2-76 setting environment variables, 2-44 special characters, 2-7 switching from AlphaBIOS, 3-37 tasks performed from, 2-9 testing the system, 2-30

version, 2-25

SRM console commands, 2-4 alphabios, 2-38 boot, 2-26 clear password, 2-84 crash, 2-32 edit, 2-41 help, 2-10 init, 2-36 login, 2-82 man, 2-10 more, 2-35 prcache, 2-28 rmc, 2-42 set, 2-44, 2-45 set password, 2-78 set secure, 2-80 show, 2-44, 2-45 show config, 2-12 show device, 2-17 show error, 2-21 show fru, 2-18 show memory, 2-22 show pal, 2-23 show power, 2-24 show version, 2-25 test, 2-30

SRM console password, 2-78 clearing, 2-84

Standard CMOS setup mode, 3-32

Standard CMOS Setup screen, 3-34

Starting AlphaBIOS, 3-2 status command (RMC), 4-30

Switching to SRM from Advanced CMOS Setup, 3-59 from the control panel, 3-59

System board configuration screen, 3-8

System configuration, displaying in

AlphaBIOS, 3-6

System partition, 3-22 arrangement on first hard disk, 3-23 purpose of, 3-21

Windows NT, 3-20

Temperature sensors, status of, 2-24 test command (SRM), 2-30

Testing memory from SRM, 2-67

Testing the system, 2-30

Time, setting in AlphaBIOS console, 3-34 tt_allow_login environment variable, 2-75

Updating firmware, 2-85

Upgrading AlphaBIOS, 3-61

Utility programs, AlphaBIOS, 3-44

VGA console tests, 2-31

VGA monitor, invoking RMC from, 2-42

Windows NT boot process, 3-43, 3-54 console for, 3-1 designating primary operating system, 3-52 express hard disk setup, 3-27 hard disk setup, 3-24 installing, 3-42 installing from CD-ROM, 3-43 network setup, 3-38 operating system selections, 3-54 selecting version, 3-50 setup errors, 3-57 starting automatically, 3-35 system partition, 3-20 test command, 2-31

Index-5

Përshëndetje! Unë jam një chatbot AI i trajnuar posaçërisht për t'ju ndihmuar me Compaq ES40 AlphaServer User Interface Guide. Unë e kam shqyrtuar plotësisht dokumentin dhe mund t'ju ndihmoj të gjeni informacionin e saktë që ju nevojitet ose të shpjegoj përmbajtjen në terma të qartë dhe të thjeshtë. Pavarësisht nëse jeni duke kërkuar udhëzime mbi veçori specifike, hapa zgjidhjeje problemesh ose përdorim të përgjithshëm, mos ngurroni të bëni pyetjet tuaja. Sa më shumë detaje të jepni rreth shqetësimeve ose nevojave tuaja, aq më saktë dhe efektivisht mund t'ju ndihmoj!

Asistenti po shkruan

Asistenti nuk është në tastierë. Ju lutemi, provoni përsëri më vonë.

Tabela e përmbajtjes

Duket se keni arritur në një dokument që është shkruar në disa gjuhë, duke përfshirë një që nuk është gjuha juaj amtare. Mund të përdorni lidhjet e mëposhtme për të fshehur përkohësisht faqet pa gjuhën që preferoni.

Reklamë

AlphaServer ES40

User Interface Guide

Compaq Computer Corporation

Contents

Preface

Chapter 1 Console Program Overview

Chapter 2 SRM Console

Chapter 3 AlphaBIOS Console

Chapter 4 RMC Commands

Figures

Tables

Examples

Preface

Intended Audience

Document Structure

Documentation Titles

Table 1 Compaq AlphaServer ES40 Documentation

Support Resources

Chapter 1

Console Program Overview

1.1

Console Overview

1.2

Console Terminal

1.3

Console Mode

1.3.1

SRM Console

1.3.2

AlphaBIOS Console

1.3.3

Remote Management Console

Chapter 2

SRM Console

2.1

Invoking the SRM Console

2.2

SRM Command Overview

Table 2–1 Summary of SRM Console Commands

Table 2–2 Notation Formats for SRM Console Commands

Table 2–3 Special Characters for SRM Console

Table 2–3 Special Characters for SRM Console (Continued)

2.3

Management Tasks Performed from SRM

Table 2–4 Management Tasks and Related SRM Commands

2.4

Getting Help on SRM Commands

Example 2–1 Help (or Man)

2.5

Displaying the Logical Configuration

Example 2–2 Show Config

Example 2–2 Show Config (Continued)

Table 2–5 Correspondence Between Logical and Physical PCI Slots

2.6

Displaying the Bootable Devices

Example 2–3 Show Device

Table 2–6 Device Naming Conventions

2.7

Displaying the System FRUs

Example 2–4 Show Fru

Table 2–7 Bit Assignments for Error Field

2.8

Displaying FRUs with Errors

Example 2–5 Show Error

2.9

Displaying the Memory Configuration

Example 2–6 Show Memory

2.10

Displaying the PAL Version

Example 2–7 Show PAL

2.11

Displaying the Power Status

Example 2–8 Show Power

2.12

Displaying the SRM Console Version

Example 2–9 Show Version

2.13

Booting Tru64 UNIX or OpenVMS

Example 2–10 OpenVMS Boot

2.14

**com*_baud**

**com*_flow**

**com*_modem**

**ei0_inet_init or ew0_inet_init**

**ei0_mode or ew0_mode**

**ei0_protocols or ew0_protocols**