AlphaServer DS10 / DS10L, AlphaStation DS10 Console Reference Order Number: EK-DS10S-CR. D01 This manual describes the general operation of Compaq AlphaServer DS10, AlphaServer DS10L and AlphaStation DS10 systems. It presents the SRM console (the command-line interface for Tru64 UNIX and OpenVMS operating systems), AlphaBIOS (the graphics interface for Linux), and remote console management.
September, 2000 2000 Compaq Computer Corporation. Compaq and the Compaq logo registered in U.S. Patent and Trademark Office. AlphaServer, AlphaStation, and OpenVMS are trademarks of Compaq Computer Corporation. Tru64 is a trademark of Compaq Information Technologies Group, L.P. in the United States and/or other countries. UNIX is a trademark of the OPEN GROUP in the United States and other countries.
Contents Preface ........................................................................................................................xi Chapter 1 1.1 1.2 1.3 1.3.1 1.1.2 1.4 1.5 1.1.1 1.1.2 1.1.3 1.6 1.7 1.7.1 1.8 1.8.1 1.8.2 1.8.3 1.1.4 1.9 1.9.1 1.9.2 1.10 1.10.1 1.10.2 1.10.3 1.10.4 1.10.5 Operations Powering Up the System....................................................................... 1-2 Power-Up Display .................................................................................
Chapter 2 2.1 2.2 2.2.1 2.2.2 2.2.3 2.3 2.3.1 2.3.2 2.3.3 2.3.4 2.3.5 2.3.6 2.4 2.5 2.6 2.7 2.8 2.8.1 2.8.2 2.9 2.9.1 2.9.2 2.9.3 2.10 2.11 2.12 2.13 2.13.1 2.13.2 2.14 2.15 2.16 2.17 2.18 2.18.1 2.18.2 2.18.3 2.18.4 2.18.5 2.18.6 iv SRM and AlphaBIOS Consoles Invoking the SRM Console.................................................................... 2-2 Commands ............................................................................................ 2-3 Command Summary .............................
2.18.7 ew*0_mode.................................................................................... 2-47 2.18.8 ew*0_protocols .............................................................................. 2-47 2.18.9 kbd_hardware_type ...................................................................... 2-48 2.18.10 language........................................................................................ 2-48 2.18.11 os_type .........................................................................
3.14.10 3.14.11 3.14.12 3.14.13 3.14.14 3.14.15 3.14.16 3.14.17 3.14.18 3.14.19 3.14.20 3.14.21 3.14.22 3.14.23 3.14.24 power off ....................................................................................... 3-34 power on........................................................................................ 3-34 quit................................................................................................ 3-35 reset ..........................................................................
1–7 1–8 1–9 1–10 1–11 1–12 1–13 2–1 2–2 2–3 2–4 2–5 2–6 2–7 2–8 2–9 2–10 2–11 2–12 2–13 2–14 2–15 2–16 2–17 2–18 2–19 2–20 2–21 2–22 2–23 2–24 2–25 3–1 3–2 Booting OpenVMS from a Disk on a Cluster ...................................... 1-17 Booting OpenVMS from a Remote Disk.............................................. 1-19 Installing OpenVMS ........................................................................... 1-21 Starting LFU from the SRM Console..................................................
1–5 1–6 2–1 2–2 2–3 2–4 2–5 3–1 3–2 3–3 3–4 3–5 3–6 3–7 3–8 3–9 3–10 3–11 A–1 A–2 A–3 A–4 A–5 A–6 Halt/Reset Button – DS10................................................................... 1-36 Halt/Reset Button - DS10L ................................................................. 1-37 AlphaBIOS Boot Screen ...................................................................... 2-54 AlphaBIOS No Selections Found Screen ............................................ 2-55 AlphaBIOS Setup Screen............
3–4 A–1 A–2 RMC Troubleshooting ......................................................................... 3-24 Factory Default Switch Settings.........................................................A-11 Jumpers and Factory Default Positions..............................................
Preface Intended Audience This manual is for service providers, managers and operators of Compaq AlphaServer DS10, AlphaServer DS10L, and AlphaStation DS10 systems. Document Structure This manual uses a structured documentation design. Topics are organized into small sections, usually consisting of two facing pages. Most topics begin with an abstract that provides an overview of the section, followed by an illustration or example. The facing page contains descriptions, procedures, and syntax definitions.
Conventions In examples of SRM console output, commands the user enters are presented in boldface type, while the system’s output is in regular type. Comments on the examples are either called out with circled numbers (➊➋➌) or are preceded by a pound sign (#) and are given in boldface italics. Revision levels, dates and devices listed in examples are for example only; your results may vary according to the configuration of your system. NOTE: In many ways DS10 and DS10L systems are identical.
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.
1.1 Powering Up the System To power up the system, check your power setting (DS10 only), then press the On/Off button ❶ to the On position. Check the control panel LEDs. See Figure 1–1 and Figure 1–2 for the DS10, and Figure 1–3 for the DS10L.
Figure 1–2 Location of DS10 Control Panel and On/Off Button PK1043b Table 1–1 Control Panel Functions – DS10 Symbol Function Halt button. Under OpenVMS and Tru64 UNIX, suspends the operating system and returns control to the SRM console. Environmental amber LED. On indicates Temperature or Fan LEDs are on. Flashes when operating system invokes it as an alert. Temperature amber LED. On indicates internal temperature exceeds operating conditions. The system shuts down 30 seconds after this LED lights.
Figure 1–3 Location of DS10L Control Panel and On/Off Button 1 PK2216 Table 1–2 Control Panel Functions - DS10L Symbol Function Halt button. Under OpenVMS and Tru64 UNIX, suspends the operating system and returns control to the SRM console. Environmental amber LED. On indicates Temperature or Fan LEDs are on. Flashes when operating system invokes it as an alert. Temperature amber LED. On indicates internal temperature exceeds operating conditions. The system shuts down 30 seconds after this LED lights.
1.2 Power-Up Display DS10 systems have four physical PCI slots; the DS10L system has one, hence the different power-up displays shown below. 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.
Figure 1–4 Physical Numbering for DS10 PCI Slots PCI Slot 4 64 Bit PCI Slot 3 64 Bit PCI Slot 2 64 Bit PCI Slot 1 32 Bit PK1045-99 ➊ ➋ Memory size is determined. ➌ Power-up slot 14 corresponds to the bottom physical slot, slot 1. The PCI bridges and attendant buses (indicated as IODn by the console) are probed and the devices are reported. I/O adapters are configured.
Example 1–2 Power-Up Display - DS10L Serial and Graphics Consoles Note: There is only one PCI slot on the DS10L; its logical slot number is 17.
Graphics Console Os_type UNIX-console CIPCA drive not started Testing the System Testing the disks (read only) Testing the Network System Temperature is 36 degrees C Initializing GCT/FRU at 1f6000 COMPAQ AlphaServer DS10L 466 MHz Console V5.
1.3 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–3 Booting Tru64 UNIX from a Local Disk >>> sho device ➊ dka100.1.0.2000.0 dka300.3.0.2000.0 dka500.5.0.2000.0 dkb0.0.0.2001.0 dkb200.2.0.2001.0 dkb400.4.0.2001.0 dkc0.0.0.16.0 dkc200.2.0.16.0 dqa1.1.0.13.0 dra1.0.0.17.0 dra2.0.0.17.0 dva0.0.0.0.0 ewa0.0.0.9.
➊ 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. The name of this device, dkc0, is used as an argument to the boot command. ➌ This command loads Tru64 UNIX from the disk dkc0, using the boot file vmunix and autobooting to multiuser mode.
1.3.2 Booting from a Remote Disk Example 1–4 Booting Tru64 UNIX from a Remote Disk >>> show device . . . ewa0.0.0.8.0 ➊ EWA0 08-00-2B-E2-9C-60 >>> >>> boot -flags an -protocols bootp ewa (boot ewa0.0.0.4.1 -flags an) Building FRU table ➋ ➌ Trying BOOTP boot. Broadcasting BOOTP Request... Received BOOTP Packet File Name: /var/adm/ris/ris0.alpha/hvmunix local inet address: 16.122.128.26 remote inet address: 16.122.128.59 TFTP Read File Name: /var/adm/ris/ris0.alpha/hvmunix .............................
➊ 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. The name of this device, ewa0, is used as an argument to the boot command. ➌ This command loads Tru64 UNIX from ewa0, autobooting to multiuser mode. See Section 2.
1.4 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–5 Installing Tru64 UNIX >>> show device . . . dka500.5.0.7.1 DKA500 RRD47 1337 ➊ . . . >>> ➊ >>> boot dka500 (boot dka500.5.0.7.1 -flags A) block 0 of dka500.5.0.7.1 is a valid boot block reading 16 blocks from dka500.5.0.7.
➊ Use the boot command to install the operating system from the CDROM, which is either dka500 or dqa0. ➋ See your operating system documentation for further installation instructions.
1.5 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–6 Booting OpenVMS from a Local Disk ➊ >>> show device . . . dka200.2.0.7.1 DKA200 RZ1CB-CA LYJ0 . . . >>> ➋ >>> show boot_reset boot_reset ON >>> show bootdef_dev bootdef_dev dka200.2.0.7.
Example 1–6 Booting OpenVMS from a Local Disk (Continued) . . . The OpenVMS system is now executing the site-specific startup commands. . . . Welcome to OpenVMS (TM) Alpha Operating System, Version V7.1-2 ➎ Username: ➊ 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.
1.5.2 Booting OpenVMS from a Disk on a Cluster Example 1–7 Booting OpenVMS from a Disk on a Cluster ➊ >>> show bootdef_dev bootdef_dev dua110.0.0.8.0 ➋ >>> show device . . . dua110.0.0.8.0 $1$DIA110 (DENVER) RF74 ➌ . . . >>> boot dua110.0.0.8.0 -flags 0) Building FRU table . . . ➍ (boot Welcome to OpenVMS Alpha (TM) Operating System, Version V7.
➊ 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. ➌ ➍ The disk dua110.0.0.8.0 is on the cluster that includes this system. No boot device is specified in the boot command; the default boot device was set with the environment variable. See Section 2.
1.5.3 Booting OpenVMS from a Remote Disk Example 1–8 Booting OpenVMS from a Remote Disk >>> show device . . . ewa0.0.0.8.0 EWA0 08-00-2B-E2-9C-60 . . . >>> >>> boot ewa0 -flags 0 (boot ewa0.0.0.2.0 -flags 0) Building FRU table ➊ ➊ ➋ Trying MOP boot.............. Network load complete. . . . Welcome to OpenVMS Alpha (TM) Operating System, Version V7.
➊ 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. See Section 2.5 for a description of the boot command. The boot command accepts the name of a boot device, a boot file name through the -file option, and boot flags through the -flags option.
1.6 Installing OpenVMS OpenVMS is installed from the CD-ROM. Refer to the documentation shipped with the OpenVMS kit for complete installation instructions. Example 1–9 Installing OpenVMS >>> boot -flags 0,0 dka500 Initializing... SROM V3.0 on cpu0 . . [The initialization display prints. See Section 1.2.] . AlphaServer DS10 Console V5.7-0 Jan 13 2000 15:17:48 ➊ CPU 0 booting (boot dka500.5.0.1.1 -flags 0,0) Building FRU table block 0 of dka500.5.0.1.
Example 1–9 Installing OpenVMS (Continued) Please choose one of the following: 1) 2) 3) 4) 5) Install or upgrade OpenVMS Alpha Version 7.1x List layered product kits that this procedure can install Install or upgrade layered product(s) Execute DCL commands and procedures Shut down this system Enter CHOICE or ? to repeat menu: (1/2/3/4/5/?) ➊ Use the boot command to install the operating system from the CDROM, which is either dka500 or dqa0.
1.7 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.
1.8 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. Example 1–10 Starting LFU from the SRM Console Revision levels and devices listed are for example only; your results may vary. >>> lfu Checking dqa0.0.0.13.0 for the option firmware files. . . Checking dva0 for the option firmware files. . . Option firmware files were not found on CD or floppy.
***** 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.
4. Use the LFU exit command to go back to the console. The sections that follow show examples of updating firmware from the local CDROM, the local floppy, and a network device. Example 1–11 Booting LFU from the CD-ROM Revision levels and devices listed are for example only; your results may vary. >>> show device . . . dka500.5.0.7.1 DKA500 RRD47 1645 . . . >>> boot dka500 (boot dka500.5.0.7.1 -flags 0,0) block 0 of dka500.5.0.7.1 is a valid boot block ..
1.8.1 Updating Firmware from Floppy Disks Create two update diskettes before starting LFU: one for console updates and one for I/O. See Section 1.8.2 for an example of the update procedure. Table 1–3 File Locations for Creating Update Diskettes on a PC Console Update Diskette I/O Update Diskette ds10fw.txt ds10fw.txt pc264nt.rom ccmab022.sys ds10srm.rom dfxaa310.sys kzpsaa12.sys cipca420.
1.8.2 Performing the Update from Floppy Disks Insert an update diskette (see Section 1.8.1) into the floppy drive. Start LFU and select dva0 as the load device. Example 1–12 Updating Firmware from the Floppy Disk Revision levels and devices listed are for example only; your results may vary. >>> lfu Checking dqa0.0.0.13.0 for the option firmware files. . . Checking dva0 for the option firmware files. . . Option firmware files were not found on CD or floppy.
***** 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.
1.8.3 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–13 Updating Firmware from a Network Device Revision levels and devices listed are for example only; your results may vary.
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. In this example, a network device is selected. ➋ For the SRM console, AlphaBIOS console, and I/O adapter firmware, select the file that has the firmware update, (ds10fw.txt ), or press Enter.
Example 1–13 Updating Firmware from a Network Device (Continued) UPD> update * -all ➍ WARNING: updates may take several minutes to complete for each device. AlphaBIOS DO NOT ABORT! Updating to V6.40-1... Verifying V6.40-1... PASSED. kzpsa0 DO NOT ABORT! Updating to A11 ... Verifying A11... PASSED. kzpsa1 DO NOT ABORT! Updating to A11 ... Verifying A11... PASSED. UPD> exit ➎ ➍ The update command updates the device specified or all devices.
1.8.4 LFU Commands The commands summarized in Table 1–4 are used to update system firmware. Table 1–4 LFU Command Summary Command display exit help Function Shows the physical configuration of the system. Terminates the LFU program. Displays the LFU command list. lfu Restarts the LFU program. list Displays the inventory of update firmware on the selected device. readme Lists release notes for the LFU program. update Writes new firmware to the module.
help The help (or ?) command displays the LFU command list, shown below. --------------------------------------------------------------------Function Description --------------------------------------------------------------------Display Displays the system’s configuration table. Exit Done exit LFU (reset). List Lists the device, revision, firmware name, and update revision. Lfu Restarts LFU. Readme Lists important release information. Update Replaces current firmware with loadable data image.
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.
1.9 Using the Halt Button Under OpenVMS and Tru64 UNIX, the halt button pauses the operating system. 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.10). The Halt button operates like issuing an SRM halt command.
Figure 1–6 Halt/Reset Button - DS10L 1 PK2220 1.9.1 Using Halt to Shut Down the Operating System You can use the Halt button if the Tru64 UNIX or OpenVMS operating system hangs. Pressing the Halt button halts the operating system back to the SRM console firmware. From the console, you can use the crash command to force a crash dump at the operating system level. See Section 2.12 for an example. 1.9.
1.10 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” the halt. The next time you power up, the system ignores the SRM power-up script (nvram) and ignores any environment variables that you have set to cause an automatic boot of the operating system.
1.10.2 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. The next time the system powers up, the saved halt status is checked.
1.10.5 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. When the SRM console prompt is displayed, edit the script to delete the offending command. See Section 2.4 for more information on editing the nvram script.
Chapter 2 SRM and AlphaBIOS Consoles The SRM console is the command-line interface that supports the Tru64 UNIX and OpenVMS operating systems. 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. The AlphaBIOS console is used to run certain utilities. This chapter describes the SRM and AlphaBIOS console commands and environment variables.
2.1 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.
2.2 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 Alphabios boot clear envar clear password continue crash deposit edit examine Function Loads and starts the AlphaBIOS console. Loads and starts the operating system. Resets an environment variable to its default value.
Continued on next page. Table 2–1 Summary of SRM Console Commands (Continued) Command more prcache set envar set host set password set secure show envar show config show cpu show device show memory show pal show power show version stop test Function Displays a file one screen at a time. Utility that initializes and displays status of the optional PCI NVRAM device. Sets or modifies the value of an environment variable. Connects to an MSCP DUP server on a DSSI device.
2.2.2 Commands: Syntax Table 2–2 Syntax for SRM Console Commands Parameter Length Case Abbreviation Options Numbers Attribute or Action 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. Upper- or lowercase characters can be used for input. Characters are displayed in the case in which they are entered.
2.2.3 Commands: Special Keystrokes and Characters Table 2–3 Special Characters for SRM Console Character Return or Enter Backslash \ ←Backspace Delete Help Ctrl/A or F14 Ctrl/B or ↑ Function Terminates a command line. No action is taken on a command until it is terminated. If no characters are entered and this key is pressed, the console just redisplays the prompt. Continues a command on the next line. Must be the last character on the line to be continued.
Character Ctrl/O Function Stops output to the console terminal for the current command. Toggles between enable and disable. The output can be re-enabled 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. Ctrl/P Halts the machine. Ctrl/Q Resumes output to the console terminal that was suspended by Ctrl/S. Ctrl/R Redisplays the current line. Deleted characters are omitted.
2.3 Show Commands Several commands are used to display the system configuration: show config, show cpu, show device, show memory, show network, show pal, show power, and show version. 2.3.1 Show Config The show config command displays a list of devices found on the system interconnect and 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: PALcode: Processors CPU 0 V5.
Bus 00 Bus 00 Slot 11: DE500-BA Network Controller ewb0.0.0.11.0 Slot 13: Acer Labs M1543C IDE dqa.0.0.13.0 dqa1.1.0.13.0 Slot 14: DEC PowerStorm Bus 00 Slot 15: DECchip 21152-AA Bus 00 Slot 16: QLogic ISP1020 pkc0.6.0.16.0 dkc0.0.0.16.0 dkc200.2.0.16.0 Slot 17: Mylex DAC960 dra.0.0.17.0 dra0.0.0.17.0 dra1.0.0.17.0 dra2.0.0.17.0 dra3.0.0.17.0 Slot 00: NCR 53C875 pka0.7.0.2000.0 dka100.1.0.2000.0 dka300.3.0.2000.0 dka500.5.0.2000.0 Slot 01: NCR 53C875 pkb0.7.0.2001.0 dkb0.0.0.2001.0 dkb200.2.0.2001.
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. If no name is given, the display is a list of all devices and controllers in the system. Example 2–2 Show Device Command >>> sho device dka0.0.0.14.
Table 2–4 Device Naming Convention dk a Category Description Driver ID Two-letter designator of port or class driver dk SCSI disk dq ATAPI CD-ROM or IDE disk mk SCSI tape dr RAID set device mu DSSI tape du DSSI disk pk SCSI port dv Diskette drive pu DSSI port ew Ethernet port fw FDDI device Storage adapter ID One-letter designator of storage adapter (a, b, c...). Device unit number Unique number (MSCP unit number). SCSI unit numbers are forced to 100 X node ID.
Table 2–5 PCI Address Assignments – DS10 Physical Slot # Logical Slot # PCI ID_SEL Description/Position 4 17 AD 28 64-bit slot (top slot) 3 16 AD 27 64-bit slot (second from top) 2 15 AD 26 64-bit slot (second from bottom) 1 14 AD 25 32-bit slot (bottom slot) Table 2–6 PCI Address Assignment - DS10L Physical Slot # Logical Slot # PCI ID_SEL Description/Position 1 17 AD 28 64-bit slot 2-12 DS10 / DS10L Console Reference
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 # ------0 1 2 3 Size ---------128 MB 128 MB 128 MB 128 MB Base Addr --------000000000 008000000 010000000 018000000 Total Bad Pages = 0 Total Good Memory = 512 MBytes >>> 2.3.4 Show PAL The show pal command displays the versions of Tru64 UNIX and OpenVMS PALcode.
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. Syntax: show power Use this command to display information if the system can be restarted after a shut down. . (If it cannot, use the RMC status command. See Chapter 3.
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.
2.4 Creating a Power-Up Script A special nonvolatile file named “nvram” is stored in EEROM, and is always invoked during the power-up sequence. You can create an nvram script to include any commands you want the system to execute at power-up. You alter, create and edit the nvram script using the SRM edit command. With edit, lines can be added, overwritten, or deleted. Syntax: edit file where file is the name of the file to be edited.
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. Example 2–7 shows how to modify the user-created power-up script, “nvram.” The pound sign (#) indicates explanatory comments.
2.5 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. -flags [value] Specifies additional information to the loaded image or operating system. In Tru64 UNIX, specifies boot flags.
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 jumping to bootstrap code OpenVMS (TM) Alpha Operating System, Version V7.
2.6 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. Syntax: prcache -{f,z,b} -f Checks configuration information and battery status. -z Clears valid data; writes zeros to memory. -b Sets the date (month and year) for battery replacement.
2.7 Testing the System The test command runs console-based exercisers for devices in the system. Ctrl/C can abort testing. Syntax: -t time -q test [-t time] [-q] [option] Specifies the run time in seconds. The default for system test is 120 seconds (2 minutes). Disables the display of status messages as exerciser processes are started and stopped during testing. Sets the environment variable d_verbose to zero.
ID -------00001ae5 00001aea 00001b07 00001b54 00001b74 00001b7b ID -------00001ae5 00001aea 00001b07 00001b54 00001b74 00001b7b ID -------00001ae5 00001aea 00001b07 00001b54 00001b74 00001b7b ID -------00001ae5 00001aea 00001b07 00001b54 00001b74 00001b7b ID -------00001ae5 00001aea 00001b07 00001b54 00001b74 00001b7b ID -------00001ae5 00001aea 00001b07 00001b54 00001b74 00001b7b Program -----------memtest memtest memtest exer_kid exer_kid exer_kid Program -----------memtest memtest memtest exer_kid exer_
ID Program Device Pass Hard/Soft -------- ------------ ------------ ------ --------00001ae5 memtest memory 17 0 0 00001aea memtest memory 17 0 0 00001b07 memtest memory 16 0 0 00001b54 exer_kid dqa0.0.0.13. 0 0 0 00001b74 exer_kid dka0.0.0.14. 0 0 0 00001b7b exer_kid dka100.1.0.1 0 0 0 Test time has expired...
2.8 2.8.1 Set Commands 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. If a password has not been set and the set password command is issued, the console prompts for a password and verification.
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. Syntax: set secure Example 2–13 Set Secure Command >>> set secure # In this example a password # has been set. Console is secure. Please login. >>> b dkb0 Console is secure - parameters are not allowed.
2.9 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. The login command turns off security features during the current console session. The boot command does not accept command line parameters in secure mode.
Example 2–14 Secure Mode and Login Command >>> login # System is not in secure mode. >>> Secure not set. Please set the password. >>> login Please enter the password: >>> # System is in secure mode. # Password is not echoed. >>> login Please enter the password: # System is in secure mode. # Incorrect password is # entered. Invalid password >>> 2.9.2 Clear Password The clear password command clears the password environment variable, setting it to zero.
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. The password is now cleared and the console cannot be put into secure mode unless a new password is set. From the RMC 1. Enter the login command: >>> login 2. At the Enter Password: prompt, enter the RMC escape sequence. 3.
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. 2.11 Updating Firmware The lfu command is used to update firmware from the SRM console prompt. The lfu command starts the Loadable Firmware Update (LFU) Utility.
***** 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.
2.12 Forcing a System Crash Dump The crash command forces a crash dump at the operating system level. 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. This command restarts the operating system and forces a crash dump to the selected device. Syntax: crash [device] where device is the name of the device to which the crash dump is written.
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.
2.13.2 show envar The show envar command displays the current value (or setting) of an environment variable. Syntax: envar show 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.
2.14 Depositing and Examining Data The deposit command stores data in a specified location. The examine command displays the contents of a memory location, a register, or a device. Syntax: deposit [-{b,w,l,q,o,h}] [-{n value, s value}] [space:] address data examine [-{b,w,l,q,o,h}] [-{n value, s value}] [space:] address -b Defines data size as byte. -w Defines data size as word. -l (default) Defines data size as longword. -q Defines data size as quadword. -o Defines data size as octaword.
data Data to be deposited. Symbolic forms can be used for the address. They are: pc The program counter. The address space is set to GPR. + The location immediately following the last location referenced in a deposit or examine command. For physical and virtual memory, the referenced location is the last location plus the size of the reference (1 for byte, 2 for word, 4 for longword). For other address spaces, the address is the last referenced address plus 1.
>>> d -l -n 3 vmem:1234 5 # Deposit 5 into four longwords starting # at virtual memory address 1234. >>> d -n 8 r0 ffffffff # Load GPRs R0 through R8 with -1. >>> d -l -n 10 -s 200 pmem:0 8 # Deposit 8 in the 1 longword of the # first 17 pages in physical memory >>> d -l pmem:0 0 # Deposit 0 to physical mem address 0. >>> d + ff # Deposit FF to physical mem address 4. >>> d scbb 820000 # Deposit 820000 to SCBB.
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. It is useful for displaying output that scrolls too quickly to be viewed.
2.16 Initializing the System The initialize command resets the system and executes powerup tests. Syntax: initialize After self-tests are executed, the system autoboots unless: • A halt assertion condition exists (see Section 1.10) –or– • The auto_action environment variable is set to halt (see Section 2.18.1). If the auto_action environment variable is set to boot or restart and no halt assertion condition exists, the system autoboots.
2.17 Finding Help The help command displays basic information about the use of console commands when the system is in console mode. Syntax: Command . . . help [command . . . ] Command or topic for which help is requested. The options are: None Displays the complete list of commands for which you can receive help. Command_name Displays information about the console command. Argument_string (such as “sh”) Displays information about all commands that begin with that string.
2.18 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. Their values are viewed with the show envar command. Table 2–7 lists the environment variables. Detailed descriptions follow.
Table 2–7 Environment Variable Summary (Continued) Environment Variable ocp_text os_type Function Overrides the default OCP display text with specified text. Specifies the operating system. Valid entries are: openvms, and unix. password A password stored in the NVRAM used to secure the console. pci_parity Disables or enables parity checking on the PCI bus. pk*0_fast pk*0_host_id pk*0_soft_term tt_allow_login Enables fast SCSI mode. Specifies the default value for a controller host bus node ID.
2.18.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 The system remains in console mode after power-up or a system crash. boot The system boots automatically when it is turned on and halts after a system failure.
2.18.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: a Load operating system software from the specified boot device (autoboot). Boot to multi-user mode. i Prompt for the name of a file to load and other options (boot interactively). Boot to single-user mode. s Stop in single-user mode.
Table 2–8 Settings for boot_osflags Bootflags (OpenVMS) Flags_Value Bit Number Meaning 1 0 Bootstrap conversationally (enables you to modify SYSGEN parameters in SYSBOOT). 2 1 Map XDELTA to running system. 4 2 Stop at initial system breakpoint. 8 3 Perform diagnostic bootstrap. 10 4 Stop at the bootstrap breakpoints. 20 5 Omit header from secondary bootstrap image. 80 7 Prompt for the name of the secondary bootstrap file. 100 8 Halt before secondary bootstrap.
2.18.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). NOTE: Disable the RMC to select a baud rate other than 9600. See Chapter3.
• 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. soft_bypass Data bypasses RMC, but RMC switches automatically into snoop mode if an alert condition or loss of carrier occurs. firm_bypass Data bypasses RMC. RMC is effectively disabled.
2.18.7 ew*0_mode Sets an Ethernet controller to run an AUI, ThinWire, or twistedpair 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: aui auto-sense Device type is AUI. Device type is sensed by the console. twisted-pair Device type is 10BaseT (twisted pair). fast duplex, twisted-pair Device type is duplex 10BaseT. fast fast FD BNC auto-negotiate 2.18.8 Device type is fast SCSI.
2.18.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 (default) lk411 Selects the default keyboard hardware type. Selects the LK411 keyboard layout for use with language variant 3C (Français).
2.18.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.
2.18.13 pci_parity Disables or enables parity checking on the PCI bus. Syntax: set pci_parity value where value can be: (default) on Enables PCI parity checking. off 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. A side effect of this is that superfluous PCI parity errors are reported by the host PCI bridge.
2.18.15 pk*0_host_id Sets the controller host bus node ID to a value between 0 and 7. Syntax: set pk*_host_id scsi_node_id 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; however, the eighth device must always be a controller. Each device on the bus, including the controller, must have a unique ID, which is a number between 0 and 7. This is the bus node ID number.
2.18.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. Syntax: set tt_allow_login value where value can be: (default) 1 Enables login through the COM2 port or a graphics monitor.
2.19 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 Type alphabios at the SRM prompt. >>> alphabios The AlphaBIOS console appears.
2.20 Running the AlphaBIOS Console AlphaBIOS is the graphical interface that supports utility programs. NOTE: AlphaBIOS contains features and menus that support multiple operating systems. The Windows NT operating system is not supported on Compaq AlphaServer DS10/DS10L and AlphaStation DS10 systems. Only the AlphaBIOS features applicable to the Tru64 UNIX and OpenVMS operating systems are discussed in this section. After switching to AlphaBIOS, you will see the following screens.
You will see the No Selections Found Screen. Figure 2–2 AlphaBIOS No Selections Found Screen No Operating System Selections Found Press to enter Setup and configure the system. F2=Setup Press F2 on this screen to enter the setup program.
The AlphaBIOS Setup screen shown in Figure 2–3 is displayed. Figure 2–3 AlphaBIOS Setup Screen AlphaBIOS Setup Display System Configuration… AlphaBIOS upgrade… Hard Disk Setup… CMOS Setup… Network Setup… Install Windows NT… Utilities About AlphaBIOS… Press ENTER to install new firmware image(s) from floppy, CD-ROM, or Network. ESC =Exit NOTE: Only the Utilities choice is applicable for the Tru64 UNIX and OpenVMS operating systems.
2.20.1 Running Configuration Utilities Configuration utilities are run directly from the AlphaBIOS Utilities menu. If you change your system configuration, for example, by adding another RAID drive, you will have to run the RAID configuration utility. As you modify your system, you might be required to run other types of configuration utilities as well. Configuration utilities (also called maintenance programs) are run directly from the AlphaBIOS Utility menu. 1.
Figure 2–5 Run Maintenance Program Dialogue Box Run Maintenance Program F1-Help Program Name: __________________ Location: A: ENTER=Execute ESC=Quit CAT0138 2-58 DS10 / DS10L Console Reference
3. In the Run Maintenance Program dialog box, type the name of the program to be run in the Program Name field. Then tab to the Location list box, and select the hard disk partition, diskette, or CD-ROM drive from which to run the program. 4. Press Enter to execute the program. NOTE: If you are running a utility from a diskette, you can simply type the utility’s name into the Program Name field, and press Enter. The diskette drive is the default selection in the Location field.
Chapter 3 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.
3.1 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 3–2 Location of RMC Components on Motherboard - DS10L RMC PIC Processor 1 RMC Jumper Halt/Reset Jumper 1 PK2204 The RMC logic is implemented using an 8-bit microprocessor, PIC17C44, as the primary control device. The RMC PIC is programmed with code to control access to various environmental status bits. You can gain access to the RMC as long as AC power is available to the system (through the wall outlet).
3.2 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.
Figure 3–4 Setups for RMC Mode - DS10L 1 A B 2 PK2219 You can connect a terminal or a modem to the COM1 port, but not both at the same time. You use the terminal to set RMC parameters for the connection, then connect the modem. See Section 3.9.
3.3 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.
3.3.1 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. If it detects the escape sequence, it enters RMC mode. The escape sequence is also delivered to the system on the bypassed data lines.
3.4 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. Invoke the RMC from a serial terminal by typing the following default escape sequence: ^[^[ rmc This sequence is equivalent to typing Ctrl/left bracket, Ctrl/left bracket, and rmc.
3.5 SRM Environment Variables for COM1 Several SRM environment variables allow you to set up the COM1 serial port for use with the RMC. You may need to set the following environment variables from the SRM console, depending on how you decide to set up the RMC. See Chapter 2 for information on setting SRM environment variables. Table 3–1 SRM Environment Variables for COM1 Variable com1_baud com1_flow com1_mode com1_modem Function Sets the baud rate of the COM1 serial/modem port. The default is 9600.
3.6 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. RMC> sta PLATFORM STATUS Firmware Revision: V1.1 Power: ON RMC Halt: Deasserted RMC Power Control: ON Power Supply: OK System Fans: OK CPU Fan: OK Temperature: 31.0°C (warnings at 55.0°C, power-off at 60.
Table 3–2 Status Command Fields (Continued) RMC Power Control On = System has powered on from RMC. Off = System has powered off from RMC. Power Supply System Fans CPU Fan Temperature Escape Sequence OK = Auxiliary 5V is working. OK = PCI and system fan are operating. FAIL = PCI or system fan failure has been detected. OK = Fan on CPU chip is operating. FAIL = CPU fan failure has been detected. Reports current temperature and system limits. Current escape sequence for access to RMC console.
3.7 Remote Power (On/Off) You can power a monitored system on or off from the RMC using console monitor commands.
Figure 3–7 Power Button - DS10L 1 PK2216 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. The Power button, however, has precedence. • If the system has been powered off with the Power button, the RMC cannot power the system on.
3.8 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. The RMC halt in command can be issued remotely to halt the system. The RMC halt out command can be issued to deassert the halt. These commands have the same function as the Halt button (see Figure 3–8 or Figure 3–9) on the control panel for OpenVMS and Tru64 UNIX.
Figure 3–9 Halt/Reset Button - DS10L 1 PK2220 The Halt/Reset button suspends the operating system and returns control to the SRM or RMC console under either the OpenVMS or Tru64 UNIX operating systems. 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.
3.9 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. Then disconnect the serial terminal, connect the modem, and check your configuration.
NOTE: The following modems require the initialization strings shown here. For other modems, see your modem documentation. Modem Initialization String Motorola 3400 Lifestyle 28.8 AT&F0E0V0X0S0=2 AT &T Dataport 14.4/FAX AT&F0E0V0X0S0=2 Hayes Smartmodem Optima 288 V-34/V.FC + FAX AT&FE0V0X0S0=2 ➊ 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.
3.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. You must configure remote dial-in for the dial-out feature to be enabled. See Section 3.9. To set up the dial-out alert feature, enter the RMC from the local serial terminal.
• 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 3.9. The elements of the dial string and alert string are shown in Table 3–3. Paging services vary, so you need to become familiar with the options provided by the paging service you will be using. The RMC supports only numeric messages. ➊ Sets the string to be used by the RMC to dial out when an alert condition occurs.
Table 3–3 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). Enter this character if the dial-out line modifies its dial tone when used for services such as voice mail. D = Dial T = Tone (for touch-tone) 9, The number for an outside line (in this example, 9).
3.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. When a prompt is displayed, type the escape sequence. In the following example, the system is at the SRM console when the modem connection is made.
3.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. See Appendix A. Figure 3–10 RMC Jumpers (Default Positions) – DS10 RMC PIC Processor 1 RMC Jumper PK0246c WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience.
Figure 3–11 RMC Jumpers (Default Positions) – DS10L RMC PIC Processor 1 RMC Jumper PK2205 Remote Management Console 3-23
3.13 Troubleshooting Tips Table 3–4 lists possible causes and suggested solutions for symptoms you might see. Table 3–4 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 connections on power-up. Reconnect the modem. See Section 3.11. RMC does not answer when the modem is called. 3-24 Modem cables may be incorrectly installed. Check modem phone lines and connections.
(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. New password and escape sequence are forgotten. RMC console must be reset to factory defaults. See Section 3.12. The remote user sees a “+++” string on the screen. The modem is confirming whether the modem has really lost carrier This is normal behavior.
3.14 RMC Commands The remote management console supports setup commands and commands for remotely managing the system.
Command Conventions Observe the following conventions for entering RMC commands: • Enter enough characters to distinguish the command. NOTE: The reset and quit commands are exceptions. You must enter the entire word for these commands to work. • For commands consisting of two words, enter the entire first word and at least one letter of the second word. For example, you can enter disable a for disable alert. • For commands that have parameters, you are prompted for the parameter.
3.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. The clear alert command clears the current alert so that the RMC can capture a new alert. The last alert is stored until a new event overwrites it.
3.14.3 disable alert The disable alert command disables the RMC from paging a remote system operator. Monitoring continues and alerts are still logged in the Last Alert field of the status command, but alerts are not sent to the remote operator. Syntax: 3.14.4 disable alert disable remote The disable remote command disables remote access to the RMC modem port and disables automatic dial-out alerts.
3.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 dialin and call-out, set an RMC password (set password command), and enable remote access (enable remote command) to the RMC modem port.
3.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. Before you can enter the enable remote command, you must configure remote dial-in by setting an RMC password (set password command) and initialization string.
3.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 3.8 for a full discussion of this feature. The halt in command is equivalent to pressing the Halt button on the control panel. The effect depends on which operating system you are running, and how the Halt/Reset switch is set.
3.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 3.14.9 help or ? The help or ? command displays the RMC command set.
3.14.10 power off The power off command is equivalent to turning off the system power from the control panel. If the system is already powered off, this command has no effect. You can override the power off command either by issuing a power on command or by toggling the Power button on the control panel. Syntax: power off 3.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.
3.14.12 quit The quit command exits RMC from a serial terminal and returns the user’s terminal to the system’s COM1 port. You must enter the entire word for the command to take effect.
3.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. Syntax: Example: reset RMC> reset Returning to COM port 3.14.14 send alert The send alert command forces an alert condition.
3.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. The alert string cannot exceed 63 characters, and consists of the following elements: ,,,,,, 5085554444# Each comma (,) provides a 2-second delay.
3.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 3.3 for descriptions of the RMC modes. Syntax: set com1_mode value where value can be: snoop Data partially bypasses the RMC, but the RMC taps into the data lines and listens passively for the RMC escape sequence. soft_bypass Data bypasses RMC, but the RMC switches automatically into snoop mode if an alert condition or loss of carrier occurs.
3.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. The dial string is limited to 31 characters.
3.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. Use the status command to verify the escape sequence. Be sure to record the new escape sequence. If you forget the escape sequence, you must reset the RMC to the factory defaults.
3.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 Example: RMC> set init Init String: at&f0e0v0x0s0=2 RMC> Because the modem commands do not allow mixed cases, the RMC converts all alphabetic characters entered in the init string to uppercase. The RMC configures the modem’s flow control according to the setting of the SRM com1_flow environment variable.
3.14.20 set logout The set logout command sets the amount of time before the RMC terminates an inactive modem connection. The default is 20 minutes. The settings are in tens of minutes, 0–9. The zero (0) setting disables logout. With logout disabled, the RMC never disconnects the idle modem session. The following example sets the logout timer to 50 minutes. Syntax: Example: set logout RMC> set logout Logout Time (0-9 tens of minutes): 5 3.14.
You may want to make notes regarding the system. The string is limited to 63 characters and is displayed in the User String field when you enter the status command. In this example, the operator leaves a reminder that the power supply needs to be replaced. Syntax: Example: set user RMC> set user User String: need to replace P/S 3.14.23 set wdt The watchdog timer is a value up to 60 seconds, in increments of 10, set by the user, that can be used by software.
Appendix A Setting Jumpers This appendix gives information on the correct settings of the jumpers on the DS10/DS10L motherboard. Sections include: • Warnings and Cautions • Remove Power from the System • Open the System • Remove the Floppy Disk Enclosure (DS10 only) • Set Jumpers • Restore Power NOTE: In many ways the DS10 and DS10L systems are identical. This manual uses DS10 systems for most illustrations and examples.
A.1 Warnings and Cautions Read the following Warning and Cautions before working on DS10/DS10L systems. 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. CAUTION: To reduce the risk of electrical shock or damage to the equipment, do not disable the power cord grounding plug.
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. Also the CPU and memory modules have parts that operate at high temperatures. Wait 2 minutes after power is removed before touching any module.
Figure A–2 Removing Power - DS10L System 1 A B 2 PK2218 1. Turn off the system and all external peripheral devices. 2. Unplug the system from the wall outlet. 3. Wait at least 15 seconds, to allow time for the power supply capacitors to fully discharge. 4. Wait 2 minutes after power is removed before touching any module.
A.3 Open the System Remove the cover to gain access to the system. Figure A–3 Opening the DS10 System Cabinet 4 2 3 1 PK2214A 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. 4. Slide the cover toward the back of the system ❹. Lift it off. NOTE: If your DS10 or DS10L system is rack mounted, refer to the appropriate rack mounting documentation (EK-DS10S-RM for the DS10 or EK-DS10LRM for the DS10L), and reverse the rack mounting procedures to gain access to the system cabinet.
Figure A–4 Opening the DS10L System Cabinet 3 2 1 PK2207A Setting Jumpers A-7
1. Remove power from the system. 2. Unscrew the two captive screws ❶ on the top of the cover. 3. Unscrew the six quarter-turn screws ❷ on the top of the cover. 4. Raise the cover up and secure it in the 60° or 90° position using a notch on the cover hold-open bracket ❸ located on the right hand side. NOTE: The 60° position on the DS10L cover hold-open bracket allows access to the cabinet interior with the rear cables attached.
A.4 Remove the Floppy Disk Enclosure (DS10 Only) To access the jumpers, remove the floppy disk drive enclosure for DS10 systems, and the hard disk(s) and/or floppy/CD-ROM drive for DS10L systems. Figure A–5 Removing the DS10 Floppy Disk 1 2 PK1018-99 1. Hold on to the cylinder pins, which secure the floppy disk enclosure. Pull the pins toward the center ➊. 2. Pull the floppy drive unit back and up ➋. 3. Place the unit on top of the CD-ROM drive. You do not need to remove the cables.
A.5 Set Jumpers There are three jumpers on the motherboard, which you can access. The switches are set according to the CPU in your system. Do not change the Timer Disable jumper or any of the switches. Figure A–6 Setting Jumpers on the Motherboard (DS10 shown; DS10L switches are in the same location.
CAUTION: Altering these switches from the specified settings may cause damage to your system and void your warranty.
A.6 Restore Power Close up the system and restore power. 1. Replace the drive(s) you removed to access the motherboard. Check that the cables are clear and not pinched. 2. Replace the system cover and secure it. 3. Plug the AC power cord back into the system or outlet, whichever you disconnected. 4. Push the On button on the control panel and power up.
Appendix B Regulatory Compliance Notices This appendix contains regulatory compliance notices for this computer system. B.1 Class A and Class B Ratings Part 15 of the Federal Communications Commission (FCC) Rules and Regulations has established Radio Frequency (RF) emission limits to provide an interference-free radio frequency spectrum. Many electronic devices, including computers, generate RF energy incidental to their intended function and are, therefore, covered by these rules.
B.1.1 Class A Device Notices FCC Notice This equipment generates, uses, and may emit radio frequency energy. The equipment has been type tested and found to comply with the limits for a Class A digital device pursuant to Part 15 of FCC rules, which are designed to provide reasonable protection against such radio frequency interference.
Taiwan Notice Japanese Notice Regulatory Compliance Notices B-3
Canadian Notice This Class A digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations. Avis Canadien Cet appareil numérique de la classe A respecte toutes les exigences du Règlement sur le matériel brouilleur du Canada. European Union Notice Products with the CE Marking comply with both the EMC Directive (89/336/EEC) and the Low Voltage Directive (73/23/EEC) issued by the Commission of the European Community.
B.1.2 Class B Device Notices This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. Any modifications to this device - unless expressly approved by the manufacturer - can void the user’s authority to operate this equipment under part 15 of the FCC rules.
Declaration of Conformity for Products Marked with the FCC Logo (United States only) The device complies with Part 15 of the FCC rules. Operation is subject to the following two conditions: • The device may not cause harmful interference, and • The device must accept any interference received, including interference that may cause undesired operation.
Canadian Notice This Class B digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations. Avis Canadien Cet appareil numérique de la classe B respecte toutes les exigences du Règlement sur le matériel brouilleur du Canada. European Union Notice Products with the CE Marking comply with the EMC Directive (89/336/EEC) and the Low Voltage Directive (73/23/EEC) issued by the Commission of European Community.
Index from cluster disk, 1-17 from local disk, 1-15 from remote disk, 1-19 passing information to command, 243 Tru64 UNIX, 1-9 from local disk, 1-9 from remote disk, 1-11 A AlphaBIOS boot screen, 2-54 configuration, 2-57 run maintenance program, 2-58 setup screen, 2-56 utilities, 2-57 alphabios command, SRM, 2-3 AlphaBIOS console, 1-6, 2-54 switching from SRM, 2-53 auto_action environment variable, SRM, 1-6, 1-7, 2-40, 2-42 Auxiliary power supply, RMC, 3-1 B Baud rate, setting for COM* ports, 2-45 boot c
Console terminal specifying type, 2-46 continue command, SRM, 2-3 using in secure mode, 2-26 cpu_enabled environment variable, SRM, 2-40 crash command, SRM, 2-3, 2-31 Crash dump, 2-31 D Default Settings jumpers, A-11 switches, A-11 deposit command, SRM, 2-3, 2-35 Depositing data, 2-35 Device naming conventions, SRM, 2-11 Dial-in configuration, 3-16 Dialing in, 3-21 Dial-out alerts, 3-18 disable alert command (RMC), 3-29 disable remote command (RMC), 3-29 display command, LFU, 1-33 Displaying system configu
halt in command (RMC), 3-32 Halt, remote, 3-15 hangup command (RMC), 3-17, 3-21, 333 help command, LFU, 1-33, 1-34 help command, SRM, 2-3, 2-39 help or ? commands (RMC), 3-33 I initialize command, SRM, 2-3, 2-17, 238 Initializing the system, 2-38 Installing OpenVMS, 1-21 Tru64 UNIX, 1-13 IOD, 1-6, 1-7 J Jumpers default settings, A-11 setting, A-10 K kbd_hardware_type environment variable, SRM, 2-32, 2-33, 2-40, 2-48 Keyboard specifying hardware type, SRM, 2-48 specifying layout, SRM, 2-48 L language env
from remote disk, 1-19 booting Tru64 UNIX, 1-9 from local disk, 1-9 from remote disk, 1-11 installing OpenVMS, 1-21 installing Tru64 UNIX, 1-13 specifying default, 2-49 os_type environment variable, SRM, 16, 1-7, 2-33, 2-49 P Pagers, 3-19 password environment variable, SRM, 2-27 PCI enabling and disabling parity checking on bus, SRM, 2-49, 2-50 PCI card cage slot numbers, 2-12 PCI options slot numbers, 2-12 pci_parity environment variable, SRM, 2-41, 2-49, 2-50 pk*0_fast environment variable, SRM, 2-41, 2-
set escape command, 3-40 set init command, 3-41 set logout command, 3-42 set password command, 3-42 set user command, 3-42 status command, 3-10, 3-43 terminal setup, 3-4 troubleshooting, 3-24 RMC mode, 3-6 Run maintenance program AlphaBIOS, 2-58 S SCSI enabling and disabling terminators, SRM, 2-51 enabling Fast SCSI, SRM, 2-50 setting controller host bus node ID, SRM, 2-51 send alert command (RMC), 3-36 Serial terminal, specifying as console terminal, SRM, 2-46 set alert command (RMC), 3-37 set dial comman
using in secure mode, 2-26 stop, 2-4, 2-29 summary of commands, 2-3 test, 2-4, 2-21 SRM console environment variables auto_action, 2-40, 2-42 boot_osflags, 2-40, 2-43, 2-44 boot_osflags, OpenVMS, 2-43 boot_osflags, Tru64 UNIX, 2-43 bootdef_dev, 2-40 com*_baud, 2-40, 2-45 commands for displaying the value or setting, 2-33 commands for modifying, 2-32 commands for setting, 2-32 commands for using, 2-32 console, 2-40, 2-46 cpu_enabled, 2-40 ew*0_mode, 2-40, 2-47 ew*0_protocols, 2-40, 2-47 kbd_hardware_type, 2-
