Page 1 AlphaServer DS10 Console Reference Order Number: EK–DS10S–CR. B01 This manual describes the general operations of the AlphaServer DS10 system. It presents the SRM console (the command-line interface for Tru64 UNIX and OpenVMS operating systems), AlphaBIOS (the graphics interface for Windows NT and Linux), and remote console management.
Page 2 WARRANTIES OF MERCHANTABILITY, FITNESS FOR PARTICULAR PURPOSE, GOOD TITLE AND AGAINST INFRINGEMENT. This publication contains information protected by copyright. No part of this publication may be photocopied or reproduced in any form without prior written consent from Compaq Computer Corporation. © 1999 Compaq Computer Corporation.
Page 3 Warning! This is a Class A product. In a domestic environment this product may cause radio interference in which case the user may be required to take adequate measures. Achtung! Dieses ist ein Gerät der Funkstörgrenzwertklasse A. In Wohnbereichen können bei Betrieb dieses Gerätes Rundfunkstörungen auftreten, in welchen Fällen der Benutzer für entsprechende Gegenmaßnahmen verantwortlich ist.
Page 5: Table Of Contents
Contents Preface xiii Chapter 1 Operations Powering Up the System Power-Up Display Booting Tru64 UNIX 1.3.1 Booting from a Local Disk 1.3.2 Booting from a Remote Disk Installing Tru64 UNIX 1-10 Booting OpenVMS 1-12 1.5.1 Booting OpenVMS from a Local Disk 1-12 1.5.2 Booting OpenVMS from a Disk on a Cluster...
Page 6 Chapter 2 SRM Console Invoking the SRM Console Commands 2.2.1 Command Summary 2.2.2 Commands: Syntax 2.2.3 Commands: Special Keystrokes and Characters Show Commands 2.3.1 Show Config 2.3.2 Show Device 2-10 2.3.3 Show Memory 2-12 2.3.4 Show PAL 2-12 2.3.5 Show Power 2-13 2.3.6 Show Version...
Page 7 2.19.6 console 2-44 2.19.7 ew*0_mode 2-45 2.19.8 ew*0_protocols 2-45 2.19.9 kbd_hardware_type 2-46 2.19.10 language 2-46 2.19.11 os_type 2-47 2.19.12 password 2-47 2.19.13 pci_parity 2-48 2.19.14 pk*0_fast 2-48 2.19.15 pk*0_host_id 2-49 2.19.16 pk*0_soft_term 2-49 2.19.17 tt_allow_login 2-50 Chapter 3 AlphaBIOS Console Starting AlphaBIOS Keyboard Conventions and Help System Configuration...
Page 8 Chapter 4 Remote Console Manager RMC Components Terminal Setup Operating Modes Entering the RMC SRM Environment Variables for COM1 Status Monitoring Remote Power (On/Off) Remote Halt (In/Out) 4-10 Configuring Remote Dial-In 4-12 4.10 Configuring Dial-Out Alert 4-14 4.11 Dialing In 4-17 4.12 Resetting the RMC to Factory Defaults...
Page 9 Appendix A Setting Jumpers Warnings and Cautions ................ A-2 Remove Power from the System ............A-3 Open the System ................... A-4 Remove the Floppy Disk Enclosure ............A-5 Set Jumpers ..................A-6 Restore Power ..................A-8 Examples 1–1 Power-Up Display ..................1-4 1–2 Booting Tru64 UNIX from a Local Disk ..........1-6 1–3...
Page 10 2–16 Lfu Command..................2-28 2–17 Crash Command ..................2-30 2–18 Setting and Showing Environment Variables........2-32 2–19 Creating a User-Defined Environment Variable .........2-32 2–20 Deposit Command................2-33 2–21 Examine Command................2-33 2–22 More Command..................2-34 2–23 Initialize Command................2-35 2–24 Help Command ..................2-36 2–25 Switching to the AlphaBIOS Console ..........2-37 2–26 Changing Baud Rate ................2-43 4–1...
Page 11 3–17 Delete Partition Dialog Box ..............3-25 3–18 Formatting a FAT Partition..............3-26 3–19 Standard Formatting ................3-27 3–20 Standard CMOS Setup Screen.............3-28 3–21 Advanced CMOS Setup Screen ............3-30 3–22 Installing Windows NT ................3-32 3–23 Operating System Selections ...............3-34 3–24 Primary Operating System ..............3-36 3–25 Operating System Selection Setup............3-38 3–26...
Page 12 4–3 Halt/Reset Button Function under Operating Systems.......4-11 4–4 Elements of Dial String and Alert String ..........4-16 4–5 RMC Troubleshooting ................4-19 A–1 Jumpers and Factory Default Positions..........A-7...
Page 13: Preface
Preface Intended Audience This manual is for anyone who manages, operates, or services an AlphaServer DS10 system. Document Structure This manual uses a structured documentation design. Topics are organized into small sections for efficient reference. Each topic begins with an abstract. You can quickly gain a comprehensive overview by reading only the abstracts.
Page 14 ( ) or are preceded by a pound sign (#) and are given in boldface italics. Documentation Titles This lists the AlphaServer DS10 documentation. Table 1 AlphaServer DS10 Documentation Title Order No.
Page 15: Operations
Chapter 1 Operations This chapter provides basic operating instructions, including powering up the system, booting, and operating system installation. Note that your choice of operating system has already been installed at the factory; this information is provided so that should you decide to change operating systems, you may. It also provides information about updating firmware.
Page 16: Powering Up The System
Powering Up the System To power up the system, check your power setting (see Figure 1– 1). Then press the On/Off button to the On position (Figure 1–2). The button is in the lower right hand corner of the front of the system.
Page 17: Location Of Control Panel And On/Off Button
Figure 1–2 Location of Control Panel and On/Off Button PK1043b Table 1–1 Control Panel Functions Symbol Function Halt button. Under OpenVMS and Tru64 UNIX, suspends the operating system and returns control to the SRM console. Under Windows NT, this button initiates a system reset. Environmental amber LED.
Page 18: Power-Up Display
Power-Up Display Testing begins after pressing the On/Off button, and screen text similar to that in Example 1–1 displays (if the console terminal is a serial terminal connected to the COM1 port), along with status messages in the control panel display. If the console terminal is a graphics monitor, only the last few lines of the power-up display print.
Page 19 Memory size is determined. The PCI bridges and attendant buses (indicated as IODn by the console) are probed and the devices are reported. I/O adapters are configured. Power-up slot 14 corresponds to the bottom physical slot, slot 0. See Figure 1–3.
Page 20: Booting Tru64 Unix
Booting Tru64 UNIX Tru64 UNIX® can be booted from a local disk or a remote disk through an Ethernet connection. Refer to the documentation shipped with the operating system for booting instructions. 1.3.1 Booting from a Local Disk Example 1–2 Booting Tru64 UNIX from a Local Disk 444Â‡vƒÂrswqsÂ...
Page 21 ÂUˆi†ˆw‚uÂ@s‡yˆƒ„ÂHƒuw‚Âƒ‚Ârw‡„€i“Â0 ÂYiwˆÂtƒ†ÂˆvsÂ@s‡yˆƒ„ÂHƒuw‚Â‡q†ss‚Âpstƒ†sÂ€ƒuuw‚uÂw‚ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ The show device command displays device information, including name and type of connection to the system. See Section 2.3.2 for a description of the show device command and the device naming convention. The operating system is on the third disk connected to the system through the controller in slot 3 of the PCI.
Page 22: Booting From A Remote Disk
1.3.2 Booting from a Remote Disk Example 1–3 Booting Tru64 UNIX from a Remote Disk 444Â‡vƒ‘ÂrswqsÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ ÂÂ s‘i ( ÂÂÂÂÂÂÂÂÂAY7 ÂÂÂÂ ( "8A")9& ÂÂÂÂÂÂÂÂ 444ÂpƒƒˆÂt€iu‡Âi‚Â„†ƒˆƒqƒ€‡Âpƒƒˆ„Âs‘iÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ pƒƒˆÂs‘i $!Ât€iu‡Âi‚ 8‰w€rw‚uÂBTWÂˆip€s V†“w‚uÂ8QQVRÂpƒƒˆ 8†ƒirqi‡ˆw‚uÂ8QQVRÂTs…‰s‡ˆ TsqswsrÂ8QQVRÂRiqysˆÂBw€sÂPis0Âi†ir†w‡†w‡ i€„viv‰‚w’ €ƒqi€Âw‚sˆÂirr†s‡‡0Â!&!""!"("& †sƒˆsÂw‚sˆÂirr†s‡‡0Â!&!""!"(%) VBVRÂTsirÂBw€sÂPis0Âi†ir†w‡†w‡ i€„viv‰‚w’ pƒƒˆ‡ˆ†i„ÂqƒrsÂ†sirÂw‚...
Page 23 The show device command displays device information, including name and type of connection to the system. See Section 2.3.2 for a description of the show device command and the device naming convention. The operating system is on a remote disk accessed through the Ethernet controller in slot 4 of the PCI.
Page 24: Installing Tru64 Unix
Installing Tru64 UNIX Tru64 UNIX is installed from the CD-ROM. Refer to the documentation shipped with the CD-ROM for installation instructions. Example 1–4 Installing Tru64 UNIX 444Â‡vƒ‘Ârswqs ÂÂ ryi% % '!ÂÂÂÂÂÂÂÂÂÂÂÂÂ@G7% ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂTT@$'ÂÂ!##'Â ÂÂ 444ÂpƒƒˆÂryi% ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ pƒƒˆÂryi% % '!Ât€iu‡Â7 p€ƒqyÂ ÂƒtÂryi% % '!Âw‡ÂiÂi€wrÂpƒƒˆÂp€ƒqy †sirw‚uÂ!&Âp€ƒqy‡Ât†ƒÂryi% % '! pƒƒˆ‡ˆ†i„ÂqƒrsÂ†sirÂw‚...
Page 25 Use the boot command to install the operating system from the CD- ROM, which is either dka500 or dqa0. See your operating system documentation for further installation instructions. Operations 1-11...
Page 26: Booting Openvms
Booting OpenVMS OpenVMS can be booted from a local disk, a disk connected through a cluster, or a remote disk through an Ethernet connection. Refer to the documentation shipped with the operating system for booting instructions. 1.5.1 Booting OpenVMS from a Local Disk Example 1–5 Booting OpenVMS from a Local Disk ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ...
Page 27 Example 1–5 Booting OpenVMS from a Local Disk (Continued) ÂÂ VvsÂQ„s‚XIUÂ‡“‡ˆsÂw‡Â‚ƒ‘Âs’sq‰ˆw‚uÂˆvsÂ‡wˆs‡„sqwtwqÂ‡ˆi†ˆ‰„Âqƒi‚r‡ ÂÂ Ys€qƒsÂˆƒÂQ„s‚XIUÂVIÂ7€„viÂQ„s†iˆw‚uÂU“‡ˆsÂXs†‡wƒ‚ÂX'!"Â W‡s†‚is0 The show device command displays device information. See Section 2.3.2 for a description of the show device command and the device naming convention. The boot_reset environment variable was previously set to “on,” causing the power-up trace to display when the system initializes (see Section 1.2).
Page 28: Booting Openvms From A Disk On A Cluster
1.5.2 Booting OpenVMS from a Disk on a Cluster Example 1–6 Booting OpenVMS from a Disk on a Cluster ÂÂÂÂÂÂÂÂ 444Â‡vƒ‘ÂpƒƒˆrstgrsÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ pƒƒˆrstgrsÂÂÂÂÂÂÂÂÂr‰i!! ( ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ 444Â‡vƒ‘Ârswqs Â Â Â r‰i!! ( ÂÂÂÂÂÂÂÂÇ!Ç@E7!! Â@APXATÂÂÂÂÂÂÂÂÂÂTB'$ ÂÂ ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ 444Âpƒƒˆ pƒƒˆÂr‰i!! ( Ât€iu‡Â 8‰w€rw‚uÂBTWÂˆip€s Â...
Page 29 The bootdef_dev environment variable specifies the default boot device. The show device command displays device information, including name and type of connection to the system. See Section 2.3.2 for a description of the show device command and the device naming convention.
Page 30: Booting Openvms From A Remote Disk
1.5.3 Booting OpenVMS from a Remote Disk Example 1–7 Booting OpenVMS from a Remote Disk 44Â‡vƒ‘ÂrswqsÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ ÂÂ ÂÂÂÂÂÂÂ s‘i ( ÂÂÂÂÂÂÂÂÂAY7 ÂÂÂÂ ( "8A")9& ÂÂ 444ÂpƒƒˆÂs‘i Ât€iu‡Â ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ pƒƒˆÂs‘i " Ât€iu‡Â 8‰w€rw‚uÂBTWÂˆip€s V†“w‚uÂIQRÂpƒƒˆ Psˆ‘ƒ†yÂ€ƒirÂqƒ„€sˆs ÂÂ Â...
Page 31 The show device command displays device information, including name and type of connection to the system. In this example the Ethernet connection is ewa0. See Section 2.3.2 for a description of the show device command and the device naming convention. The boot command specifies ewa0 as the boot device.
Page 32: Installing Openvms
Installing OpenVMS OpenVMS is installed from the CD-ROM. Refer to the documentation shipped with the OpenVMS kit for complete installation instructions. Example 1–8 Installing OpenVMS 444ÂpƒƒˆÂt€iu‡Â Âryi% ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ E‚wˆwi€w”w‚u UTQIÂX# Âƒ‚Âq„‰ ÂÂcVvsÂw‚wˆwi€w”iˆwƒ‚Ârw‡„€i“Â„†w‚ˆ‡ÂUssÂUsqˆwƒ‚Â!"e 7€„viUs†s†Â@U" Â9ƒ‚‡ƒ€sÂX%$’Â"7RT!)))Â!%0!'0$( 9RWÂ Âpƒƒˆw‚u pƒƒˆÂryi% % !!Ât€iu‡Â 8‰w€rw‚uÂBTWÂˆip€s p€ƒqyÂ...
Page 33 Example 1–8 Installing OpenVMS (Continued) ÂR€si‡sÂqvƒƒ‡sÂƒ‚sÂƒtÂˆvsÂtƒ€€ƒ‘w‚u0 ÂÂÂÂ!ÂÂE‚‡ˆi€€Âƒ†Â‰„u†irsÂQ„s‚XIUÂ7€„viÂXs†‡wƒ‚Â'!’ ÂÂÂÂ"ÂÂHw‡ˆÂ€i“s†srÂ„†ƒr‰qˆÂywˆ‡ÂˆviˆÂˆvw‡Â„†ƒqsr‰†sÂqi‚Âw‚‡ˆi€€ ÂÂÂÂ#ÂÂE‚‡ˆi€€Âƒ†Â‰„u†irsÂ€i“s†srÂ„†ƒr‰qˆ‡ ÂÂÂÂ$ÂÂA’sq‰ˆsÂ@9HÂqƒi‚r‡Âi‚rÂ„†ƒqsr‰†s‡ ÂÂÂÂ%ÂÂUv‰ˆÂrƒ‘‚Âˆvw‡Â‡“‡ˆs A‚ˆs†Â9DQE9AÂƒ†Â5ÂˆƒÂ†s„siˆÂs‚‰0Â!"#$%5 Use the boot command to install the operating system from the CD- ROM, which is either dka500 or dqa0. See your operating system documentation for installation instructions. Operations 1-19...
Page 34: Booting Windows Nt
Booting Windows NT Microsoft Windows NT is started from the AlphaBIOS Boot screen. Figure 1–4 AlphaBIOS Boot Screen 7€„vi8EQUÂUsˆ‰„ B!3ÂDs€„ @w‡„€i“ÂU“‡ˆs 7€„vi8EQUÂW„u†irs| Di†rÂ@w‡yÂUsˆ‰„| 9IQUÂUsˆ‰„| Psˆ‘ƒ†yÂUsˆ‰„| E‚‡ˆi€€ÂQ„s†iˆw‚uÂU“‡ˆs Wˆw€wˆws‡ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ 7pƒ‰ˆÂ7€„vi8EQU| R†s‡‡ÂAPVATÂˆƒÂw‚‡ˆi€€ÂYw‚rƒ‘‡ÂPV AU9 3ÂA’wˆ DS10 Console Reference 1-20...
Page 35 Two SRM environment variables must be set properly for Windows NT to boot. The setting of the SRM os_type environment variable determines if AlphaBIOS is loaded and started on reset and power-up. If os_type is set to nt, after the power-up display the SRM console is loaded and started, and it then loads and starts the AlphaBIOS console.
Page 36: Installing Windows Nt
Installing Windows NT Windows NT is installed from the CD-ROM. Insert the CD-ROM into the drive, start AlphaBIOS Setup, select the menu item Install Windows NT, and follow the prompts. Figure 1–5 Installing Windows NT 7€„vi8EQUÂUsˆ‰„ B!3ÂDs€„ @w‡„€i“ÂU“‡ˆs 7€„vi8EQUÂW„u†irs| Di†rÂ@w‡yÂUsˆ‰„| 9IQUÂUsˆ‰„| Psˆ‘ƒ†yÂUsˆ‰„| E‚‡ˆi€€ÂYw‚rƒ‘‡ÂPV...
Page 37 Windows NT requires a partitioned and formatted hard disk drive. If your drive is not partitioned or formatted, follow the instructions in Section 3.5 before installing the Windows NT operating system. Up to three versions of Windows NT can be resident in a system at one time. If this is a new Windows NT installation, start with this procedure: 1.
Page 38: Switching Between Operating Systems
Switching Between Operating Systems The system supports multiple operating systems on different system and data disks not in the machine at the same time. That is, you can have a set of disks for each operating system. CAUTION: This operation is not for the faint hearted especially if you have a shadow system disk and shadow arrays.
Page 39: Switching To Tru64 Unix Or Openvms
memory test and password, in Advanced CMOS Setup as needed. Press F10 to save the changes. 10. From the AlphaBIOS Setup screen select Utilities. In the selection box, choose OS Selection Setup. Make sure the selections (boot name, boot file, and so on) are what you want. Press F10 to save the changes. 11.
Page 40: Updating Firmware
1.10 Updating Firmware Start the Loadable Firmware Update (LFU) utility by issuing the lfu command at the SRM console prompt, booting it from the CD-ROM while in the SRM console, or selecting Update AlphaBIOS in the AlphaBIOS Setup screen. Example 1–9 Starting LFU from the SRM Console 444ÂPJY ÂÂÂÂÂÂÂÂÂÂÂHƒirip€sÂBw†‘i†sÂW„riˆsÂWˆw€wˆ“Â Us€sqˆÂtw†‘i†sÂ€ƒirÂrswqsÂqri Âri Âs‘i Âƒ†...
Page 41 Use the Loadable Firmware Update (LFU) utility to update system firmware. You can start LFU from either the SRM console or the AlphaBIOS console. • From the SRM console, start LFU by issuing the lfu command (see Example 1–9). Also from the SRM console, LFU can be booted from the Alpha CD-ROM (V5.4 or later), as shown in Example 1–10.
Page 42: Updating Firmware From The Cd-Rom
1.10.1 Updating Firmware from the CD-ROM Insert the Alpha CD-ROM, start LFU, and select cda0 as the load device. Example 1–11 Updating Firmware from the CD-ROM ÂHƒirip€sÂBw†‘i†sÂW„riˆsÂWˆw€wˆ“Â ÂÂÂÂÂÂÂÂÂÂ Us€sqˆÂtw†‘i†sÂ€ƒirÂrswqsÂqri Âri Âs‘i Âƒ† R†s‡‡Â2†sˆ‰†‚4ÂˆƒÂp“„i‡‡Â€ƒirw‚uÂi‚rÂ„†ƒqssrÂˆƒÂHBW0ÂGHEÂÂÂÂÂÂÂ R€si‡sÂs‚ˆs†ÂˆvsÂ‚isÂƒtÂˆvsÂƒ„ˆwƒ‚‡Âtw†‘i†sÂtw€s‡Â€w‡ˆÂƒ† R†s‡‡Â2†sˆ‰†‚4ÂˆƒÂ‰‡sÂˆvsÂrsti‰€ˆÂtw€s‚isÂc@U! BYe0Â(7'4ÂÂÂÂÂ 9ƒ„“w‚uÂ@U! 9RÂt†ƒÂ@G7% % !!Â 9ƒ„“w‚uÂc@U! eV9TA7@IAÂt†ƒÂ@G7% % !!Â 9ƒ„“w‚uÂc@U! eV9UTITQIÂt†ƒÂ@G7% % !!Â 9ƒ„“w‚uÂc@U! eV97T9TQIÂt†ƒÂ@G7% % !!Â...
Page 43 Select the device from which firmware will be loaded. The choices are the internal CD-ROM, the internal floppy disk, or a network device. In Example 1–11, the internal CD-ROM is selected. Select the file that has the firmware update, or press Enter to select the default file.
Page 44 Example 1–11 Updating Firmware from the CD-ROM (Continued) WR@4Â€w‡ˆÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ @swqsÂÂÂÂÂÂÂÂÂ9‰††s‚ˆÂTsw‡wƒ‚ÂÂÂÂBw€s‚isÂÂÂÂÂÂÂW„riˆsÂTsw‡wƒ‚ B‡pÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ#!’ÂÂÂÂÂÂÂÂÂÂÂÂt‡pgt‘ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ#’ PˆÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ%&)ÂÂÂÂÂÂÂÂÂÂÂÂÂ‚ˆgt‘ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ%’’ Ry’ ÂÂÂÂÂÂÂÂÂÂÂÂÂÂ7!!ÂÂÂÂÂÂÂÂÂÂÂÂÂÂy”„‡igt‘ÂÂÂÂÂÂÂÂÂÂÂÂÂÂ7!! U†ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ%$’ÂÂÂÂÂÂÂÂÂÂÂÂ‡†gt‘ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ%$’’ R‰iÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ7"!$ÂÂÂÂÂÂÂÂÂÂÂÂÂqw„qigt‘ÂÂÂÂÂÂÂÂÂÂÂÂÂÂ7"’’ WR@4Â‰„riˆsÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Y7TPEPC0Â‰„riˆs‡Âi“ÂˆiysÂ‡ss†i€Âw‚‰ˆs‡ÂˆƒÂqƒ„€sˆsÂtƒ†ÂsiqvÂrswqs 9ƒ‚tw†Â‰„riˆsÂƒ‚0Â7€„vi8EQUÂÂÂÂÂÂÂcaPeÂ“ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ@QÂPQVÂ78QTVÄ 7€„vi8EQUÂÂÂÂÂW„riˆw‚uÂˆƒÂX&$ !ÂXs†wt“w‚uÂX&$ !ÂR7UUA@ 9ƒ‚tw†Â‰„riˆsÂƒ‚0Â‡†t€i‡vÂÂÂÂÂÂÂÂcaPeÂ“ ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ@QÂPQVÂ78QTVÄ ‡†t€i‡vÂÂÂÂÂÂÂÂW„riˆw‚uÂˆƒÂX& #ÂÂXs†wt“w‚uÂX& #ÂÂR7UUA@ WR@4Âs’wˆÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ DS10 Console Reference 1-30...
Page 45 Use the LFU list command to determine the revision of firmware in a device and the most recent revision of that firmware available in the selected file. In this example, the resident firmware for each console (SRM and AlphaBIOS) is at an earlier revision than the firmware in the update file.
Page 46: Updating Firmware From Floppy Disks
1.10.2 Updating Firmware from Floppy Disks Create two update diskettes before starting LFU: one for console updates and one for I/O. See Section 1.10.3 for an example of the update procedure. Table 1–2 File Locations for Creating Update Diskettes on a PC Console Update Diskette I/O Update Diskette DS10FW.TXT...
Page 47 Example 1–12 Creating Update Diskettes on an OpenVMS System Console update diskette ÇÂw‚…‰w†sÂwu‚ƒ†sÂÅE‚‡s†ˆÂp€i‚yÂD@Ât€ƒ„„“Âw‚Â@X7 Âˆvs‚Âqƒ‚ˆw‚‰sÅ ÇÂ‡sˆÂs†wt“ ÇÂ‡sˆÂ„†ƒq„†w3i€€ ÇÂw‚wˆÂrs‚‡wˆ“3vrw‚rs’3psuw‚Âri 0Âˆqƒr‡"q„ ÇÂƒ‰‚ˆÂri 0Âˆqƒr‡"q„ ÇÂq†siˆsÂrw†sqˆƒ†“Âri 0cr‡! e ÇÂqƒ„“Âˆq†sirs‡“‡Âri 0cr‡! eˆq†sirs‡“‡ ÇÂqƒ„“Â@U! t‘ˆ’ˆÂri 0cr‡! er‡! t‘ˆ’ˆ ÇÂqƒ„“Â@U! q„ˆ’ˆÂri 0cr‡! er‡! q„ˆ’ˆ ÇÂqƒ„“Âˆq‡††ƒ‡“‡Âri 0cr‡! eˆq‡††ƒ‡“‡ ÇÂqƒ„“Âˆqi†q†ƒ‡“‡Âri 0cr‡! eˆqi†q†ƒ‡“‡ ÇÂrw‡ƒ‰‚ˆÂri 0 ÇÂ‡sˆÂ‚ƒs†wt“...
Page 48: Performing The Update From Floppy Disks
1.10.3 Performing the Update from Floppy Disks Insert an update diskette (see Section 1.10.2) into the floppy drive. Start LFU and select dva0 as the load device. Example 1–13 Updating Firmware from the Floppy Disk ÂHƒirip€sÂBw†‘i†sÂW„riˆsÂWˆw€wˆ“Â ÂÂÂÂÂÂÂÂÂÂ Us€sqˆÂtw†‘i†sÂ€ƒirÂrswqsÂqri Âri Âs‘i Âƒ† R†s‡‡Â2†sˆ‰†‚4ÂˆƒÂp“„i‡‡Â€ƒirw‚uÂi‚rÂ„†ƒqssrÂˆƒÂHBW0ÂHZEÂÂÂÂÂÂÂÂÂÂÂÂ...
Page 49 Select the device from which firmware will be loaded. The choices are the internal CD-ROM, the internal floppy disk, or a network device. In this example, the internal floppy disk is selected. Select the file that has the firmware update, or press Enter to select the default file.
Page 50 Example 1–13 Updating Firmware from the Floppy Disk (Continued) WR@4Â‰„riˆsÂ„tw ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Y7TPEPC0Â‰„riˆs‡Âi“ÂˆiysÂ‡ss†i€Âw‚‰ˆs‡ÂˆƒÂqƒ„€sˆsÂtƒ†ÂsiqvÂrswqs 9ƒ‚tw†Â‰„riˆsÂƒ‚0Â„tw ÂÂÂÂÂÂÂÂÂÂÂÂcaPeÂ“ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ@QÂPQVÂ78QTVÄ „tw ÂÂÂÂÂÂÂÂÂÂÂÂW„riˆw‚uÂˆƒÂ#! ÂXs†wt“w‚uÂˆƒÂ#! ÂR7UUA@ WR@4Â€t‰ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ ÂÂÂÂÂÂÂÂÂÂÂHƒirip€sÂBw†‘i†sÂW„riˆsÂWˆw€wˆ“Â Us€sqˆÂtw†‘i†sÂ€ƒirÂrswqsÂqri Âri Âs‘i Âƒ† R†s‡‡Â2†sˆ‰†‚4ÂˆƒÂp“„i‡‡Â€ƒirw‚uÂi‚rÂ„†ƒqssrÂˆƒÂHBW0Âri R€si‡sÂs‚ˆs†ÂˆvsÂ‚isÂƒtÂˆvsÂƒ„ˆwƒ‚‡Âtw†‘i†sÂtw€s‡Â€w‡ˆÂƒ† R†s‡‡Â2†sˆ‰†‚4ÂˆƒÂ‰‡sÂˆvsÂrsti‰€ˆÂtw€s‚isÂc@U! EQ@U! 9Re0ÂÂÂÂ ÂVvsÂt‰‚qˆwƒ‚Âˆip€sÂrw‡„€i“‡Âtƒ€€ƒ‘srÂp“ÂˆvsÂWR@4Â„†ƒ„ˆ ÂÂ9ƒ‚‡ƒ€sÂtw†‘i†sÂqi‚Â‚ƒ‘ÂpsÂ‰„riˆsr WR@4Âs’wˆÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ DS10 Console Reference 1-36...
Page 51 The update command updates the device specified or all devices. For each device, you are asked to confirm that you want to update the firmware. The default is no. Once the update begins, do not abort the operation. Doing so will corrupt the firmware on the module. The lfu command restarts the utility so that console firmware can be updated.
Page 52: Updating Firmware From A Network Device
1.10.4 Updating Firmware from a Network Device Copy files to the local MOP server’s MOP load area, start LFU, and select ewa0 as the load device. Example 1–15 Updating Firmware from a Network Device ÂÂÂÂÂÂÂÂÂÂÂHƒirip€sÂBw†‘i†sÂW„riˆsÂWˆw€wˆ“Â Us€sqˆÂtw†‘i†sÂ€ƒirÂrswqsÂqri Âri Âs‘i Âƒ† R†s‡‡Â2†sˆ‰†‚4ÂˆƒÂp“„i‡‡Â€ƒirw‚uÂi‚rÂ„†ƒqssrÂˆƒÂHBW0ÂI[EÂÂÂÂÂÂÂ R€si‡sÂs‚ˆs†ÂˆvsÂ‚isÂƒtÂˆvsÂƒ„ˆwƒ‚‡Âtw†‘i†sÂtw€s‡Â€w‡ˆÂƒ†...
Page 53 Before starting LFU, download the update files from the Internet. You will need the files with the extension .SYS. Copy these files to your local MOP server’s MOP load area. Select the device from which firmware will be loaded. The choices are the CD-ROM, the internal floppy disk, or a network device.
Page 54 Example 1–15 Updating Firmware from a Network Device (Continued) WR@4Â‰„riˆsÂÂi€€ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Y7TPEPC0Â‰„riˆs‡Âi“ÂˆiysÂ‡ss†i€Âw‚‰ˆs‡ÂˆƒÂqƒ„€sˆsÂtƒ†ÂsiqvÂrswqs ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ@QÂPQVÂ78QTVÄ 7€„vi8EQUÂÂÂÂW„riˆw‚uÂˆƒÂX&$ !ÂXs†wt“w‚uÂX&$ !ÂÂR7UUA@ ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ@QÂPQVÂ78QTVÄ y”„‡i ÂÂÂÂÂÂÂÂW„riˆw‚uÂˆƒÂÂ7!!ÂÂÂÂÂÂXs†wt“w‚uÂ7!!ÂÂR7UUA@ ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ@QÂPQVÂ78QTVÄ y”„‡i!ÂÂÂÂÂÂÂÂW„riˆw‚uÂˆƒÂÂ7!!ÂÂÂÂÂÂXs†wt“w‚uÂ7!!ÂÂR7UUA@ ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ@QÂPQVÂ78QTVÄ ‡†t€i‡vÂÂÂÂÂÂW„riˆw‚uÂˆƒÂX& #ÂÂXs†wt“w‚uÂX& #ÂÂR7UUA@ WR@4Âs’wˆÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ The update command updates the device specified or all devices. In this example, the wildcard indicates that all devices supported by the selected update file will be updated.
Page 55: Lfu Commands
1.10.5 LFU Commands The commands summarized in Table 1–3 are used to update system firmware. Table 1–3 LFU Command Summary Command Function display Shows the physical configuration of the system. exit Terminates the LFU program. help Displays the LFU command list. Restarts the LFU program.
Page 56 help The help (or ?) command displays the LFU command list, shown below. ÂB‰‚qˆwƒ‚ÂÂÂÂ@s‡q†w„ˆwƒ‚ Â@w‡„€i“ÂÂÂÂÂ@w‡„€i“‡ÂˆvsÂ‡“‡ˆsk‡Âqƒ‚twu‰†iˆwƒ‚Âˆip€s ÂA’wˆÂÂÂÂÂÂÂÂ@ƒ‚sÂs’wˆÂHBWÂ†s‡sˆ ÂHw‡ˆÂÂÂÂÂÂÂÂHw‡ˆ‡ÂˆvsÂrswqsÂ†sw‡wƒ‚Âtw†‘i†sÂ‚isÂi‚rÂ‰„riˆs ÂÂÂÂÂÂÂÂÂÂÂÂÂ†sw‡wƒ‚ ÂHt‰ÂÂÂÂÂÂÂÂÂTs‡ˆi†ˆ‡ÂHBW ÂTsirsÂÂÂÂÂÂHw‡ˆ‡Âw„ƒ†ˆi‚ˆÂ†s€si‡sÂw‚tƒ†iˆwƒ‚ ÂW„riˆsÂÂÂÂÂÂTs„€iqs‡Âq‰††s‚ˆÂtw†‘i†sÂ‘wˆvÂ€ƒirip€sÂriˆiÂwius ÂXs†wt“ÂÂÂÂÂÂ9ƒ„i†s‡Â€ƒirip€sÂi‚rÂvi†r‘i†sÂwius‡ Â5Âƒ†ÂDs€„ÂÂÂUq†ƒ€€‡Âˆvw‡Ât‰‚qˆwƒ‚Âˆip€s The lfu command restarts the LFU program. This command is used when the update files are on a floppy disk. The files for updating both console firmware and I/O firmware are too large to fit on a 1.44 MB disk, so only one type of firmware can be updated at a time.
Page 57 update The update command writes new firmware 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 source image. 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 58: Hard Disk Partitioning For Windows Nt
1.11 Hard Disk Partitioning for Windows NT The recommended hard disk partition on the first hard disk in your system is: Partition 1 should be 6 megabytes less than the total size of the drive, but no more than 4095 MB. This large partition holds the operating system and the application and data files.
Page 59 • Disk controller malfunction. Most controllers come with a diagnostic utility to test controller functioning. If a controller error is found, call the manufacturer for a replacement. • Improper SCSI termination. Many SCSI controllers require that the terminating resistor packs be removed from all drives between the controller and last drive.
Page 60: System Partitions
1.11.2 System Partitions To install Windows NT, a system partition must be defined. If no system partition is found, the user is asked to choose from the available FAT partitions. The purpose of the system partition is twofold. First, it tells the Windows NT installation program where to place the OS Loader and hardware support files.
Page 61: How Alphabios Works With System Partitions
1.11.3 How AlphaBIOS Works with System Partitions If you are installing Windows NT for the first time, AlphaBIOS will determine that a system partition has not been defined when you select Install Windows NT in the AlphaBIOS Setup screen (see Figure 1–7). When this occurs, AlphaBIOS searches for all FAT partitions on the system.
Page 62: Using The Halt Button
1.12 Using the Halt Button Under OpenVMS and Tru64 UNIX, the halt button pauses the operating system. Under Windows NT, the Halt button resets the system, generating power-up tests and output to the console terminal. Figure 1–8 Halt/Reset Button PK1043b Figure 1–9 Halt/Reset Jumper Setting for Setting for...
Page 63 Use the Halt button to halt the Tru64 UNIX or OpenVMS operating system when it hangs, clear the SRM console password (see Section 2.9.2), or force a halt assertion (see Section 1.13). The Halt button operates like issuing an SRM halt command.
Page 64: Halt Assertion
1.13 Halt Assertion A halt assertion allows you to disable automatic boots of the operating system so that you can perform tasks from the SRM console. Under certain conditions, you might want to force a “halt assertion A halt .” assertion differs from a simple halt in that the SRM console “remembers”...
Page 65 Halt Assertion with RMC Haltin Command Enter the RMC haltin command at any time except during power-up. For example, enter haltin during an operating system session or when the AlphaBIOS console is running. If you enter the RMC haltin command during a Tru64 UNIX or OpenVMS session, the system halts back to the SRM console, and the halt status is saved.
Page 66 Disabling the SRM Power-Up Script The system has a power-up script (file) named “nvram” that runs every time the system powers up. If you accidentally insert a command in the script that will cause a system problem, disable the script by using one of the methods described previously to force a halt assertion.
Page 67: Srm Console
Chapter 2 SRM Console The SRM console is the command-line interface that supports the Tru64 UNIX and OpenVMS operating systems. (Windows NT uses the SRM test command, only.) The SRM console is used to bootstrap the operating system, configure and test the system hardware, examine system options for errors, and set or change environment variables.
Page 68: Invoking The Srm Console
Invoking the SRM Console When a system is powered up, the SRM console runs and either remains running or passes control to another console or an operating system. If the system is already running, invoke the SRM console by shutting down the operating system or by pressing the Halt button on the control panel.
Page 69: Commands
Commands This section presents a command summary (Table 2–1), Gives the syntax for the console commands (Table 2–2), and explains the special keystrokes and characters available in SRM console mode (Table 2–3). 2.2.1 Command Summary Table 2–1 Summary of SRM Console Commands Command Function alphabios...
Page 70 Table 2–1 Summary of SRM Console Commands (Continued) Command Function more Displays a file one screen at a time. prcache Utility that initializes and displays status of the optional PCI NVRAM device. set envar Sets or modifies the value of an environment variable.
Page 71: Commands: Syntax
2.2.2 Commands: Syntax Table 2–2 Syntax for SRM Console Commands Parameter Attribute or Action Length Up to 255 characters, not including the terminating carriage return or any characters deleted as the command is entered. A command longer than 80 characters and without the backslash character (see Table 2–3) causes display of an error message.
Page 72: Commands: Special Keystrokes And Characters
2.2.3 Commands: Special Keystrokes and Characters Table 2–3 Special Characters for SRM Console Character Function Return or Terminates a command line. No action is taken on a Enter command until it is terminated. If no characters are entered and this key is pressed, the console just redisplays the prompt.
Page 73 Character Function Stops output to the console terminal for the current Ctrl/O command. Toggles between enable and disable. The output can be reenabled by other means as well: when the console prompts for a command, issues an error message, or enters program mode, or when Ctrl/P is entered.
Page 74: Show Commands
I/O buses. This is the configuration at the most recent initialization. Syntax: show config Example 2–1 Show Config Command >>> show config AlphaServer DS10 466 MHz SRM Console: V5X-XXX PALcode: OpenVMS PALcode V1.56-45, Tru64 UNIX PALcode V1.50-48 Processors...
Page 75 Bus 00 Slot 11: DE500-BA Network Controller ewb0.0.0.11.0 08-00-2B-86-1B-BB Bus 00 Slot 13: Acer Labs M1543C IDE dqa.0.0.13.0 dqa1.1.0.13.0 CD-532E Bus 00 Slot 14: DEC PowerStorm Bus 00 Slot 15: DECchip 21152-AA Bridge to Bus 2, PCI Bus 00 Slot 16: QLogic ISP1020 pkc0.6.0.16.0 SCSI Bus ID 6 dkc0.0.0.16.0...
Page 76: Show Device
2.3.2 Show Device The show device command displays status for devices and controllers in the system: SCSI and MSCP devices, the internal floppy drive, and the network. Syntax: show device [ controller_name ] controller_name The controller name or abbreviation. When abbreviations or wildcards are used, all controllers that match the type are displayed.
Page 77: Device Naming Convention
Table 2–4 Device Naming Convention Category Description Driver ID Two-letter designator of port or class driver SCSI disk FDDI device ATAPI CD-ROM SCSI tape RAID set device DSSI tape DSSI disk SCSI port Diskette drive DSSI port Ethernet port Storage adapter One-letter designator of storage adapter (a, b, c...).
Page 78: Show Memory
2.3.3 Show Memory The show memory command displays information about each memory bank: slot number, size in megabytes, and the starting address. Syntax: show memory Example 2–3 Show Memory Command >>> show memory Array # Size Base Addr ------- ---------- --------- 128 MB 000000000...
Page 79: Show Power
2.3.5 Show Power The show power command displays status information about the power supply, the system, PCI and CPU fans, and temperature. This command is useful for displaying the error state of a Tru64 UNIX or OpenVMS system that shuts down because of a fan, temperature, or power supply failure.
Page 80: Show Version
2.3.6 Show Version The show version command displays the version of the SRM console program that is installed on the system. Syntax: show version Example 2–6 Show Version Command >>> show version version V5.4-2 MAY 19 1999 14:24:16 >>> Creating a Power-Up Script A special nonvolatile file named “nvram”...
Page 81 NOTE: It is possible to disable the system by editing the nvram script. For example, if you include the initialize command in the script, the system will go into an endless loop. To fix this, press the Halt button while the system is powering up. You can then edit the script to delete the offending command.
Page 82: Booting The Operating System
Booting the Operating System The boot command is used to boot the operating system. The boot command initializes the processor, loads a program image from the specified boot device, and transfers control to that image. Syntax: boot [-file filename ] [-flags [ value ]] [-halt] [-protocols enet_protocol ] [ boot_dev ] -file filename The boot file.
Page 83 Example 2–9 Boot Command >>> b dkc0 (boot dkc0.0.0.16.0 -flags 0) block 0 of dkc0.0.0.16.0 is a valid boot block reading 898 blocks from dkc0.0.0.16.0 bootstrap code read in base = 200000, image_start = 0, image_bytes = 70400 initializing HWRPB at 2000 initializing page table at ffb6000 initializing machine state setting affinity to the primary CPU...
Page 84: Configuring A Pci Nvram Module
Configuring a PCI NVRAM Module The prcache command is used for system configuration to check PCI NVRAM configuration information and battery status, to clear data from the NVRAM module, and to set the date of the next battery replacement. The command is used only with Tru64 UNIX systems.
Page 85: Testing The System
Testing the System The test command runs console-based exercisers for devices in the system. Ctrl/C can abort testing. Syntax: test [-t time ] [-q] [ option ] -t time Specifies the run time in seconds. The default for system test is 120 seconds (2 minutes).
Page 86 Program Device Pass Hard/Soft Bytes Written Bytes Read -------- ------------ ------------ ------ --------- ------------- ----------- 00001ae5 memtest memory 310378496 310378496 00001aea memtest memory 306184192 306184192 00001b07 memtest memory 310378496 310378496 00001b54 exer_kid dqa0.0.0.13. 215040 00001b74 exer_kid dka0.0.0.14. 8732672 00001b7b exer_kid dka100.1.0.1 8732672 Program Device...
Page 87 00001b7b exer_kid dka100.1.0.1 27066368 Program Device Pass Hard/Soft Bytes Written Bytes Read -------- ------------ ------------ ------ --------- ------------- ----------- 00001ae5 memtest memory 1254096896 1254096896 00001aea memtest memory 1249902592 1249902592 00001b07 memtest memory 1254096896 1254096896 00001b54 exer_kid dqa0.0.0.13. 1043456 00001b74 exer_kid dka0.0.0.14. 32800768 00001b7b exer_kid dka100.1.0.1...
Page 88 Default zone extended at the expense of memzone. Use INIT before booting Testing Ethernet device(s) Testing VGA Testing Memory Testing IDE/ATAPI disks (read-only) Testing SCSI disks (read-only) Testing floppy drive (dva0, read-only) Test time has expired... System test complete >>> 2-22 DS10 Console Reference...
Page 89: Set Commands
Set Commands 2.8.1 Set Password The set password command sets the console password for the first time or changes an existing password. It is necessary to set the password only if the system is going to operate in secure mode. Syntax: set password The password length must be between 15 and 30 alphanumeric characters.
Page 90: Set Secure
2.8.2 Set Secure The set secure command enables secure mode without requiring a restart of the console. If the password has been set, the console will be secured and only a small subset of commands can be performed. If a password has not been set, you are prompted to do so.
Page 91: Secure Mode
Secure Mode When the console is in secure mode, the only commands recognized are boot, login, continue, and start. Placing the console in secure mode ensures that unauthorized persons cannot gain access to the system. The commands for console security are set password, clear password, and set secure.
Page 92: Clear Password
Example 2–14 Secure Mode and Login Command # System is not in secure mode. >>> login >>> Secure not set. Please set the password. # System is in secure mode. >>> login # Password is not echoed. Please enter the password: >>>...
Page 93: Resetting The Password
2.9.3 Resetting the Password If you have forgotten the current password, clear the password as follows: From the Local Console Terminal 1. Enter the login command: >>> login 2. At the Enter Password: prompt, press the Halt button, then press the Return key.
Page 94: Stopping And Starting Cpu
2.10 Stopping and Starting CPU The halt (or stop) command stops program execution on a CPU that is still running a booted program. Syntax: halt (or stop) 0 where 0 is the number of the CPU to halt. For the DS10 system, this command has no effect because the single CPU is halted when the system is at the console prompt.
Page 95 ***** Loadable Firmware Update Utility ***** ------------------------------------------------------------------ Function Description ------------------------------------------------------------------ Display Displays the system’s configuration table. Exit Done exit LFU (reset). List Lists the device, revision, firmware name, and update revision. Readme Lists important release information. Update Replaces current firmware with loadable data image. Verify Compares loadable and hardware images.
Page 96: Forcing A System Crash Dump
2.12 Forcing a System Crash Dump The crash command forces a crash dump at the operating system level (Tru64 UNIX or OpenVMS; has no effect on Windows NT). This command is used when an error has caused the system to hang and can be halted with the Halt button or the RMC halt command.
Page 97: Using Environment Variables
2.13 Using Environment Variables Environment variables pass configuration information between the console and the operating system. Their settings determine how the system powers up, boots the operating system, and operates. You issue an init command to activate a new environment variable. Environment variables are set or changed with the set envar command (where envar is a placeholder for the environment to be changed) and set to default values with the set -default envar command.
Page 98: Show Envar
show envar 2.13.2 The show envar command displays the current value (or setting) of an environment variable. Syntax: show envar envar The name of the environment variable to be displayed. The wildcard * displays all environment variables, which are: console, kbd_hardware_type, language, ocp_text and os_type.
Page 99: Depositing And Examining Data
2.14 Depositing and Examining Data Example 2–20 Deposit Command # Clear 1st 512 bytes of physical mem. >>> dep -b -n 1ff pmem:0 0 # Deposit 5 into four longwords starting >>> d -l -n 3 vmem:1234 5 # at virtual memory address 1234. # Load GPRs R0 through R8 with -1.
Page 100: Reading A File
2.15 Reading a File The more command displays a file one screen at a time. Syntax: more [ file ...] where file is the name of the file to be displayed. The more command is similar to that used in the MS-DOS and UNIX operating systems.
Page 101: Initializing The System
------- ---------- --------- 512 MB 000000000 512 MB 020000000 128 MB 050000000 256 MB 040000000 Total Bad Pages = 0 Total Good Memory = 1408 MBytes AlphaServer DS10 466 MHz Console V5.4-2 MAY 19 1999 14:24:16 >>> SRM Console 2-35...
Page 102: Finding Help
2.17 Finding Help The help command displays basic information about the use of console commands when the system is in console mode. Syntax: help [ command . . . ] Command . . . Command or topic for which help is requested. The options are: None Displays the complete list of commands for which you can receive help.
Page 103: Switching From Srm To Alphabios Console
2.18 Switching from SRM to AlphaBIOS Console The alphabios command loads and starts the AlphaBIOS console. This is necessary for running AlphaBIOS-based utilities (such as the RAID configuration utility). To switch from SRM to AlphaBIOS, issue the alphabios command. Syntax: alphabios To return to the SRM console: •...
Page 104: Environment Variable Summary
2.19 Environment Variable Summary Environment variables pass configuration information between the console and the operating system. Their settings determine how the system powers up, boots the operating system, and operates. Environment variables are set or changed with the set envar command and returned to their default values with the clear envar command.
Page 105 Table 2–6 Environment Variable Summary (Continued) Environment Variable Function ocp_text Overrides the default OCP display text with specified text. os_type Specifies the operating system. Valid entries are: openvms, unix, and nt. password A password stored in the NVRAM used to secure the console.
Page 106: Auto_Action
2.19.1 auto_action Specifies the action the console takes any time the system powers up, fails, or resets. When the setting involves autoboot, the system boots from the default boot device specified by the value of the bootdef_dev environment variable. Syntax: set auto_action value where value can be: halt...
Page 107: Boot_Osflags
2.19.3 boot_osflags The boot_osflags environment variable passes information to the boot command. That information is dependent on the operating system to be booted. Syntax for Tru64 UNIX: set boot_osflags flags_value where flags_value can be: Load operating system software from the specified boot device (autoboot).
Page 108: Settings For Boot_Osflags Bootflags (Openvms)
Table 2–7 Settings for boot_osflags Bootflags (OpenVMS) Flags_Value Bit Number Meaning Bootstrap conversationally (enables you to modify SYSGEN parameters in SYSBOOT). Map XDELTA to running system. Stop at initial system breakpoint. Perform diagnostic bootstrap. Stop at the bootstrap breakpoints. Omit header from secondary bootstrap image.
Page 109 2.19.4 com1_baud The default baud rate for the system is 9600. With the com1_baud environment variable, you can set the baud rate to match that of the device connected to the port. Syntax: set com1_baud baud_value where baud_value is the new baud rate. A list of possible values is displayed by attempting to set this environment variable to an unacceptable value (for example, set com2_baud xxx).
Page 110: Console
• In firm bypass mode, you cannot enter RMC mode. To enter RMC mode from firm bypass mode, reset the com1_mode variable from the SRM console. Syntax: set com1_mode value where value can be: snoop Data partially bypasses RMC, but RMC taps into the data lines and listens passively for the RMC escape sequence.
Page 111: Ew*0_Mode
2.19.7 ew*0_mode Sets an Ethernet controller to run an AUI, ThinWire, or twisted- pair Ethernet network. The default is auto-sense. For the fast setting, the device defaults to fast. Syntax: set ew*0_mode value where value can be: Device type is AUI. auto-sense Device type is sensed by the console.
Page 112: Language
2.19.9 kbd_hardware_type Used only on systems with the language variant 3C (Français), this environment variable sets the keyboard hardware type as either PCXAL or LK411 and enables the system to interpret the terminal keyboard layout correctly. Syntax: set kbd_hardware_type keyboard_type where keyboard_type can be: pcxal Selects the default keyboard hardware type.
Page 113: Os_Type
2.19.11 os_type The os_type environment variable specifies the default operating system. This variable is set at the factory to the setting for the operating system purchased. Use this command to change the factory default setting. Whenever you change the value of os_type, you must reset the system by pressing the Halt/Reset button or issuing the initialize command.
Page 114: Pci_Parity
2.19.13 pci_parity Disables or enables parity checking on the PCI bus. set pci_parity value Syntax: where value can be : (default) on Enables PCI parity checking. Disables PCI parity checking. Some PCI devices do not implement PCI parity checking, and some have a parity-generating scheme in which the parity is sometimes incorrect or is not fully compliant with the PCI specification.
Page 115: Pk*0_Host_Id
2.19.15 pk*0_host_id Sets the controller host bus node ID to a value between 0 and 7. set pk*_host_id scsi_node_id Syntax: where scsi_node_id is the bus node ID, a number from 0 to 7. Each SCSI bus in the system requires a controller. Buses can theoretically support up to eight devices;...
Page 116: Tt_Allow_Login
2.19.17 tt_allow_login Enables or disables login to the SRM console firmware on alternate console ports. If the environment variable console is set to serial, the primary console device is the terminal connected through the COM1 port. The command set tt_allow_login 1 enables logins through either the COM2 port or a graphics monitor.
Page 117: Alphabios Console
Chapter 3 AlphaBIOS Console AlphaBIOS is the graphical interface that supports the Microsoft Windows NT operating system and some utility programs. This chapter explains how to perform common system management tasks with AlphaBIOS. Sections in this chapter are: • Starting AlphaBIOS •...
Page 118: Starting Alphabios
Starting AlphaBIOS Start AlphaBIOS Setup by pressing F2 from the Boot screen displayed at power-up or reset. Figure 3–1 Boot Screen PK1450 - 98 3-2 DS10 Console Reference...
Page 119: Alphabios Setup Screen
The boot screen shown in Figure 3–1 is displayed at power-up and reset. Press F2 at this screen to enter the setup program. The AlphaBIOS Setup screen (Figure 3–2) is displayed. From this screen you can select the tasks to perform. Use the arrow keys to select the menu item you want and press Enter.
Page 120: Keyboard Conventions And Help
Keyboard Conventions and Help AlphaBIOS uses widely accepted keys and key combinations for navigating the interface and selecting items. Figure 3–3 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 121: Second-Level Help Screen
Figure 3–4 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 122: System Configuration
F1= Help Systemboard Configuration Hard Disk Configuration PCI Configuration SCSI Configuration ISA Configuration Memory Configuration Integrated Peripherals System Type: AlphaServer DS10 Processor: Alpha 21264-4, Revision V1.8.208 (1 Processor) Speed: 466 MHz Cache: 2 MB Memory: 512 MB Floppy Drive A: 3.5”...
Page 123 Display the system configuration as follows: 1. Start AlphaBIOS, select Display System Configuration, and press Enter. 2. 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: •...
Page 124: System Board Configuration
F1= Help Systemboard Configuration Hard Disk Configuration PCI Configuration SCSI Configuration ISA Configuration Memory Configuration Integrated Peripherals System Type: AlphaServer DS10 Processor: Alpha 21264-4, Revision V1.8.208 (1 Processor) Speed: 466 MHz Cache: 2 MB Memory: 512 MB Floppy Drive A: 3.5”...
Page 125 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 of the processor. Cache — The amount of static RAM cache memory installed. Memory —...
Page 126: Hard Disk Configuration
3.3.3 Hard Disk Configuration Figure 3–7 Hard Disk Configuration Display System Configuration F1= Help Systemboard Configuration Hard Disk Configuration PCI Configuration SCSI Configuration ISA Configuration Memory Configuration Integrated Peripherals Disk 0 ATAPI #0, SCSI ID 0 8063 MB QUANTUM FIREBALL SE8 API. Partition 1 4095 MB Partition 2...
Page 127 Physical Disk ID – Based on the SCSI ID. The disk with the lowest SCSI ID is disk 0, the disk with the next lowest SCSI ID is disk 1. Controller – The brand and model of the SCSI chip used on the SCSI controller.
Page 128: Pci Configuration
3.3.4 PCI Configuration Figure 3–8 PCI Configuration Display System Configuration F1= Help Systemboard Configuration Hard Disk Configuration PCI Configuration SCSI Configuration ISA Configuration Memory Configuration Integrated Peripherals Device Name Device Type Revision Physical Slot AcerLabs USB 5237 Embedded AcerLabs PCI-ISA ISA bridge Embedded DIGITAL...
Page 129: Pci Slots
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 130: Advanced Pci Information
Figure 3–10 Advanced PCI Information Display System Configuration F1=Help Advanced PCI Information Bus Number=0, Device Number=1, Function Number=0 Configuration Space: Register Hex offset Vendor ID 1090 Device ID 5237 Command 0280 Status 0280 Revision ID Prog. I/F Sub Class Code Class Code Cache Line Size Latency Timer...
Page 131: Scsi Configuration
3.3.5 SCSI Configuration Figure 3–11 SCSI Configuration Display System Configuration F1= Help Systemboard Configuration Hard Disk Configuration PCI Configuration ATAPI #0 SCSI Configuration ATAPI #1 ISA Configuration Memory Configuration Integrated Peripherals ATAPI #0, SCSI ID 255, SCSI Bus 0 SCSI Device Size Description...
Page 132 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 133: Memory Configuration
3.3.6 Memory Configuration Figure 3–12 Memory Configuration Display System Configuration F1= Help Systemboard Configuration Hard Disk Configuration PCI Configuration SCSI Configuration ISA Configuration Memory Configuration Integrated Peripherals System Memory Configuration Bank 0: 64 MB (32 MB per DIMM) -- Starting Address = 0x00000000 Bank 1: 64 MB (32 MB per DIMM) -- Starting Address = 0x40000000 ESC =Exit...
Page 134: Integrated Peripherals
3.3.7 Integrated Peripherals Figure 3–13 Integrated Peripherals Display System Configuration F1=Help Systemboard Configuration Hard Disk Configuration PCI Configuration SCSI Configuration ISA Configuration Memory Configuration Integrated Peripherals Integrated Peripheral State Serial 0: Enabled [ port 0x3f8, IRQ 4 ] Serial 1: Enabled [ port 0x2f8, IRQ 3] Parallel: Enabled [ port 0x3bc, IRQ 7]...
Page 135: Updating Firmware
Updating Firmware Insert the CD-ROM or diskette with the updated firmware and select Upgrade AlphaBIOS from the main AlphaBIOS Setup screen. Use the Loadable Firmware Update Utility (LFU) to perform the update. The LFU exit command causes a system reset. Figure 3–14 Updating Firmware AlphaBIOS Setup F1=Help...
Page 136 As new versions of Windows NT are released, it might be necessary to upgrade AlphaBIOS to the latest version. Also, as improvements are made to AlphaBIOS, you may wish to upgrade to take advantage of new features. Use this procedure to upgrade from an earlier version of AlphaBIOS: 1.
Page 137: Setting Up The Hard Disk
Setting Up the Hard Disk Either execute an express or a custom hard disk setup. An express setup, described here, creates the recommended partitions on the first hard disk, but it does not map bad sectors. Custom hard disk setup is described in Sections 3.5.1 and 3.5.2. Figure 3–15 Hard Disk Setup Screen Hard Disk Setup F1= Help...
Page 138 SCSI ID number — A unique number you assign each SCSI device in the system. This is usually done by jumpers or a thumb wheel attached to the drive. Size — The raw capacity of the drive. Formatting the drive with different file systems (for example, FAT and NTFS) may result in different usable sizes because of the differences in how storage is managed under those file systems.
Page 139 Exit (Escape key) — Return to the AlphaBIOS Setup screen. An express hard disk setup creates the recommended partition arrangement on the first hard disk (disk 0). It does not, however, format the large partition with NTFS, and it does not map bad sectors on the disk. The NTFS formatting can be done once Windows NT has been installed.
Page 140: Creating And Deleting Partitions Manually
3.5.1 Creating and Deleting Partitions Manually 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 3–16 Create New Partition Dialog Box Hard Disk Setup Disk 0 QLISP1040 #0, SCSI ID 3...
Page 141: Delete Partition Dialog Box
To delete a partition 1. Start AlphaBIOS and select Hard Disk Setup. Press Enter. 2. Select the partition to be deleted (see in Figure 3–17). 3. Press Delete. A dialog box is displayed (see 4. Press F10 to confirm the deletion. Figure 3–17 Delete Partition Dialog Box Hard Disk Setup Disk 0...
Page 142: Formatting A Fat Partition
3.5.2 Formatting a FAT Partition AlphaBIOS can format partitions with the FAT file system. Use Windows NT to format a partition using NTFS. Figure 3–18 Formatting a FAT Partition Hard Disk Setup Disk 0 QLISP1040 #0, SCSI ID 3 510 MB Partition 1 NTFS Partition 2...
Page 143: Standard Formatting
To format a FAT partition 1. Start AlphaBIOS and select Hard Disk Setup. Press Enter. 2. Select the partition to be formatted (see in Figure 3–18). 3. Press F6. A dialog box is displayed, asking whether to perform a quick or standard format (see ).
Page 144: Performing Setup Tasks
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 3–20 Standard CMOS Setup Screen CMOS Setup F1=Help April...
Page 145 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 146: Advanced Cmos Setup Screen
Figure 3–21 Advanced CMOS Setup Screen CMOS Setup Advanced CMOS Setup Disabled PCI Parity Checking: Full Power-up Memory Test: Disabled AlphaBIOS Password Option: Windows NT Console Console Selection: ¹ (AlphaBIOS) Enabled Warm Reboot: º ¹ Press to to enable or disable detection of PCI bus parity error. Some non-compliant PCI option boards do not work properly with PCI parity checking enabled.
Page 147 PCI parity checking — Enables and disables settings for PCI parity checking, which ensures data integrity across the PCI bus. Because some third-party PCI options do not correctly implement PCI parity generation, the default is Disabled. Power-up memory test — Enables and disables settings for the power- up memory test.
Page 148: Installing Operating System
Installing Operating System Install your operating system from the CD-ROM. Up to three versions of the operating system can be resident in the system at one time. Read the instructions carefully; it is easy to install the wrong CD-ROM driver. Figure 3–22 Installing Windows NT AlphaBIOS Setup F1= Help...
Page 149 If Windows NT was installed at the factory, Windows NT setup will start automatically the first time the system powers up. NOTE: Steps 1 and 2 in the following procedure are necessary only when you are first setting up your system. On subsequent installations and upgrades, begin at step 3.
Page 150: Selecting The Version Of Windows Nt
Selecting the Version of Windows NT Up to three versions of Windows NT can reside on the system at one time. Select the version that will be started from the Operating System Selection Setup screen. Figure 3–23 Operating System Selections Operating System Selection Setup Windows NT Server 4.0 Primary Operating System...
Page 151 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 Tru64 UNIX and OpenVMS operating systems. Each operating system selection is a set of information for a version of Windows NT.
Page 152: Designating A Primary Operating System
Designating a Primary Operating System 3.9.1 Selecting a Primary Operating System Figure 3–24 Primary Operating System AlphaBIOS 5.29 Please select the operating system to start: Windows NT Server 4.0 Windows NT Server 5.0 to move the highlight to your choice. Press Enter to choose.
Page 153 Three versions of Windows NT can reside on the system at the same time. This is 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 154: Primary Operating System And The Auto Start Option
3.9.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 3–25 Operating System Selection Setup Operating System Selection Setup Primary Operating System...
Page 155 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. Boot name —...
Page 156 OS options — Lists the startup parameters passed to the operating system for an operating system selection. One example of a startup parameter is whether to start the operating system in debug mode. By default, Windows NT does not add any entries to this field. This field can be modified.
Page 157 Primary operating system (F8 key) — Sets the selected OS selection as the primary operating system. When you make an OS selection primary, it is displayed first on the Operating System Selection Setup screen with the text “Primary Operating System.” In addition, the primary operating system is displayed first on the AlphaBIOS Boot screen and is automatically started if Auto Start is enabled.
Page 158: Switching From Alphabios To Srm Console
3.10 Switching from AlphaBIOS to SRM Console You can run firmware-based diagnostics from the SRM console. You must be in the SRM to boot OpenVMS or UNIX. To switch from AlphaBIOS to the SRM console, press the Halt/Reset button on the control panel, and the system will power up. Press the Halt/Reset button as the system is going through self-tests and you will be at the SRM console.
Page 159 Firmware-based diagnostics are run from the SRM console. To boot Tru64 UNIX or OpenVMS, you need to change the Halt/Reset jumper on the motherboard (see Appendix A). Follow this procedure to switch from AlphaBIOS to SRM: 1. In AlphaBIOS, select CMOS Setup and press Enter. 2.
Page 160: Running Utility Programs
3.11 Running Utility Programs Maintenance programs such as RAID configuration utilities are run from the AlphaBIOS Utilities menu. Figure 3–27 Run Maintenance Program Dialog Box PK14656-98 Program name — The program to be run. It must be an executable program with an .EXE extension. It is not necessary to type the extension.
Page 161: Running Utilities From A Graphics Monitor
3.11.1 Running Utilities from a Graphics Monitor 1. Start AlphaBIOS Setup. If the system is in the SRM console, set the SRM console environment variable to graphics and issue the command alphabios. 2. From AlphaBIOS Setup, select Utilities, then select Run Maintenance Program from the submenu that is displayed, and press Enter.
Page 162: Running Utilities From A Serial Terminal
3.11.2 Running Utilities from a Serial Terminal Utilities are run from a serial terminal in the same way as from a monitor with graphics capabilities enabled. The menus are the same, but some keys are different. Table 3-1 AlphaBIOS Option Key Mapping AlphaBIOS Key VTxxx Key Ctrl/A...
Page 163 Chapter 4 Remote Management Console The remote management console (RMC) provides a command-line user interface for entering commands to monitor and control the system. In addition to doing routine monitoring, you can invoke the command-line interface to perform remote power on/off, halt, and reset. The RMC can detect alert conditions such as overtemperature, fan failure, and power supply failure and automatically dial a pager phone number or another computer system to notify the remote operator of the alert condition.
Page 164: Rmc Components
RMC Components The RMC resides in an independent microprocessor on the system motherboard and allows a remote operator to connect to the system COM1 port from a modem or from a serial terminal or terminal emulator. Figure 4–1 Location of RMC Components on Motherboard RMC PIC Processor Halt/Reset...
Page 165: Terminal Setup
Terminal Setup Remote connection is made through a modem connected to the COM1 port. To set up the modem, you first use a local terminal on the COM1 port to set up the parameters of the modem and RMC connection. You then disconnect the terminal and connect the modem.
Page 166: Operating Modes
Operating Modes RMC runs in three modes on this system: Snoop, soft bypass, and firm bypass. The bypass modes are set with the set com1_mode command from the SRM console. Figure 4–3 Bypass Mode System DUART COM1 COM1 Port SRM/AlphaBIOS UART Consoles RMC PIC...
Page 167 Snoop Mode (Default Mode) In snoop mode data partially bypasses the RMC. The data and control signals are routed from the system COM1 port to the external modem port, but the RMC taps into the data lines and listens passively for the RMC escape sequence.
Page 168: Entering The Rmc
Entering the RMC You type an escape sequence to invoke the RMC. You can enter RMC from a modem or the local serial console terminal. You can enter the RMC from the local terminal regardless of the current operating mode. You can set up RMC parameters. 1.
Page 169: Status Monitoring
Status Monitoring Use the RMC status command to check the current state of the system’s sensors as well as the current escape sequence and alarm information. RH7VBQTIÂUV7VWU Bw†‘i†sÂTsw‡wƒ‚0ÂX! Us†s†ÂRƒ‘s†0ÂQP TI9ÂDi€ˆ0Â@si‡‡s†ˆsr TI9ÂRƒ‘s†Â9ƒ‚ˆ†ƒ€0ÂQP Rƒ‘s†ÂU‰„„€“0ÂQG U“‡ˆsÂBi‚‡0ÂQGÂÂÂÂÂÂÂ9RWÂBi‚0ÂQG Vs„s†iˆ‰†s0Â#! ®9Â‘i†‚w‚u‡ÂiˆÂ%% ®9Â„ƒ‘s†ƒttÂiˆÂ& ®9 A‡qi„sÂUs…‰s‚qs0ÂfcfcTI9 TsƒˆsÂ7qqs‡‡0Â@w‡ip€sr TI9ÂRi‡‡‘ƒ†r0Â‡sˆ...
Page 170 Table 4–2 Status Command Fields (Continued) On = System has powered on from RMC. Power Control Off = System has powered off from RMC. Power Supply OK = Auxiliary 5V is working. System Fans OK = PCI and system fan are operating. FAIL = PCI or system fan failure has been detected.
Page 171: Remote Power (On/Off)
Remote Power (On/Off) You can power a monitored system on or off from the RMC using console monitor commands. Figure 4–4 Power Button PK1043b Remote Power-On The RMC power {on, off} commands can be issued remotely to power the system on or off. They have the same function as the Power button on the control panel.
Page 172: Remote Halt (In/Out)
Remote Halt (In/Out) You can issue a halt to a monitored system from the RMC using console monitor commands. Under OpenVMS and Tru64 UNIX, the system will halt. Under Windows NT, the command will be ignored. Figure 4–5 Halt/Reset Jumper Setting for Setting for Windows NT...
Page 173: Halt/Reset Button
Figure 4–6 Halt/Reset Button PK1043c Table 4–3 Halt/Reset Button Function under Operating Systems Operating System Function OpenVMS and Suspends the operating system and Tru64 UNIX returns control to the SRM or RMC console. Windows NT Resets the system. The Halt button, however, does not override the halt {in, out} commands. If you halt the system with halt in, you must use halt out to deassert the halt state.
Page 174: Configuring Remote Dial-In
Configuring Remote Dial-In Before you can dial in through the RMC modem port or enable the system to call out in response to system alerts, you must configure the RMC for remote dial-in. Connect your serial terminal to the COM1 port and turn it on. Set up the RMC parameters.
Page 175 Sets the password that is prompted for at the beginning of a modem session. The string cannot exceed 14 characters and is not case sensitive. For security, the password is not echoed on the screen. When prompted for verification, type the password again. Sets the initialization string.
Page 176: Configuring Dial-Out Alert
4.10 Configuring Dial-Out Alert When you are not monitoring the system through a modem connection, you can use the RMC dial-out alert feature to remain informed of system status. If dial-out alert is enabled, and the RMC detects alarm conditions within the managed system, it can call a preset pager number.
Page 177 • When the problem is resolved, the operator powers up and reboots the system. • The dial-out alert feature is enabled as part of the dial-in setup. See Section 4.9. The elements of the dial string and alert string are shown in Table 4–4. Paging services vary, so you need to become familiar with the options provided by the paging service you will be using.
Page 178: Elements Of Dial String And Alert String
Table 4–4 Elements of Dial String and Alert String Dial String The dial string is case sensitive. The RMC automatically converts all alphabetic characters to uppercase ATXDT AT = Attention. X = Forces the modem to dial “blindly” (not seek the dial tone).
Page 179: Dialing In
4.11 Dialing In To start a remote monitoring session, dial in, using the dial string you entered during the setup procedure. Enter the RMC modem password, and then type the escape sequence. 1. After completing the setup procedure, dial in, enter the RMC password at the Modem password: prompt.
Page 180: Resetting The Rmc To Factory Defaults
4.12 Resetting the RMC to Factory Defaults If the RMC escape sequence is set to something other than the default, and the sequence has been lost or forgotten, the RMC must be reset to factory settings to restore the default escape sequence.
Page 181: Troubleshooting Tips
4.13 Troubleshooting Tips Table 4–5 lists possible causes and suggested solutions for symptoms you might see. Table 4–5 RMC Troubleshooting Symptom Possible Cause Suggested Solution If you are not at the RMC prompt, a system reset or initialization disconnects the modem. SRM clears modem Reconnect the modem.
Page 182 Table 4–5 RMC Troubleshooting (Continued) Symptom Possible Cause Suggested Solution After the system is powered up, the COM1 port seems to hang and then starts working after a few seconds. This delay is normal. Wait a few seconds for the COM1 port to start working.
Page 183: Rmc Commands
4.14 RMC Commands The remote management console supports setup commands and commands for remotely managing the system. clear {alert, port} disable (alert, reboot, remote) enable (alert, reboot, remote) halt {in, out} hangup help or ? power {on, off} quit reset send alert {alert, com1_mode, dial, escape, init, logout, password, user, wdt} status...
Page 184 Command Conventions Observe the following conventions for entering RMC commands: • Enter enough characters to distinguish the command. NOTE: The reset and quit commands are exceptions. You must enter the entire word for these commands to work. • For commands consisting of two words, enter the entire first word and at least one letter of the second word.
Page 185: Clear Alert
4.14.1 clear alert The clear alert command clears the current alert condition and causes the RMC to stop paging the system operator at the remote location. If the alert is not cleared, the RMC continues to page the remote operator every 30 minutes if both remote access and alerts are enabled.
Page 186: Disable Remote
4.14.4 disable remote The disable remote command disables remote access to the RMC modem port and disables automatic dial-out alerts. Syntax: disable remote 4.14.5 enable alert The enable alert command enables the RMC to page a remote system operator. Before you can enter the enable alert command, you must configure remote dial-in and call-out, set an RMC password (set password command), and enable remote access (enable remote command) to the RMC modem port.
Page 187: Enable Remote
4.14.6 enable remote The enable remote command enables remote access to the RMC modem port by configuring the modem with the setting stored in the initialization string. This command also allows the RMC to automatically dial the phone number set with the set dial command upon detection of alert conditions.
Page 188: Halt (In/Out)
4.14.7 halt (in/out) You can issue a halt to a monitored system from RMC using console monitor commands. The effect of this command depends on the setting of the HALT/RESET jumper on the motherboard. See Section 4.8 for a full discussion of this feature.
Page 189: Hangup
4.14.8 hangup The hangup command terminates the modem session. If you do not issue the hangup command, the session is disconnected automatically after a period of idle time set by the set logout command. The default is 20 minutes Syntax: hangup 4.14.9 help or ? The help or ? command displays the RMC command set.
Page 190: Power On
4.14.11 power on The power on command is equivalent to turning on the system power from the control panel. If the system is already powered on, this command has no effect. After the power on command is issued, the user’s terminal exits the RMC and reconnects to the system’s COM1 port.
Page 191: Reset
4.14.13 reset The reset command is equivalent to pushing the Reset button on the control panel. The reset command restarts the system. The terminal exits RMC and reconnects to the server’s COM1 port. You must enter the entire word for the command to take effect.
Page 192: Set Alert
4.14.15 set alert The set alert command sets the alert string that is transmitted through the modem when an alert condition is detected. Set the alert string to the phone number of the modem connected to the remote system. The alert string is appended after the dial string, and the combined string is sent to the modem.
Page 193 4.14.16 set com1_mode The set com1_mode command specifies the COM1 data flow paths, so that data either passes through the RMC or bypasses it. See Section 4.3 for descriptions of the RMC modes. Syntax: set com1_mode value where value can be: Data partially bypasses the RMC, but the RMC taps into the snoop data lines and listens passively for the RMC escape sequence.
Page 194: Set Dial
4.14.17 set dial The set dial command sets the dial string to be used by the RMC to dial out when an alert condition occurs. The dial string must be in the correct format for the attached modem. If a paging service is to be contacted, the dial string must include the appropriate modem commands to dial the number, wait for the line to connect, and send the appropriate touch tones to leave a pager message.
Page 195: Set Escape
4.14.18 set escape The set escape command changes the escape sequence used for invoking the RMC. The escape sequence can be any character string, not to exceed 14 characters. A typical sequence consists of two or more control characters. It is recommended that control characters be used in preference to ASCII characters.
Page 196: Set Init
4.14.19 set init The set init command sets the modem initialization string. The initialization string is limited to 31 characters and can be modified depending on the type of modem used. Syntax: set init Some typical initialization strings are: Initialization String Modem at&f0e0v0x0s0=2 Motorola 3400 Lifestyle 28.8...
Page 197: Set Logout
4.14.20 set logout The set logout command sets the amount of time before the RMC terminates an inactive modem The default is 20 connection. minutes. The settings are in tens of minutes, 0–9. The zero (0) setting disables logout. With logout disabled, the RMC never disconnects the idle modem session. The following example sets the logout timer to 50 minutes.
Page 198: Set User
4.14.22 set user The set user command allows you to set a user string to be displayed in the status command. You may want to make notes regarding the system. The string is limited to 63 characters and is displayed in the User String field when you enter the status command.
Page 199 Appendix A Setting Jumpers This appendix gives information on the correct settings of the jumpers on the DS10 motherboard. If you are switching to Windows NT from OpenVMS or Tru64 UNIX, you may want to change the HALT jumper. Sections include: •...
Page 200 A.1 Warnings and Cautions WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience. Such persons are expected to understand the hazards of working within this equipment and take measures to minimize danger to themselves or others. The CPU module, RMC PIC processor, and memory modules have parts that operate at high temperatures.
Page 201: Removing Power From The System
A.2 Remove Power from the System Be sure to remove the AC power cord from either the wall outlet or the system cabinet. Power remains active in the RMC PIC processor when the system is powered off using only the control panel power switch.
Page 202: Opening The System Cabinet
A.3 Open the System Remove the cover to gain access to the system. See Figure A–2. Figure A–2 Opening the System Cabinet PK1021a-99 1. Unlock the top cover 2. Loosen the captive screw at the top of the bulkhead 3. Push down on the lever to the right of the screw and pull it out, perpendicular to the system.
Page 203: Removing The Floppy Disk Enclosure
A.4 Remove the Floppy Disk Enclosure To access the jumpers, remove the floppy disk drive enclosure. Figure A–3 Removing the Floppy Disk Enclosure PK1018-99 1. Hold on to the cylinder pins, which secure the floppy disk enclosure. Pull the pins toward the center (see Figure A–3 2.
Page 204: Setting Jumpers On The Motherboard
A.5 Set Jumpers There are three jumpers on the motherboard, which you can now access. Do not change the Timer Disable jumper or any of the switches. Correct positions are given in Figure A–4. Figure A–4 Setting Jumpers on the Motherboard Halt/Reset Select Remote Console Management Jumper...
Page 205: Jumpers And Factory Default Positions
• The Halt/Reset Select jumper affects the operation of the control panel Halt button. You may be changing this jumper if you are switching to or from the Windows NT operating system. • The RMC jumper enables or disables the remote management console. •...
Page 206 A.6 Restore Power Close up the system and restore power. 1. Replace the floppy drive enclosure (see Section A.4). Check that the cables are clear and not pinched. 2. Replace the system cover, sliding it forward (see Section A.3). Secure with the handle and lock on the bulkhead.
Page 207 Index boot_file environment variable, SRM, 1-7, 1-9, 1-13, 1-15, 1-17, 2-25 boot_flags environment variable, Advanced CMOS setup screen, SRM, 2-25 AlphaBIOS, 3-30 boot_osflags environment variable, Alphabios command, SRM, 2-3, 2-38 SRM, 1-7, 1-9, 1-13, 1-15, 1-17, 2- AlphaBIOS console, 1-5 38, 2-41 boot screen, 1-20, 3-2 OpenVMS, 2-41, 2-42...
Page 208: Crash Command
Command conventions, RMC, 4-22 Command syntax, SRM console, 2-5 edit command, SRM, 2-3, 2-33 Configuring parameters, AlphaBIOS enable alert command (RMC), 4-24 console, 3-28 enable remote command (RMC), 4-25 Console Environment variables, SRM, 2-31 AlphaBIOS, 1-5 auto_action, 1-5 specifying, 3-31 boot_file, 1-7, 1-9, 1-13, 1-15, 1-17, SRM, 1-5 2-25...
Page 209: Initialize Command
updating from SRM, 2-28 OpenVMS, 1-18 updating, AlphaBIOS selection, 1- Tru64 UNIX, 1-10 Windows NT, 1-22 updating, SRM command, 1-26 Installing Windows NT, 3-32 Formatting hard disk, AlphaBIOS, 3- Integrated peripherals screen, 21, 3-24, 3-26 AlphaBIOS, 3-18 IOD, 1-5 Graphics monitor, specifying as console terminal, SRM, 2-44 kbd_hardware_type environment variable, SRM, 2-31, 2-32, 2-38, 2-...
Page 210: More Command
list, 1-27, 1-31, 1-35, 1-37, 1-39, 1- specifying as default operating 40, 1-41, 1-42 system, 2-47 readme, 1-41, 1-42 Operating system summary, 1-41 booting OpenVMS, 1-12 update, 1-27, 1-31, 1-41, 1-43 from cluster disk, 1-14 verify, 1-41, 1-43 from local disk, 1-12 list command, LFU, 1-27, 1-31, 1-35, from remote disk, 1-16 1-39, 1-41, 1-42...
Page 211 PCI options enable alert command, 4-24 slot numbers, 2-12 enable remote command, 4-25 pci_parity environment variable, entering, 4-6 SRM, 2-39, 2-47, 2-48 escape sequence, 4-6 pk*0_fast environment variable, SRM, exiting, 4-6 2-39, 2-48 halt in command, 4-26 pk*0_host_id environment variable, hangup command, 4-13, 4-17, 4-27 SRM, 2-39, 2-49 help or ? commands, 4-27...
Page 212 Serial terminal, specifying as console summary of environment variables, terminal, SRM, 2-40 2-35 set alert command (RMC), 4-15, 4-18, switching from AlphaBIOS, 3-31, 4-33 3-42 set dial command (RMC), 4-18, 4-34 switching to AlphaBIOS, 2-34 Set dial command (RMC), 4-15 SRM console commands set envar command, SRM, 2-4, 2-28, alphabios, 2-3, 2-35...
Page 213: Updating Firmware
auto_action, 2-35, 2-37 System failure, specifying console boot_osflags, 2-35, 2-38, 2-39 action, SRM, 2-37 boot_osflags, DIGITAL UNIX, 2- boot_osflags, OpenVMS, 2-38 Terminal setup (RMC), 4-3 bootdef_dev, 2-35 test command, SRM, 2-4, 2-19 com*_baud, 2-35, 2-40 Testing the system (all operating commands for displaying the value systems), 2-19 or setting, 2-28...
Page 214 designating primary operating specifying as default operating system, 3-36 system, 2-47 installing, 1-22, 3-32 starting automatically, 3-29, 3-38 selecting version, 3-34 Index-8...

Compaq AlphaServer DS10 Reference Manual

Preface

Chapter 1 Operations

Chapter 2 SRM Console

Chapter 3 Alphabios Console

Chapter 4 Remote Console Manager

Quick Links

Related Manuals for Compaq AlphaServer DS10

Summary of Contents for Compaq AlphaServer DS10

Table of Contents