AlphaServer DS20L User’s Guide Order Number: EK-DS20L-UG. B01 This manual is for managers and operators of HP AlphaServer DS20L (Series EA2014) systems.
May 2002 © 2002 Compaq Computer Corporation. Compaq, the Compaq logo, Compaq Insight Manager, AlphaServer, Hewlett-Packard, HP, the Hewlett-Packard logo, StorageWorks, and TruCluster Registered in U.S. Patent and Trademark Office. Tru64 is a trademark of Compaq Information Technologies Group, L.P. in the United States and other countries. Linux is a registered trademark of Linus Torvalds in several countries. UNIX is a trademark of The Open Group in the United States and other countries.
Japanese Notice 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.
Contents Preface ........................................................................................................................xi Chapter 1 Overview 1.1 1.1.1 1.1.2 1.2 1.2.1 1.2.2 1.2.3 1.2.3.1 1.2.3.2 1.2.3.3 1.2.4 1.2.4.1 1.2.5 1.3 1.3.1 1.3.2 1.3.3 1.4 1.5 System Features and Components........................................................ 1-1 Features ................................................................................................ 1-1 Components............................
Memory Configuration Rules.......................................................... 2-6 2.3.2.1 2.3.3 PCI Options........................................................................................... 2-8 2.3.4 Hard Drive ............................................................................................ 2-9 2.3.5 CD-ROM.............................................................................................. 2-14 Chapter 3 Operation 3.1 3.1.1 3.1.1.1 3.1.2 3.1.4 3.1.5 3.2 3.2.1 3.2.1.
4.3.4 4.3.5 4.3.6 4.3.7 Exit Status ............................................................................................ 4-5 Error Conditions ................................................................................... 4-5 Examples............................................................................................... 4-6 Environment Variables ......................................................................... 4-7 Chapter 5 Basic Troubleshooting 5.1 5.1.1 5.2 5.3 5.3.1 5.
Resetting the Password ................................................................A-34 A.11.1 A.12 Stopping and Starting CPU ................................................................A-34 A.13 Updating Firmware.............................................................................A-35 A.14 Forcing a System Crash Dump ...........................................................A-36 A.15 Using Environment Variables.............................................................A-37 A.15.
A–4 A–5 A–6 A–7 A–8 A–9 A–10 A–11 A–12 A–13 A–14 A–15 A–16 A–17 A–18 A–19 A–20 A–21 A–22 A–23 A–24 A–25 A–26 A–27 Show IDE Command...........................................................................A-18 Show Memory Command ....................................................................A-19 Show PAL Command ..........................................................................A-19 Show Power Command .......................................................................
2-10 2-11 2-12 5-1 5-2 5-3 Assembling and Installing the SCSI Hard Drive Carrier................... 2-12 Installing the Hard Drive Assembly ................................................... 2-13 Installing the CD-ROM ....................................................................... 2-15 Network Connector LEDs ..................................................................... 5-2 J2 Firmware Configuration Jumper Block ........................................... 5-4 Fan Locations..................
Preface Intended Audience This manual is for managers and operators of HP AlphaServer DS20L systems. Document Structure This manual has five chapters and one appendix. • Chapter 1, Overview, describes the DS20L system features and components. • Chapter 2, Installation and Options, explains how to set up your DS20L system and how to install optional devices. • Chapter 3, Operation, explains how to turn on your DS20L system, install and boot the operating system, and update the firmware.
Documentation Titles HP AlphaServer DS20L Documentation Title Order Number AlphaServer DS20L User Guide EK–DS20L–UG AlphaServer DS20L Service Guide EK–DS20L–SV AlphaServer DS20L Power Distribution Unit Installation Guide EK–DS20L–PD Information on the Internet Visit the HP Web site at www.compaq.com for service tools and more information about the HP AlphaServer DS20L system. Tru64 UNIX documentation is available at http://www.tru64unix.compaq.
Chapter 1 Overview 1.1 System Features and Components The AlphaServer DS20L is a 1U rack-mountable system that contains dual EV68B 833 MHz CPUs. 1.1.1 Features The DS20L system is a 1U-sized dual processor system with up to 2 GB memory, two PCI slots, an optional CD-ROM drive, and a SCSI hard drive. Table 1–1 summarizes the features of the DS20L system. Table 1–1 AlphaServer DS20L Product Features Feature Description Physical Form Factor 1U Rackmount (1.75 inch x 17 inches x 20 inches).
Table 1-1 AlphaServer DS20L Product Features (continued) Feature Main Memory Description Up to eight 168-pin dual inline memory modules (DIMMs); Min 512 MB, Max 2 GB. Supports phase locked loop (PLL) or register-based synchronous direct random access memory (SDRAM) serial presence detect (SPD) modules of 128 MB, and 256 MB. Low-voltage transistor/transistor logic (LVTTL) compatible memory I/O. Cache External L2 cache with 128-bit data path supports: 4MB cache per processor, DDR SRAMs.
Table 1-1 AlphaServer DS20L Product Features (continued) Feature Description Disk controller Embedded Ultra3SCSI controller for internal SCSI disk drive. Storage Two storage bays – one 3.5” x 1” hard drive bay, one CDROM drive bay. Optional CD-ROM 18.2-GB, 36.4-GB, and 72.8-GB UltraSCSI disk drives that can connect to the embedded SCSI disk controller. Expansion Ports Parallel – One bidirectional enhanced port.
1.1.2 Components The DS20L system has the following observable components: Enclosure The system enclosure measures 1.75 inches high by 17.5 inches wide by 20.5 inches deep. Fans There are a total of 11 fans in the DS20L system: five on the front of the system (connected by cables to the system motherboard) and six mounted internally. Two of the six internal fans are located between the hard drive bay and the PCI card assembly. These are cabled onto the PCI riser.
Figure 1-1 Power Connectors 2 1 MR0069 X Y Main power connector - one 7x2 (14-pin) Disk power connector - one 4x1 (4-pin) 1.2.2 Estimated Power Consumption The typical power consumption for the AlphaServer DS20L is 275 watts AC.
1.2.3 Environmental Table 1–2 lists the environmental requirements for the DS20L system. Table 1– 2 Environmental Parameters Parameter Temperature Specification Operating 50 to 95° F/10 to 35° C NOTE: Maximum operating temperature at sea level; reduce by 1.0F per 1,000 ft (1.8C per 1,000 m) above sea level.
Table 1-2 Environmental Parameters (continued) Parameter Airflow and Quality Altitude Specification Intake location Front Exhaust location Rear Particle size N/A Concentration N/A Operating 10,000 ft/3,048 m Non-operating 40,000 ft/12,192 m NOTE: Higher altitudes are possible if maximum operating temperature is reduced (see Temperature); other restrictions may apply such as maximum permissible altitude for hard drives. 1.2.3.
• VCCI Class A ITE (Japan) • AS/NZS 3548:1995/ Class A ITE (Australia) • CNS13438 Class A (Taiwan) • The DS20L is designed for professional use in cluster applications. DS20L clusters deployed in European Community (EC) countries must be configured with a minimum of four (4) DS20Ls to meet the requirements of EN61000-3-2. Hewlett-Packard has certified and labeled the DS20L as European Conforming (CE) compliant based on the minimum four (4) node installation requirement. 1.2.3.
1.2.5 Acoustical The following table shows the AlphaServer DS20L (Series EA2014) acoustical specifications. Preliminary declared values per ISO 9296 and ISO 7779: LWAd, B LpAm, dBA (bystander positions) With 1 or 0 HDD Idle Operate Idle 6.7 6.7 51 Operate 51 Current values for specific configurations are available from HewlettPackard representatives. 1 B = 10 dBA.
1.3 Front Panel Controls and Indicators The front panel of the DS20L system contains five fans with connectors to the motherboard, a slimline CD-ROM drive bay, a hard disk drive bay, and three LEDs. Figure 1-2 Front View of the System 1 1 23 2 X Y Z [ \ ] 3 4 5 6 MR0359 CD-ROM drive (optional) Hard disk storage bay Four fans (connected to motherboard) System LEDs (see Section 5.
1.3.1 Removing the Front Bezel The front bezel must be removed to insert or eject a CD. Figure 1-3 shows how to remove the front bezel X from the enclosure Y. Z 1. Place a finger in each side tab of the bezel and pull it gently forward to disengage the bezel from the tabs on the front of the enclosure. 2. Reverse these procedures to replace the bezel. Figure 1-3 Removing the Front Bezel 2 3 3 hp r erve haS Alp 0L DS2 1 MR0360 1.3.
1.3.3 Halt Button The AlphaServer DS20L has a Halt button under the front bezel. The Halt button is accessible through an opening on the front panel of the system. To use it, remove the bezel (see Section 1.3.1) and insert a slender object through the access hole to push it in. See Figure 1-4.
1.4 Rear Panel Ports, Slots, and Indicators The I/O rear panel contains the dual Ethernet connectors and the parallel and dual serial connectors. Figure 1-5 Rear View of the System 1 2 3 123 10 X Y Z [ \ ] ^ _ ` a 9 8 7 6 5 4 MR0362 AC power connector Parallel port PCI bus 1 PCI bus 0 Ethernet (for Tru64 UNIX, port 1; for Linux, port 0); two LEDs 1 Ethernet (for Tru64 UNIX, port 0; for Linux, port 1); two LEDs 1 COM1 COM2 On/Off button System LEDs (See Section 5.
1.5 Internal View of the System The AlphaServer DS20L has dual CPUs in a 1U enclosure.
X Y Z [ \ ] ^ _ ` Dual CPUs; left – CPU 1, right – CPU 0, as oriented in illustration Memory slots Hard drive bay CD-ROM bay PCI slots located on the PCI riser I/O daughter card Power supply Cover Front bezel Overview 1-15
Chapter 2 Installation and Options 2.1 System Setup and Installation The AlphaServer DS20L is rack-mountable in M-Series racks. Whether in a rack, or in a stand-alone configuration, first connect all external devices, then connect the system to a grounded AC power source. ! WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience.
2.1.1 Rackmounting See the documentation that came with your rack rails for installing the AlphaServer DS20L in an M-Series rack. 2.1.2 Connecting the System Connect the appropriate external devices first, then connect the AC power cord to the DS20L and a grounded power source. Figure 2-1 shows the location of all connectors.
2.2 Installing Options This section describes how to remove the bezel and/or cover and install memory, PCI options, CD-ROM, or a hard drive. 2.2.1 Bezel Removal NOTE: It is not necessary to remove the front bezel to open the cover to access the inside of the enclosure. You only have to remove the front bezel if you need to access the front of the enclosure to insert or remove a CD, to remove or install the hard drive or the CD-ROM drive, or remove the system from a rack.
2.3 Removal from a Rack If the system is mounted in a rack, refer to Figure 2-3 and follow these procedures to remove it from the rack in order to open the cover. 1. Remove power from the system. 2. Disconnect all external cables from the system. X that hold the system’s chassis slides to the 3. Loosen the two captive screws rack rails, and lift the system forward and out of the rack. 4. To replace the system in the rack, reverse these steps as necessary.
2.3.1 Removing the Cover To remove the cover, refer to Figure 2-4 and follow these steps: 1. Remove power from the system. 2. Remove the retaining screw X from the rear of the cover. Y. Remove three screws Z from each side of the cover [. 3. Remove the top screw 4. 5. Slide the cover back and lift it away from the system.
2.3.2 Memory Memory may be added to or removed from the AlphaServer DS20L. Each memory bank has four slots that accept 168-pin PC100 SDRAM PLL registered/buffered based SPD DIMMs. Memory is supported in a size range from 512 MB to 2 GB. There are two DIMM banks designated Bank 0 and Bank 1. The slots are arranged in an alternating pattern. See Figure 2-5. 2.3.2.1 Memory Configuration Rules • A bank must be fully populated; that is, all four slots in a given bank (0 or 1) must be filled.
Refer to Figure 2-6 and follow these steps to add or remove memory. 1. Review the memory configuration and guidelines. 2. Remove the cover (see Section 2.3.1). X Z 3. To insert a memory DIMM , slide it into the appropriate memory slot and press down gently but firmly to engage the side tabs . Y 4. To remove a memory DIMM, disengage the side tabs and lift it out from the slot.
2.3.3 PCI Options Refer to Figure 2-7 and follow these steps to add or remove PCI options. CAUTION: To prevent over-flexing the PCI riser or module, use your hands to support them as you install or remove the PCI module. 1. Remove the cover (see Section 2.3.1). X you wish to use for the PCI module 2. Determine the slot retaining screw and slot cover to expose the slot. Y. Remove the Z Insert the retaining screw [ through the side of the enclosure and the PCI module’s bracket \. 3.
Figure 2-7 Adding or Removing a PCI Module 3 2 1 4 5 MR0367 2.3.4 Hard Drive Follow these steps to add or remove a SCSI hard drive. 1. Remove the front bezel (see Section 2.2.1) and cover (Section 2.3.1). X (part of CK2. See Figure 2-8. Install the SCSI hard drive backplane DS20L-AA SCSI cable kit) onto its connector on the back of the SCSI hard drive. Attach the power cable connector , and one end of the data cable to the backplane .
Figure 2-8 Installing the SCSI Backplane 3 2 1 MR0368 3. Lift the PCI riser and route the SCSI hard drive cable (17-05034-06) under the notch in the PCI riser card by following these steps. a. Refer to Figure 2-7 to remove any PCI option modules, then refer to Figure 2-9 for the remainder of these procedures. X during these procedures. CAUTION: Do not remove the PCI fan bracket It holds and supports the motherbard in place, making it easier to unplug and lift the PCI riser. b.
[ d. Route the SCSI cable through the notch in the PCI fan bracket . One end of the SCSI cable was connected to the SCSI backplane in Step 3, above. \ on the PCI riser. e. Slide the protector on the SCSI cable into the notch f. Push down firmly and squarely on the PCI riser to seat it back in the motherboard (making sure that the cable remains positioned in the notch) and secure the two screws to the rear bracket. g. Connect the end of the SCSI cable to its connector on the PCI riser.
X Y Z 4. See Figure 2-10. Assemble the SCSI drive carrier by attaching the right and with four tension clips and four UNC screws as shown, left arms ensuring that the handle is secured to the drive by the front of the arms. [ \ NOTE: When installing the arms, bias them upward as high as possible on the disk to ensure that the disk does not interfere with the CD-ROM.
\ ] or , into the enclosure, sliding it 6. Insert the hard drive shield, either from right to left to seat the left-hand tabs. (Use if you have a CD-ROM drive; use if your system does not have a CD-ROM drive.) Secure the drive with the captive snap-in fastener or . ] \ ^ _ CAUTION: If you are installing a SCSI drive, prevent over-flexing backplane by using your hand to support the backplane as you slide the drive into its connector.
2.3.5 CD-ROM A CD-ROM may be added to or removed from the AlphaServer DS20L. \ NOTE: If you are installing a CD-ROM for the first time, you will have to remove the hard drive shield that is on your system (Figure 2-11 ), and replace it with the one that came with the CD-ROM drive (Figure 2-11, ), to allow access to operate the CD-ROM. ] To add or remove a CD-ROM, refer to Figure 2-12 and follow these steps. 1. Remove the front bezel (see Section 2.2.1) and cover (Section 2.3). X Z Y 2.
Figure 2-12 Installing the CD-ROM TOP VIEW 5 2 1 5 4 3 MR0372 Installation and Options 2-15
Chapter 3 Operation 3.1 Powering Up the System This section describes how to turn on the system and what happens when you do. 3.1.1 Turning the System On ` After installing the system as discussed in Chapter 2, push the On/Off button to for the location of the On/Off button). power up the system (see Figure 1-5 Check the LEDs to ensure that the system has power and that there are no initial errors. 3.1.1.
• Performs power-on self-test (POST) of the basic system needed to run diagnostics (memory, etc.). • Initializes the system memory. • Initializes the L2 cache. • Loads diagnostic firmware used by Hewlett-Packard Customer Services engineers. 3.1.
3.1.5 Power-Up Display The power-up display shows the results of power-on self-test (POST). AlphaServer DS20L systems may have various options that will cause the power-up display to differ slightly from the sample shown here. Testing begins after pressing the On/Off button, and screen text similar to that in Example 3–1 displays. Example 3–1 Power-Up Display - Serial Console !! initializing GCT/FRU at 1e0000 Testing the System Testing the Memory Testing the Disks (read only) Testing ei* devices.
3.2 Operating Systems This section discusses booting the Tru64 UNIX and the Linux operating systems, and starting an installation of the operating systems. NOTE: Your system may have factory-installed software (FIS); that is, the operating system has already been installed. If so, refer to the FIS documentation included with your system to boot the operating system for the first time. Linux-ready systems do not come with factoryinstalled software. 3.2.
3.2.1.1 auto_action The SRM auto_action environment variable determines the default action the system takes when the system is power cycled, reset, or experiences a failure. Systems can boot automatically (if set to autoboot) from the default boot device under the following conditions: • When you first turn on system power • When you power cycle or reset the system • When system power comes on after a power failure • After a panic The factory setting for auto_action is halt.
3.2.1.2 bootdef_dev The bootdef_dev environment variable specifies one or more devices from which to boot the operating system. When more than one device is specified, the system searches in the order listed and boots from the first device. Enter the show bootdef_dev command to display the current default boot device. Enter the show device command for a list of all devices in the system.
3.2.1.3 boot_file The boot_file environment variable specifies the default file name to be used for booting when no file name is specified by the boot command. The syntax is: set boot_file filename Example P00>>> set boot_file “” NOTE: This command clears the boot file setting and sets the string to empty.
3.2.1.4 boot_osflags The boot_osflags environment variable sets the default boot flags. Boot flags contain information used by the operating system to determine some aspects of a system bootstrap. Under normal circumstances, you can use the default boot flag settings. To change the boot flags for the current boot only, use the flags_value argument with the boot command. The syntax is: set boot_osflags flags_value The flags_value argument is specific to the operating system.
Linux Systems If aboot.conf contains (0: 1/vmlinux.gz ro root=/dev/sda2), the system can be booted by one of the following methods: 1. set boot_file set boot_osflags 0 boot dkb0 ---or--2. boot dkb0 -file "" -flags 0 ---or--3. set boot_file 1/vmlinuz.gz set boot_osflags "ro root=/dev/sda2" boot dkb0 Example Single-user mode is typically used for troubleshooting. To make system changes at this run level, you must have read/write privileges.
3.2.1.5 ei*0_inet_init or ew*0_inet_init The ei*0_inet_init or ew*0_inet_init environment variable determines whether the interface’s internal Internet database is initialized from nvram or from a network server (through the bootp protocol). Legal values are nvram and bootp. The default value is bootp. Set this environment variable if you are booting Tru64 UNIX from a RIS server. To list the network devices on your system, enter the show device command.
3.2.1.6 ei*0_protocols or ew*0_protocols The ei*0_protocols or ew*0_protocols environment variable sets network protocols for booting and other functions. To list the network devices on your system, enter the show device command. The Ethernet controllers start with the letters “ ei” or “ ew,” for example, ewa0. The third letter is the adapter ID for the specific Ethernet controller. Replace the asterisk (*) with the adapter ID letter when entering the command.
3.2.2 Booting Tru64 UNIX Tru64 UNIX can be booted from a local disk or from a Remote Installation Services (RIS) server over a local area network. To boot from a RIS server, you must first register your system as a RIS client. Refer to the Tru64 UNIX Sharing Software on a Local Area Network manual for information about setting up and using RIS and the Tru64 UNIX Installation Guide - Advanced Topics manual for information about installing Tru64 UNIX from a RIS server. 3.2.2.
X Y Z [ \ The show boot command displays the current default boot device. The show device command displays device information, including name and type of connection to the system. The operating system is on this device. The name of this device, dkb0, is used as an argument to the boot command. This command loads Tru64 UNIX from the disk dkb0, using the boot file vmunix and autobooting to multiuser mode.
3.2.2.2 Booting from a Remote Disk Example 3– 3 Booting Tru64 UNIX from a Remote Disk X P00>>> show device . . . eia0.0.3.1 EIA0 08-00-2B-E2-9C-60 >>> >>> boot -flags an -protocols bootp eia0 (boot eia0.0.3.1 -flags an) Building FRU table Y Z 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 ..........................
X Y Z [ The show device command displays device information, including name and type of connection to the system. The operating system is on a remote disk, eia0. The name of this device, eia0, is used as an argument to the boot command. This command loads Tru64 UNIX from eia0, autobooting to multiuser mode. 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.
3.2.3 Starting a Tru64 UNIX Installation Tru64 UNIX can be installed from the CD-ROM drive connected to the system or from a Remote Installation Services (RIS) server over a local area network. The user interface that you see after you boot your system depends on whether your system console is a VGA monitor or a serial terminal. To install the operating system from a RIS server, you must first register your system as a RIS client.
Loading installation process and scanning system hardware. Welcome to the UNIX Installation Procedure This procedure installs UNIX onto your system. You will be asked a series of system configuration questions. Until you answer all questions, your system is not changed in any way.
3.2.4 Installing and Booting Linux Obtain the Linux installation document and install Linux on the system. Then verify the firmware version, boot device, and boot parameters, and issue the boot command. You need V5.6-3 or higher of the SRM console to install Linux. If you have a lower version of the firmware, you will need to upgrade. For instructions and the latest firmware images, see the following URL. http://ftp.digital.
3. Ensure that the SRM console environment sysvar is set to 5 prior to installing or booting Linux. P00>>> set sysvar 5 P00>>> init 4. When switching back from Linux to Tru64 UNIX, verify that the SRM console environment sysvar is equal to 12. P00>>> set sysvar 12 P00>>> init 5. After installing Linux, set boot environment variables appropriately for your installation. The typical values indicating booting from dka0 with the first aboot.conf entry are shown in this example.
aboot: valid disklabel found: 3 partitions. aboot: loading uncompressed vmlinuz-2.4.3-7privateer2smp... aboot: loading compressed vmlinuz-2.4.3-7privateer2smp... aboot: zero-filling 369720 bytes at 0xfffffc0000ce9400 aboot: starting kernel vmlinuz-2.4.3-7privateer2smp with arguments root=/dev/sda2 console=ttyS0 Linux version 2.4.3-7privateer2smp (root@privateer) (gcc version 2.96 20000731 (Red Hat Linux 7.1 2.
3.3 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 3– 6 Starting LFU from the SRM Console Revision levels and devices listed are for example only; your results may vary. >>> lfu Checking dqb0.0.1.16.0 for the option firmware files. . . Option firmware files were not found on CD or floppy.
NOTE: If the system has been shut down from a booted program (most commonly, the operating system) or in some other way halted back to the SRM console, the system must be reset before running LFU. Use the Loadable Firmware Update (LFU) utility to update system firmware. From the SRM console, start LFU by issuing the lfu command (see Example 3–6). A typical update procedure is: 1. Start LFU. 2.
3.3.1 Updating Firmware from a Network Device Updating firmware from a network device can be done using the bootp command or using a local MOP server. Example 3– 7 Updating Firmware from a Network Device X –proto bootp eia0 P00>>> boot –file ds20lsrm (boot eia0.0.0.3.1 -flags A) Trying BOOTP boot. Broadcasting BOOTP Request... .. X Name of the firmware image (.exe extension) to be loaded. You can also use the default image using this command.
***** 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.
3.3.2 LFU Commands The commands summarized in Table 3– 1 are used to update system firmware. See Section A.13 for an example of the LFU command output. Table 3– 1 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.
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.
Chapter 4 Remote Management This chapter contains an overview of the remote control features and describes how remote management is supported. 4.1 Overview An AlphaServer DS20L system is usually configured in a network cluster with other rack-optimized nodes. Each system has integrated network interfaces so that management stations can be used for control rather than duplicating central management functions on each system. These management stations provide for remote access to the rest of the systems.
4.2 Basic Remote Control The DS20L motherboard includes two Intel i82559 Ethernet controllers. Each controller is on a different host PCI bus (device 4 on host bus 0 and device 3 on host bus 1). The controller on host bus 0 is the primary controller (and its RJ45 connector is the left-hand one on the rear of the chassis; the other controller is the secondary controller. The primary Ethernet is kept separate and protected from general access when special management functions are enabled.
In order to start the desired system, use the administrative command /usr/sbin/cs20wake00:02:56:00:00:fd on any other system directly connected to the privileged primary Ethernet network. 4.2.2 Shutdown The status of a running system is normally monitored using network connections over the primary (or secondary) Ethernet controllers (that is, using ICMP or SNMP messages). It is also monitorable via network management services.
4.3.1 Operation To enable the wake-on-LAN feature, set the target system’s wol_enable console variable to on and reset the system so that the network controller can read the new state.
4.3.2 Restrictions The following restrictions apply to the WOL utility. • You must be logged in as root or have superuser privileges to use the WOL utility. • The target system must be on the same subnet as the system where the WOL utility is involked. • The target system’s power cannot be turned off with the WOL utility. 4.3.3 Syntax: Commands /usr/sbin/wol [nw_interface] hw_address nw_interface Specifies the network interface to use in making the connection to the target system, for example:tu1.
Patterns must be specified as hex digits The Magic Packet address must be specified as 00-11-22-33-44-55 Explanation: The hardware network address entered was in the wrong format. The argument must be in the following format: xx-xx-xx-xx-xx-xx where x is a hexadecimal character (0 through 9 and A through F, inclusive). User Action: Specify the hardware network address correctly.
4.3.7 Environment Variables The following command enables or disables the wake-on-LAN feature on the target system. Valid values are on and off. wol_enable NOTE: This is a system console variable, not a Tru64 UNIX environment variable. Section 4.3.1 tells you how to enable the wake-on-LAN feature on the target system. You must enable this feature before you use the WOL utility.
Chapter 5 Basic Troubleshooting 5.1 LED Error Indicators There are system LED indicators are on both the front and back of the AlphaServer DS20L, and each of the network connectors has status LEDs. Figure 1-2 in the first chapter identifies the system LED indicators on the front of the system. Table 5–1 Front System LED Status Indicators LED Function 1 Steady red when system failure needs attention. Off when the system is functioning properly. 2 Blinks amber to indicate system activity.
Figure 1-5 in the first chapter identifies the system LED indicators on the rear of the system. Table 5– 2 Rear System LED Status Indicators LED Function 1 Steady red when system failure needs attention. Off when the system is functioning properly. 2 Blinks amber to indicate system activity. 3 Blinks green when the system is in Standby mode. Glows green to indicate that system power is on. Glows red when the system power has failed.
Table 5– 3 Network Connector LEDs LED LED Status Meaning Speed LED (upper left-hand corner) Off Connector running at 10 M-bits Green Connector running at 100 M-bits Orange Connector on Standby Off Not linked Yellow Linked Blinking Yellow Activity Activity LED (upper right-hand corner) 5.1.1 Internal Power Failure Take these steps if your system experiences an internal power failure. In the event of an internal power failure, clear the red power fail LED with the steps shown.
5.3 Firmware Configuration Jumpers Motherboard jumpers are used to change the configuration of the AlphaServer DS20L system. The factory default firmware configuration jumper block in the AlphaServer DS20L is J2. Remove the cover to locate the jumper block. See Section 2.3.1. Figure 5-2 shows the relative positioning of the J2 jumper with other jumpers and connectors, and depicts all jumpers in their default position. Section 5.3.1 describes the functions of the pins.
X Y Z [ \ 5.3.1 Firmware configuration jumper block, J2; the pins are numbered as shown: 15 13 11 9 7 5 3 1 16 14 12 10 8 6 4 2 Jumper J41 (not used) CPU disable jumper J1 (for factory use only) IDE connector 1 (CD-ROM) PCI riser slot J2 Firmware Configuration Jumper Block The J2 jumper may be used by customers to change the firmware configuration setting.
Table 5– 4 J2 Configuration Jumper Pin Functions Install Jumper on Pins Function 5-6 3-4 1-2 Normal operations; execute firmware and boot to operating system using current or default environment settings. 0 0 0 Restore factory default environmental settings. 0 0 1 Upgrade or recover firmware (COM1). 0 1 0 Failsafe reflash from CD-ROM (COM1). 0 1 1 Field installation and test mode. 1 * * Note: 0 = no jumper installed, 1 = jumper installed * indicates reserved pins 5.
Example 5– 1 Fan Statuses Using the SRM Show Power Command P00>>> show power Processor Module Information Proc 1 Proc 2 Dimm I/O OK OK OK Fan1 Status OK Fan2 Status OK OK OK 2.5V OK OK OK Vccp1 OK OK OK 3.3V OK OK OK OK 5.0V OK OK OK 12.0V OK OK OK OK Vccp2 Temperature 28.00 27.00 45.00 33.
Appendix A SRM Console The SRM console is the command-line interface that supports the Tru64 UNIX and Linux 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. This appendix describes the SRM console commands and environment variables. A.1 SRM Console Overview This section contains an overview of the SRM console and its use.
>>> set bootdef_def dka0 If you set an undefined variable, it will be created for you; however, it will not persist across reboots. The bootdef_dev variable specifies the device that will be booted from if no device is specified on the ERRW command line, or in an automatic boot. The boot_file variable contains the filename to be loaded by the secondary bootloader, while boot_flags contains any extra flags. auto_action specifies the action which the console should take on power-up.
a flag-word at offset 496, which is always 0, and a checksum at offset 504. The checksum is simply the sum of the first 63 long integers in the first sector. If the checksum in the first sector is correct, SRM goes ahead and reads the size sectors starting from the sector given in the sector number field and places them in virtual memory at address 0x20000000. If the reading completes successfully, SRM performs a jump to address 0x20000000. A.
A.3 Command Summary This section presents a command summary, gives the syntax for the console commands, and explains the special keystrokes and characters available in SRM console mode. Table A–1 Summary of SRM Console Commands Command boot clear envar clear password continue crash deposit edit examine Function Loads and starts the operating system. Resets an environment variable to its default value. Sets the password to zero. Resumes program execution.
Table A-1 Summary of SRM Console Commands (continued) Command more prcache set envar set host set password set secure show envar show config show cpu 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. Sets the console password for the first time or changes an existing password.
A.3.1 Commands: Syntax Table A– 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 A–3) causes display of an error message. Case Upper- or lowercase characters can be used for input. Characters are displayed in the case in which they are entered.
A.3.2 Commands: Special Keystrokes and Characters Table A– 3 Special Characters for SRM Console Character Function Return or Enter 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. Backslash \ Continues a command on the next line. Must be the last character on the line to be continued.
Table A-3 Special Characters for SRM Console (continued) Character Function Ctrl/J Deletes the previous word. Ctrl/O 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.
A.4 Show Commands Several commands are used to display the system configuration: show config, show device, show hwrpb, show ide, show memory, show pal, show power, and show version. A.4.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.
Bus 00 Slot 03: Adaptec 29160 Bus 00 pka0.7.0.3.0 dka0.0.0.3.0 Slot 04: Intel 8255x Ethernet eib0.0.0.4.0 Slot 07: Acer Labs M1543C Bus 00 SCSI Bus ID 7 COMPAQ BF01865222 00-02-56-00-08-7D Bridge to Bus 1, ISA Bus 00 Bus 00 PCI Hose 01 Bus 00 ISA Slot 0 Slot 16: Acer Labs M1543C IDE dqa.0.0.16.0 dqb0.0.1.16.0 Slot 17: Acer Labs M1543C PMU SAMSUNG CD-ROM SN-12 Slot 03: Intel 8255x Ethernet eia0.0.0.3.
A.4.2 Show Device The show device command displays status for devices and controllers in the system: SCSI and MSCP devices, 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 A– 2 Show Device Command P00>>> show device dkb0.0.0.5.0 dqb0.0.1.16.0 eia0.0.0.3.
Table A– 4 Device Naming Convention dk Category Description Driver ID Two-letter designator of port or class driver dk SCSI disk dq ATAPI CD-ROM mk SCSI tape dr RAID set device mu DSSI tape du DSSI disk pk SCSI 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. 2 Bus node number Bus node ID.
A.4.3 Show hwrpb The show hwrpb command displays the hwrpb memory location.
312 00000000 00000AC0 Offset to DSRDB 00002180 slot at index 0 00000000 00000000 KSP 00000000 00000000 ESP 00000000 00000000 SSP 00000000 00000000 USP 00000000 00000000 PTBR 00000000 00000000 ASN 00000000 00000000 ASTEN_SR 00000000 00000000 FEN 00000000 00000000 CC 00000000 00000000 SCRATCH [0] 00000000 00000000 SCRATCH [1] 00000000 00000000 SCRATCH [2] 00000000 00000000 SCRATCH [3] 00000000 00000000 SCRATCH [4] 00000000 00000000 SCRATCH [5] 000001CC 00000000 SCRATCH [6] 0 Boot in progress 0 Restart capab
00002400 slot at index 1 00000000 00000000 KSP 00000000 00000000 ESP 00000000 00000000 SSP 00000000 00000000 USP 00000000 00000000 PTBR 00000000 00000000 ASN 00000000 00000000 ASTEN_SR 00000000 00000000 FEN 00000000 00000000 CC 00000000 00000000 SCRATCH [0] 00000000 00000000 SCRATCH [1] 00000000 00000000 SCRATCH [2] 00000000 00000000 SCRATCH [3] 00000000 00000000 SCRATCH [4] 00000000 00000000 SCRATCH [5] 000001CC 00000000 SCRATCH [6] 0 Boot in progress 0 Restart capable 1 Processor available 1 Processor pre
00002680 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 console terminal block 00000004 TYPE 00000000 ID 00000000 RSVD 00000160 DEV_DEP_LEN 00000015 DEV_IPL 00000000 TX_SCB_OFFSET 00000000 RX_SCB_OFFSET 00000002 TERM
00002840 00002AC0 memory descriptor 00000000 00000106 CHECKSUM 00000000 00000000 IMP_DATA_PA 00000000 00000005 CLUSTER_COUNT 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000100 00000000 00000000 00000000 00000000 00000001 0 START_PFN PFN_COUNT TEST_COUNT BITMAP_VA BITMAP_PA BITMAP_CHKSUM USAGE bad page(s) 00000000 00000000 00000000 00000000 00000000 00000007 00000000 00000100 0001FEA3 0001FEA3 00000000 3FF58000 FFFFF805 00000000 0 START_PFN PFN_COUNT TEST_COUNT BITMAP_VA
00000000 00000000 FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF 00000000 00000000 00000000 Platform 00000009 LURT Count 0000004B LURT Column 1 FFFFFFFF LURT Column 2 FFFFFFFF LURT Column 3 FFFFFFFF LURT Column 4 FFFFFFFF LURT Column 5 FFFFFFFF LURT Column 6 FFFFFFFF LURT Column 7 0000041A LURT Column 8 0000041A LURT Column 9 00000020 Name Count Name = hp AlphaServer DS20L 833 MHz P00>>> A.4.
A.4.5 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 A– 5 Show Memory Command P00>>> show memory Array # ------0 Size ---------1024 MB Base Addr --------000000000 Total Bad Pages = 0 Total Good Memory = 1024 MBytes P00>>> A.4.6 Show PAL The show pal command displays the versions of Tru64 UNIX PALcode.
A.4.7 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 system that shuts down because of a fan, temperature, or power supply failure. Use this command to display information if the system can be restarted after a shut down. Syntax: show power [option] -status (default) All monitored values are displayed as either OK or FAIL.
Temperature 28.00 27.00 45.00 33.00 33.00 39.00 I/O 8231 0 Riser 8766 8083 PSU 8385 8282 2.52 1.50 3.36 4.97 12.18 3.28 5.36 12.18 3.35 4.94 12.12 5.52 12.25 45.00 37.00 37.00 44.
2.5V Vccp1 3.3V 5.0V 12.0V Vccp2 Temperature Dimm Megabytes 1 128 3.30 5.62 12.12 35.00 2 128 3 128 4 128 5 X 6 X 7 X 8 X System fail LED Extinguished System enters standby on AC power Normal SROM deselected A.4.8 Show Version The show version command displays the version of the SRM console program that is installed on the system. Syntax: show version Example A– 8 Show Version Command P00>>> show version version P00>>> V5.
A.5 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 powerup. 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.
Example A– 9 Editing the nvram Script >>> edit nvram editing ‘nvram’ 0 bytes read in *10 set ewa0_protocols bootp *list 10 set ewa0_protocols bootp *exit 27 bytes written out to nvram >>> nvram #Modify user power-up script, nvram. #List current file with line numbers. #Close file and save changes. #Execute the script. To clear the script, enter line numbers without any text. This deletes the lines. See Example A–10.
A.6 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 it specifies boot flags.
Example A– 11 Boot Command P00>>> b (boot dkb0.0.0.5.0 -flags A) block 0 of dkb0.0.0.5.0 is a valid boot block reading 14 blocks from dkb0.0.0.5.0 bootstrap code read in base = 200000, image_start = 0, image_bytes = 1c00 initializing HWRPB at 2000 initializing page table at 1ff4a000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code . . . The system is ready. Compaq Tru64 UNIX V5.1A (Rev.
A.7 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.
A.8 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 150 seconds (2.5 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 Program Device Pass Hard/Soft Bytes Written Bytes Read -------- ------------ ------------ ------ --------- ------------- ------------000003cb memtest memory 1 0 0 444596224 444596224 000003ca memtest memory 1 0 0 452984832 452984832 000003cc memtest memory 1 0 0 444596224 444596224 0000042a exer_kid dqa0.0.0.16. 0 0 0 0 145920 0000042c exer_kid dqb0.0.1.16.
A.9 Set Commands This section lists some of the more common set commands and how to use them. A.9.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.
A.9.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 A– 15 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.
A.10 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 A– 16 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 >>> A.11 Clear Password The clear password command clears the password environment variable, setting it to zero.
A.11.1 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. A.12 Stopping and Starting CPU The halt (or stop) command stops program execution on a CPU that is still running a booted program.
A.13 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. The syntax is: lfu Example A– 18 Lfu Command >>> lfu Checking dqb0.0.1.16.0 for the option firmware files. . . Copying ds20lsrm.rom from dqb0.0.1.16.0. . . Copying diags.rom from dqb0.0.1.16.0. . .
NOTE: If the system has been shut down from a booted program (most commonly, the operating system) or in some other way halted back to the SRM console, the system must be reset before running LFU. See Chapter 3 for more information about LFU. A.14 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.
A.15 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.
A.15.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.
A.16 Depositing and Examining Data The deposit command stores data in a specified location. The examine command displays contents of a memory location, register, or 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.
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.
Example A– 22 Deposit Command >>> dep -b -n 1ff pmem:0 0 # Clear 1st 512 bytes of physical mem. >>> 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.
A.17 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. For example, when you power up the system, the system startup messages scroll, and the messages are logged to an event log.
A.18 Initializing the System The initialize command resets the system and executes power-up tests. Syntax: initialize After self-tests are executed, the system autoboots unless: • A halt assertion condition exists –or– • The auto_action environment variable is set to halt. If the auto_action environment variable is set to boot or restart and no halt assertion condition exists, the system autoboots. In all other cases, the system stops in console mode and does not attempt to boot.
A.19 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.
A.20 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 A–5 lists the environment variables. Detailed descriptions follow.
Table A-5 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 unix and linux. 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 Enables fast SCSI mode. pk*0_host_id Specifies the default value for a controller host bus node ID.
A.20.1 ac_action Specifies the action the system takes when AC power is applied. Syntax: set ac_action boot where value can be: boot standby The system boots automatically when AC power is applied. Boot is the default. The system goes to standby when AC power is applied. A.20.2 auto_action Specifies the action the console takes any time the system powers up, fails, or resets.
A.20.3 bootdef_dev The bootdef_dev environment variable specifies one or more devices for booting the operating system. When more than one device is listed, the system searches in the order listed and boots from the first device with operating system software. Syntax: set bootdef_dev boot_device Where boot_device is the name of the device on which the system software has been loaded. To specify more than one device, separate the names with commas.
A.20.5 com1_baud The default baud rate for the system is 9600. The upper limit is 115200. 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). You will be asked to confirm the change, as shown in Example A–27.
A.20.6 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: aui Device type is AUI. bnc Device type is ThinWire. fast Device type is fast 100BaseT. fastfd Device type is fast full duplex 100BaseT. full Device type is full duplex twisted-pair. twisted-pair Device type is full duplex twisted-pair. A.20.
A.20.8 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 button or issuing the initialize command.
A.20.10 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 paritygenerating 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.
A.20.12 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.
A.20.14 sysvar Determines if the system variation value should be overridden from 12 to 5. This allows operating system versions before those that are aware of the DS20L to run properly. Syntax: set syvar value where value can be: 5 (default) low For Linux. For Tru64 UNIX. A.20.15 tt_allow_login Enables or disables login to the SRM console firmware on alternate console ports.
A.20.16 wol_enable Sets the remote power cycle toggle capability for eib0 (the Ethernet NIC on hose 0 device 4). This state is held in the EEPROM associated with this NIC. Syntax: set wol_enable value where value can be: (default) off Wake on LAN utility disabled. on Wake on LAN utility enabled.
Index A ac_action environment variable, SRM, A45, A-47 Acoustical specifications, 1-9 Alpha Diagnostics, 1-3 auto_action environment variable, SRM, 3-3, 3-5, A-45, A-47 B Baud rate, setting for COM* ports, A-49 Bays CD-ROM, 1-4 storage, 1-4 Bezel, 1-4 Bezel removal, 1-11, 2-3 boot command, SRM, 3-12, 3-13, 3-15, A-4, A-26 using in secure mode, A-32 Boot flags Linux, 3-9 Tru64 UNIX, 3-8 Boot options, 3-4 setting, 3-4 boot_file environment variable, SRM, 37, 3-13, 3-15, A-32 boot_flags environment variable,
Cover removal, 2-5 CPU, 1-1, 3-1 cpu_enabled environment variable, SRM, A-45 crash command, SRM, A-4, A-36 Crash dump, A-36 D deposit command, SRM, A-4, A-41 Depositing data, A-41 Device naming conventions, SRM, A-12 Dimensions, 1-8 Disk controller Ultra3SCSI, 1-3 Display power-up, 3-3 display command, LFU, 3-25 Display fan status, 5-6 Displaying system configuration, A-9 Displaying the value or setting of an environment variable, A-38 Double Data Rate (DDR) transfers, 1-2 DS20L system features, 1-1 E edi
Firmware configuration jumper block, 5-5 jumper pins, 5-6 jumpers, 5-4 Front bezel removal, 1-11, 2-3 Front panel, 1-10 Front view, 1-10 H Halt button, 1-12, 5-3 halt command, SRM, A-4, A-34 Halting the system, 5-3 Hard drive inserting, 2-13 installing or removing, 2-9 Hard drive assembly, 2-12 Hard drives, 1-3 help command, LFU, 3-25, 3-26 help command, SRM, A-4, A-44 I I/O card, 1-2 shield, 1-8 slots, 1-2 specifications, 1-8 initialize command, SRM, A-4, A-23, A43 Initializing the system, A-43 Inserting
installing, 3-18 list command, LFU, 3-22, 3-25, 3-26 Loadable Firmware Update utility.
link status, 4-3 overview, 4-1 shutdown, 4-3 startup, 4-2 WOL utility, 4-3 Removing a CD, 1-11 Removing the bezel, 1-11, 2-3 Removing the cover, 2-5 Removing the system from rack, 2-4 Reset, specifying console action, SRM, A-47 RIS Booting Tru64 UNIX, 3-12 Tru64 UNIX installation, 3-16 Routing SCSI cable, 2-11 S Safety, 1-7 SCSI enabling fast SCSI, SRM, A-52 setting controller host bus node ID, SRM, A-53 SCSI backplane installing or removing, 2-10 SCSI cable routing, 2-11 SCSI disk controller, 1-3 set enva
initialize, A-4, A-23, A-43 lfu, 3-22, A-4, A-35 login, A-4, A-33 using in secure mode, A-32 more, A-5, A-42 prcache, A-5, A-27 set envar, A-5, A-37, A-38 set host, A-5 set password, A-5, A-30 set secure, A-5, A-31 show boot, 3-13 show config, A-5, A-9 show device, 3-13, 3-15, A-5, A-11 show envar, A-5, A-38 show hwrpb, A-13 show ide, A-5, A-18 show memory, A-5, A-19 show pal, A-5, A-19 show power, A-5, A-20 show version, A-5, A-22 start using in secure mode, A-32 stop, A-5, A-34 summary of commands, A-4 te
Testing the system (all operating systems), A-28 Thermal specifications, 1-8 Troubleshooting, 5-1 Tru64 UNIX booting, 3-12 from local disk, 3-12 from remote disk, 3-14 console for, A-1 installing, 3-16 specifying as default operating system, A-51 text-based installation display, 3-16 tt_allow_login environment variable, SRM, A-46, A-54 U Ultra3SCSI disc controller, 1-3 update command, LFU, 3-22, 3-25, 3-27 Updating firmware, 3-21 Updating firmware from SRM console, 3-21, A-35 V verify command, LFU, 3-25,
