Page 1 AlphaServer GS60/140 and 8200/8400 Operations Manual Order Number: EK–T8030–OP. C01 This manual is intended for the system manager or system operator and covers the basic operation of these AlphaServer systems. The systems with the latest Alpha chip, the 21264, are offered as GS60 and GS140 systems.
Page 2 FURNISHING, PERFORMANCE, OR USE OF THIS MATERIAL. 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 document is furnished under a license agreement or nondisclosure agreement and may be used or copied only in accordance with the terms of the agreement.
Page 3: Table Of Contents
Contents Preface ......................xiii Chapter 1 Introduction AlphaServer 8200/8400 System Overview ..........1-2 Console Firmware and Utilities Overview..........1-4 System Architecture.................1-6 Chapter 2 AlphaServer 8200 System System Characteristics ................2-2 Sample 8200 System ................2-4 System Front View...................2-6 System Rear View..................2-8 System Components- ................2-10 2.5.1 Processor System Unit..............
Page 4 3.6.1 Control Panel Keyswitch..............3-22 3.6.2 Control Panel Indicator Lights............3-24 3.6.3 Circuit Breaker and AC Power Indicators........3-26 Chapter 4 I/O Subsystems I/O Subsystem Overview................4-2 I/O Port Modules..................4-4 System Configuration Information ............4-6 PCI Adapter ................... 4-16 KFE70 and KFE72 Adapters ..............4-18 EISA Configuration Utility ..............
Page 5 6.11 Self-Test Lines NODE# and TYP............6-22 6.12 Self-Test Lines ST and BPD ..............6-24 6.13 Self-Test Lines C0, C1, C2,…,Cn ............6-26 6.14 Self-Test Lines ILV and MB..............6-28 6.15 Self-Test Identification Line ..............6-30 6.16 Show Commands ................... 6-32 6.16.1 Show Configuration ................
Page 6 7.5.23 Set Host ..................7-45 7.5.24 Set Power..................7-47 7.5.25 Set SEEPROM ................7-48 7.5.26 Show Configuration ................ 7-49 7.5.27 Show CPU..................7-51 7.5.28 Show Device ................... 7-52 7.5.29 Show EEPROM ................7-53 7.5.30 Show <envar> ................. 7-54 7.5.31 Show Memory................. 7-55 7.5.32 Show Network.................
Page 7 Appendix A OpenVMS and DIGITAL UNIX Boot Options Appendix B Updating Firmware Booting LFU with OpenVMS and DIGITAL UNIX Systems ....B-2 List ......................B-4 Update ....................B-6 Exit ....................... B-10 Display and Verify Commands ............. B-12 How to Update Corrupted Firmware ............. B-14 How to Modify Device Attributes ............
Page 8 6–3 Testing Sequence ................... 6-18 6–4 Self-Test Results ..................6-20 6–5 Self-Test Results: Node# and TYP ............6-22 6–6 Self-Test Results: ST and BPD.............. 6-24 6–7 Self-Test Results: C0, C1, C2,…,Cn ............. 6-26 6–8 Self-Test Results: ILV and MB ............. 6-28 6–9 Self-Test Results: Identification Line ............
Page 9 7–26 Show Configuration Command .............. 7-50 7–27 Show CPU Command ................7-51 7–28 Show Device Command................. 7-52 7–29 Show EEPROM Command ..............7-53 7–30 Show <envar> Command............... 7-54 7–31 Show Memory Command............... 7-55 7–32 Show Network Command ..............7-56 7–33 Show Power Command ................
Page 10 3–4 System Rear View..................3-8 3–5 Accessing the Console Load Device............3-10 3–6 Power System ..................3-12 3–7 TLSB Card Cage..................3-14 3–8 Control/Status and I/O Connections ............3-16 3–9 Cabinet Airflow ..................3-18 3–10 System Options ..................3-20 3–11 Control Panel Keyswitch................ 3-22 3–12 Control Panel Indicator Lights ...............
Page 11 Run Maintenance Program Dialog Box ..........8-41 8–29 Operating System Selections..............8-42 8–30 Primary Operating System ..............8-44 8–31 Operating System Selection Setup............8-46 Tables AlphaServer GS60/140 and 8200/8400 Documentation......xvi 2–1 Electrical Characteristics................2-3 2–2 Environmental Characteristics..............2-3 2–3 Control/Status and I/O Connections ............2-13 2–4 Control Panel Pushbuttons ..............
Page 12 7–1 SRM Console Command Language Syntax ..........7-4 7–2 SRM Console Special Characters .............7-6 7–3 Environment Variables................7-10 7–4 Deposit Command Options ..............7-28 7–5 Device Name and Address Space Options ..........7-29 7–6 Examine Command Options..............7-31 7–7 Device Name and Address Space Options ..........7-32 7–8 Test Command Options................
Page 13: Preface
Preface This manual describes both the Compaq AlphaServer GS60 and GS140 systems as well as the AlphaServer 8200 and 8400 systems. The AlphaServer 8200 and 8400 systems were introduced by Digital Equipment Corporation in 1995. Now Compaq Computer Corporation, with the introduction of the Alpha 21264 chip, is calling the latest offering Compaq AlphaServer Global Solutions (GS) systems.
Page 14 Intended Audience This manual is written for the system manager or system operator who has training in systems management and is running a Compaq AlphaServer GS60 or GS140 system or an AlphaServer 8200 or 8400 system. Document Structure This manual uses a structured documentation design.
Page 15 This manual has eight chapters and three appendixes, as follows: • Chapter 1, Introduction, provides a brief overview of the AlphaServer 8200 and AlphaServer 8400 hardware, firmware, and system architecture. • Chapter 2, AlphaServer 8200 System, and Chapter 3, AlphaServer 8400 System, give a basic introduction to your system and its parts.
Page 16: Alphaserver Gs60/140 And 8200/8400 Documentation
Table 1 AlphaServer GS60/140 and 8200/8400 Documentation Title Order Number Hardware User Information and Installation Operations Manual EK–T8030–OP Site Preparation Guide EK–T8030–SP AlphaServer GS60/8200 Installation Guide EK–T8230–IN AlphaServer GS140/8400 Installation Guide EK–T8430–IN KFE72 Installation Guide EK–KFE72–IN AlphaServer GS60/140 8200/8400 Windows NT EK–T8WNT–RN...
Page 17: Chapter 1 Introduction
Chapter 1 Introduction The AlphaServer 8200 and 8400 systems are high-performance, symmetric multiprocessing systems that are suitable for office and datacenter environments. They offer access to multiple high-bandwidth I/O buses, very large memory capacities, up to 14 high-performance Alpha CPUs, and many other features normally associated with mainframe systems.
Page 18: Alphaserver 8200/8400 System Overview
1.1 AlphaServer 8200/8400 System Overview The AlphaServer 8200 and 8400 systems are separate, but related, systems that use the same system bus, the TLSB. The processor, memory, and I/O adapter units that can be configured on this bus are also the same. The cabinets, and some of their components, vary.
Page 19 AlphaServer 8200 System The AlphaServer 8200 system main cabinet contains the processor system unit (PSU) including a five-slot card cage, power regulators, and space for PCI I/O shelves or StorageWorks shelves. The 8200 system can have up to two expander cabinets, containing additional PCI I/O shelves and StorageWorks shelves.
Page 20: Accessing Firmware At The Console Device
1.2 Firmware and Utilities Overview Firmware residing in flash ROM on CPU and other modules in the system provides commands for booting the operating system, testing devices and I/O adapters, and other tasks useful in operating and maintaining a running system. You type the commands or select from menus at the console device.
Page 21 SRM Console The SRM console firmware is the first to be executed after system self-test when the system is powered up. If you have requested automatic boot (see Chapter 5), the operating system is booted automatically. Otherwise, the system halts at the SRM console prompt.
Page 22: System Architecture
1.3 System Architecture The high-speed TLSB system bus is used to interconnect processors, memory modules, and I/O port modules. Figure 1-3 Sample System Architecture Processors Memory System Bus I/O Bus Port Adapter I/O Bus Controller Controller Controller Devices Devices Devices BX0501-94 1-6 AlphaServer 8200/8400 Operations Manual...
Page 23 The TLSB bus is a synchronous bus (with a 256-bit data bus and a 40-bit command/address bus) that interconnects processors, memory modules, and the I/O port. The I/O port (KFTHA or KFTIA) module connects the TLSB bus to I/O buses through separate I/O adapter modules.
Page 25: Chapter 2 Alphaserver 8200 System
Chapter 2 AlphaServer 8200 System The DIGITAL AlphaServer 8200 system, designed for use in an office environment, can support many users in a time-sharing environment. The 8200 system: • Supports the full range of system applications of OpenVMS, DIGITAL UNIX, and Windows NT operating systems •...
Page 26: System Characteristics
2.1 System Characteristics Figure 2-1 shows the cabinet dimensions and the required clearance space. The tables list the electrical and environmental characteristics. Figure 2-1 Sample System Footprint Expander System Expander Cabinet Cabinet Cabinet 60 cm (23.6 in) 60 cm (23.6 in) 60 cm (23.6 in) Rear Clearance...
Page 27: Electrical Characteristics
The values in Table 2–1 and Table 2–2 apply to the system cabinet only. The values are configuration dependent. Table 2-1 Electrical Characteristics Electrical Specification Single-phase AC input voltage 202–240 (208) – North America (nominal) 202–240 (230) – Europe/AP 202–240 (202) – Japan Nominal frequency 50–60 Hz AC current (nominal)
Page 28: Sample 8200 System
2.2 Sample 8200 System Figure 2-2 shows a sample system. The system includes a console terminal and printer, an accessories kit, and a documentation set, which includes this manual. The system can have up to two optional expander cabinets, additional disk drives, and optional battery backup.
Page 29 Your DIGITAL customer service engineer has installed your system and verified that it is running properly. Before you turn on the system, familiarize yourself with its components: • The system cabinet houses the power system (with optional battery backup) and the processor system unit (PSU) which contains a storage drawer, the TLSB card cage, control panel, the cabinet control logic panel, and a CD-ROM drive.
Page 30: System Front View
2.3 System Front View With the front door open, you can see the control panel, the TLSB card cage, blower, PCI shelves, StorageWorks shelves, and power regulators. Figure 2-3 System Front View CD-ROM Drive TLSB Card Cage StorageWorks Drive Front StorageWorks Power Supply Control Panel...
Page 31 The following components are visible from the inside front of the cabinet: • TLSB card cage • CD-ROM drive • Floppy drive • Control panel • Cabinet control logic (CCL) panel • PCI or StorageWorks shelves • Power regulators NOTE: Four optional storage devices installed in the processor system unit are not visible.
Page 32: System Rear View
2.4 System Rear View With the rear door open, DIGITAL customer service engineers can access the circuit breaker and AC power cord. Figure 2-4 System Rear View TLSB Card Cage Rear Blower PCI or StorageWorks Shelves Space for Power Regulators Circuit Breaker BX-0605A-97 2-8 AlphaServer 8200/8400 Operations Manual...
Page 33 The following components are visible from the inside rear of the cabinet: • TLSB card cage • Blower • PCI or StorageWorks shelves • Power regulators • Circuit breaker Optional components visible from the inside rear (and front) of the cabinet include PCI shelves, StorageWorks shelves, and an additional power regulator.
Page 34: System Components
2.5 System Components 2.5.1 Processor System Unit The processor system unit (PSU) contains the 5-slot TLSB card cage and blower, a storage drawer housing integrated I/O devices, an optional floppy drive, a cabinet control logic (CCL) panel, and the control panel. Figure 2-5 Processor System Unit Front Expander...
Page 35: Tlsb Card Cage
The PSU is located in the upper half of the system cabinet, as viewed from the front. The PSU storage drawer can house up to six optional SCSI devices, including one 5.25-inch removable media device and five 3.5-inch devices. The 5.25-inch device and one 3.5-inch device are accessible from the front of the cabinet;...
Page 36: Cabinet Control Logic Panel
2.5.2 Cabinet Control Logic Panel Console terminal I/O and expander cabinet remote power control/status connections are located on the cabinet control logic (CCL) panel to the right of the control panel. See Table 2-3 for a list of the other connections shown in Figure 2-7.
Page 37: Control/Status And I/O Connections
Table 2-3 Control/Status and I/O Connections Connector Name Function Console Serial console device connection for OpenVMS, DIGITAL UNIX, and Windows NT systems. (For Windows NT systems, the graphics monitor is connected through the KFE72 adapter installed in the primary DWLPB adapter (connected to hose 1 on the KFTHA or KFTIA in slot 8 of the TLSB).
Page 38: Console Load Device
2.5.3 Console Load Device The CD-ROM drive is the in-cabinet console load device. Figure 2-8 Accessing the Console Load Device TLSB KFTIA (ISP1020 Controller) KFTHA (KZPAA in PCI shelf) CD-ROM BX-0601A-97 2-14 AlphaServer 8200/8400 Operations Manual...
Page 39 The console load device is used for: • Installing or updating firmware or software • Loading a backup utility program • Interchanging user data • Updating module firmware The CD-ROM drive is the console load device. It is installed in the system cabinet and is used to access software and online documentation.
Page 40: Power System
2.5.4 Power System The power system consists of one or two power regulators (with optional battery backup), a cabinet control logic (CCL) module, and power distribution and signal interconnect cables. The AC circuit breaker controls power to the entire system. Figure 2-9 Power System Front Rear...
Page 41 The power regulator is located in the lower third of the cabinet. The CCL panel is located in the processor system unit (PSU), next to the control panel. The system can have up to two power regulators. In this configuration an optional power strip is installed at the rear of the cabinet so that only one AC input connection is required.
Page 42: Controls And Indicators
2.6 Controls and Indicators This section describes the control panel and the AC power circuit breaker. Figure 2-10 Control Panel On/Off Enable Secure Front Restart Fault BX-0607-98 Table 2-4 Control Panel Pushbuttons Push- button Position Effect On/Off Supplies power to the PSU. When this button is pressed and the Secure button is not pressed, OpenVMS or DIGITAL UNIX users can interrupt operating system program execution and enter console mode by typing Ctrl/P at the...
Page 43: Control Panel Indicator Lights
Table 2-4 Control Panel Pushbuttons (Continued) Push- button Position Effect Secure Prevents input from the console device. On DIGITAL UNIX or OpenVMS systems, used to protect inadvertent or inadvisable entry into SRM console mode by typing Ctrl/P at the console device. For example, you might push this button in when a critical program is running, in case someone might unknowingly try to enter SRM console mode to load new console code or otherwise use the console device.
Page 44: Ac Power Circuit Breaker
2.6.1 AC Power Circuit Breaker The circuit breaker is located on the power regulator at the rear of the cabinet. Figure 2-11 Circuit Breaker Rear Up Position: On Down Position: Off BX-0608-94 2-20 AlphaServer 8200/8400 Operations Manual...
Page 45 Each power regulator has a circuit breaker. The circuit breaker controls power to the entire system. For normal operation, the circuit breaker must be in the on position, in which the handle is pushed up. To shut the circuit breaker off, push the handle down. AlphaServer 8200 System 2-21...
Page 46: Options
2.7 Options System options include a floppy drive, PCI shelves, StorageWorks shelves, an additional power regulator, and optional battery backup. Figure 2-12 System Options Front Expander Console On/Off Enable PowerComm 3 External Enable (XMI/FBUS) Secure PowerComm 2 External UPS Power Restart Fault PowerComm 1...
Page 47 PCI I/O PCI I/O is used in the 8200 system. The PCI shelf has 12 slots, a PCI adapter module, a hose interface to the TLSB bus, and a power supply. The KFE70 adapter provides a bridge module for access to EISA I/O. The KFE72 adapter provides a graphics and keyboard and mouse ports for a system using a graphics console monitor.
Page 49: Alphaserver 8400 System
Chapter 3 AlphaServer 8400 System The DIGITAL AlphaServer 8400 system is designed for growth, offering configuration flexibility, an outstanding I/O subsystem, and expansion capability in a single or multi-cabinet environment. Functionally, this system is identical to the AlphaServer 8200 system. The 8400 system, however, can have: •...
Page 50: System Characteristics
3.1 System Characteristics DIGITAL AlphaServer 8400 characteristics are shown in Table 3-1 and Table 3- 2. Figure 3-1 shows a system footprint. Figure 3-1 Sample System Footprint Expander System Expander Cabinet Cabinet Cabinet 80 cm (31.5 in) 80 cm (31.5 in) 80 cm (31.5 in) Rear Clearance...
Page 51: Electrical Characteristics
The values in Table 3-1 apply to the 8400 system cabinet only. The values are configuration dependent. Additional options will increase electrical requirements so that an additional power regulator may be needed. Table 3-1 Electrical Characteristics Electrical Specification 120/208 V Wye (30A) – North America 3-phase AC input voltage 380–415 V Wye (30 A) –...
Page 52: Sample 8400 System
3.2 Sample 8400 System Figure 3-2 shows a sample AlphaServer 8400. The system includes a CD-ROM drive, a console device and printer, an accessories kit, and a documentation set. The system options include battery backup PIUs, three different types of I/O bus PIUs (depending on the operating system) and StorageWorks disk drive.
Page 53 Your DIGITAL customer service engineer has installed your system and verified that it is running properly. Before you turn on the system, familiarize yourself with its components: • The system cabinet houses the TLSB card cage, power system, cooling system, the control panel with status indicators, and a CD-ROM drive.
Page 54: System Front View
3.3 System Front View The control panel, plug-in unit panels, and CD-ROM and optional floppy drive are on the front of the system cabinet. With the front door open, DIGITAL customer service engineers can access the TLSB card cage, the power regulator, cooling system, and optional plug-in units.
Page 55 These components are visible from the inside front of the cabinet (see Figure 3-3 for their location): • Control panel • CD-ROM drive • Optional floppy drive • Power regulator(s) (48 VDC) • TLSB card cage (holds CPU/memory; slots 0–3) •...
Page 56: System Rear View
3.4 System Rear View With the rear door open, DIGITAL customer service engineers can access the TLSB card cage, DC distribution box, battery connections, AC power cord, circuit breaker, blower, and I/O PIU area. Figure 3-4 System Rear View Distribution Battery I/O Module Connections...
Page 57 The following components are visible from the rear of the cabinet (see Figure 3-4): • TLSB card cage (slots 4–8) • I/O port module (slot 8) • DC distribution box • Battery PIU connections • AC power cord and connector •...
Page 58: System Components
3.5 System Components 3.5.1 Console Load Device The CD-ROM drive is the in-cabinet console load device. Figure 3-5 Accessing the Console Load Device TLSB KFTIA (ISP1020 Controller) KFTHA (KZPAA in PCI shelf) CD-ROM BX-0601A-97 3-10 AlphaServer 8200/8400 Operations Manual...
Page 59 The console load device is used for: • Installing or updating software • Loading a backup utility program • Interchanging user data • Updating module firmware The CD-ROM drive is the console load device. It is installed in the system cabinet and is used to access software and online documentation.
Page 60: Power System
3.5.2 Power System The power system includes an AC input box, DC distribution box, power regulator(s), cabinet control logic module, power distribution cables, signal interconnect cables, and an optional battery PIU (with H7263-AC/AD regulators only). Figure 3-6 Power System CCL Module Rear Front AC Input Box...
Page 61 The power system uses H7263 power regulators (see Figure 3-6), requiring three-phase AC. Two types of H7263 regulators are available. The H7263–AA/AB regulators (optional) have the ability to use and charge optional battery packs. The H7263– AC/AD regulators, shipped with a standard 8400 system, do not allow battery backup. Both types of power regulator allow switching between regulators in the event one fails.
Page 62: Tlsb Card Cage
3.5.3 TLSB Card Cage The TLSB card cage is a 9-slot card cage that contains slots for up to six or seven (KN7CF only) CPU modules, up to seven memory array modules, and up to three I/O modules. The TLSB bus interconnects the CPU, memory, and I/O modules. Figure 3-7 TLSB Card Cage TLSB Card Cage...
Page 63 The 9-slot TLSB card cage is located in the upper left (front and rear) of the system cabinet, as viewed from the front. The TLSB card cage must contain one I/O port module, which is always installed in slot 8. The other eight slots contain a combination of KFTHA/KFTIA I/O modules (rear only), memory, and CPU modules.
Page 64: Control/Status And I/O Connections
3.5.4 Control/Status and I/O Connections An I/O connection for the serial console device, and expander cabinet remote power control/status connections are located to the right of the control panel. Ethernet and other I/O connections are located off the I/O modules. For the PCI and FBUS+ PIUs, these connections are directly off the modules.
Page 65 Three modular jacks to the right of the control panel allow power control/status connections to the left expander cabinet, right expander cabinet, and I/O connections to a serial console terminal. This serial console terminal modified modular jack is keyed so that an expander cabinet connector cannot be plugged into its jack. The system cabinet has four quadrants in the bottom of the cabinet.
Page 66: Cooling System
3.5.5 Cooling System The cooling system cools the power system, the TLSB card cage, control logic, and PIUs. Figure 3-9 Cabinet Airflow BX0509-94 3-18 AlphaServer 8200/8400 Operations Manual...
Page 67 The cooling system is designed to keep system components at an optimal operating temperature. It is important to keep the front and rear doors free of obstructions, leaving a minimum clearance space of 1.5 meters (59 inches) in the front and 1 meter (39 inches) in the rear between cabinets (see Figure 3-9) to maximize airflow.
Page 68: System Options
3.5.6 System Options System options include a floppy drive beside the CD-ROM, additional power regulators and additional PIUs for I/O, disks, tapes, and batteries. Figure 3-10 System Options Front Additional Power Regulators Optional PIUs BX0510-94 3-20 AlphaServer 8200/8400 Operations Manual...
Page 69 SCSI Disk and Tape PIUs A maximum of three SCSI PIUs can be installed in the system cabinet or six in an expander cabinet. The PIU can occupy any quadrant in the main or expander cabinet. The PIU can contain up to seven 3.5-inch or two 5.25-inch disks. Supported devices include SCSI disk drives, CD-ROM, and tape drives.
Page 70: Controls And Indicators
3.6 Controls and Indicators This section introduces the system controls and indicators. The system control panel, located in the upper right front of the cabinet, contains a keyswitch and status lights. The keyswitch regulates power going into the system, secures the console device, and controls system operation.
Page 71: Keyswitch Positions
The keyswitch labels can be in English or international versions as shown in Figure 3-11. Table 3–3 Keyswitch Positions Position Effect Removes 48 VDC power from the system. Power is still supplied to the Disable CCL module. This switch is useful for field service when they wish to power down the system in an orderly way, prior to switching the power off completely while replacing or installing a new piece of hardware.
Page 72: Control Panel Indicator Lights
3.6.2 Control Panel Indicator Lights The control panel has three status indicator lights: Key On, Run, and Fault. These lights indicate the operating status of the system. Figure 3-12 Control Panel Indicator Lights Disable Secure Front Enable Restart Key On Fault BX0512-94 3-24 AlphaServer 8200/8400 Operations Manual...
Page 73: Control Panel Indicator Lights
Three status indicator lights (see Figure 3-12) show the state of the system: (Key On) DC power supplied, (Run) execution, and (Fault) errors. Table 3–4 describes the conditions indicated by the lights. Table 3–4 Control Panel Indicator Lights Light Color State Meaning Key On...
Page 74: Circuit Breaker And Ac Power Indicators
3.6.3 Circuit Breaker and AC Power Indicators The circuit breaker is located on the left side of the rear of the system cabinet, just above the blower assembly. With three–phase power, the circuit breaker can be secured in the off position with a lock. Figure 3-13 Circuit Breaker and AC Power Indicators Single-Phase Power Rear...
Page 75 The circuit breaker and power indicators are at the rear of the cabinet. Circuit Breaker The circuit breaker controls power to the entire system, including the power regulators, blower, battery backup, and in-cabinet options. Current overload causes the breaker to trip to the off position, so that power to the system is turned off.
Page 77: Chapter 4 I/O Subsystems
Chapter 4 I/O Subsystems This chapter describes the AlphaServer 8200 and AlphaServer 8400 I/O subsystems. Sections include: • I/O Subsystem Overview • I/O Port Modules • System Configuration Information • PCI Adapter • KFE70 and KFE72 Adapters • EISA Configuration Utility I/O Subsystems 4-1...
Page 78: I/O Subsystem Overview
4.1 I/O Subsystem Overview Figure 4-1 illustrates CPU, memory, and I/O port module (KFTHA and KFTIA) interfaces to the system bus. Figure 4-1 I/O Subsystem System Bus CPUs Memory KFTHA KFTIA (Integrated PCI bus) Hose Hose Hoses 3 FWD SCSI Ports 1 SE SCSI Port I/O Bus 1 FDDI Port (optional)
Page 79 The interface from the AlphaServer 8200 and 8400 system bus to I/O is provided by two types of I/O adapter modules, the KFTHA and the KFTIA. The KFTHA has four channels, or hoses, to connect to I/O devices (see Figure 4-1). The KFTIA has one internal hose (an integrated PCI bus) and one hose to connect to external I/O.
Page 80: I/O Port Modules
4.2 I/O Port Modules The KFTHA module has four channels, or “hoses,” to external I/O subsystems such as the PCI bus (for any 8200 system and 8400 systems with Windows NT), or the PCI, Futurebus+, and XMI buses (for 8400 systems with OpenVMS or DIGITAL UNIX).
Page 81 KFTHA The KFTHA module is designed for high-speed, high-volume data transfers. The KFTHA has four channels (called hoses) connecting (see Figure 4-2) to external I/O buses. Each I/O bus may be a PCI bus (for 8200 systems and 8400 systems with Windows NT systems), or a PCI, Futurebus+, or XMI bus (for 8400 systems with OpenVMS or DIGITAL UNIX).
Page 82: System Configuration Information
4.3 System Configuration Information Basic information on the system and I/O subsystem configuration is displayed on power-up. Example 4-1 shows an AlphaServer 8400 system self-test display. Example 4-1 System Self-Test Display NODE # + ++ . EB + ++ . EB + ++ .
Page 83: Hose Numbering Scheme For Kftia And Kftha
On power-up, the console displays the self-test results. (Chapter 6 describes the system self-test in detail.) The AlphaServer 8400 system shown in Example 4-1 has one dual-CPU module in node (slot) 0 of the TLSB card cage, one 256-megabyte memory module in slot 1, and two I/O adapters, located in slots 7 and 8. The I/O adapter in slot 7 is a KFTHA and in slot 8 , a KFTIA.
Page 84 Example 4-2 Sample Show Configuration Command for a DIGITAL UNIX or OpenVMS System with a KFE70 P00>>> show config Name Type Rev Mnemonic TLSB KN7CF-AB 8014 0000 kn7cf-ab0 MS7CC 5000 0000 ms7cc0 KFTHA 2000 0D02 kftha0 KFTIA 2020 0000 kftia0 C0 Internal PCI connected to kftia0 pci0 ISP1020...
Page 85 The SRM console command show configuration displays system configuration information detailing the I/O adapters connected to your system and their status. Example 4-2 shows a display for an 8400 running either OpenVMS or DIGITAL UNIX (since XMI and Futurebus+ buses are included). The information is displayed in five columns: module slot number module name...
Page 86 Example 4-2 Sample Show Configuration Command for a DIGITAL UNIX or OpenVMS System (Continued) C4 XMI connected to kftha0 xmi0 DEMNA 0803 demna0 DEMFA 0514 demfa0 DWLMA 102A 020A dwlma0 KZMSA 5256 kzmsa0 C7 PCI connected to kftha0 pci1 4828086 0003 KZPSA 8101...
Page 87 The KFTHA module in TLSB slot 8 has an XMI PIU attached to its first hose (C4) . The are four modules in the XMI card cage: • Slot 1 - DEMNA - Ethernet controller • Slot 3 - DEMFA - FDDI controller •...
Page 88 Example 4-3 Sample Show Configuration Command for a System with a KFE72 P08> show config Name Type Mnemonic TLSB KN7CD-AB 8014 0000 kn7cd-ab0 MS7CC 5000 0000 ms7cc0 KFTHA 2000 0000 kftha0 C0 PCI connected to kftha0 pci0 DEC PCI FDDI F1011 0000 pfi0...
Page 89 Example 4-3 shows a sample show config SRM command for an AlphaServer 8200 configured with a KFE72 adapter, providing support for a graphics monitor, keyboard and mouse, serial and parallel ports. The processor module is located in TLSB slot 4, the lowest-numbered slot on an 8200.
Page 90: Show Device Command
Example 4-4 Sample Show Device Command P00>>> show dev polling for units on kzmsa0, slot 14, bus 0, xmi0... dkb100.1.1.14.0 DKB100 RZ26L 440C dkb200.2.1.14.0 DKB200 RZ26L 440C dkb300.3.1.14.0 DKB300 RZ26L 440C polling for units on floppy0, slot 0, bus 1, hose3... dva0.0.0.1100.3 DVA0 RX26...
Page 91 The SRM command show device is useful for locating the boot device for the Loadable Firmware Utility, or the boot device for the operating system for OpenVMS or DIGITAL UNIX systems. The show device command is also helpful in isolating non-functioning I/O devices detected by a test command.
Page 92: Pci Adapter
4.4 PCI Adapter The PCI adapter, DWLPA/DWLPB, provides a complete PCI bus subsystem for use with the AlphaServer 8200 and 8400 systems. The KFE70 adapter provides PCI/EISA capability on the DWLPA/DWLPB. The KFE72 adapter provides I/O output needed for systems using a graphics device and must connect to a DWLPB adapter.
Page 93 If a PCI shelf has neither a KFE70 or KFE72, it contains 12 slots for PCI adapters. numbered right-to-left from 0 to 11. Configurations with a KFE70 The KFE70 consists of two modules. With OpenVMS and DIGITAL UNIX, the KFE70 adapter provides I/O for the floppy device in the system cabinet, and provides the capacity for EISA options.
Page 94: Kfe70 And Kfe72 Adapters
4.5 KFE70 and KFE72 Adapters The KFE70 adapter contains two modules and supplies EISA capability and a floppy I/O port for the in-cabinet load device (see Figure 4-6). The KFE72 provides I/O support for systems with a graphics console device (see Figure 4-7). Figure 4-6 KFE70 Modules Floppy Unused...
Page 95 KFE70 Adapter The KFE70 adapter contains two modules: the standard I/O module (part number B2110-AA) and a connector module (part number 54-23491-01) supplying floppy, keyboard, and mouse ports (see Figure 4-6). The keyboard and mouse ports are not supported. The KFE70 also provides EISA support for DIGITAL UNIX and OpenVMS systems, as described in Section 4.4.
Page 96: Eisa Configuration Utility
4.6 EISA Configuration Utility There are two reasons for running ECU. On OpenVMS or DIGITAL UNIX systems, run ECU from the SRM console whenever you add, remove, or move an EISA board in your system. For Windows NT, you run ECU from AlphaBIOS Setup to initialize NVRAM on the standard I/O module after installation of a KFE72.
Page 97 The EISA Configuration Utility (ECU) is supplied on the system configuration diskette shipped with the KFE70 and KFE72 adapters. How ECU Is Used with OpenVMS or DIGITAL UNIX Systems You need to run ECU from the SRM console whenever you add, remove, or move an EISA board in your system.
Page 99: Chapter 5 Booting An Operating System
Chapter 5 Booting an Operating System This chapter describes how to boot the OpenVMS, DIGITAL UNIX, and Windows NT operating systems on AlphaServer 8200/8400 systems. Sections include: • Preparation • Selecting a Boot Device • Booting OpenVMS • Booting DIGITAL UNIX •...
Page 100: Preparation
5.1 Preparation There are some steps you must take preparatory to booting and other steps that can make booting thereafter easier. 5.1.1 Set os_type Environment Variable For factory-installed software (FIS), a default operating system is defined. If you do not have factory-installed software, or you wish to change the default operating system, you use the set os_type command.
Page 101: Set Console Environment Variable
5.1.2 Set console Environment Variable For Windows NT systems, you must set the console environment variable to both. For OpenVMS systems and DIGITAL UNIX systems, the console environment variable should be set to serial (the default). Example 5-4 Set Console to Serial for DIGITAL UNIX and OpenVMS Systems P00>>>...
Page 102: Set Auto_Action Environment Variable
5.1.3 Set auto_action Environment Variable You can direct the SRM console to automatically boot the operating system upon system power-up, Restart, or init. The default is to halt the system after system self-test and leave the console device in SRM console mode. Example 5-6 Setting the auto_action Environment Variable P00>>>...
Page 103 The auto_action environment variable is set to halt by default. In this case, at system restart (power-up, reset, or init command), the SRM console software will display the system self-test and display the SRM console prompt to accept commands. If you set the auto_action environment variable to boot, at system restart, the SRM console software will display the system self-test and then automatically boot the operating system according to the default boot parameters you defined.
Page 104: Selecting A Boot Device
5.2 Selecting a Boot Device The OpenVMS, DIGITAL UNIX, and Windows NT operating systems can be booted from a number of devices: the CD-ROM drive, a local system disk, a disk connected to the system through a CIXCD/CIPCA adapter, or by Ethernet from a remote disk on another system.
Page 105: Boot Devices
For systems with factory-installed software (FIS), a default boot device (OpenVMS or DIGITAL UNIX) or boot path (Windows NT) has already been selected for you. If you want to change this default, follow the instructions here. NOTE: The default boot device or boot path selected applies to the operating system. If you wish to boot the Loadable Firmware Update (LFU) utility, you must specify the CD-ROM device on your system, if you use the SRM console boot command.
Page 106 5.2.1 Show Config and Show Device Commands (for Booting OpenVMS and DIGITAL UNIX Systems) If you do not wish to use the default boot device selected for factory-installed OpenVMS or DIGITAL UNIX systems, the show config and show device SRM console commands display your system configuration, allowing you to identify and select an appropriate boot device.
Page 107 Example 5-7 Show Config and Show Device Commands (Continued) dkb300.3.0.7.1 DKB300 RZ28M 0568 dkb400.4.0.7.1 DKB400 RZ28M 0568 dkb600.6.0.7.1 DKB600 RZ28M 0568 polling for units on kzpsa2, slot 9, bus 0, hose1... kzpsa2.7.0.9.1 TPwr 1 Fast 1 Bus ID 7 dkc200.2.0.9.1 DKC200 RZ28M 0568...
Page 108 Table 5-2 SRM Console Device Naming Conventions Field Meaning Description Device driver Two-letter designator for a port or class device driver. Usually one of: dk SCSI disk fw FDDI network dr RAID set disk mk SCSI tape du DSSI disk mu DSSI tape dv Floppy disk pk SCSI class...
Page 109 5.2.2 Boot Environment Variables (for OpenVMS and DIGITAL UNIX) With OpenVMS or DIGITAL UNIX systems, you can change the factory-installed default boot device, or, if your operating system is not factory-installed, define a default boot device, to be used automatically if no device is specified in the boot command itself.
Page 110: Boot Path For Windows Nt Systems
5.2.3 Boot Path for Windows NT Systems Multiple versions of the Windows NT operating system may be available for booting on your system. One is defined as the primary operating system, which is booted by default. You can select a different operating system for booting from the boot screen, displayed after AlphaBIOS is started.
Page 111 You use the AlphaBIOS firmware to boot a Windows NT system (the SRM command boot does not apply to Windows NT systems). Figure 5-2 shows an AlphaBIOS boot screen where the primary operating system will be booted within a specified amount of time. You can use the arrow keys to select another of the installed operating systems, if any, during this time.
Page 112: Booting Openvms
5.3 Booting OpenVMS Check the environment variables for default boot parameters and make any changes needed. Issue the boot command. Example 5-9 OpenVMS Boot P00>>> show boot* boot_dev boot_file boot_osflags boot_reset bootdef_dev booted_dev booted_file booted_osflags P00>>> set bootdef_dev dkb100 P00>>> show boot* boot_dev boot_file boot_osflags...
Page 113 Example 5-1 OpenVMS Boot (Continued) 6-JAN-1998 11:36:18.27 OpenVMS (TM) Alpha Operating System, Version V7.1 [more informational messages specific to the site] Accounting information: Buffered I/O count: 79521 Peak working set size: 6080 Direct I/O count: 4042 Peak virtual size: 173104 Page faults: 4845 Mounted volumes:...
Page 114: Booting Digital Unix
5.4 Booting DIGITAL UNIX Use the show boot* command to ensure that the device from which to boot the operating system, and other boot parameters, are correct. Issue the boot command. Example 5-10 DIGITAL UNIX Boot P00>>> show boot* boot_dev dkc300.3.0.7.1 boot_file boot_osflags...
Page 115 Type the show boot* command to show the current settings for boot environment variables. If you wish to change anything, use the appropriate set command to make the change. Type the boot command. The DIGITAL UNIX operating system boots, displays the system banner, and prompts the user for login information.
Page 116: Booting Windows Nt
5.5 Booting Windows NT Microsoft Windows NT is started from the AlphaBIOS Boot screen. 5.5.1 Effect of SRM Console auto_action Environment Variable The way you boot Windows NT depends upon how the SRM console auto_action environment variable is set. Figure 5-3 AlphaBIOS Boot Screen with Auto Start Disabled AlphaBIOS Version 5.35 Please select the operating system to start: Windows NT Server 4.0...
Page 117 Once you have installed a Windows NT system (see Chapter 8), the Windows NT operating system is booted from the AlphaBIOS firmware. How this firmware is started depends on the setting of the SRM console’s auto_action environment variable (see Table 5-3) and the setting of the Auto Start and Auto Start Count options in the CMOS Setup screen of AlphaBIOS Setup.
Page 118: Effect Of Alphabios Auto Start And Auto Start Count Options
5.5.2 Effect of AlphaBIOS Auto Start and Auto Start Count Options Booting Windows NT also depends upon the Auto Start, Auto Start Count, and Password options of the AlphaBIOS CMOS Setup screens. Figure 5-4 AlphaBIOS Boot Screen with Auto Start Enabled AlphaBIOS Version 5.35 Please select the operating system to start: Windows NT Server 4.0...
Page 119 AlphaBIOS allows multiple versions of the Windows NT operating system to be installed. A primary operating system is designated during installation (see Section 8.9) as the default. The action taken before booting proceeds depends upon the setting of three AlphaBIOS options from the CMOS Setup and Advanced CMOS Setup screens.
Page 120: Effect Of Alphabios Password Option
5.5.3 Effect of the AlphaBIOS Password Option If Startup Password in the AlphaBIOS Password Option in the Advanced CMOS Setup has been selected, you will have to enter a password before Windows NT will boot. If Setup Password in the AlphaBIOS Password Option has been selected, Windows NT will boot according to the SRM console and AlphaBIOS Auto Start options described in Section 5.5.1 and 5.5.2, but you will be asked for a Setup password if you press F2 to select AlphaBIOS Setup.
Page 121 You can enable the Setup Password option of the Advanced CMOS Setup screen of AlphaBIOS to limit access to AlphaBIOS Setup mode, but allow booting of the operating system. You can enable the Startup Password option of the Advanced CMOS Setup screen of AlphaBIOS to limit access to AlphaBIOS Setup and operating system booting.
Page 123: Chapter 6 System Troubleshooting
Chapter 6 System Troubleshooting This chapter describes system problems and their symptoms during power- up, booting, and normal operation. Advanced troubleshooting is discussed in the Service Manual. Topics discussed include: • Troubleshooting During Power-Up • Troubleshooting During Booting • Troubleshooting a PCI Shelf •...
Page 124: Troubleshooting During Power-Up
6.1 Troubleshooting During Power-Up Figure 6-1 shows the power-up sequence and steps to take if a problem occurs. Figure 6-1 Power-Up Troubleshooting Flowchart Power-On Check Power and Self-Test Console Terminal Starts Self-Test Completes Troubleshoot System Passes Failed Module Self-Test Console Prompt P00>>>...
Page 125: Power-Up Troubleshooting Steps
Troubleshooting steps during power-up are described in Figure 6-2. Figure 6-2 Power-Up Troubleshooting Steps Check Power and Are the power regulator Run lights on? If no: Console Terminal Is the AC power cord plugged in? Is the circuit breaker in the On position? Check for air blockage at the top of the cabinet.
Page 126: Boot Devices
6.2 Troubleshooting During Booting (OpenVMS and DIGITAL UNIX) When booting fails for an OpenVMS or DIGITAL UNIX system, you can check several parameters. Figure 6-3 shows the boot sequence. Figure 6-4 shows the steps to take if a problem occurs during booting. If you are unable to correct the problem, call your DIGITAL customer service engineer.
Page 127 Figure 6-4 Troubleshooting Steps During Booting Check Boot Specifi- cation and Boot Device Check the boot status message. Is the correct boot device specified? Check that the boot device specified is listed in the console display. If the boot device is not listed, check all physical connections.
Page 128: Troubleshooting A Pci Shelf
6.3 Troubleshooting a PCI Shelf LEDs show the status of power supplies as well as the adapter self-test results in the PCI shelf, mounted vertically in the AlphaServer 8400 and horizontally in the AlphaServer 8200. Figure 6-5 PCI Shelf in a BA655 PIU Hose 48V Power DWLPA/...
Page 129: Pci Shelf In An 8200
Figure 6-6 PCI Shelf in an 8200 DWLPA/DWLPB LED numbers BX-0174-95 Figure 6-7 Troubleshooting Steps for PCI Shelf Check Cabling to PCI shelf. LED 3 lit Check to make sure the clip connectors are engaged properly. If so, proceed to Check 48V Power Supply.
Page 130: Troubleshooting An Xmi Plug-In Unit
6.4 Troubleshooting an XMI Plug-In Unit You can perform several checks if you suspect a problem with an XMI plug-in unit. See Figure 6-8. If you are unable to correct the problem, call your DIGITAL customer service engineer. Figure 6-8 Troubleshooting an XMI Plug-In Unit Check the XMI Power Regulators Is the 48V light on?
Page 131: Sample Self-Test Display, Failing Dwlma Adapter
In Example 6-1, an initialize command is issued, causing a system reset and self-test. Self-test results indicate a failing DWLMA adapter. See Section 6.10 for more information on the self-test display. Example 6-1 Sample Self-Test Display, Failing DWLMA Adapter P00>>> initialize # Resets the entire system.
Page 132: Troubleshooting A Futurebus+ Plug-In Unit
6.5 Troubleshooting a Futurebus+ Plug-In Unit You can perform several checks if you suspect a problem with a Futurebus+ plug- in unit. If the 48V LED indicates a power problem, refer to Figure 6-9. If the MOD OK LED indicates a problem, see Figure 6-10. If you are unable to correct the problem, call your DIGITAL customer service engineer.
Page 133: Fbus+ Piu Troubleshooting - Mod Ok Led Off
Figure 6-10 FBUS+ PIU Troubleshooting – MOD OK LED Off MOD OK MOD OK RESET V-OUT DISABLE ENABLE Front Both MOD OK LEDs Off Check that the DISABLE/ENABLE switch is in the ENABLE position (down). Check the CCL-to-PIU cabling. Only one MOD OK LED Replace that regulator.
Page 134: Troubleshooting A Ba655 Plug-In Unit
6.6 Troubleshooting a BA655 Plug-In Unit SCSI indicator LEDs are located on each disk drive and power supply. Table 6-1 and Table 6-2 list the functions of the LEDs shown in Figure 6-11. Figure 6-11 SCSI Indicator LEDS Shelf 2 Shelf 1 Front Disk...
Page 135: Scsi Disk Drive
Table 6-1 SCSI Disk Drive LEDs Indicator LED LED State Meaning Green No activity Flashing Activity Activity Yellow Normal Flashing Spinup/spin down Not used Table 6-2 SCSI Power Supply LEDs Indicator LED LED State Meaning Green (left) Shelf fault Shelf OK Green (right) Power fault Power OK...
Page 136: Troubleshooting A Battery Plug-In Unit
6.7 Troubleshooting a Battery Plug-In Unit The H7237 battery PIU houses one to three battery blocks, each providing backup power to one H7263-AA/AB power regulator. The battery PIU is installed in the bottom of the system or expander cabinet (8400 with three-phase power and H7263-AA/AB power regulators only).
Page 137: Show Power Command
The show power command is used to see the status of the power system (AlphaServer 8400 system with three-phase power only). Example 6-2 Show Power Command P00>>> show power Cabinet: Main Regulator: ------------------------------------------------------------------------ Primary Micro Firmware Rev : Secondary Micro Firmware Rev : Power Supply State : NORMAL NORMAL NORMAL AC Line Voltage (V RMS) :...
Page 138: Self-Test Overview
6.8 Self-Test Overview The system provides a record of its testing in the self-test display. The control panel Fault light and the module self-test LEDs also indicate success or failure. Figure 6-13 Determining Self-Test Results Enable Key On Fault Fault Front Front Rear...
Page 139 Following power-up and system reset, the system performs testing. Self-test results are indicated by the following: • Fault light on the control panel • Self-test LEDs on the modules • Self-test display During system self-test, the yellow Fault light on the control panel lights. If a module fails self-test, the Fault light remains lit.
Page 140: Testing Sequence
6.9 Testing Sequence The self-test display shows the results of system self-test. The pass (+) or fail (–) status of each module is indicated. Dual-processor modules report the status of each CPU. The first self-test display in the following example is for an AlphaServer 8400;...
Page 141 During the first round of testing each module runs its own self-test and the results are shown on the ST1 line. The boot processor is then determined (indicated by a B on the first BPD line). This processor then generates the results of testing to this point ( ). If one processor on a dual-CPU module fails self-test (ST1), the failing CPU is displayed as a minus under the node # (for example, –...
Page 142: Sample Self-Test Display
6.10 Sample Self-Test Display The primary processor reports the results of self-test. Results are displayed on the console terminal, as shown in Example 6-4, for an AlphaServer 8400. With an AlphaServer 8200, however, nodes 0 through 3 on the self-test display do not apply (see Section 2.5.1 and the second part of Example 6-3).
Page 143: System Configuration For Example 6-4
The self-test display reflects the system configuration listed in Table 6-3 and Table 6-4. Each numbered item in the example is explained in Section 6.11 through Section 6.15. These sections assume the same system configuration (see Section 6.16.1 for the results of the show configuration command for this example). Table 6-3 System Configuration for Example 6-4 TLSB Module...
Page 144: Self-Test Lines Node# And Typ
6.11 Self-Test Lines NODE# and TYP The first two lines of the self-test printout provide the node number identification (NODE #) and the type of module (TYP). Example 6-5 Self-Test Results: Node # and TYP 0 NODE # P TYP + ++ ++ ST1 .
Page 145 The NODE # line lists the node numbers on the TLSB and I/O buses. The nodes on this line are numbered in hexadecimal. Note that TLSB entries use nodes 0 through 8 (the 8400 TLSB has 9 slots). Nodes 4 through 8 are used for the AlphaServer 8200.
Page 146: Self-Test Lines St And Bpd
6.12 Self-Test Lines ST and BPD The next six lines of the self-test display provide test information on the processors (ST1, ST2, and ST3) and boot processor designation (BPD). Example 6-6 Self-Test Results: ST and BPD 0 NODE # P TYP + ++ ++ ST1 .
Page 147 The ST1 line shows the results of self-test. The entries are: • ++ (dual processor) • + (pass) • – (fail) • o (does not apply) NOTE: If a uniprocessor fails self-test (ST1) in a multiprocessor system or if both CPUs fail on a dual-processor module, there is no indication of the failure in the self-test display.
Page 148: Self-Test Lines C0, C1, C2
6.13 Self-Test Lines C0, C1, C2, ... Cn The I/O channel lines (C0, C1, C2, ...) of the self-test display provide information on the node numbers and self-test status for modules in the I/O subsystems, which are connected to the system bus. Example 6-7 Self-Test Results: C0, C1.
Page 149 The I/O channel lines (C0, C1, C2, ...) indicate the: • I/O channel that connects the I/O adapter bus to the system bus • DWLMA adapter self-test results • XMI adapters’ self-test results • PCI adapters’ self-test results • Internal PCI self-test results •...
Page 150: Self-Test Lines Ilv And Mb
6.14 Self-Test Lines ILV and MB The ILV line details the interleaving of the memories, and the MB line gives the Mbytes of each memory module and the total size of the system memory. Example 6-8 Self Test Results: ILV and MB 0 NODE # P TYP + ++...
Page 151 The ILV line contains a memory interleave value (ILV) for each memory. The default memory configuration algorithm attempts to maximize memory interleaving; arrays on a single memory module are interleaved by default. In Example 6-8, the memory modules at nodes 2 and 6 are each in a two-way system internal interleave (they are not interleaved with each other).
Page 152: Self-Test Identification Line
6.15 Self-Test Identification Line The last line of the self-test display gives the firmware revision numbers, the SROM revision numbers, and the date and time stamp of the console. Example 6-9 Self-Test Results: Identification Line 0 NODE # P TYP + ++ ++ ST1 .
Page 153 In Example 6-9, the primary processor indicates the version of the console firmware. The date and time stamp indicates the production date of the running console. The SROM Rev information indicates the primary processor’s serial ROM version. The serial ROM contains the first level of console, diagnostic, and bootstrap code.
Page 154: Show Commands
6.16 Show Commands To get system information for OpenVMS or DIGITAL UNIX systems, you can use the SRM commands show configuration, show network, or show device. The show command output identifies the subsystem, module, or device you may want to test. The following sections explain the show command output. 6.16.1 Show Configuration Enter a show configuration command to display the system hardware configuration.
Page 155 Example 6-10 Sample System Hardware Configuration (Continued) C4 XMI connected to kftha0 xmi0 DWLMA 102A 020A dwlma0 C7 PCI connected to kftha0 pci1 4828086 0003 sio0 KZPSA 8101 0000 kzpsa0 KZPSA 8101 0000 kzpsa1 DAC960 11069 0000 dac0 Controllers on SIO sio0 DECchip 21040-AA 21011...
Page 156: Show Network
6.16.2 Show Network Enter a show network command to display network devices. Example 6-11 Sample Output of Show Network Command P00>>> show network polling for units on demna0 ,slot 1, xmi0... exa0.0.0.1.0: 08-00-2B-27-D7-96 polling for units on demna1 ,slot 2, xmi1... exb0.0.0.2.1: 08-00-2B-27-D7-BB polling for units on tulip0, slot 2, bus 0, hose0...
Page 157 In Example 6-11, the operator enters a show network command to show the network adapters in the system. The first DEMNA adapter is identified by the demna0 mnemonic. This DEMNA adapter is in slot 1 of the I/O card cage connected to I/O channel 0. The unit number for demna0 is exa0.0.0.1.0.
Page 158: Show Device
6.16.3 Show Device Enter a show device command to display system devices. Example 6-12 Sample Output of Show Device Command P00>>> show device polling for units on kzmsa0, slot 14, bus 0, xmi0... dkb100.1.1.14.0 DKB100 RZ26L 440C dkb100.2.1.14.0 DKB200 RZ26L 440C dkb100.3.1.14.0 DKB300...
Page 159 In Example 6-12, the operator enters a show device command to show all disks and tapes supported by the system. The first adapter polled is the KZMSA with the mnemonic kzmsa0. This KZMSA is located in slot 14 of the XMI card cage. The bus number is 0. Device information is displayed.
Page 160: Test Command
6.17 Test Command You can use the test command to test the entire system, an I/O subsystem, a module, a group of devices, or a specific device. Enter a show configuration command to see a list of the subsystems and devices that you may want to test. Examples of the test command are shown in the following sections.
Page 161: Test Command Environment Variables
Two helpful test command options are outlined in Table 6-5. Environment variables commonly used with test are listed in Table 6-6. Table 6-5 Test Command Options Option Meaning Specifies the test run time in seconds. For a system test the default -t <value>...
Page 162: Testing The System
6.17.1 Testing the System To test the entire system (except for memory), enter the test command. Example 6-14 Sample Test Command, System Test P00>>> test -t 180 Configuring system... Testing system... Type Ctrl/C to abort Starting network exerciser on exa0.0.0.4.0 in external mode (id #62) Starting network exerciser on exb0.0.0.5.0 in external mode (id #63) Starting network exerciser on exc0.0.0.4.1 in external mode (id #64) Starting device...
Page 163 In Example 6-14: At the console prompt, the operator enters a test -t 180 command. The option -t specifies a system test run time of 180 seconds. To stop execution of the test command before normal completion, use Ctrl/C (^C). Termination using ^C may take a number of seconds depending upon the particular configuration being tested.
Page 164: Testing A Subsystem
6.17.2 Testing a Subsystem To test a portion of the system, such as an I/O subsystem, enter the test command and the I/O subsystem mnemonic. I/O subsystem mnemonics are displayed when you enter a show configuration command. Example 6-15 Sample Test Command, I/O Subsystem Test P00>>>...
Page 165 At the console prompt, the operator enters a test xmi0 command to test all adapters and I/O devices on the XMI I/O bus. The status message indicates that the DWLMA adapter passes all tests. Next, the adapters in the XMI card cage are initialized. All XMI adapters pass self-test.
Page 166: Testing A Module Or Devices
6.17.3 Testing a Module or Devices To test a processor, memory module, or an I/O adapter and its associated devices, enter the test command and the correct mnemonic. Mnemonics are displayed when you enter a show configuration or a show device command. Example 6-16 Sample Test Command, I/O Adapter Test P00>>>...
Page 167: Sample Test Command, Memory Module Test
Example 6-17 Sample Test Command, Memory Module Test P00>>> test ms7cc0 Testing ms7cc0 Type Ctrl/C to abort Starting memory exerciser, running on kn7ce0 (id #77) Stopping memory exerciser on kn7ce0 (id #77) Done testing... P00>>> In Example 6-17: Enter test ms7cc0. The ms7cc0 memory module is tested by the memory exerciser, a series of tests executed from the processor module.
Page 168: Sample Test Command, Testing Devices
Example 6-18 Sample Test Command, Testing Devices P00>>> test kz* Device adapter test selected for runtime of 120 seconds Type ^C to stop testing Self-test passed on device kzmsa0 Configuring kzmsa0 polling for units on kzmsa0, slot 14, bus 0, xmi0... dkb0.0.1.14.0 DKB0 RZ26L...
Page 169 In Example 6-18: At the console prompt, the operator enters test kz*. The wildcard entered will test all "kz" devices. Not enough time to test devices, so this status message is displayed. Testing is stopped, drivers halted, and the console prompt returns. System Troubleshooting 6-47...
Page 170: Testing Network Adapters
Example 6-19 Testing Network Adapters P00>>> set d_report full P00>>> test demna0 Console is in diagnostic mode Network adapter test selected for runtime of 120 seconds Initializing demna0 Waiting for self tests to complete... Self-test passed on device demna0 Configuring demna0 polling for units on demna0, slot 2, bus 0, xmi0...
Page 171 This command requests an extended report format for following tests. The demna is the network adapter for an XMI bus. The full test is conducted and displayed. When the time allotted expires, testing stops. This command requests that full tracing for the test be omitted. Note that the listing following at does not “trace”...
Page 172: Error Reports
6.18 Error Reports In the event of an error, either a summary or a full error report is displayed at the console. Error reports are specified by setting the d_report environment variable. See Example 6-20 and Example 6-21. Example 6-20 Sample Summary Error Report P00>>>...
Page 173 In Example 6-20: Testing begins on each disk. A hard error, error #1, is reported on FRU duc4.0.0.12.0, a disk associated with the kzmsa adapter. The three types of errors reported are hard, soft, and fatal. The error number, in this case error #1, corresponds to the location of the actual error report call within the source code for the failing diagnostic.
Page 174: Sample Full Error Report
Example 6-21 Sample Full Error Report P00>>> set d_report full # Command to set the type of # error report to full. P00>>> test demna0 # Command to test the DEMNA # adapter with the mnemonic # demna0. Console in diagnostic mode Network adapter test selected for runtime of 120 seconds Initializing demna0 Waiting for self-test to complete .
Page 175 NOTE: Except for the extended error information shown in Example 6-21, the information shown in a full and a summary error report is the same. See Example 6-20 for a description of the common error report entries. In Example 6-21: This full error report shows a list of addresses and the expected and received data values for each address.
Page 177: Srm Console Commands
Chapter 7 SRM Console Commands This chapter describes the SRM console program’s command language, console special characters, console environment variables, and console commands. Sections in this chapter include: • Overview • SRM Command Syntax • SRM Console Special Characters • SRM Console Environment Variables •...
Page 178: Overview
7.1 Overview The SRM console firmware has evolved to provide capabilities for the three operating systems offered with DIGITAL AlphaServer 8200 and 8400 systems. Figure 7-1 SRM Console Command and Feature Breakdown OpenVMS and Windows NT DIGITAL UNIX build clear create date boot...
Page 179 For OpenVMS and DIGITAL UNIX systems, SRM console commands allow you to boot the OpenVMS and DIGITAL operating systems, display the configuration, and verify the system. The control character Ctrl/P allows you to halt the operating system and return to SRM console mode; the SRM command continue will then restart the operating system where it left off.
Page 180: Srm Command Syntax
7.2 SRM Command Syntax The SRM console command language has syntax rules for forming commands. Commands can contain up to 80 characters on a single line, can be abbreviated, and accept options. Tabs and spaces are compressed. Table 7-1 SRM Console Command Language Syntax Command Parameter Attribute or Action Length...
Page 181 Length: The SRM console program accepts commands of up to 255 characters. This does not include the terminating carriage return or any characters deleted as the command is entered. A command longer than 80 characters, without the backslash character (see Section 7.2) causes the display of an error message. Case: Upper- or lowercase characters can be used for input.
Page 182: Srm Console Special Characters
7.3 SRM Console Special Characters The console program supports control characters, entered by holding down the Control (Ctrl) key and pressing the desired key, and other special characters. Table 7-2 SRM Console Special Characters Character Function Return Carriage return; ends a command line. Backslash Line continuation.
Page 183 Table 7–2 SRM Console Special Characters (Continued) Character Function Ctrl/Q Resume output to console terminal. Ctrl/R Redisplay the current line. Ctrl/S Stop output to console terminal. Ctrl/U Delete entire line. Wildcarding for certain commands. “ “ Quotes for set environment variable name. Comment specifier.
Page 184 Output is also reenabled when the console prompts for a command, issues an error message, enters program mode, or when Ctrl/P is entered. It is not reenabled by displaying a repeat command. Ctrl/P works like Ctrl/C and is echoed as ^C, if the console terminal is in SRM console mode.
Page 185: Srm Console Environment Variables
7.4 SRM Console Environment Variables Console environment variables allow the user to modify the way the console commands operate. An environment variable is a name and value association maintained by the console program. The value associated with an environment variable is an ASCII string (up to 127 characters in length) or an integer.
Page 186: Environment Variables
Table 7-3 Environment Variables Variable Attribute Function arc_enable Nonvolatile Enables you to issue to run and runecu commands for OpenVMS and DIGITAL UNIX systems. Default value is off. auto_action Nonvolatile Specifies the action the console will take following an error halt or power-up. Values are: restart - For OpenVMS and DIGITAL UNIX systems, automatically restart.
Page 187 Table 7-3 Environment Variables (Continued) Variable Attribute Function boot_reset Nonvolatile For OpenVMS and DIGITAL UNIX systems, the default file name used for the primary bootstrap when no file name is specified in the boot command. Not used with Windows console Nonvolatile Defines the type of console device.
Page 188 Table 7-3 Environment Variables (Continued) Variable Attribute Function enable_audit Nonvolatile If set to on (default), enables the generation of audit trail messages. If set to off, audit trail messages are suppressed, Console initialization sets this to on. ew*0_loop_count Nonvolatile Specifies the number of times each message is looped for a test command exercising a PCI network adapter.
Page 189 Table 7-3 Environment Variables (Continued) Variable Attribute Function interleave Nonvolatile Specifies interleave arrangement for memory modules. Defined values are: DEFAULT The SRM console decides how to interleave memories. NONE Memory modules are not interleaved. os_type Nonvolatile Used to store operating system type that user will be operating under.
Page 190: Srm Console Commands
7.5 SRM Console Commands Console commands provide the capabilities to examine and modify system state. Additionally, they allow tests to be directed to functional components of the system. 7.5.1 AlphaBIOS (for Windows NT only) The alphabios command is used to enter the AlphaBIOS firmware, either to boot the Windows NT operating system, or to use the AlphaBIOS Setup menus.
Page 191: Boot Command
7.5.2 Boot The boot command boots the DIGITAL UNIX and OpenVMS operating systems, and the Loadable Firmware Update (LFU) utility. See Section 5.5 for information on booting Windows NT systems. Example 7-2 Boot Command P00>>> show boot* boot_dev dkc300.3.0.7.1 boot_file boot_osflags boot_reset bootdef_dev...
Page 192: Building The Eeprom
7.5.3 Building the EEPROM The build -e command is used to initialize a module’s EEPROM during installation or to restore a corrupted serial EEPROM image. Example 7-3 Building the EEPROM P00>>> build -e # Initialize the EEPROM # on kn7cf. Build EEPROM on kn7cf-ab0? [Y/N]>...
Page 193: Building The Nonvolatile Ram
7.5.4 Building the Nonvolatile RAM The build -n command is used to initialize the CPU’s nonvolatile RAM (NVR). Example 7-4 Building the Nonvolatile RAM P00>>> build -n Build NVR on kn7cd-ab0? [Y/N]Y NVR built on kn7cd-ab0 P00>>> The build -n command syntax is: bu[ild] -n <device>...
Page 194: Building The Seeprom
7.5.5 Building the SEEPROM The build -s command is used to restore a module’s corrupted serial EEPROM. Example 7-5 Building the SEEPROM P00>>> build -s ms7cc0 # Initialize the serial # EEPROM on ms7cc0. Build serial EEPROM on ms7cc0? [Y/N]> Y This program will take at most several minutes Serial EEPROM built on ms7cc0 P00>>>...
Page 195: Clear Eeprom
7.5.6 Clear EEPROM The clear eeprom command allows you to clear the selected EEPROM option. Example 7-6 Clear EEPROM Command P00>>> clear eeprom log # Clears all failure # information logged in # EEPROM. The clear eeprom command syntax is: cl[ear] ee[prom] <option>...
Page 196: Clear
7.5.7 Clear <envar> Clear <envar> is used to remove an environment variable. Example 7-7 Clear <envar> P00>>> create fred # Create fred with null value fred set to P00>>> set fred "this is a string in an environment variable" P00>>> show fred fred this is a string in an environment variable P00>>>...

Page 197: Clear Screen
7.5.8 Clear Screen The clear screen commands allows you to clear the terminal screen. Example 7-8 Clear Screen Command P00>>> clear screen # Refresh the terminal # screen. The clear screen command syntax is: cl[ear] sc[reen] There are no parameters or options. SRM Console Commands 7-21...
Page 198: Continue
7.5.9 Continue (for OpenVMS or DIGITAL UNIX Only) For OpenVMS or DIGITAL UNIX systems, the continue command resumes processing at the point where it was interrupted by a Ctrl/P. Programs continue executing at the address currently in the program counter of the processor. Example 7-9 Continue Command $ ^P # Stop processing on boot processor;...
Page 199 The continue command syntax is: c[ontinue] Continue causes the primary processor to resume program mode, executing at the address currently in the program counter (PC). This address is the address that was in the PC when the primary processor received a Ctrl/P command. The system displays the hexadecimal PC value.
Page 200: Crash
7.5.10 Crash (for OpenVMS or DIGITAL UNIX Only) For Open VMS or DIGITAL UNIX systems, the crash command causes the operating system to be restarted and generates a memory dump. Example 7-10 Crash Command P01>>> crash [operating system output appears] The crash command causes the operating system to be restarted.
Page 201: Create
7.5.11 Create The create command allows you to create an environment variable. Example 7-11 Create Command 1. P00>>> create fred # Create a new environment fred set to # variable fred with a value P00>>> show fred # equal to null. fred 2.
Page 202: Date
7.5.12 Date The date command is used to display or set the system date and time. Example 7-12 Date Command P02>>> date 15:30:27 February 3, 1998 # System displays time # and date. The date command syntax is: da[te] [<yyyymmddhhmm.ss>] where you can set the date and time by using yyyy for the year, mm for the month, dd for the day, hh for the hour, mm for minutes, and ss for seconds.
Page 203: Deposit
7.5.13 Deposit The deposit command stores data in a specified location. Example 7-13 Deposit Command 1. P00>>> dep -b -n 1FF pmem:0 0 # Clear first 512 bytes # of physical memory. 2. P00>>> d -l -n 3 vmem:1234 5 # Deposit 5 into four # longwords starting at # virtual memory address...
Page 204: Deposit Command Options
The deposit command syntax is: d[eposit] [-{b,w,l,q,o,h}] [-{n val, s val}] [space:]<address> <data> where the options are values from Table 7-4, and <data> is the value to be stored. If the specified value is too large to fit in the data size to be deposited, the console ignores the command and issues an error response.
Page 205: Device Name And Address Space Options
longword). For other address spaces, the address is the last referenced address minus one. • *, the last location referenced in an examine or deposit command. • @, the location addressed by the last location referenced in an examine or deposit command.
Page 206: Examine
7.5.14 Examine The examine command displays the contents of a memory location, a register, or a device. The options are similar to the deposit command options. Example 7-14 Examine Command 1. P00>>> examine pc # Examine the PC psr: 0 ( PC) 0000000000001170 # program counter.
Page 207: Examine Command Options
The examine command syntax is: e[xamine] [-{b,w,l,q,o,h,d}] [-{n val, s val}] [space:] <address> where the options are values from Table 7-6, space: is the optional device name (or address space) of the device to access, and address is a longword that specifies the first location to be examined.
Page 208: Device Name And Address Space Options
Examine uses most of the same options as deposit. Additionally, the examine command supports the -d option (instruction decode, which will disassemble the instructions at the current address). When using examine, if no options are given in subsequent commands, the system uses the options from the preceding commands as the defaults for address or location referenced, data type, including -d, (-b, -l, -w, and so forth), data size for increment (-s), and address space (gpr, ipr, pmem, and so forth).
Page 209: Halt
7.5.15 Halt (OpenVMS or DIGITAL UNIX Only) The halt command halts the specified processor or device. Equivalent to the stop command. Example 7-15 Halt Command P00>>> halt P00>>> The halt command syntax is: halt [-drivers[<device_prefix>]][<processor_num>] where -drivers[device_prefix] specifies the name of the device or device class to stop. If no device prefix is specified, then all drivers are stopped.
Page 210: Help Or Man
7.5.16 Help or Man The help (or man) command provides basic information on the console commands. Example 7-16 Help Command 1. P00>>> help create # Display basic create command NAME # information. Minimum create # command input is highlighted. FUNCTION create environment variable SYNOPSIS create <envar>...
Page 211 Example 7-14 Help Command (Continued) 3. P02>>> help runecu NAME runecu FUNCTION Run the EISA Configuration Utility from floppy. SYNOPSIS runecu P02>>> help run NAME FUNCTION Run an ARC utility program. SYNOPSIS run <program> [-d <device>][-p <n>][-s <parameter string>] where: <device>...
Page 212: Init
7.5.17 Init The init command performs a reset. Example 7-17 Init Command P00>>> init The init command syntax is: i[nit] The init command is used to reset, or initialize, the entire system. The init command resets the machine and runs systemwide self-test. Self-test results are displayed after a system reset.
Page 213: Prcache
7.5.18 Prcache The prcache command manipulates an optional NVRAM disk cache. Example 7-18 Prcache Command P00>>> prcache -f PCI NVRAM Disk Cache: passed Size: Base Address: 040000000 System ID: 21000035 State: valid Battery Status: good Battery Disconnect Circuit Status: disabled The prchache command syntax is: prcache [-z] [-f] [-u] [nvram_bus] where -z zeros the NVRAM disk cache...
Page 214: Run Command
7.5.19 Run (for OpenVMS or DIGITAL UNIX Only) For OpenVMS or DIGITAL UNIX systems, the run command is used to run an ARC utility program. Run has four options: rcu (the RAID Configuration Utility), swxcrfw, eeromcfg, and util_cli. The arc_enable environment variable must be set to on before this command can be used.
Page 215 ---------------------------------------------------------- ISP1020/1040 EEROM Configuration Utility V2.1-102 ---------------------------------------------------------- +============ Select ISP1020 ============+ Virtual Slot Address |----------------------------------------| < (O)K > < E(x)it > +========================================+ SRM Console Commands 7-39...
Page 216 The run command has four options: - Run the RAID Configuration Utility swxcrfw - Update firmware on RAID controller. eeromcfg - Run the ISP1020/1040 EEROM Configuration Utility. util_cli - Run the KZPSA Configuration Utility Options 1 and 2 (rcu and swxcrfw) are on floppy and require a floppy drive. Options 3 and 4 (eeromcfg and util_cli) are on CD.
Page 217: Runecu Command
7.5.20 Runecu (for OpenVMS and DIGITAL UNIX Only) For OpenVMS and DIGITAL UNIX systems, the runecu command is used to invoke the EISA Configuration Utility (ECU). ECU comes on a floppy. The arc_enable environment variable must be set to on before this command can be used. Example 7-20 Runecu Command P00>>>...
Page 218: Runecu (For Openvms Or Digital Unix Systems Only)
EISA Configuration Utility +----------- Steps in configuring your computer----------+ | Step 1: Important EISA configuration information | Step 2: Add or remove boards | Step 3: View or edit details | Step 4: Examine required switches | Step 5: Save and exit +--------------------------------------------------------+ | >Select=ENTER<...
Page 219: Set Eeprom
7.5.21 Set EEPROM The set eeprom command allows you to set the selected EEPROM option. Example 7-21 Set EEPROM Command 1. P00>>> set eeprom field LARS #> 09494820 # Enter labor activity Message> EEPROM update # reporting system (LARS) P00>>> # number (8 digits) and # message (up to 68 # characters).
Page 220: Set
7.5.22 Set <envar> Set <envar> allows you to modify environment variables. Example 7-22 Set <envar> 1. P00>>> set auto_action restart # On an error halt, # system will automatic- # ally restart. If restart # fails, boot the operat- # ing system. 2.

Page 221: Set Host
7.5.23 Set Host The set host command allows you to connect to another console or service. Example 7-23 Set Host Command P00>>> show configuration Name Type Mnemonic TLSB 0++ KN7CC-AB 8014 0000 kn7cc-ab0 MS7CC 5000 0000 ms7cc0 MS7CC 5000 0000 ms7cc1 KFTHA 2020...
Page 222 The set host command syntax is: se[t] h[ost] <device_adapter> The set host <device_adapter> command is used to connect to a remote XMI adapter for running XMI module-resident ROM-based diagnostics, as shown in Example 7-23. Use Ctrl/C to terminate the command and return to the primary processor. Set host can only be issued from the boot processor, and only one set host command is in effect at a time.
Page 223: Set Power
7.5.24 Set Power The set power command is used to configure the system power regulators for battery backup (AlphaServer 8400 with three-phase power only). Example 7-24 Set Power Command P00>>> set power -b 8 left P00>>> The set power command syntax is: se[t] p[ower] -b <value>...
Page 224: Set Seeprom
7.5.25 Set SEEPROM The set seeprom command allows you to set the selected SEEPROM option. Example 7-25 Set SEEPROM Command 1. P00>>> set seeprom field LARS #> 09494820 # Enter labor activity Message> SEEPROM update # reporting system (LARS) P00>>> # number (8 digits) and # message (up to 68 # characters).
Page 225: Show Configuration
7.5.26 Show Configuration The show configuration command displays the last configuration seen at system initialization. Example 7-26 Show Configuration Command P00>>> show configuration Name Type Mnemonic TLSB 0++ KN7CC-AB 8014 0000 kn7cc-ab0 MS7CC 5000 0000 ms7cc0 KFTIA 2020 0000 kftia0 KFTHA 2000 0D02...
Page 226: Show Configuration Command
Example 7-23 Show Configuration Command (Continued) C4 Internal PCI connected to kftia0 pci1 ISP1020 10201077 0001 isp2 ISP1020 10201077 0001 isp3 DECchip 21040-AA 21011 0023 tulip1 ISP1020 10201077 0001 isp4 ISP1020 10201077 0001 isp5 DECchip 21040-AA 21011 0023 tulip2 PCI NVRAM 71011 0000 pci_nvram0...
Page 227: Show Cpu
7.5.27 Show CPU The show CPU command displays information on CPUs in the system. Example 7-27 Show CPU Command P08>>> show cpu Primary CPU: Active CPUs: 08 09 10 Configured CPUs: 08 09 10 11 P08>>> The show cpu command syntax is: sh[ow] cpu The console displays CPU information.
Page 228: Show Device
7.5.28 Show Device Displays device information for any disk/tape adapter or group of adapters. Example 7-28 Show Device Command P00>>> show device polling for units on isp0, slot 0, bus 0, hose0... dka200.2.0.0.0 DKA200 RZ26L 440C dka200.4.0.0.0 DKA400 RZ26L 440C polling for units on isp1, slot 1, bus 0, hose0...
Page 229: Show Eeprom
7.5.29 Show EEPROM The show EEPROM command allows you to display selected EEPROM information. Example 7-29 Show EEPROM Command 1. P00>>> show eeprom serial # Display system serial # number. System Serial Number = GAO1234567 2. P00>>> show eeprom manufacturing # Display manufactur- # ing information.
Page 230: Show
7.5.30 Show <envar> Show <envar> displays the current state of the specified environment variable. Example 7-30 Show <envar> Command 1. P00>>> show auto_action auto_action restart P00>>> 2. P00>>> show tta0_baud tta0_baud 9600 3. P00>>> show d_harderr d_harderr halt 4. P00>>> show enable* # Displays status enable_audit # of enable_audit...

Page 231: Show Memory
7.5.31 Show Memory The show memory command displays memory module information. Example 7-31 Show Memory Command P00>>> show memory Set Node Size Base Address Intlv Position --- ---- ---- ------------------ ----- -------- 256 Mb 00000000 000000000 2-Way The show memory command syntax is: sh[ow] m[emory] In the above example, the memory module at node 7 is in an on-board two-way interleave indicated by the interleave set A.
Page 232: Show Network
7.5.32 Show Network The show network command displays the names and physical addresses of all known network devices in the system. Example 7-32 Show Network Command P00>>> show network polling for units on demna0, slot 14, xmi0... exa0.0.0.14.0: 08-00-2B-24-3F-E1 polling for units on demfa0, slot 14, xmi1... exb0.0.0.14.2: 08-00-2B-0B-BB-FF polling for units on tulip0, slot 2, bus 0, hose0...
Page 233: Show Power
7.5.33 Show Power The show power command gives the power status of the system (AlphaServer 8400 system with H7263 power regulators installed). Example 7-33 Show Power Command >P00>>> show power Cabinet: Main Regulator : ---------------------------------------------------------------------- Primary Micro Firmware Rev : Secondary Micro Firmware Rev : Power Supply State : NORMAL NORMAL NORMAL...
Page 234: Show Seeprom
7.5.34 Show SEEPROM The show SEEPROM command allows you to display selected SEEPROM information. Example 7-34 Show SEEPROM Command 1. P00>>> show seeprom field kftha0 # Displays field LARS # = 0949820 # entered Labor Activity Message = EEPROM update # Number and message.
Page 235: Start
7.5.35 Start (OpenVMS or DIGITAL UNIX Only) The start command begins execution of an instruction at the address specified in the command string. The start command does not initialize the system. Example 7-35 Start Command P00>>> start 40000000 # Start processor at # address 40000000.
Page 236: Stop
7.5.36 Stop The stop command halts a specified processor or device. Equivalent to the halt command. Example 7-36 Stop Command P00>>> stop 1 # Stop CPU 1. The stop command syntax is: stop [-drivers[<device_prefix>]][<processor_num>] where -drivers[device_prefix] specifies the name of the device or device class to stop. If no device prefix is specified, then all drivers are stopped.
Page 237: Test
7.5.37 Test The test command allows you to test the entire system (focusing on memory and I/O), a portion of the system (subsystem), or a specific device. By default, the entire system is tested. Example 7-37 Test Command P00>>> test Complete Test Suite for runtime of 600 seconds Type ^C to stop testing Configuring system...
Page 238: Test Command Options
The test command syntax is: t[est][-write][-nowrite "list"][-t time][-q][dev_arg] where <dev_arg> specifies the target device, group of devices, or subsystem to test. A list of available devices and subsystem mnemonics can be obtained by issuing a show configuration, show device, or show network command. You would then issue the test dev_arg command to test the desired device.
Page 239: Type
7.5.38 Type The type command displays the contents of a specified file, one screen at a time. One common use of type is to display the event log, as shown in Example 7-38. Type a space to see the next screen, or Enter to see the next line. Example 7-38 Type Command P00>>>...
Page 240: Vga
7.5.39 Vga The vga command tests the graphics console monitor. Example 7-39 Vga Command P00>>> vga test 0 [displays character set on graphics monitor] The vga command syntax is: vga [reinit] [test <test_nbr> [<n>]] where reinit reinitializes the graphics monitor, and test_nbr can have three values: test_nbr = 0 Display the entire character set on the graphics monitor <n>...
Page 241: Comment (#)
7.5.40 Comment (#) A comment can be introduced using the # symbol. The entire comment is ignored. Example 7-40 Comment (#) Command 1. P00>>> # This example illustrates the comment command. P00>>> 2. P00>>> exam pmem:0400EC # Examine physical memory. pmem: 000400EC D0FFFFFD P00>>>...
Page 243: Alphabios Firmware
Chapter 8 AlphaBIOS Firmware The AlphaBIOS firmware boots the Windows NT operating system, either automatically or when you request, depending on the setup factors described in Section 5.5. AlphaBIOS Setup, reached by pressing the F2 key before the operating system boots, is the graphical interface that supports the Microsoft Windows NT operating system and some utility programs.
Page 244: Introduction
8.1 Introduction AlphaBIOS boots the Windows NT operating system, as described in Section 5.5. AlphaBIOS Setup (reached by pressing F2 before the operating system boots) is the Windows NT system management tool. It allows you to display the system configuration, upgrade firmware using the LFU utility, perform hard disk setup, install Windows NT, and run utility programs.
Page 245 As shown in Figure 8-1, AlphaBIOS Setup has six major functions, provided through menus displayed on the graphics monitor: Display System Configuration The displays provided include: • System board configuration • Hard disk configuration • PCI configuration • EISA configuration •...
Page 246: Switching Between Windows Nt, Alphabios Setup And The Srm Console
8.2 Switching Between Windows NT, AlphaBIOS Setup, and the SRM Console To switch from Windows NT to the SRM console, to boot DIGITAL UNIX or OpenVMS, or to run firmware-based diagnostics, restart the system from the Windows NT taskbar or at the control panel on the front of the machine. If you have selected auto_action boot, then set the system to Secure at the control panel before AlphaBIOS is started.
Page 247 Figure 8-3 8400 Control Panel Disable Secure Front Enable Restart Key On Fault BX0511-94 Switch from Windows NT to the SRM Console There are two ways to switch from Windows NT to the SRM console. Using the Windows NT taskbar to shut down the system ensures that files are closed properly before the system shuts down, and is preferred to switching to the SRM console from the control panel.
Page 248 If the auto_action environment variable has been set to boot, press the Secure pushbutton in (8200) or turn the keyswitch to Secure (8400) before AlphaBIOS starts automatically. When the display stops at the SRM console prompt, return the Secure pushbutton to out (8200) or turn the keyswitch to Enable (8400).
Page 249 Switch from AlphaBIOS Setup to SRM Console To return to the SRM console from AlphaBIOS Setup, Press Ctrl/Alt/Delete. If the auto_action environment variable is set to halt, the system will stop at the SRM console prompt and you can enter commands. Otherwise, proceed to Step 3. If the auto_action environment variable has been set to boot, press the Secure pushbutton in (8200) or turn the keyswitch to Secure (8400) before AlphaBIOS starts automatically.
Page 250: Keyboard Conventions And Help
8.3 Keyboard Conventions and Help AlphaBIOS uses universally accepted keys and key combinations for navigating the interface and selecting items. Figure 8-4 Typical First-Level Help Screen Help: CMOS Setup F1=Key Help Change color scheme. Enter Advanced CMOS Setup. Set factory default CMOS settings. Exit CMOS Setup and discard any changes.
Page 251: Second-Level Help Screen
Figure 8-5 Second-Level Help Screen AlphaBIOS Setup F1=Help Help: Action Keys 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.
Page 252: Boot Screen
8.4 Starting AlphaBIOS When NT is selected as the startup operating system, you can start AlphaBIOS Setup by pressing F2 from the Boot screen displayed at power-up or reset. You are allowed some time to select setup before the operating system is booted automatically.
Page 253: Alphabios Setup Screen
You define Windows NT as the operating system to be booted by setting the os_type environment variable to nt from the SRM console. When the system is powered up, reset, or initialized, the graphics monitor shows status and initialization messages, terminating in the Boot screen shown in Figure 8–6.
Page 254: Displaying The System Configuration
8.5 Displaying the System Configuration The Display System Configuration screen provides information about the system’s installed processor, memory, attached devices, and option boards. Figure 8-8 Display System Configuration Screen Display System Configuration Systemboard Configuration Hard Disk Configuration PCI Configuration EISA Configuration SCSI Configuration Memory Configuration Integrated Peripherals...
Page 255 Use this procedure to display the system configuration. Enter AlphaBIOS Setup, select Display System Configuration, 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: •...
Page 256: System Board Configuration
8.5.1 System Board Configuration Figure 8-9 System Board Configuration Display System Configuration F1=Help Systemboard Configuration Hard Disk Configuration PCI Configuration EISA Configuration SCSI Configuration Memory Configuration Integrated Peripherals System Type: AlphaServer 8200/8400 Processor: Digital Alpha 21164, Revision 4.0 (4 Processors) Speed: 300 MHz Cache:...
Page 257 System type — The model number of the system. Processor — The model and revision of the processor chip. Revision level information can be useful in troubleshooting problems with technical support personnel. Speed — The speed at which the processor runs. Cache —...
Page 258: Hard Disk Configuration
8.5.2 Hard Disk Configuration Figure 8-10 Hard Disk Configuration Display System Configuration Systemboard Configuration Hard Disk Configuration PCI Configuration EISA Configuration SCSI Configuration Memory Configuration Integrated Peripherals Disk SWXCR #0, SCSI ID 8 3003 MB MYLEX DAC960 Partition 1 2997 MB NTFS Partition 2 6 MB...
Page 259 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 8.7). Figure 8-10 shows a configuration with multiple hard disks, such that the bottom display shows an arrow to the left, indicating that the display continues.
Page 260 8.5.3 PCI Configuration Figure 8-11 PCI Configuration Display System Configuration Systemboard Configuration Hard Disk Configuration PCI Configuration EISA Configuration SCSI Configuration Memory Configuration Integrated Peripherals Device Name Device Type Revision Physical Slot DIGITAL 21040 Ethernet Embedded Intel 82375 PCEB EISA bridge Bus 0 : Slot 6 DIGITAL DEFPA FDDI...
Page 261 Device name — The name and model of the device as recorded in the device’s firmware. Device type — Lists the function of the device in the system. Revision — The revision level of the device signifies the number of times it has been updated by the manufacturer.
Page 262: Advanced Pci Information
Figure 8-12 Advanced PCI Information Advanced PCI Information Bus Number=0, Device Number=11, Function Number=0 Configuration Space: Register Name Hex Offset Value Vendor ID 1001 Device ID 0008 Command 0147 Status 0200 Revision ID Prog. I/F Sub Class Code Class Code Cache Line Size Latency Timer Header Type...
Page 263: Eisa Configuration
8.5.4 EISA Configuration Figure 8-13 EISA Configuration Display System configuration Systemboard Configuration Hard Disk Configuration PCI Configuration EISA Configuration SCSI Configuration Memory Configuration Integrated Peripherals Device Name Device Type Physical Slot ENTER=Select ESC=Exit BX-0577-97 Device name — Includes a three-character manufacturer code, followed by a three-digit board type, followed by a one-digit revision number.
Page 264: Scsi Configuration
8.5.5 SCSI Configuration Figure 8-14 SCSI Configuration Display System Configuration Systemboard Configuration Hard Disk Configuration PCI Configuration EISA Configuration SCSI Configuration NCR8xx #0 Memory Configuration SWXCR # 0 Integrated Peripherals KZPSX #0 NCR8xx #0, SCSI ID 7, SCSI Bus 0 SCSI ID Device Size...
Page 265 SCSI controller information — Describes the physical characteristics of the selected SCSI controller. This line includes: 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.
Page 266: Memory Configuration
8.5.6 Memory Configuration Figure 8-15 Memory Configuration Display System Configuration Systemboard Configuration Hard Disk Configuration PCI Configuration EISA Configuration SCSI Configuration Memory Configuration Integrated Peripherals System Memory Configuration Memory: 256 MB BX-0599-98 This screen shows the current memory configuration. 8-24 AlphaServer 8200/8400 Operations Manual...
Page 267: Integrated Peripherals
8.5.7 Integrated Peripherals Figure 8-16 Integrated Peripherals Display System Configuration Systemboard Configuration Hard Disk Configuration PCI Configuration EISA Configuration SCSI Configuration Memory Configuration Integrated Peripherals Serial Port 1: Enabled as COM1: 3F8, IRQ17 Serial Port 2: Enabled as COM2: 2F8, IRQ10 Parallel Port 1: Enabled as LPT1: 3BC, IRQ11 BX-0581-98...
Page 268: Updating Firmware
8.6 Updating Firmware Insert the CD-ROM with the updated firmware and select Upgrade AlphaBIOS from the main AlphaBIOS Setup screen. Use the Loadable Firmware Update (LFU) utility to perform the update. The LFU exit command causes a system reset. Figure 8-17 Updating Firmware AlphaBIOS Setup Display System Configuration...
Page 269: Lfu Load Screen
You can use this procedure to boot the Loadable Firmware Update (LFU) utility to upgrade firmware. (You can also use the SRM console command boot to run LFU, as described in Appendix B.) Insert the upgrade CD-ROM. Enter SRM console mode. Make sure that the auto_action environment variable is set to boot, since this setting will be used by the AlphaBIOS firmware to boot LFU.
Page 270: Setting Up The Hard Disk
8.7 Setting Up the Hard Disk You can perform either an express or a custom hard disk setup. An express setup, described in this section, creates the recommended partition arrangement on the first hard disk, but it does not map bad sectors. Custom hard disk setup is described in Sections 8.7.1 and 8.7.2.
Page 271 Partition number — Within a single drive, partition numbers are assigned in sequential order: 1, 2, 3, and so on, or unused. The partitions populate the drive from the innermost cylinders to the outermost. Partition size — The raw (unformatted) storage capacity of the partition. Actual storage space will differ based on the file system with which the partition is formatted.
Page 272: Manually Creating And Deleting Partitions
8.7.1 Manually Creating and Deleting Partitions Use the Create Partition and Delete Partition options if you need to create a custom hard disk partition arrangement or otherwise manually manage your hard disk partitions. Figure 8-20 Create New Partition Dialog Box Hard Disk Setup Disk KZPSX #0, SCSI ID 1...
Page 273: Delete Partition Dialog Box
To delete a partition Enter AlphaBIOS Setup and select Hard Disk Setup. Press Enter. Select the partition to be deleted (see in Figure 8-21). Press Delete. A dialog box displays (see Press F10 to confirm the deletion. Figure 8-21 Delete Partition Dialog Box Hard Disk Setup Disk KZPSX #0, SCSI ID 1...
Page 274: Formatting A Fat Partition
8.7.2 Formatting a FAT Partition AlphaBIOS can format partitions with the FAT file system. Use Windows NT to format a partition using NTFS or to convert a FAT partition to NTFS. Figure 8-22 Formatting a FAT Partition Hard Disk Setup F1=Help Disk KZPSX #0, SCSI ID 1...
Page 275: Standard Formatting
To format a FAT partition Enter AlphaBIOS Setup and select Hard Disk Setup. Press Enter. Select the partition to be formatted (see in Figure 8-22). Press F6. A dialog box displays, asking whether to perform a quick or standard format (see ).
Page 276: Performing Setup Tasks
8.8 Performing Setup Tasks 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. Figure 8-24 Standard CMOS Setup Screen CMOS Setup F1=Help December...
Page 277 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 only drive type supported is 3.5 inch, 1.44 MB. Keyboard — The keyboard setting makes it possible to use most language keyboards.
Page 278: Advanced Cmos Setup Screen
Figure 8-25 Advanced CMOS Setup Screen Advanced CMOS Setup F1=Help AlphaBIOS Password Option: Disabled ESC=Discard Changes F10=Save Changes BX-0591-97 8-36 AlphaServer 8200/8400 Operations Manual...
Page 279 To enter Advanced CMOS Setup Enter AlphaBIOS Setup, select CMOS Setup, and press Enter. In the Standard CMOS Setup screen, press F6. 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.
Page 280: Installing Windows Nt
8.9 Installing Windows NT Install Windows NT from CD-ROM. Multiple versions of the operating system can be resident in the system at one time. Figure 8-26 Installing Windows NT AlphaBIOS Setup Display System Configuration... Upgrade AlphaBIOS Hard Disk Setup... CMOS Setup... Install Windows NT Utilities About AlphaBIOS...
Page 281 If Windows NT was installed at the factory, enter Windows NT setup as described in Section 8.4. If it was not installed, or if you are installing another version, you must have a CD-ROM drive attached to your system. If this is a new Windows NT installation, start with this procedure: Start AlphaBIOS.
Page 282: Running Utility Programs
8.10 Running Utility Programs Maintenance programs such as RAID and EISA configuration utilities are run from the AlphaBIOS Utilities menu. Figure 8-27 Utilities Selection AlphaBIOS Setup Display System Configuration... Upgrade AlphaBIOS Hard Disk Setup... CMOS Setup... Install Windows NT Utilities Run ECU from floppy About AlphaBIOS OS Selection Setup...
Page 283 The Utilities selection from the AlphaBIOS Setup screen includes running the EISA configuration utility (ECU) from floppy, setting up a version or versions of the Windows NT operating system for selection, and running maintenance programs such as the RAID configuration and management utility (RA200RCU). AlphaBIOS Firmware 8-41...
Page 284: Selecting The Version Of Windows Nt
8.11 Selecting the Version of Windows NT Multiple versions of Windows NT can be resident on the system at one time. It is necessary to select the version that will be started. Figure 8-28 Operating System Selections Operating System Selection Setup Primary Operating System Windows NT Server 4.0 Windows NT Server 4.0...
Page 285 NOTE: The term “operating system selection,” as it is used in this context, refers to a version of Windows NT. It does not pertain to the DIGITAL UNIX and OpenVMS operating systems. Each operating system selection is a set of information for a version of Windows NT. It describes the disk and partition containing the OSLOADER.EXE file associated with a particular operating system installation, as well as the path to the operating system itself.
Page 286: Designating A Primary Operating System
8.11.1 Designating a Primary Operating System Figure 8-29 Primary Operating System AlphaBIOS Version 5.33 Please select the operating system to start: Windows NT Server 4.0 Windows NT Server 4.0 to move the highlight to your choice. Press Enter to choose. CMOS Setup Date: Wednesday, December 17, 1997...
Page 287 Up to three versions of Windows NT can be installed at the same time. This can be very useful in a variety of circumstancesfor example, when testing application compatibility across different versions of Windows NT. Each time you install a separate version of Windows NT, a new operating system selection is created.
Page 288: Primary Operating System And The Auto Start Option
8.11.2 Primary Operating System and the Auto Start Option 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 8-30 Operating System Selection Setup Operating System Selection Setup Primary Operating System...
Page 289 Primary operating system — The OS that appears first on the AlphaBIOS Boot screen. It is also the version of the OS that automatically starts if Auto Start is selected. Any of the operating system selections can be the primary operating system.
Page 290 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.
Page 291 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 displays describing the results of the validation.
Page 293: Digital Unix Boot Options
Appendix A OpenVMS and DIGITAL UNIX Boot Options Table A-1 lists the DIGITAL UNIX options used with the boot command. Table A-2 lists the Alpha primary boot (APB) options used with the boot command for OpenVMS. These options allow you to control various phases of booting. Table A-1 DIGITAL UNIX Boot Options Option Function...
Page 294 Table A-2 OpenVMS Boot Options Hexadecimal Value Function Allows a conversational boot. Maps XDELTA to a running system Stops the boot procedure at the initial system breakpoint. Performs a diagnostic bootstrap. Stops the boot procedure at the bootstrap breakpoints. Omits the header from the secondary bootstrap image. Inhibits memory testing.
Page 295: Appendix B Updating Firmware
Appendix B Updating Firmware Use the Loadable Firmware Update (LFU) utility to update system firmware. LFU runs without any operating system and can update the firmware on any system module. LFU handles modules on the TLSB bus (for example, the CPU) as well as modules on the I/O buses (for example, a CI controller on the XMI bus).
Page 296: B–1 Booting Lfu From Cd-Rom
B.1 Booting LFU LFU is supplied on the Alpha CD-ROM (Part Number AG–PTMW*–BE, where * is the letter that denotes the disk revision). Make sure this CD-ROM is mounted in the in-cabinet CD drive. Boot LFU from the CD-ROM. Example B-1 Booting LFU from CD-ROM P00>>>...
Page 297 ***** Loadable Firmware Update Utility ***** ------------------------------------------------------------------------ Function Description ------------------------------------------------------------------------ Display Displays the system’s configuration table. Exit Return to loadable offline operating environment. List Lists the device types and firmware revisions supported by this revision of LFU. Modify Modifies port parameters and device attributes. Show Displays device mnemonic, hardware and firmware revisions.
Page 298: B.2 List
B.2 List The list command displays the inventory of update firmware on the CD-ROM. Only the devices listed at your terminal are supported for firmware updates. Example B-2 List Command UPD> list Device Current Revision Filename Update Revision kn7cc-ab0_arc V5.3-14 arcrom V5.3-14 kn7cc-ab0...
Page 299 The list command shows three pieces of information for each device: • Current revision — The revision of the device’s current firmware • Filename — The name of the file that is recommended for updating that firmware • Update revision — The revision of the firmware update Updating Firmware B-5...
Page 300: Update
B.3 Update The update command writes new firmware from the CD-ROM to the module. Then LFU automatically verifies the update by reading the new firmware image from the module into memory and comparing it with the CD-ROM image. Example B-3 Update Command UPD>...
Page 301 This command requests a firmware update for a specific module. If you want to update more than one device, you may use a wildcard but not a list. For example, update k* updates all devices with names beginning with k, and update * updates all devices.
Page 302 Example B–3 Update Command (Continued) UPD> update confirm update on: kzpsa0 kzpsa1 pfi0 [Y/(N)]n UPD> update kzpsa0 -path cipca_fw WARNING: updates may take several minutes to complete for each device. Confirm update on: kzpsa0 [Y/(N)]y DO NOT ABORT! Kzpsa0 firmware filename ’kdm70_fw’ is bad UPD>...
Page 303 When you do not specify a device name, LFU tries to update all devices. LFU lists the selected devices to update and prompts before devices are updated. In this next example, the -path option is used to update a device with different firmware from the LFU default.
Page 304: Exit
B.4 Exit The exit command terminates the LFU program, causes system initialization and self-test, and returns the system to console mode. Example B-4 Exit Command UPD> exit Initializing... [self-test display appears] P00>>> UPD> update kzpsa0 WARNING: updates may take several minutes to complete for each device. Confirm update on: kzpsa0 [Y/(N)]y...
Page 305 At the UPD> prompt, exit causes the system to be initialized. The console prompt appears. Errors occurred during an update. Because of the errors, confirmation of the exit is required. Typing y causes the system to be initialized and the console prompt to appear. Updating Firmware B-11...
Page 306: Display And Verify Commands
B.5 Display and Verify Commands Display and verify commands are used in special situations. Display shows the physical configuration. Verify repeats the verification process performed by the update command. Example B-5 Display and Verify Commands UPD> display Name Type Mnemonic TLSB KN7CC-AB 8014...
Page 307 Display shows the system physical configuration. Display is equivalent to issuing the console command show configuration. Because it shows the slot for each module, display can help you identify the location of a device. Verify reads the firmware from the module into memory and compares it with the update firmware on the CD-ROM.
Page 308: How To Update Corrupted Firmware
B.6 How to Update Corrupted Firmware If LFU identifies a device as unknown, either the firmware on the module is corrupted or the console does not support or does not recognize the device. Example B-6 Updating an “Unknown” Device UPD> display Name Type Mnemonic...
Page 309 Issue the display command. The display indicates an unknown device — LFU is unable to recognize the device type. You can identify the unknown device by looking at the physical configuration. Display shows that the unknown devices are in slot 2 of the first XMI bus and slots 2 and 12 of the second XMI.
Page 310 Example B–6 Updating an “Unknown” Device (Continued) unknown2 Updating to 2... Verifying 2... PASSED. UPD> exit Initializing... [self-test display appears] P00>>> sho config Name Type Mnemonic TLSB KN7CC-AA 8014 0000 kn7cc-aa0 MS7CC 5000 0000 ms7cc0 MS7CC 5000 0000 ms7cc1 KFTHA 2000 0000 kftha0...
Page 311 Status message indicates that the update succeeded. To make the device known, initialize the system by exiting LFU. The modules in slot 2 of the first XMI and slot 2 of the second are still unknown. The console either does not support or does not recognize these devices.
Page 312: How To Modify Device Attributes
B.7 How to Modify Device Attributes The modify command can change parameters stored in EEPROM on the following devices: KZMSA, DEC LANcontroller 400 (DEMNA), KCM44, and KFMSB. The attributes are specific to each device. Example B-7 Modify Command UPD> modify kzmsa0 kzmsa0 Local Console: ENABLED...
Page 313 When you modify the KZMSA, LFU first displays all the parameters. LFU asks if you want to modify any parameter values. The default response is Continued on next page Updating Firmware B-19...
Page 314 Example B–7 Modify Command (Continued) Local Console: ENABLED Change? [y/(n)] Log Selftest Errors: ENABLED Change? [y/(n)] Log NRC 53C710 RBD Errors: ENABLED Change? [y/(n)] y Log XMI RBD Errors: ENABLED Change? [y/(n)] Log XZA RBD Errors: ENABLED Change? [y/(n)] RBD Error Logging: DISABLED Change? [y/(n)] Disable Reset Channel 0:...
Page 315 LFU prompts for parameters to modify. This example modifies one parameter on the KZMSA0; logging of ROM-based diagnostic errors is now enabled. LFU displays the list of parameters with modifications. If these modified values are acceptable, type y. Updating Firmware B-21...
Page 317: Appendix C Running Configuration Utilities From The Srm Console
Appendix C Running Configuration Utilities from the SRM Console The run command has four options, as follows: • - Run the RAID Configuration Utility • swxcrfw - Update the firmware on the RAID Controller • eeromcfg - Run the ISP1020 EEPROM Configuration Utility •...
Page 318: C.1 Configuring A Raid Storage Array
C.1 Configuring a RAID Storage Array Once you have selected the run command and the rcu option, the utility displays the main menu: +---------------------------------------+ Main Menu +---------------------------------------+ |[01. View/Update Configuration] | 02. Automatic Configuration | 03. New Configuration | 04. Initialize Logical Drive | 05.
Page 319 Understanding the Configuration Methods You can configure your array in either of the following ways: Automatically. You can configure automatically only if: You want to configure one RAID 5 logical RAID drive (requires between three and eight drives of same capacity) You want to configure up to 8 JBODs of any capacity Interactively.
Page 320 Selecting the Automatic Configuration Option To configure automatically, follow these steps: Select the Automatic Configuration option from the main menu and either one of the following happens depending upon whether a configuration currently exists. If a configuration currently exists, the utility displays a warning message saying that a valid configuration exists and if you proceed, you will destroy it.
Page 321 Configuring Interactively To configure interactively, do the following: Create one or more drive groups Create one or more logical RAID drives Create a logical RAID drive of RAID level 0, 0 + 1, or 1 Define a spare drive Specify caching policy To configure interactively, you must do the following: Create one or more drive groups A drive group defines the drives that you want to work together as the available...
Page 322 Creating a Drive Group A drive group is from one to eight drives that operate as a single drive. Determine how many drives to use for each drive group based on the following: The RAID levels of the logical RAID drives you will create See Table C-1 to see the minimum and maximum number of drives allowed for each RAID level.
Page 323: Number Of Drives You Can Use In A Drive Group For Each Raid Level
Table C-1 Number of Drives You Can Use in a Drive Group for Each RAID Level Number of Amount of Storage RAID Drives in Available for Unique Level Drive Group Data (percent) Data Redundancy 2 to 8 0 + 1 3 to 8 3 tp 8 66 to 87...
Page 324 Defining a Drive Group Use this option to bind drives together into drive groups. To maximize your disk space resources, use drives of the same capacity in a drive group. To define a drive group, follow these steps: Select the New Configuration option from the main menu and either one of the following things happens depending upon whether a configuration currently exists.
Page 325 NOTE: If you select a drive for the drive group by mistake or you want to redefine a drive group, highlight the Cancel Group option and press the Enter key. The cursor appears on the first drive in a group on the matrix. Move the cursor to the drive group you want to cancel and press the Enter key.
Page 326: Isp1020 Configuration Utility
C.2 ISP1020/1040 Configuration Utility When the EEROMCFG configuration utility is selected, after the "transferring control" message, a screen such as that shown in Example C-1 is displayed. This shows the ISP1020/1040 devices on the PCI device unit number you selected (if you are running the EEROMCFG utility from the SRM console) or all ISP1020/1040 devices on your system (if you are running EEROMCFG from AlphaBIOS Setup).
Page 327 Example C-3 shows an example of host adapter parameters for a KZPBA adapter. Table C-3 describes the host adapter parameters. (You can also refer to your adapter Installation Guide for further information.) You use the arrow keys to select a parameter to modify from the default and type in the modification.
Page 328: Host Adapter Parameters
Table C-3 Host Adapter Parameters Parameter Default Description Reason to Change FIFO 2 (KFTIA) Sets the FIFO threshold Optimize system Threshold point at which burst performance. ¹ 3 (KZPBA) transfers are requested on the ISP1020/1040 adapter. Host Adapter Determines whether the Disable the host adapter Enable BIOS recognizes the...
Page 329 Table C-3 Host Adapter Parameters (Continued) Parameter Default Description Reason to Change REQ/ACK Provide active pullup Active assist in single-ended Negation mode. (the REQ and ACK signals are pulled up.) By enabling active negation, the ISP1020/1040 host adapter is less sensitive to an imperfect SCSI bus.
Page 330 Table C-3 Host Adapter Parameters (Continued) Parameter Default Description Reason to Change Low Term If termination not required Enable on the board. High Term If termination not required Enable on high-order 8 bits, or not required on the board Selection Sets the selection phase Optimize system Timeout...
Page 331: Glossary
Glossary AC input box Receives single or three-phase AC power and outputs that to the power regulators. The system circuit breaker and a Dranetz port are on the AC input box. See also Power. Address space See Physical address space and Virtual address space. AlphaBIOS The firmware subsystem that provides facilities for setup and maintenance of Windows NT systems.
Page 332 Bootblock Block zero on the system disk; it contains the block number where the Alpha primary boot (APB), DIGITAL UNIX boot, NT boot, or virtual memory boot (VMB) program is located on the system disk and contains a program that, with the boot primitive, reads APB or VMB from the system load device into memory.
Page 333 Console mode A mode of operation where the processor is not running the operating system but allows an operator to issue SRM console commands. Console program The code that the boot processor executes during console mode. Each processor has a copy of this code in flash ROMs. After a boot processor has been determined, that processor begins console initialization.
Page 334 Disk array A set of disk drives and a specialized aarray controller, which keeps track of how data is distributed across the drives. Drive group A set of drives logically tied together and addressed as a single unit. DSSI DIGITAL Storage Systems Interconnect. A DIGITAL Storage Architecture interconnect used by the KFMSB adapter and RF and TF series integrated storage elements to transfer data and to communicate with each other.
Page 335 Flash ROM Flash-erasable programmable read-only memory, which can be bulk erased and reprogrammed. The processor module uses flash ROMs to hold the console and diagnostic firmware. In addition, one flash ROM holds initialization code that bootstraps the main console/diagnostic firmware. See also SROM code. Gbus The path between the processor and the console/diagnostic firmware and to two UART chips.
Page 336 KFTIA module The TLSB module that provides the interface from the TLSB bus to I/O buses. The KFTIA module has one port, known as a “hose,” to provide access to a single PCI, XMI (8400 only), or Futurebus+ (8400 only) card cage. A system can support up to three KFTIAs with the first one in node 8 of the TLSB.
Page 337 LFU (Loadable Firmware Update) Utility Used to update firmware in EEPROM on modules. Firmware can include the SRM console, AlphaBIOS, and firmware on TLSB and I/O device modules. Mailbox A software-created data structure in memory used to read and write to I/O device registers on XMI and FBUS+ controllers.
Page 338 Plug-in units (PIUs) Self-contained assemblies that are easily installed in the 8400 system cabinet or expander cabinet. There are PIUs for the XMI bus, the Futurebus+ bus, PCI/EISA buses, as well as for StorageWorks disks and batteries. Power regulators The AlphaServer 8400 system can have H7264 single-phase power regulators, H7263-AA/AB three-phase power regulators, or H7263-AC/AD three-phase power regulators, which allow battery backup.
Page 339 Symmetric multiprocessing A multiprocessing system configuration in which all processors have equal access to operating system code residing in shared memory and can perform all, or almost all, system tasks. Transactions TLSB transactions consist of a command and two data cycles, which follow some fixed time after an arbitration cycle.
Page 341: Index
Index Blower, 3-9 AC input box, 3-13 Blower (8200), 2-11 AC power cord, 3-9 Blower (8400), 3-18 AC power indicators, 3-27 Boot command, 7-15 Advanced CMOS setup screen, Boot device, 5-6 AlphaBIOS, 8-36 default with factory-installed AlphaBIOS software, 5-7 Auto Start Count option, 5-20 setting default, 5-7 Auto Start Option, 5-20 Boot processor, 1-7, 6-25, 7-23...
Page 342 D_softerr environment variable, 7-11 D_trace environment variable, 7-11 Date command, 7-26 Cabinet control logic panel (CCL), Date, setting in AlphaBIOS firmware, 2-12 8-35 CCL module, 3-13, 3-23 DC distribution box, 3-9, 3-13 CD-ROM drive, 2-15, 3-7 Delete key, 7-7 Channel lines, 6-26 Deposit command, 7-27 CI disk, 5-7 Device name format...
Page 343: Installing Windows Nt
interleave, 7-13 creating and deleting partitions, 8- os_type, 7-13 removal, 7-20 formatting a FAT partition, 8-32 simm_callout, 7-13 setting up, 8-28 tta0_baud, 7-13 Help Environment variables AlphaBIOS firmware, 8-8 affecting test command, 6-39 AlphaBIOS first-level help screen, ew* (network), 7-12 Environmental characteristics AlphaBIOS second-level help 8200, 2-3...
Page 344: Exit Command
Options, 1-3, 3-20 Os_type environment variable, 5-2, LEDs 7-13 self-test, 6-17 Overstrike mode, 7-7 LFU, B-1 booting, B-2 display command, B-12 exit command, B-10 PAL temp register set, 7-29, 7-32 list command, B-4 Parameters, configuring in AlphaBIOS modify command, B-18 firmware, 8-34 modifying device attributes, B-18 Password, setting in AlphaBIOS...
Page 345: Show Device Command
Running maintenance programs, Show SEEPROM command, 7-58 AlphaBIOS, 8-40 Simm_callout environment variable, Running utility programs, 8-40 7-13 SRM console switching from AlphaBIOS, 8-4 SRM console command SCSI configuration screen, overview, 7-3 AlphaBIOS, 8-22 syntax, 7-4 SCSI configuration utilities, 1-5 SRM console firmware, 1-5 Secondary processor, 1-7 SRM console prompt, 7-3 Self-test...
Page 346: Updating Firmware
AlphaServer options, 1-3 Wildcarding, 7-18, 7-44 Uniprocessor Windows NT in self-test display, 6-25 auto start, 8-46 Update command, LFU, B-6 booting, 5-1, 5-18 Updating firmware designating primary operating AlphaBIOS, 8-26 system, 8-44 UTIL_CLI, 1-5, 7-40, C-1 installing, 8-38 Utilities overview, 1-4 selecting version, 8-42 Utility programs, 8-40 starting, 8-46...

This manual is also suitable for:

Alphaserver 8200 Alphaserver 8400 Alphaserver gs140

Compaq AlphaServer GS60 Operation Manual

Preface

Chapter 1 Introduction

Chapter 2 Alphaserver 8200 System

Chapter 3 Alphaserver 8400 System

Chapter 4 I/O Subsystems

Chapter 5 Booting an Operating System

Chapter 6 System Troubleshooting

Chapter 7 SRM Console Commands

Chapter 8 Alphabios Firmware

Appendix A Openvms and DIGITAL UNIX Boot Options

Appendix B Updating Firmware

Appendix C Running Configuration Utilities from the SRM Console

Glossary

Index

Quick Links

Troubleshooting

Related Manuals for Compaq AlphaServer GS60

Summary of Contents for Compaq AlphaServer GS60