AlphaServer 1200 User’s Guide Order Number: EK–AS120–UG. A01 This manual is for anyone who manages, operates, or services the AlphaServer 1200 system. It covers operation, firmware, initial troubleshooting, and component installation.
First Printing, October 1997 Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description.
Contents Preface ............................................................................................................... xi Chapter 1 1.1 1.2 1.3 1.4 1.5 1.6 System Architecture .................................................................................1-2 System Features .......................................................................................1-4 Front Panel Controls and Indicators ..........................................................1-6 Rear Panel Ports and Slots .......
3.9.3 3.9.4 3.9.5 3.10 3.10.1 3.10.2 3.10.3 3.11 3.12 Updating Firmware from Floppy Disk—Performing the Update ......3-36 Updating Firmware from a Network Device ....................................3-40 LFU Commands ..............................................................................3-44 Hard Disk Partitioning............................................................................3-47 Hard Disk Error Conditions .............................................................
.3.8 5.4 5.5 5.5.1 5.5.2 5.6 5.7 5.8 5.8.1 5.8.2 5.9 5.10 5.10.1 5.10.2 Integrated Peripherals ......................................................................5-20 Updating Firmware ................................................................................5-22 Setting up the Hard Disk ........................................................................5-24 Creating and Deleting Partitions Manually ......................................5-26 Formatting a FAT Partition........................
Examples 3–1 3–2 3–3 3–4 3–5 3–6 3–7 3–8 3–9 3–10 3–11 3–12 3–13 3–14 3–15 3–16 4–1 4–2 4–3 4–4 4–5 4–6 4–7 4–8 4–9 4–10 4–11 4–12 4–13 4–14 4–15 4–16 4–17 4–18 4–19 4–20 4–21 4–22 4–23 4–24 4–25 vi Power-Up Display ....................................................................................3-4 Booting DIGITAL UNIX from a Local Disk ............................................3-8 Booting DIGITAL UNIX from a Disk on a Cluster ................................
4–26 4–27 4–28 4–29 4–30 6–1 6–2 6–3 6–4 Examine Command ................................................................................4-39 More Command .....................................................................................4-42 Initialize Command ................................................................................4-43 Help (or Man) Command .......................................................................4-45 Switching to the AlphaBIOS Console..............................
5–18 5–19 5–20 5–21 5–22 5–23 5–24 5–25 5–26 5–27 5–28 5–29 6–1 6–2 6–3 7–1 7–2 7–3 7–4 7–5 7–6 7–7 7–8 7–9 7–10 7–11 7–12 8–1 8–2 8–3 Delete Partition Dialog Box ...................................................................5-27 Formatting a FAT Partition ....................................................................5-28 Standard Formatting ...............................................................................5-29 Standard CMOS Setup Screen .............................................
4–7 6–1 6–2 6–3 8–1 Settings for boot_osflags Bootflags (OpenVMS) ....................................4-51 RCM Command Summary .......................................................................6-7 RCM Status Command File ....................................................................6-15 RCM Troubleshooting ............................................................................6-18 Control Panel Display ..............................................................................
Preface Intended Audience This manual is for anyone who manages, operates, or services an AlphaServer 1200 system. Document Structure This manual uses a structured documentation design. Topics are organized into small sections for efficient online and printed reference. Each topic begins with an abstract. You can quickly gain a comprehensive overview by reading only the abstracts. Next is an illustration or example, which also provides quick reference.
Documentation Titles Table 1 lists the books in the AlphaServer 1200 documentation set.
Chapter 1 Overview This chapter provides an overview of the AlphaServer 1200 system features and capabilities.
1.1 System Architecture The AlphaServer 1200 is a high-performance system. Figure 1–1 shows the system architecture.
The AlphaServer 1200 pedestal system is housed in an enclosure containing the motherboard, CPU cards, memory modules, and power supplies. This enclosure allows for up to ten internal storage devices: one dedicated diskette drive slot, two removable media slots, and seven 3.5-inch hard disk drives. The control panel includes Halt, Reset, and On/Off buttons.
1.2 System Features The system provides a number of features that enhance its reliability and improve its expansion capabilities, as well as facilitate hardware management and improve security. Reliability • 64-bit Alpha architecture Provides significantly better performance than 32-bit architecture. • Error correction code (ECC) on memory and CPU cache Allows recovery from most cache and memory errors. • Variable fan speed Adjusts fan speed according to system temperature.
• UltraSCSI backplane Supports high-performance drive technology. • Hot swap disk capability Allows replacement of StorageWorks disk drives while the system continues to operate. System Management • System diagnostics Allow local and remote diagnosis of system problems. • Hardware configuration Allows local and remote system configuration. • Unique asset management Unique system identifier in nonvolatile memory provides easy asset management. • RAM-based error log Records startup error messages.
1.3 Front Panel Controls and Indicators The controls and indicators on the front panel of the system unit are shown in Figure 1-1 and described in Table 1-2. The control panel display shows start-up messages during power-up.
Table 1-1 Front Panel Controls and Indicators Control or Indicator Function (1) Halt button Halts an OpenVMS or DIGITAL UNIX system, returning it to console mode control. Does not affect a Windows NT system. (2) Reset button Reinitializes the system and performs startup tests. Can be used with the Halt button to bring up the SRM console while in AlphaBIOS. (3) On/Off indicator Lights when the system is turned on. (4) On/Off button Turns system on and off.
1.4 Rear Panel Ports and Slots The ports and slots on the rear of the system unit are shown in Figure 1–3 and described in Table 1-2.
Table 1-2 Rear Panel Ports and Slots Port or Slot Used to connect....
1.5 Console Terminal The console terminal can be either a serial terminal or a graphics monitor. The power-up display prints to this terminal.
The console terminal can be a serial (character cell) terminal connected to the COM1 port or a graphics monitor connected to a VGA adapter on PCI 0. If the console terminal is connected to COM1, the entire power-up display prints. (See Section 3.2 for information about the power-up display.) If the console terminal is a VGA monitor, console power-up messages are sent to those devices but SROM and XSROM power-up messages are lost.
1.6 Options Options include storage, PCI and EISA/ISA I/O cards, and memory cards. Figure 1–4 shows storage option compartments. Figure 1–4 Storage Option Compartments CD-ROM Drive Compartment Diskette Drive Compartment StorageWorks Drives Shelf IP00195 Storage Options Storage options are located in several compartments inside the system as shown in Figure 1-4.
• • Graphics Sound Memory Options You can increase your system’s memory to 2 gigabytes by using various combinations of memory options. Adding more memory allows your system to run memory-intensive software more quickly. The system supports the following memory option sizes: 64 MB 256 MB Memory options include a 64-MB option consisting of two 32 MB DIMMs, and a 256-MB option consisting of two 128 MB DIMMs. Ordering Options The list of supported options is subject to change.
Chapter 2 Installing the System This chapter explains how to set up and install your system hardware. The following topics are discussed: • System Setup Overview • • Selecting a Location Environmental Requirements • • Power Requirements Acoustical Data • System Accessories • • • Connecting the System Connecting to Network Hardware Locking the System 2.1 System Setup Overview The following list summarizes the steps for setting up your system.
Figure 2–1 System Dimensions and Service Area 35 cm (14.1 in) 53 cm (21 in) 44 cm (17.4 in) 1m (36 in) 65 cm (26 in) MA00908 2.3 Environmental Requirements Table 2-1 Environmental Requirements Condition Specification Temperature range Room temperature: Between 10º C and 40º C (50º F and 104º F). Relative humidity Between 10% and 90% (20% to 80% with removable media options).
2.4 Power Requirements Your system ships with two power supplies. Both power supplies connect to an AC outlet. Figure 2–2 Power Supply Requirements 100-120 VAC 7.5A 50-60 Hz 220-240 VAC 3.5A 50-60 Hz IP00211 100-120 VAC 7.5A 50-60 Hz 220-240 VAC 3.5A 50-60 Hz = Properly Grounded Power Receptacle NOTE: Current ratings are maximum with a fully loaded system.
2.5 Acoustical Data Table 2-2 Acoustics - Declared Values per ISO 9296 and ISO 7779 Sound Power Level LWAd B Product Sound Pressure Level LpAm dBA (bystander positions) Idle Operate Idle Operate 54HHA-AA/B, 54KHA-AA/B, and 54ZHA-AA, and all AlphaServer 1200 systems without hard drives 5.6 5.6 37 37 All AlphaServer 1200 systems with 1xRZ1CB disk drive 5.6 5.7 37 38 [Current values for specific configurations are available from Digital Equipment Corporation representatives. 1 B = 10 dBA.
2.6 System Accessories Figure 2-3 shows the accessories that are included with the system. Table 2-2 describes the accessories. Figure 2–3 System Accessories 1 4 2 5 3 6 1 2 3 4 5 6 7 System keys (2) Installation card User’s Guide H8571-5 serial connector Mouse Power cord (2) Keyboard 7 IP00204 If you are using a keyboard, a mouse, or a printer, connect each to the appropriate connector at the rear of the system. See Figure 1-2 to verify the location of the connectors.
2.7 Connecting the System Connect the system components as shown in Figure 2–4.
2.8 Connecting to Network Hardware The system supports various network options. You can connect to ThinWire, as shown in Figure 2-5. With appropriate options, you can also connect to FDDI and token ring networks.
2.9 Locking the System Pedestal systems are protected by a key lock located on the front. Turning the key to the left locks the front door. When the front door is locked, the top cover and side panel latch cannot be accessed. Figure 2–6 System Lock and Key IP00192 Turning the key to the right unlocks the system unit and allows you access to install or remove system components. When the system unit is unlocked, push the lock to open the door. Figure 2–6 shows the system lock in the unlocked position.
Chapter 3 Operation This chapter provides basic operating instructions, including powering up the system, booting, and operating system installation. It also provides information about updating firmware.
3.1 Powering Up the System To power up the system, press the On/Off button to the On position.
Power up the system by pressing in the On/Off button (see Figure 3–1). Testing begins, and screen text similar to that in Example 3-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. See Section 3.2 for more information.
3.2 Power-Up Display The entire power-up display prints to a serial terminal (if the console environment variable is set to serial); the last several lines print to either a serial terminal or a graphics monitor. Power-up status also displays on the control panel display. Example 3–1 Power-Up Display P00>>> initialize Initializing… SROM V3.0 on cpu0 SROM V3.0 on cpu1 XSROM V5.0 on cpu1 XSROM V5.0 on cpu0 BCache testing complete on cpu1 BCache testing complete on cpu0 mem_pair0 - 256 MB 20..20..21..21..
² On power-up, the SROM code on each CPU module loads into that module’s Icache and tests the processor chip. If any test fails, power-up terminates. The primary CPU is determined for the first of three times. The primary CPU then executes a loopback test on each PCI bridge. If this test passes, the bridge LED lights. If it fails, the LED remains clear and power-up continues. The EISA system controller, PCI-to-EISA bridge, COM1 port, and control panel port are all initialized.
Example 3–1 Power-Up Display (Continued) · ¸ starting console on CPU 0 sizing memory 0 256 MB DIMM starting console on CPU 1 probing IOD1 hose 1 bus 0 slot 1 - NCR 53C810 probing IOD0 hose 0 bus 0 slot 1 - PCEB probing EISA Bridge, bus 1 bus 0 slot 2 - S3 Trio64/Trio32 bus 0 slot 3 - DECchip 21040-AA configuring I/O adapters... ncr0, hose 1, bus 0, slot 1 floppy0, hose 0, bus 1, slot 0 tulip0, hose 0, bus 0, slot 3 System temperature is 23 degrees C AlphaServer 1200 Console V5.
· ¸ ¹ º The primary CPU is determined for the last time. The primary CPU unloads PALcode and decompression code from the FEPROM on the system board to its B-cache. The primary CPU then jumps to the PALcode to start the SRM console. The primary CPU prints a message indicating that it is running the console. Starting with this message, the power-up display is printed to any console terminal, regardless of the state of the console environment variable.
3.3 Booting DIGITAL UNIX ® DIGITAL UNIX 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. Example 3–2 Booting DIGITAL UNIX from a Local Disk P00>>> show device polling ncr0 (NCR 53C810) slot 1, bus 0 PCI, hose 1 dka500.5.0.1.1 DKa500 polling ncr1 (NCR 53C810) slot 3, bus 0 PCI, hose 1 dkb100.1.0.3.1 DKb100 dkb200.2.0.3.1 DKb200 dkb400.4.0.3.
Example 3–2 Booting DIGITAL UNIX from a Local Disk (Continued) The system is ready. DIGITAL UNIX Version 4.0B ² ³ ´ µ µ The show device command displays device information, including name and type of connection to the system. See Section 4.3 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 PCI1. The name of this device, dkb400, is used as an argument to the boot command.
Example 3–3 Booting DIGITAL UNIX from a Disk on a Cluster P00>>> show boot* boot_arg0 boot_arg1 boot_dev boot_file boot_osflags boot_reset bootdef_dev booted_dev booted_file booted_osflags 0 ² dkb0.0.0.5.1 vmunix a OFF dkb0.0.0.5.1 P00>>> boot (boot dkb0.0.0.5.1 -flags a) halted CPU 1 halt code = 1 operator initiated halt PC = fffffc0000264600 Building FRU table block 0 of dkb0.0.0.5.1 is a valid boot block reading 16 blocks from dkb0.0.0.5.
² ³ ´ The show boot* command lists all environment variables that begin with the string “boot.” In this example, the bootdef_dev environment variable sets the default boot device to dkb0.0.0.5.1, and boot_osflags indicates that the system will autoboot to multiuser mode. See Section 4.18 for descriptions of these environment variables. The boot command needs no options, since the environment variables pass all necessary information.
Example 3–4 Booting DIGITAL UNIX from a Remote Disk P00>>> show network polling tulip0 (DECchip 21040-AA) slot 2, bus 0 PCI, hose 1 ewa0.0.0.2.1: 08-00-2B-E5-B4-1A polling tulip1 (DECchip 21041-AA) slot 3, bus 0 PCI, hose 1 ewb0.0.0.3.1: 00-00-F8-00-AC-B4 P00>>> boot -flags an -protocols bootp ewa0 (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.
² ³ ´ µ The show network command displays device information, including name and type of connection to the system. See Section 4.3 for a description of the show network command and the device naming convention. The operating system is on a remote disk accessed through the Ethernet controller in slot 4 of PCI1. The name of this device, ewa0, is used as an argument to the boot command. This command loads DIGITAL UNIX from ewa0, autobooting to multiuser mode. See Section 4.
3.4 Installing DIGITAL UNIX DIGITAL UNIX is installed from the CD-ROM. Refer to the documentation shipped with the CD-ROM for installation instructions. Example 3–5 Installing DIGITAL UNIX P00>>> boot dka500 (boot dka500.5.0.1.1 -flags a) Building FRU table block 0 of dka500.5.0.1.1 is a valid boot block reading 16 blocks from dka500.5.0.1.
Example 3–5 Installing DIGITAL UNIX (Continued) Alpha boot: available memory from 0x2dfe000 to 0x7fff6000 physical memory = 2048.00 megabytes. available memory = 2001.96 megabytes. using 7856 buffers containing 61.37 megabytes of memory Firmware revision: 5.0 PALcode: DIGITAL-UNIX/OSF version 1.21-19 AlphaServer 1200 pci1 at mcbus0 slot 5 psiop0 at pci1 slot 1 . . . Printer service started The system is ready. DIGITAL UNIX Version 4.
3.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. Example 3–6 Booting OpenVMS from a Local Disk ² P00>>> show device polling ncr0 (NCR 53C810) slot 1, bus 0 PCI, hose 1 SCSI Bus ID 7 dka500.5.0.1.1 DKa500 RRD46 0557 polling ncr1 (NCR 53C810) slot 2, bus 0 PCI, hose 1 SCSI Bus ID 7 dkb0.0.0.2.1 DKb0 RZ29B 0016 dkb100.1.0.2.
Example 3–6 Booting OpenVMS from a Local Disk (Continued) CPU 0 booting (boot dkb0.0.0.2.1 -flags 0) Building FRU table block 0 of dkb0.0.0.2.1 is a valid boot block reading 1002 blocks from dkb0.0.0.2.1 bootstrap code read in . . . Welcome to OpenVMS Alpha (TM) Operating System, Version V7.1x ² ³ ´ µ ¶ ¶ The show device command displays device information, including name and type of connection to the system. See Section 4.3 for a description of the show device command and the device naming convention.
Example 3–7 Booting OpenVMS from a Disk on a Cluster ² ³ P00>>> show bootdef_dev bootdef_dev dua1.8.0.4.1 P00>>> show device polling ncr0 (NCR 53C810) slot 1, bus 0 PCI, hose 1 SCSI Bus ID 7 dka500.5.0.1.1 DKa500 RRD45 1645 polling dac0 (Mylex DAC960) slot 3, bus 0 PCI, hose 1 dra0.0.0.3.1 DRA0 1 Member JBOD dra1.0.0.3.1 DRA1 1 Member JBOD dra2.0.0.3.1 DRA2 4 Member RAID 5 polling cipca0 (CIPCA) slot 4, bus 0 PCI, hose 1 cixcd_poll_comp cipca_a.4.0.4.1 dua CI Bus ID 4 dua24.2.0.4.
² ³ ´ µ ¶ The bootdef_dev environment variable specifies the default boot device. In this example, the default boot device was previously set to dua1.8.0.4.1. See Section 4.18 for commands used with environment variables. The show device command displays device information, including name and type of connection to the system. See Section 4.3 for a description of the show device command and the device naming convention. The disk dua1.8.0.4.1 is on the CI cluster that includes this system.
Example 3–8 Booting OpenVMS from a Remote Disk ² P00>>> show device polling ncr0 (NCR 53C810) slot 1, bus 0 PCI, hose 1 SCSI Bus ID 7 dka500.5.0.1.1 DKa500 RRD45 1645 polling kzpsa0 (DEC KZPSA) slot 2, bus 0 PCI, hose 1 TPwr 1 Fast 1 Bus ID 5 kzpsa0.5.0.2.1 dkb TPwr 1 Fast 1 Bus ID 5 N01 A10 polling kzpsa1 (DEC KZPSA) slot 3, bus 0 PCI, hose 1 TPwr 1 Fast 1 Bus ID 5 kzpsa1.5.0.3.1 dkc TPwr 1 Fast 1 Bus ID 5 N01 A10 polling kzpsa2 (DEC KZPSA) slot 4, bus 0 PCI, hose 1 TPwr 1 Fast 1 Bus ID 5 kzpsa2.5.0.4.
² ³ ´ 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 4.3 for a description of the show device command and the device naming convention. The boot command specifies ewa0 as the boot device. See Section 4.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.
3.6 Installing OpenVMS OpenVMS is installed from the CD-ROM. Refer to the documentation shipped with the CD-ROM for complete installation instructions. Example 3–9 Installing OpenVMS ² P00>>> boot -flags 0,0 dka500 Initializing... SROM V3.0 on cpu0 . . [The initialization display prints. See Section 3.2.] . AlphaServer 1200 Console V5.0-2, 2-APR-1997 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 3–9 Installing OpenVMS (Continued) Installing required known files... Configuring devices... **************************************************************** You can install or upgrade the OpenVMS Alpha operating system or you can install or upgrade layered products that are included on the OpenVMS Alpha operating system CD-ROM. You can also execute DCL commands and procedures to perform "standalone" tasks, such as backing up the system disk.
3.7 Booting Windows NT Microsoft Windows NT is started from the AlphaBIOS Boot screen. Figure 3–2 AlphaBIOS Boot Screen AlphaBIOS 5.32 Please select the operating system to start: Windows NT Server 4.0 Use and to move the highlight to your choice. Press Enter to choose.
Two SRM environment variables must be set properly for Windows NT to boot. The setting of the SRM os_type environment variable determines if AlphaBIOS is loaded and started on reset and power-up. If os_type is set to nt, after the power-up display the SRM console is loaded and started, and it then loads and starts the AlphaBIOS console. AlphaBIOS must be running before Windows NT can be booted. Windows NT requires a graphics monitor as its console.
3.8 Installing Windows NT Windows NT is installed from the CD-ROM. Insert the CD-ROM into the drive, start AlphaBIOS Setup, select the menu item Install Windows NT, and follow the prompts. Figure 3–3 Installing Windows NT AlphaBIOS Setup Display System Configuration... Upgrade AlphaBIOS Hard Disk Setup... CMOS Setup... Install Windows NT Utilities About AlphaBIOS... Press ENTER to install Windows NT.
Windows NT requires a partitioned and formatted hard disk drive. If your drive is not partitioned or formatted, follow the instructions in Section 3.10 before installing the Windows NT operating system. Up to four versions of Windows NT can be resident in a system at one time. If this is a new Windows NT installation, start with this procedure: 1. Start AlphaBIOS. If the system is in the SRM console, issue the command alphabios. 2.
3.9 Updating Firmware Start the Loadable Firmware Update (LFU) utility by issuing the lfu command at the SRM console prompt, booting it from the CD-ROM while in the SRM console, or selecting Update AlphaBIOS in the AlphaBIOS Setup screen. Example 3–10 Starting LFU from the SRM Console P00>>> lfu ***** Loadable Firmware Update Utility ***** Select firmware load device (cda0, dva0, ewa0), or Press to bypass loading and proceed to LFU: cda0 . . .
Use the Loadable Firmware Update (LFU) utility to update system firmware. You can start LFU from either the SRM console or the AlphaBIOS console. • From the SRM console, start LFU by issuing the lfu command (see Example 3–10). Also from the SRM console, LFU can be booted from the Alpha CD-ROM (V3.7 or later), as shown in Example 3–11. • From the AlphaBIOS console, select Update AlphaBIOS from the AlphaBIOS Setup screen (see Figure 3–4). A typical update procedure is: 1. Start LFU. 2.
3.9.1 Updating Firmware from the CD-ROM Insert the Alpha CD-ROM, start LFU, and select cda0 as the load device. Example 3–12 Updating Firmware from the CD-ROM ***** Loadable Firmware Update Utility ***** Select firmware load device (cda0, dva0, ewa0), or Press to bypass loading and proceed to LFU: cda0 ² Please enter the name of the options firmware files list, or Press to use the default filename [AS1200FW]: AS1200CP ³ Copying Copying Copying Copying AS1200CP from DKA500.5.0.1.1 .
² ³ ´ µ Select the device from which firmware will be loaded. The choices are the internal CD-ROM, the internal floppy disk, or a network device. In this example, the internal CD-ROM is selected. Select the file that has the firmware update, or press Enter to select the default file. The file options are: AS1200FW (default) SRM console, AlphaBIOS console, and I/O adapter firmware. AS1200CP SRM console and AlphaBIOS console firmware only. AS1200IO I/O adapter firmware only.
Example 3–12 Updating Firmware from the CD-ROM (Continued) UPD> update * WARNING: updates may take several minutes to complete for each device. Confirm update on: AlphaBIOS AlphaBIOS [Y/(N)] y DO NOT ABORT! Updating to V6.0-3... Verifying V6.0-3... UPD> exit 3-32 · DO NOT ABORT! Updating to V6.40-1... Verifying V6.40-1... PASSED. Confirm update on: srmflash srmflash PASSED.
¶ · ¸ The update command updates the device specified or all devices. In this example, the wildcard indicates that all devices supported by the selected update file will be updated. For each device, you are asked to confirm that you want to update the firmware. The default is no. Once the update begins, do not abort the operation. Doing so will corrupt the firmware on the module. The exit command returns you to the console from which you entered LFU (either SRM or AlphaBIOS).
3.9.2 Updating Firmware from Floppy Disk — Creating the Diskettes Create the update diskettes before starting LFU. See Section 3.9.3 for an example of the update procedure. Table 3–1 File Locations for Creating Update Diskettes on a PC Console Update Diskette I/O Update Diskette AS1200FW.TXT AS1200IO.TXT AS1200CP.TXT TCREADME.SYS TCREADME.SYS CIPCA315.SYS TCSRMROM.SYS DFPAA310.SYS TCARCROM.SYS KZPAAA11.
Example 3–13 Creating Update Diskettes on an OpenVMS System Console update diskette $ $ $ $ $ $ $ $ $ $ $ $ $ $ inquire ignore "Insert blank HD floppy in DVA0, then continue" set verify set proc/priv=all init /density=hd/index=begin dva0: tcods2cp mount dva0: tcods2cp create /directory dva0:[as1200] copy tcreadme.sys dva0:[as1200]tcreadme.sys copy as1200fw.txt dva0:[as1200]as1200fw.txt copy as1200cp.txt dva0:[as1200]as1200cp.txt copy tcsrmrom.sys dva0:[as1200]tcsrmrom.sys copy tcarcrom.
3.9.3 Updating Firmware from Floppy Disk — Performing the Update Insert an update diskette (see Section 3.9.2) into the floppy drive. Start LFU and select dva0 as the load device.
² ³ Select the device from which firmware will be loaded. The choices are the internal CD-ROM, the internal floppy disk, or a network device. In this example, the internal floppy disk is selected. Select the file that has the firmware update, or press Enter to select the default file. When the internal floppy disk is the load device, the file options are: AS1200CP (default) SRM console and AlphaBIOS console firmware only. AS1200IO I/O adapter firmware only.
Example 3–14 Updating Firmware from the Floppy Disk (Continued) µ UPD> update pfi0 WARNING: updates may take several minutes to complete for each device. Confirm update on: pfi0 [Y/(N)] y ¶ DO NOT ABORT! Updating to 3.10... Verifying to 3.10... PASSED.
µ ¶ · ¸ ¹ The update command updates the device specified or all devices. For each device, you are asked to confirm that you want to update the firmware. The default is no. Once the update begins, do not abort the operation. Doing so will corrupt the firmware on the module. The lfu command restarts the utility so that console firmware can be updated. (Another method is shown in Example 3–15, where the user specifies the file AS1200FW and is prompted to insert the second diskette.
3.9.4 Updating Firmware from a Network Device Copy files to the local MOP server’s MOP load area, start LFU, and select ewa0 as the load device.
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 CDROM, the internal floppy disk, or a network device. In this example, a network device is selected. Select the file that has the firmware update, or press Enter to select the default file.
Example 3–16 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. srmflash DO NOT ABORT! Updating to V6.0-3... Verifying V6.0-3... PASSED.
µ ¶ The update command updates the device specified or all devices. In this example, the wildcard indicates that all devices supported by the selected update file will be updated. Typically LFU requests confirmation before updating each console’s or device’s firmware. The -all option eliminates the update confirmation requests. The exit command returns you to the console from which you entered LFU (either SRM or AlphaBIOS).
3.9.5 LFU Commands The commands summarized in Table 3–2 are used to update system firmware. Table 3–2 LFU Command Summary Command Function display Shows the physical configuration of the system. exit Terminates the LFU program. help 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.
display The display command shows the physical configuration of the system. Display is equivalent to issuing the SRM console command show configuration. Because it shows the slot for each module, display can help you identify the location of a device. exit The exit command terminates the LFU program, causes system initialization and testing, and returns the system to the console from which LFU was called. help The help (or ?) command displays the LFU command list, shown below.
list The list command displays the inventory of update firmware on the CD-ROM, network, or floppy. Only the devices listed at your terminal are supported for firmware updates. The list command shows three pieces of information for each device: • Current Revision — The revision of the device’s current firmware • Filename — The name of the file used to update that firmware • Update Revision — The revision of the firmware update image readme The readme command lists release notes for the LFU program.
3.10 Hard Disk Partitioning The recommended hard disk partition on the first hard disk in your system is: partition 1 should be 6 megabytes less than the total size of the drive (this large partition holds the operating system and the application and data files) and partition 2 should be the remaining 6 megabytes (this small partition holds only the few files necessary for your computer to boot).
No Hard Disks Found When you start hard disk setup, if you receive a “No hard drives were found connected to your computer ” message, it means that AlphaBIOS could not locate a hard drive. The likely conditions that cause this error are: • Cable not connected to either the disk or controller. The cable may have worked loose from the connector on the controller or disk drive. Check the cable connections, making sure the cable connectors are fully seated. • No power to the drive.
3.10.3 How AlphaBIOS Works with System Partitions If you are installing Windows NT for the first time, AlphaBIOS will determine that a system partition has not been defined when you select Install Windows NT in the AlphaBIOS Setup screen (see Figure 3–5). When this occurs, AlphaBIOS searches for all FAT partitions on the system. If only one FAT partition exists, AlphaBIOS designates that FAT partition as the system partition and continues with the Windows NT installation.
3.11 Using the Halt Button Use the Halt button to halt the DIGITAL UNIX or OpenVMS operating system when it hangs, clear the SRM console password, or force a halt assertion, as described in Section 3.12. Using Halt to Shut Down the Operating System You can use the Halt button if the DIGITAL UNIX or OpenVMS operating system hangs. Pressing the Halt button halts the operating system back to the SRM console firmware.
3.12 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.
the interrupt is ignored. However, you can enter the RCM haltin command followed by the RCM reset command to force a halt assertion. Upon reset, the system powers up to the SRM console, but the SRM console does not load the AlphaBIOS console. Clearing a Halt Assertion Clear a halt assertion as follows: • If the halt assertion was caused by pressing the Halt button or remotely entering the RCM halt command, the console uses the halt assertion once, then clears it.
Chapter 4 SRM Console The SRM console is the command line interface that supports the DIGITAL 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. This chapter describes the SRM commands and environment variables.
4.1 Invoking the SRM Console Invoke the SRM console by shutting down the operating system or by pressing the Halt button on the control panel. In a system running the DIGITAL UNIX or OpenVMS Alpha operating system, do one of the following steps to invoke the SRM console mode: • Shut down the operating system according to the procedure described in your operating system documentation. The SRM console prompt, P00>>>, will be displayed. • Press the Halt button on the control panel.
4.2 Command Summary The SRM (Alpha System Reference Manual) console is a command line interface used when the operating system is either DIGITAL UNIX or OpenVMS. Console commands enable the user to examine and modify the system state. Table 4-1 gives the most commonly used SRM console commands. Table 4-2 gives the syntax for the console commands. Table 4-3 gives special characters you can use in console mode.
Table 4-1 Summary of SRM Console Commands (Continued) Command Function more Displays a file one screen at a time. prcache Utility that initializes and displays status of the PCI NVRAM. set envar Sets or modifies the value of an environment variable. set host Connects to a MSCP DUP server on a DSSI device. set password Sets the console password for the first time or changes an existing password. set secure Enables secure mode without requiring a restart of the console.
Table 4-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 4-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.
Table 4-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. Delete Deletes the previous character. Help By itself, displays first-level help.
Table 4-3 Special Characters for SRM Console (Continued) Character Function Ctrl/R Redisplays the current line. Deleted characters are omitted. This command is useful for hardcopy terminals. Ctrl/S Suspends output to the console terminal until Ctrl/Q is entered. Cleared by Ctrl/C. Ctrl/U Deletes the current line. * Wildcarding for commands such as show. "" Double quotes enable you to denote a string for environment variable assignment.
4.3 Displaying the System Configuration Several commands are used to display the system configuration: show config, show cpu, show device, show fru, show memory, show network, show pal, show power, and show version. Example 4-1 Show Config Command P00>>> show config Digital Equipment Corporation AlphaServer 1200 Console V5.0-2 OpenVMS PALcode V1.19-12, DIGITAL UNIX PALcode V1.
The show config command displays a list of devices found on the system bus and I/O buses. This is the configuration at the most recent initialization. The syntax is: show config Example 4-2 Show CPU Command P00>>> show cpu Primary CPU: Active CPUs: Configured CPUs: SROM Revision: 00 00 00 V3.0 01 01 V3.0 P00>>> The show cpu command displays the status of each CPU.
Example 4-3 Show Device Command P00>>> show dev polling ncr0 (NCR 53C810) slot 1, bus 0 PCI, hose 1 SCSI Bus ID 7 dka500.5.0.1.1 Dka500 RRD46 0557 polling isp0 (QLogic ISP1020) slot 0, bus 2 PCI, hose 1 SCSI Bus ID 7 dkb0.0.0.2000.1 DKb0 RZ29B 0007 polling floppy0 (FLOPPY) PCEB - XBUS hose 0 dva0.0.0.1000.0 DVA0 RX23 polling tulip0 (DECchip 21040-AA) slot 2, bus 0 PCI, hose 1 ewa0.0.0.2.1 08-00-2B-E6-4B-CC BNC polling tulip1 (DECchip 21140-AA) slot 4, bus 0 PCI, hose 0 ewb0.0.0.4.
Table 4-4 Device Naming Convention dk Category Description Driver ID Two-letter designator of port or class driver dk SCSI disk fw FDDI device dr RAID set device mk SCSI tape du DSSI disk mu DSSI tape dv Diskette drive pk SCSI port ew Ethernet port pu DSSI port a Storage adapter ID One-letter designator of storage adapter (a, b, c...). 500 Device unit number Unique number (MSCP unit number). SCSI unit numbers are forced to 100 X node ID. 5 Bus node number Bus node ID.
Example 4-4 Show FRU Command P00>>> show fru Digital Equipment Corporation AlphaServer 1200 Console V5.0-2 OpenVMS PALcode V1.19-12, Digital UNIX PALcode V1.
Example 4-5 Show Memory Command P00>>> show memory Slot ---0 1 2 3 Type ---DIMM DIMM DIMM DIMM Total P00>>> MB ---64 64 64 64 Base -------0 20000000 40000000 60000000 256 The show memory command displays information about each memory pair: slot number, type (DIMM), size of the memory pair in megabytes, and the starting address of the pair. The syntax is: show memory Example 4-6 Show Network Command P00>>> show net polling tulip0 (DECchip 21040-AA) slot 2, bus 0 PCI, hose 1 ewa0.0.0.2.
Example 4-8 Show Power Command P00>>> show power Power Supply 0 Power Supply 1 System Fans CPU Fans Temperature Status good good good good good Current ambient temperature is 23 degrees C System shutdown temperature is set to 55 degrees C The system was last reset via a system software reset 0 Environmental events are logged in nvram Do you want to view the events? (Y/) y Total Environmental Events: 5 (5 logged) 1 2 3 4 5 JUL Jul Jul Jul Jul 25 1:17 29 23:44 29 23:51 30 0:18 30 19:22 Temperature, Te
Example 4-9 Show Version Command P00>>> show version version P00>>> V5.0-2 20-OCT-1997 13:59:28 The show version command displays the version of the SRM console program that is installed on the system.
4.4 Creating a Power-Up Script The system comes with a special nonvolatile file named “nvram” that is stored in EEROM. Nvram is a user-created power-up script (set of commands) that is always invoked during the power-up sequence. Use the SRM edit command to create or alter the nvram script.
Editing the Nvram Script You can create an nvram script to include any commands you want the system to execute at power-up. You create and edit the nvram script using the SRM edit command. With edit, lines may be added, overwritten, or deleted. The syntax is: edit file file is the name of the file to be edited. The editing commands are: help Displays the brief help file. list Lists the current file prefixed with line numbers. renumber Renumbers the lines of the file in increments of 10.
4.5 Booting the Operating System The boot command is used to boot the operating system. Example 4-12 Boot Command P00>>> boot dkb0 SROM V3.0 on cpu0 SROM V3.0 on cpu1 XSROM V5.0 on cpu0 XSROM V5.0 on cpu1 BCache testing complete on cpu0 BCache testing complete on cpu1 mem_pair0 - 64 MB mem_pair1 - 64 MB mem_pair2 - 64 MB mem_pair3 - 64 MB 20..20..21..21..23.. please wait 9 seconds for T24 to complete 24..24..
(boot dkb0.0.0.4.1 -flags a) . . . setting affinity to the primary CPU jumping to bootstrap code Digital UNIX boot –Fri Nov 22 21:24:46 EST 1997 The boot command initializes the processor, loads a program image from the specified boot device, and transfers control to that image. The syntax is: 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.
4.6 Configuring the System 4.6.1 Configuring DSSI The set host command is used for system configuration when a DSSI device is in the system. Example 4-13 Set Host Command P00>>> show device kfpsa0 dud0.0.0.3.0 R2YQYA$DIA0 P00>>> set mode diag P00>>> config kfpsa* P00>>> set host -dup dud0 starting DIRECT on pud0.0.0.3.0 (R2YQYA) RF72 Copyright (C) 1997 Digital Equipment Corporation PRFMON V1.0 D 2-NOV-1995 10:30:58 DKCOPY V1.0 D 2-NOV-1995 10:30:58 DRVEXR V2.0 D 2-NOV-1995 10:30:58 DRVTST V2.
The set host command connects the console program to another DUP server on an MSCP DSSI device. You can use the DUP protocol to examine and modify parameters of a DSSI device. The syntax is: set host -dup [-task task_name] device -dup Connect to an MSCP DUP server. The DUP service may be used to examine and modify parameters of a DSSI device. -task task_name Specifies the DUP utility to invoke. If -task is not specified, a directory of utilities displays.
4.6.2 Configuring a PCI NVRAM Module The prcache command is used for system configuration when a PCI NVRAM module is in the system. The command is used only with DIGITAL UNIX systems.
4.7 Testing the System The test command runs firmware diagnostics for components of the system drawer. This command is used to test Windows NT systems as well as DIGITAL UNIX and OpenVMS systems. Example 4-15 Test Command P00>>> test Console is in diagnostic mode System test, runtime 1200 seconds Type ^C if you wish to abort testing once it has started Configuring adapters.. polling ncr0 (NCR 53C810) slot 1, bus 0 PCI, hose 1 dka500.5.0.1.
Testing SCSI disks No CD/ROM present, skipping embedded SCSI test Testing other SCSI devices (read-only)..
The test command runs console-based exercisers for devices in the system. Testing can be aborted by Ctrl/C. NOTE: If you are running the Microsoft Windows NT operating system, switch from AlphaBIOS to the SRM console in order to enter the test command. From the AlphaBIOS console, press the Reset button, wait 5 seconds, then press the Halt button. Or, select DIGITAL UNIX Console (SRM) or OpenVMS Console (SRM) from the Advanced CMOS Setup screen and reset the system.
4.8 Making the System Secure 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.
Example 4-17 Set Secure Command P00>>> set secure # In this example a password # has been set. Console is secure. Please login. P00>>> b dkb0 Console is secure - parameters are not allowed. P00>>> login Please enter the password: # Password is not echoed. P00>>> b dkb0 (boot dkb0.0.0.3.1) . . P00>>> set secure # Password has not been set. Secure not set. Please set the password. P00>>> The set secure command enables secure mode without requiring a restart of the console.
Example 4-18 Login Command P00>>> login # System is not in secure # mode. Secure not set. Please set the password. P00>>> P00>>> login Please enter the password: P00>>> # System is in secure mode. # Password is not echoed. P00>>> login Please enter the password: # System is in secure mode. # Incorrect password is # entered. Invalid password P00>>> The login command turns off the security features, enabling access to all SRM console commands during the current session.
If you have forgotten the current password, clear the password as follows: • From the Local Console Terminal 1. Enter the login command: P00>>> 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 RCM 1. Enter the login command: P00>>> login 2. At the Enter Password: prompt, enter the RCM escape sequence. 3.
Example 4-19 Clear Password Command P00>>> clear password Please enter the password: # Password is not echoed. Password successfully cleared. P00>>> P00>>> clear password Please enter the password: Console is secure P00>>> # Invalid password entered. The clear password command clears the password environment variable, setting it to zero. This command is used when you want access to all the SRM console commands, but the system is in secure mode.
4.9 Stopping and Starting CPUs The start, halt, and continue commands are used to stop and start a program on the specified CPU.
start The start command starts a program that was previously loaded on the processor specified. If none is specified, the program is started on the primary processor. The syntax is: start [&pn] [address] &pn Specifies the processor. n is 0 or 1. address The starting address of the program. halt (or stop) The halt (or stop) command stops program execution on a secondary CPU that is still running a booted program.
4.10 Updating Firmware The lfu command is used to update firmware from the SRM console prompt. Example 4-21 Lfu Command P00>>> lfu ***** Loadable Firmware Update Utility ***** Select firmware load device (cda0, dva0, ewa0), or Press to bypass loading and proceed to LFU: cda0 Please enter the name of the options firmware files list, or Press to use the default filename [AS1200FW]: AS1200CP Copying Copying Copying Copying AS1200CP from DKA500.5.0.1.1 . [as1200]TCREADME from DKA500.5.0.1.
Example 4-21 Lfu Command (Continued) WARNING: updates may take several minutes to complete for each device. Confirm update on: AlphaBIOS AlphaBIOS DO NOT ABORT! Updating to V6.40-1... Verifying V6.40-1... PASSED. Confirm update on: srmflash srmflash [Y/(N)] y [Y/(N)] y DO NOT ABORT! Updating to V6.0-3... Verifying V6.0-3... PASSED. UPD> exit The lfu command starts the Loadable Firmware Update (LFU) Utility.
4.11 Forcing a System Crash Dump The crash command forces a crash dump to the selected device on DIGITAL UNIX and OpenVMS systems. Example 4-22 Crash Command P00>>> crash CPU 0 restarting DUMP: 401408 blocks available for dumping. DUMP: 38535 required for a partial dump. DUMP: 0x805001 is the primary swap with 401407, start our last 38534 : of dump at 362873, going to end (real end is one more, for header) DUMP.prom: dev SCSI 1 3 0 4 400 0 0, block 131072 DUMP: Header to 0x805001 at 401407 (0x61fff) DUMP.
4.12 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.
set envar The set command sets or modifies the value of an environment variable. It can also be used to create a new environment variable if the name used is unique. Environ ment variables are used to pass configuration information between the console and the operating system. The setting of these variables determines how the system powers up, boots the operating system, and operates. The syntax is: set [-default] envar value -default Restores an environment variable to its default setting.
Example 4–24 Creating a User-Defined Environment Variable P00>>> edit nvram editing ‘nvram’ 0 bytes read in *10 set mopv3_boot 1 *exit 17 bytes written out to nvram P00>>> In Example 4–24 the nvram script is edited so that an environment variable called “mop3_boot” is created and set to 1 on each power-up. By default, MOP boots send four MOP V4 requests before defaulting to MOP V3. This user-created environment variable forces the SRM console to bypass MOP V4 requests.
4.13 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. Example 4-25 Deposit Command P00>>> dep -b -n 1ff pmem:0 0 # Clear first 512 bytes of # physical memory. P00>>> d -l -n 3 vmem:1234 5 # # # # P00>>> d -n 8 r0 ffffffff # Load GPRs R0 through R8 # with -1. P00>>> d -l -n 10 -s 200 pmem:0 # # # Deposit 5 into four longwords starting at virtual memory address 1234.
Example 4-26 Examine Command (Continued) grp: grp: grp: grp: grp: grp: grp: 20 28 30 38 40 48 50 ( ( ( ( ( ( ( R4) R5) R6) R7) R8) R9) R10) 0000000000005000 000000000FFFE000 00000003F8000C00 0000000053F761AE 0000010000000000 00000003F7800100 00000000000C7FFC P00>>> examine pmem:400EC # Examine physical memory. pmem: 400EC A49D0078A47D0070 deposit The deposit command stores data in the location specified.
-o Defines data size as octaword. -h Defines data size as hexword. -d Instruction decode (examine command only) -n value The number of consecutive locations to modify. -s value The address increment size. The default is the data size. space: Device name (or address space) of the device to access. address Offset within a device to which data is deposited. Can be: data dev_name A device name. fpr- name The floating-point register set; name is F0 to F31.
4.14 Reading a File The more command displays a file one screen at a time. Example 4-27 More Command P00>>> more el #Display the contents of the #SRM console’s event log one # screen at a time. P00>>> help * | more #Display the contents of online #help one screen at a time. The more command is similar to that used in the MS-DOS and UNIX operating systems. It is useful for displaying output that scrolls too quickly to be viewed.
4.15 Initializing the System The initialize command resets the system and executes the power-up tests. Example 4-28 Initialize Command P00>>> initialize Initializing. . . SROM V3.0 on cpu0 SROM V3.0 on cpu1 XSROM V5.0 on cpu1 XSROM V5.0 on cpu0 BCache testing complete on cpu1 BCache testing complete on cpu0 mem_pair0 - 64 MB 20..20..21..21..23.. please wait 9 seconds for T24 to complete 24..24..
The initialize command resets the system. Issuing this command is equivalent to pressing the Reset button. The syntax is: initialize After self-tests are executed, the system autoboots unless one of the following is true: • A halt assertion condition exists (see Section 3.12) • 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.
4.16 Finding Help The help (or man) command displays basic information about a command. Example 4-29 Help (or Man) Command P00>>> help set # or man set NAME set FUNCTION Set an option or modify the value of an environment variable. SYNOPSIS set
4.17 Switching from SRM to AlphaBIOS Console It is necessary to switch to the AlphaBIOS console to run configuration utilities. To switch from SRM to AlphaBIOS, issue the alphabios command. Example 4-30 Switching to the AlphaBIOS Console P00>>> alphabios The alphabios command loads and starts the AlphaBIOS console. This is necessary for running AlphaBIOS-based utilities (such as the RAID configuration utility).
4.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 4-6 lists the environment variables. Detailed descriptions follow.
Table 4-6 Environment Variable Summary (Continued) Environment Variable Function memory_test Specifies the extent to which memory will be tested. For DIGITAL UNIX systems only. ocp_text Overrides the default OCP display text with specified text. 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.
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. The syntax is: set auto_action value The options for value are: 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.
boot_osflags The boot_osflags environment variable passes information to the boot command. That information is dependent on the operating system to be booted. When the operating system is DIGITAL UNIX, the syntax is: set boot_osflags flags_value The options for flags_value are: 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.
Table 4-7 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.
console The console terminal can be either a graphics monitor or a serial terminal. The console environment variable specifies which is used. The syntax is: set console output_device The options for output_device are: graphics (default) The console terminal is a graphics monitor or a device connected to the VGA or TGA module. serial The console terminal is the device connected to the COM1 port.
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. The syntax is: set ew*0_mode value The options for value are: aui Device type is AUI. auto-sense Device type is sensed by the console. twisted-pair Device type is 10BaseT (twisted pair). autonegotiate DE500-BA ew*0_protocols Enables network protocols for booting and other functions.
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. Whenever you change the value of kbd_hardware_type, you must reset the system by pressing the Reset button or issuing the initialize command.
memory_test Determines the extent of memory testing on the next reset. The syntax is: set memory_test value The options for value are: full (default) Specifies that the full memory test will be run. Systems using the OpenVMS operating system must run the full memory test. partial Specifies that the first 256 MB of memory will be tested. none Specifies that memory will not be tested. (However, tests are always run on the first 32 MB.
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 Reset button or issuing the initialize command.
pci_parity Disables or enables parity checking on the PCI bus. 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 aberrant behavior is that superfluous PCI parity errors are reported by the host PCI bridge.
pk*0_host_id Sets the controller host bus node ID to a value between 0 and 7. Each SCSI bus in the system requires a controller. Buses can 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. On each bus, the default bus node ID for the controller is set to 7.
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. The syntax is: set tt_allow_login value The options for value are: 0 Disables login through the COM2 port or a graphics monitor.
Chapter 5 AlphaBIOS Console AlphaBIOS is the graphical interface that supports the Microsoft Windows NT operating system and some utility programs. This chapter explains how to perform common system management tasks with AlphaBIOS.
5.1 Starting AlphaBIOS Start AlphaBIOS Setup by pressing F2 from the Boot screen displayed at powerup or reset. Figure 5-1 Boot Screen AlphaBIOS 5.32 Please select the operating system to start: Windows NT Server 4.0 Use and to move the highlight to your choice. Press Enter to choose.
The Boot screen shown in Figure 5-1 is displayed at power-up and reset. Press F2 at this screen to enter the setup program. The AlphaBIOS Setup screen (Figure 5-2) is displayed. From this screen you can select the tasks to perform. Use the arrow keys to select the menu item you want and press Enter. (Refer to Section 5.2 for information on navigating the AlphaBIOS screens.) Figure 5-2 AlphaBIOS Setup Screen AlphaBIOS Setup Display System Configuration... Upgrade AlphaBIOS Hard Disk Setup... CMOS Setup...
5.2 Keyboard Conventions and Help AlphaBIOS uses universally accepted keys and key combinations for navigating the interface and selecting items. Figure 5-3 Typical First-Level Help Screen Help: CMOS Setup F1=Key Help F3 Change color scheme. F6 Enter Advanced CMOS Setup. F7 Set factory default CMOS settings. ESC Exit CMOS Setup and discard any changes. F10 Exit CMOS Setup and save changes, including changes from Advanced CMOS Setup.
Figure 5-4 Second-Level Help Screen AlphaBIOS Setup F1=Help Help: Action Keys TAB Move highlight forward between fields of a dialog. SHIFT+TAB Move highlight backward between fields of a dialog. Move highlight within a menu, or cycle through available field values in a dialog window. ALT+ Drop down a menu of choices from a drop-down listbox. drop-down listbox can be recognized by the symbol. HOME Move to the beginning of a text entry field. END Move to the end of a test entry field.
5.3 Displaying the System Configuration The Display System Configuration screen gives information about the system’s installed processor, memory, attached devices, and option boards. From the AlphaBIOS Setup screen select Display System Configuration, then the category for the information you need.
Display the system configuration as follows: 1. Start AlphaBIOS, select Display System Configuration, and press Enter. 2. In the Display System Configuration screen, use the arrow keys to select the configuration category you want to see.
5.3.1 System Board Configuration Figure 5-6 System Board Configuration Display System Configuration F1=Help Systemboard Configuration Hard Disk Configuration PCI Configuration EISA Configuration SCSI Configuration MC Bus Configuration Memory Configuration 1 System Type: AlphaServer 1200 5/533 2 Processor: 3 Speed: 4 Cache: 5 Memory: Digital Alpha 21164, Revision 7.1 533 MHz 4 MB 512 MB Floppy Drive A: 3.5" 1.44 MB Floppy Drive B: None Keyboard: U.S.
² ³ ´ µ ¶ · System type — The model number of the system. Processor — The model and revision of the processor chip. Revision-level information can be useful in troubleshooting problems with technical support personnel. Speed — The speed of the processor. Cache — The amount, in kilobytes, of static RAM cache memory installed. Memory — The amount, in megabytes, of main memory in the system. Firmware versions — The versions of AlphaBIOS and SRM currently running on the system.
5.3.
² ³ ´ µ ¶ · ¸ ¹ Physical disk ID — Based on the SCSI ID. The disk with the lowest SCSI ID is disk 0, the disk with the next lowest SCSI ID is disk 1, and so on. Controller — The brand and model of SCSI chip used on the SCSI controller. Controller number — Based on how many SCSI controllers of a particular type are installed in the system. The first controller of a type is always numbered 0. SCSI ID number — A unique number you assign to each SCSI device installed in the system.
5.3.
² ³ ´ µ Device name — The name and model of the device as recorded in the device’s firmware. Device type — Lists the function of the device in the system. Revision — The revision level of the device signifies the number of times it has been updated by the manufacturer. Physical slot — Lists the actual PCI slot number to which the device is attached. You can find additional detail about any of the PCI devices listed in the Advanced PCI Information screen. Follow this procedure to view this screen: 1.
Figure 5-9 Advanced PCI Information Advanced PCI Information 2 1 3 Bus Number=0, Device Number=7, Function Number=0 4 Configuration Space: Register Name Hex Offset Vendor ID Device ID Command Status Revision ID Prog. I/F Sub Class Code Class Code Cache Line Size Latency Timer Header Type BIST Base Address 0 00 02 04 06 08 09 0A 0B 0C 0D 0E 0F 10 Hex Value 8086 0482 0047 0200 05 00 00 00 00 20 00 00 00000000 ENTER=Continue PK-0741A-96 ² ³ ´ µ Bus number — The virtual PCI bus number.
5.3.
5.3.
² SCSI controller information — Describes the physical characteristics of the selected SCSI controller. This line includes: Controller — Brand and model of SCSI chip used on the SCSI controller. Controller number — Based on the number of SCSI controllers of a particular type in the system. The first controller of a type is always numbered 0. SCSI ID number — A unique number assigned to the SCSI controller. The standard scheme in numbering controllers is for controllers to be SCSI ID 7.
5.3.
5.3.
5.3.
² ³ ´ µ Device type — The physical device as it exists on the system board. MS DOS name — Shows if the device is enabled, and if it is enabled, the addressable MS-DOS name for the device. Port address — The physical memory location for data received into the device, and sent from the device, respectively. Interrupt — The interrupt request line (IRQ) used by the device to get the CPU’s attention.
5.4 Updating Firmware Insert the CD-ROM or diskette with the updated firmware and select Upgrade AlphaBIOS from the main AlphaBIOS Setup screen. Use the Loadable Firmware Update Utility (LFU) to perform the update. The LFU exit command causes a system reset. Figure 5-15 Updating Firmware AlphaBIOS Setup Display System Configuration... Upgrade AlphaBIOS Hard Disk Setup CMOS Setup... Install Windows NT Utilities About AlphaBIOS... Press ENTER to upgrade your AlphaBIOS from floppy or CD-ROM.
As new versions of Windows NT are released, it might be necessary to upgrade AlphaBIOS to the latest version. Also, as improvements are made to AlphaBIOS, you may wish to upgrade to take advantage of new features. Use this procedure to upgrade from an earlier version of AlphaBIOS: 1. Insert the diskette or CD-ROM containing the AlphaBIOS upgrade. 2. If you are not already running AlphaBIOS Setup, restart your system and press F2 when the Boot screen is displayed. 3.
5.5 Setting Up the Hard Disk You can perform either an express or a custom hard disk setup. An express setup, described in this section, creates the recommended partition arrangement on the first hard disk, but it does not map bad sectors. Custom hard disk setup is described in Sections 5.5.1 and 5.5.2.
· ¸ ¹ º Partition number — Within a single drive, partition numbers are assigned in sequential order: 1, 2, 3, and so on. The partitions populate the drive from the innermost cylinders to the outermost. If you have a large hard disk (over 800 MB) and plan to use the FAT file system, it is a good idea to break the disk into several smaller partitions because the FAT file system uses disk space more efficiently at smaller partition sizes.
5.5.1 Creating and Deleting Partitions Manually Use the Create Partition and Delete Partition options if you need to create a custom hard disk partition arrangement or otherwise manually manage your hard disk partitions.
To delete a partition 1. Start AlphaBIOS and select Hard Disk Setup. Press Enter. 3. ² in Figure 5-18). Press Delete. A dialog box is displayed (see ³). 4. Press F10 to confirm the deletion. 2.
5.5.2 Formatting a FAT Partition AlphaBIOS can format partitions with the FAT file system. Use Windows NT to format a partition using NTFS.
To format a FAT partition 1. Start AlphaBIOS and select Hard Disk Setup. Press Enter. 2. Select the partition to be formatted (see 3. Press F6. A dialog box is displayed, asking whether to perform a quick or standard format (see ). If you select Quick Format, the formatting is completed immediately, but no bad sectors are mapped. If you select Standard Format, a dialog box similar to that in Figure 5-20 is displayed while the drive is formatted, showing the progress of the formatting.
5.6 Performing Setup Tasks CMOS Setup is used to configure several system parameters. CMOS Setup has two modes: Standard CMOS Setup is used to configure basic system parameters; Advanced CMOS Setup is used for system-specific parameters and password protection. Figure 5-21 Standard CMOS Setup Screen CMOS Setup 1 Date: Time: Friday, 13:22:27 May 10 F1=Help 1997 2 Floppy Drive A: 3.5" 1.44 MB Floppy Drive B: None U.S.
² ³ ´ µ ¶ Date and time — When setting the time, use the 24-hour format. (For example, 10:00 p.m. is 22:00:00.) Floppy drive — The only drive type supported is 3.5 inch, 1.44 MB. Keyboard — The keyboard setting makes it possible to use most language keyboards. To ensure correct character mappings, the language of your keyboard, Windows NT, and the keyboard language selection in CMOS Setup should all match.
Figure 5-22 Advanced CMOS Setup Screen Advanced CMOS Setup 1 PCI Parity Checking: Disabled 2 Power-up Memory Test: Enabled 3 AlphaBIOS Password Option: 4 Console Selection: F1=Help Disabled Windows NT Console (AlphaBIOS) 5 Power-up Memory Test Windows Length: NTFull Console (AlphaBIOS) OpenVMS Console (SRM) Digital UNIX Console (SRM) Press or to select the firmware console that will be presented the next time the system is power-cycled.
² ³ ´ µ ¶ · PCI parity checking — Enables and disables settings for PCI parity checking, which ensures data integrity across the PCI bus. Because some third-party PCI options do not correctly implement PCI parity generation, the default is Disabled. Power-up memory test — Enables and disables settings for the power-up memory test. Password setup — Enables and disables settings for password setup.
5.7 Installing Windows NT Install Windows NT from CD-ROM. Up to four versions of the operating system can be resident in the system at one time. Figure 5-23 Installing Windows NT AlphaBIOS Setup Display System Configuration... Upgrade AlphaBIOS Hard Disk Setup... CMOS Setup... Install Windows NT Utilities About AlphaBIOS... Press ENTER to install Windows NT.
If Windows NT was installed at the factory, Windows NT setup will start automatically the first time the system powers up. NOTE: Steps 1 and 2 in the following procedure are necessary only when you are first setting up your system. On subsequent installations and upgrades, begin at step 3. 1. Use CMOS Setup to set the system date and time: start AlphaBIOS Setup, select CMOS Setup, and press Enter. 2.
5.8 Selecting the Version of Windows NT Up to four versions of Windows NT can reside on the system at one time. Select the version that will be started from the Operating System Selection Setup screen. Figure 5-24 Operating System Selections Operating System Selection Setup Primary Operating System Windows NT Server 4.0 Windows NT Server 5.0 Boot Name: Windows NT Server 4.0 Boot File: Disk 0, Partition 2 \os\winnt400\osloader.
NOTE: The term “operating system selection,” as it is used in this context, refers to a version of Windows NT. It does not pertain to the DIGITAL UNIX and OpenVMS operating systems. Each operating system selection is a set of information for a version of Windows NT. It describes the disk and partition containing the OSLOADER.EXE file associated with a particular operating system installation, as well as the path to the operating system itself.
5.8.1 Designating a Primary Operating System Figure 5-25 Primary Operating System AlphaBIOS 5.29 Please select the operating system to start: 1 Windows NT Server 4.0 Windows NT Server 5.0 Use and to move the highlight to your choice. Press Enter to choose. CMOS Setup Date: Time: Friday, 11:26:22 Nov 7 1997 Floppy Drive A: 3.5" 1.44 MB Floppy Drive B: None Keyboard: U.S. 101-key keyboard Auto Start: Enabled Auto Start Count: 30 Seconds 2 Operating System Selection Setup Windows NT Server 4.
Multiple versions of Windows NT can be installed at the same time. This can be very useful in a variety of circumstances for example, when testing application compatibility across different versions of Windows NT. Each time you install a separate version of Windows NT, a new operating system selection is created. Although you can start any of the installed versions of Windows NT, one of them must be the primary operating system.
5.8.2 Primary Operating System and the Auto Start Option The process of setting up your operating system selections is similar to using an editor. You can make changes to your operating system selections and then either save your changes or exit without saving. Figure 5-26 Operating System Selection Setup Operating System Selection Setup Windows NT Server 4.0 2 3 4 5 1 Primary Operating System Boot Name: Windows NT Server 4.0 Boot File: Disk 0, Partition 2 \os\winnt400\osloader.
² ³ ´ µ Primary operating system — The OS that appears first on the AlphaBIOS Boot screen. It is also the version of the OS that automatically starts if Auto Start is selected. Any of the operating system selections can be the primary operating system. Boot name — Each boot name is associated with an operating system selection. Windows NT setup automatically creates a boot name each time you install the operating system.
¶ · OS options — Lists the startup parameters passed to the operating system for an operating system selection. One example of a startup parameter is whether to start the operating system in debug mode. By default, Windows NT does not add any entries to this field. This field can be modified. Operating System Selection Setup options — You can use the options listed at the bottom of the screen to edit operating system selections.
Validate OS selection (F9 key) — Validates the fields in the currently selected OS selection. The validation routine checks that the OS loader file and OS directory fields contain valid paths and that the OSLOADER.EXE file exists in the directory specified. At the end of the validation, a dialog box is displayed describing the results of the validation. If there is an error in an OS selection, the validation routine displays a dialog box describing the component of the OS selection that is in error.
5.9 Switching from AlphaBIOS to SRM Console It is necessary to switch to the SRM console to boot DIGITAL UNIX or OpenVMS or to run firmware-based diagnostics. To switch from AlphaBIOS to the SRM console, press the Rest button on the control panel, wait 5 seconds, and press the Halt button. Alternatively, select DIGITAL UNIX (SRM) or OpenVMS (SRM) from the Advanced CMOS Setup screen and reset the system.
DIGITAL UNIX and OpenVMS are booted and firmware-based diagnostics are run from the SRM console. Follow this procedure to switch from AlphaBIOS to SRM: 1. Select CMOS Setup and press Enter. 2. In the CMOS Setup screen press F6. The Advanced CMOS Setup screen is displayed. 3. Select DIGITAL UNIX console (SRM) or OpenVMS console (SRM) and press F10. 4. The CMOS Setup screen is displayed. Press F10 to save the change. 5. Reset the system.
5.10 Running Utility Programs Maintenance programs such as RAID and EISA configuration utilities are run from the AlphaBIOS Utilities menu. Figure 5-28 Run Maintenance Program Dialog Box AlphaBIOS Setup Display System Configuration... Upgrade AlphaBIOS Hard D Run Maintenance Program CMOS S Instal Utilit 1 Program Name: swxcrmgr.exe About 2 Location: A: ENTER=Execute A: CD: Disk 0, Partition 1 Disk 0, Partition 2 Disk 1, Partition 1 PK-0747A-96 ² ³ Program name — The program to be run.
5.10.1 Running Utilities from a Graphics Monitor 1. Start AlphaBIOS Setup. If the system is in the SRM console, set the SRM console environment variable to graphics and issue the command alphabios. 2. From AlphaBIOS Setup, select Utilities, then select Run Maintenance Program from the submenu that is displayed, and press Enter. See Figure 5-29. 3. In the Run Maintenance Program dialog box (Figure 5-28), type the name of the program to be run in the Program Name field.
5.10.2 Running Utilities from a Serial Terminal Utilities are run from a serial terminal in the same way as from a graphics monitor. The menus are the same, but some keys are different. Table 5-1 AlphaBIOS Option Key Mapping AlphaBIOS Key VTxxx Key F1 Ctrl/A F2 Ctrl/B F3 Ctrl/C F4 Ctrl/D F5 Ctrl/E F6 Ctrl/F F7 Ctrl/P F8 Ctrl/R F9 Ctrl/T F10 Ctrl/U Insert Ctrl/V Delete Ctrl/W Backspace Ctrl/H Escape Ctrl/[ 1. Start AlphaBIOS Setup by issuing the command alphabios. 2.
Chapter 6 Managing the System Remotely This chapter describes how to manage the system from a remote location using the Remote Console Manager (RCM). You can use the RCM from a console terminal at a remote location. You can also use the RCM from the local console terminal.
6.1 RCM Overview The remote console manager (RCM) monitors and controls the system remotely. The control logic resides on the system board. The RCM is a separate console from the SRM and AlphaBIOS consoles. The RCM is run from a serial console terminal or terminal emulator. A command interface lets you to reset, halt, and power the system on or off, regardless of the state of the operating system or hardware. You can also use RCM to monitor system power and temperature.
6.2 First-Time Setup To set up the RCM to monitor a system remotely, connect the console terminal and modem to the ports at the back of the system, configure the modem port for dial-in, and dial in.
6.2.1 Configuring the Modem The RCM requires a Hayes-compatible modem. The controls that the RCM sends to the modem are acceptable to a wide selection of modems. After selecting the modem, connect it and configure it. Qualified Modems The modems that have been tested and qualified with this system are: • Motorola 3400 Lifestyle 28.8 • AT&T Dataport 14.4/FAX • Hayes Smartmodem Optima 288 V-34/V.FC + FAX Modem Configuration Procedure 1.
6.2.2 Dialing In and Invoking RCM To dial in to the RCM modem port, dial the modem, enter the modem password at the # prompt, and type the escape sequence. Use the hangup command to terminate the session. A sample dial-in dialog would look similar to the following: Example 6–1 Sample Remote Dial-In Dialog ² ATQ0V1E1S0=0 OK ATDT30167 CONNECT 9600 # RCM V2.0 RCM> ³ ´ Dialing In and Invoking RCM 1. Dial the number for the modem connected to the modem port. See Example 6–1 for an example.
4. To terminate the modem connection, enter the RCM hangup command. RCM> hangup If the modem connection is terminated without using the hangup command or if the line is dropped due to phone-line problems, the RCM will detect carrier loss and initiate an internal hangup command. If the modem link is idle for more than 20 minutes, the RCM initiates an auto hangup. NOTE: Auto hangup can take a minute or more, and the local terminal is locked out until the auto hangup is completed. 6.2.
6.3 RCM Commands The RCM commands given in Table 6-1 are used to control and monitor a system remotely. Table 6-1 RCM Command Summary Command Function alert_clr Clears alert flag, stopping dial-out alert cycle alert_dis Disables the dial-out alert function alert_ena Enables the dial-out alert function disable Disables remote access to the modem port enable Enables remote access to the modem port halt Halts the server. Emulates pressing the Halt button and immediately releasing it.
Command Conventions • • • • • The commands are not case sensitive. A command must be entered in full. You can delete an incorrect command with the Backspace key before you press Enter. If you type a valid RCM command, followed by extra characters, and press Enter, the RCM accepts the correct command and ignores the extra characters.
Two conditions must be met for the alert_enable command to work: • A modem dial-out string must be entered from the system console. • Remote access to the RCM modem port must be enabled with the enable command. If the alert_enable command is entered when remote access is disabled, the following message is displayed: *** error *** disable The disable command disables remote access to the RCM modem port. It also disables RCM dial-out.
The enable command can fail for the following reasons: • No modem access password was set. • The initialization string or the answer string might not be set properly. (See Section 6.7.) • The modem is not connected or is not working properly. • The modem has been disabled from the RCM switchpack. To enable the modem, reset switch 2 (MODEM OFF) on the switchpack to OFF (enabled ).
haltin The haltin command halts a managed system and forces a halt assertion. The haltin command is equivalent to pressing the Halt button on the control panel and holding it in. This command can be used at any time after system power-up to allow you to perform system management tasks. See Section 3.12 for information on halt assertion. NOTE: If you are running Windows NT, the haltin command does not affect the operating system session, but it does cause a halt assertion.
poweron The poweron command requests the RCM to power on the system. The poweron command is equivalent to pressing the On/Off button on the control panel to the on position. For the system power to come on, the following conditions must be met: • AC power must be present at the power supply inputs. • The On/Off button must be in the on position. • All system interlocks must be set correctly. The RCM exits command mode and reconnects the user’s terminal to the system console port.
The following events occur when the reset command is executed: • The system restarts and the system console firmware reinitializes. • The console exits RCM command mode and reconnects the serial terminal to the system COM1 serial port. • The power-up messages are displayed, and then the console prompt is displayed or the operating system boot messages are displayed, depending on how the startup sequence has been defined. setesc The setesc command resets the default escape sequence for invoking RCM.
The minimum password length is one character, followed by a carriage return. If only a carriage return is entered, the command fails with the message: *** ERROR - illegal password *** If you forget the password, you can enter a new password. status The status command displays the current state of the system sensors, as well as the current escape sequence and alarm information. The following is an example of the display. RCM>status Firmware Rev: V2.
Table 6-2 RCM Status Command Fields Item Description Firmware Rev: Revision of RCM firmware. Escape Sequence: Current escape sequence to invoke RCM. Remote Access: Modem remote access state. (ENABLE/DISABLE) Alerts: Alert dial-out state. (ENABLE/DISABLE) Alert Pending: Alert condition triggered. (YES/NO) Temp (C): Current system temperature in degrees Celsius. RCM Power Control: Current state of RCM system power control.
6.4 Dial-Out Alerts When you are not monitoring the system remotely, you can use the RCM dialout feature to notify you of a power failure within the system. When a dial-out alert is triggered, the RCM initializes the modem for dial-out, sends the dial-out string, hangs up the modem, and reconfigures the modem for dial-in. The modem must continue to be powered, and the phone line must remain active, for the dial-out alert feature to work.
Composing the Dial-Out String Enter the set rcm_dialout command from the SRM console to compose the dial-out string. Use the show command to verify the string. See Example 6–4. Example 6–4 Typical RCM Dial-Out Command P00>>> set rcm_dialout “ATXDT9,15085553333,,,,,,5085553332#;” P00>>> show rcm_dialout rcm_dialout ATXDT9,15085553333,,,,,,5085553332#; The dial-out string has the following requirements: • The string cannot exceed 47 characters.
Table 6-3 Elements of the Dial-Out String ATXDT AT = Attention X = Forces the modem to dial “blindly” (not look for a dial tone). Enter X if the dial-out line modifies its dial tone when used for services such as voice mail. D = Dial T = Tone (for touch-tone) , = Pause for 2 seconds 9, In the example, “9” gets an outside line. Enter the number for an outside line if your system requires it. 15085553333 Dial the paging service.
6.5 Using the RCM Switchpack The RCM operating mode is controlled by a switchpack on the system board. Use the switches to enable or disable certain RCM functions, if desired.
1 ON 2 3 4 Figure 6-3 RCM Switches (Factory Settings) PKW0950-97 Switch Name Description 1 EN RCM Enables or disables the RCM. The default is ON (RCM enabled). The OFF setting disables RCM. 2 MODEM OFF Enables or disables the modem. The default is OFF (modem enabled). 3 RPD DIS Enables or disables remote poweroff. The default is OFF (remote poweroff enabled). 4 SET DEF Sets the RCM to the factory defaults. The default is OFF (reset to defaults disabled).
Uses of the Switchpack You can use the RCM switchpack to change the RCM operating mode or disable the RCM altogether. The following are conditions when you might want to change the factory settings. • Switch 1 (EN RCM)—Set this switch to OFF (disable) if you want to reset the baud rate of the COM1 port to a value other than the system default of 9600. You must disable RCM to select a baud rate other than 9600.
Resetting the RCM to Factory Defaults You can reset the RCM to factory settings, if desired. You would need to do this if you forgot the escape sequence for the RCM. Follow the steps below. 1. Turn off the system. 2. Unplug the AC power cords. NOTE: If you do not unplug the power cords, the reset will not take effect when you power up the system. 3. Remove the system covers. See Section 7.2. 4. Locate the RCM switchpack on the system board, and set switch 4 to ON. 5.
6.6 Troubleshooting Guide Table 6-4 is a list of possible causes and suggested solutions for symptoms you might see. Table 6-4 RCM Troubleshooting Symptom Possible Cause Suggested Solution The local console terminal is not accepting input. Cables not correctly installed. Check external cable installation. Switch 1 on switchpack set to disable. Set switch 1 to ON. Modem session was not terminated with the hangup command. Wait several minutes for the local terminal to become active again.
Table 6-4 RCM Troubleshooting (continued) Symptom Possible Cause Suggested Solution RCM does not answer when the modem is called. Modem cables may be incorrectly installed. Check modem phone lines and connections. Enable remote access. RCM remote access is disabled. RCM does not have a valid modem password set. Switch setting incorrect. The local terminal is currently attached to the RCM.
Table 6-4 RCM Troubleshooting (continued) Symptom Possible Cause Suggested Solution RCM installation is complete, but system does not power up. RCM Power Control: is set to DISABLE. Invoke RCM and issue the poweron command. You reset the system to factory defaults, but the factory settings did not take effect. AC power cords were not removed before you reset switch 4 on the RCM switchpack. Refer to Section 6.5. The remote user sees a “+++” string on the screen.
6.7 Modem Dialog Details This section is intended to help you reprogram your modem if necessary. Default Initialization and Answer Strings The modem initialization and answer command strings set at the factory for the RCM are: Initialization string: AT&F0EVS0=0S12=50 Answer string ATXA NOTE: All modem commands must be terminated with a character (0x0d hex). Modifying Initialization and Answer Strings The initialization and answer strings are stored in the RCM’s NVRAM.
Initialization String Substitutions The following modems require modified initialization strings. Modem Model 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.
Chapter 7 Installing Components This chapter provides system component removal and replacement procedures. Sections include: • Preparing to Install or Remove Components • • Top Cover and Side Panel Removal and Replacement Installing a CPU Module • • Installing a Memory DIMM Pair Installing a PCI or EISA/ISA Card • Installing a Power Supply CAUTION: Be sure to follow the appropriate antistatic precautions whenever handling internal components.
7.1 Preparing to Install or Remove Components To prepare your system for installation and removal of components, you will need to assemble the required equipment, familiarize yourself with antistatic precautions, and remove the top and side panels of the system unit.
When handling internal system components, use an antistatic wrist strap to avoid damaging the components. Figure 7–1 shows how to attach the antistatic wrist strap to your wrist and to the system unit. CAUTION: Do not disconnect the power cords from the system or the power outlets. The power cord grounds the system unit, preventing damage to the components.
7.2 Top Cover and Side Panel Removal and Replacement Depending on the components involved, you may not need to remove all panels from the system unit. The top cover and left side panel must be removed to install or remove any internal component; the right side panel, to install or remove a power supply or a second SCSI controller.
Top Cover and Side Panel Removal CAUTION: Make sure the system unit On/Off button is in the "off" position before removing the system cover and panels. To remove the top cover and side panels, refer to Figure 7–2 and follow these steps: 1. 2. 3. Shut down the operating system following the instructions listed in the operating system documentation. Press the On/Off switches on all external options connected to the syst em to the off position. Press the On/Off button on the system unit to the off position.
Top Cover and Side Panel Replacement Refer to Figure 7–3 to replace the top cover and side panels of the system unit.
1. 2. 3. 4. Align the guides on the top and bottom inside of the side panel with the lip of the system unit frame. Tilt the side panel top toward the unit and lift the flange at the top of the panel over the system unit frame. Slide the panel forward into position. (Repeat steps 1 to 3 for the other panel.) Align the top cover with the top of the side panels and slide the cover gently onto the unit from the rear. CAUTION: The top cover has a tab on the underside.
7.3 Installing a CPU Module Remove the top cover and left side panel to access the system board. After you have installed the new module, verify the installation by issuing the show cpu command from the SRM console or display the system bus configuration from the AlphaBIOS console. Figure 7–4 CPU Module Slots CPU 0 CPU 1 PK-0903C-97 WARNING: CPU modules and memory modules have parts that operate at high temperatures. Wait 2 minutes after power is removed before touching any module.
NOTE: Before removing the CPU card, you must remove the memory card adjacent to it. See Section 7.4 for the memory card removal procedure. 3. 4. Unscrew the module handle that secures the outer edge of the CPU module (two retainer screws). Release the card by extending the handle clip on each end outward. 5. Holding the outer edge of the card, gently pull it out of the slot. Installation 1. Slide the CPU card into the system board slot. 2.
7.4 Installing a Memory DIMM Pair Remove the top cover and side panel to access the system board. After you have re-installed the memory card, verify the installation by issuing the show memory command from the SRM console or display the memory configuration from the AlphaBIOS console. Figure 7–6 shows the memory slots on the system board. Configuration Rules • • There are two riser cards; one DIMM of each pair is installed in the same slot on each riser card (see Figure 7–7).
Figure 7–7 Riser Card DIMM Slots 7 6 5 4 3 2 1 0 PKW0505A-97 Memory Card Removal and DIMM Installation 1. 2. Shut down the operating system and power down the system. Remove the top cover and left side panel. 3. Unscrew the module handle that secures the outer edge of the memory card (two retainer screws). See Figure 7–8. 4. Holding the outer edge of the card, gently pull it out of the slot. CAUTION: Hold the memory card in your hands while installing DIMMs.
Figure 7–8 Memory Card Installation IP00216B WARNING: CPU modules and memory modules have parts that operate at high temperatures. Wait 2 minutes after power is removed before touching any module. CAUTION: Wear an antistatic wrist strap when working on this system.
7.5 Installing a PCI or EISA/ISA Card Remove the top cover and left side panel to access the system board. After you have installed the new module, verify the installation by issuing the show config and show device commands from the SRM console or display the PCI configuration from the AlphaBIOS console. Configuration Rules • SCSI controllers (KZPxx-xx) must be installed in PCI0. • A graphics card can be installed in PCI0 slot 2.
Option Card Installation 1. 2. Shut down the operating system and power down the system. Remove the top cover and left side panel. 3. Select the I/O slot you wish to use and remove the screw that secures the slot cover to the chassis. 4. 5. Install the option card by pressing it into the connector on the system board. Secure the option card with the screw you removed from the slot cover.
7.6 Installing a Power Supply The following procedures describe how to install and remove a power supply. The procedures for installing and removing both power supplies are similar, unless otherwise noted.
Power Supply Removal 1. 2. Shut down the operating system and power down the system. Remove the top cover and right side panel. 3. Disconnect all internal and external cables from the power supply. 4. 5. Loosen the four screws that secure the power supply to the outside of the unit. Loosen the two screws that secure the internal end of the power supply to the system unit. 6. Slide the power supply toward the internal side, lift it up off its tabs, and remove it through the top of the enclosure.
Figure 7–12 Installing a Power Supply Connecting Cable Cable Connections Internal Second Power Supply Position for Second Power Supply Rear Screws Internal Screws IP00176 Installing Components 7-17
Chapter 8 Troubleshooting This chapter contains basic troubleshooting information. For more about troubleshooting, see the AlphaServer 1200 Service Manual.
8.1 System Does Not Power Up When the system does not power up, the problem may be a disconnected power cord, a loose cable, a faulty fan, or a disengaged cover interlock.
If the system does not power up • Are the power cords plugged in? • Are the cover and side panels closed and the interlock engaged? The cover interlock must be engaged to enable power-up. See Figure 8–1 for the interlock location. • Is J2 engaged? • Are the power supplies operating? • Are the system fans operating? • Are the CPU fans operating? • Is RCM functional? If yes, has a poweroff command been issued? • Are the system board LEDs on? See Figure 8–2.
8.2 Control Panel Display Indicates an Error The control panel display indicates the likely device causing the failure. Figure 8–3 Control Panel Display 1 2 3 4 P0 TE S T 1 1 CP U0 PK-0905-97 If the control panel display indicates an error Check the failing device called out in the control panel display. See Figure 8–3 and Table 8–1 for the location and meaning of the fields in the display.
Table 8–1 Control Panel Display Field ² ³ ´ µ Content Display Meaning CPU number P0–P1 CPU reporting status Status TEST Tests are executing FAIL Failure has been detected MCHK Machine check has occurred INTR Error interrupt has occurred Test number (for DIGITAL use only) Suspected device 1 CPU module 2 Memory module 3 System board 1 CPU0–1 CPU module number MEM0–7 and L, H, or * Memory pair number and low 2 module, high module, or either IOD0 Bridge to PCI bus 0 3 IOD1 Bridg
Index ? B ? command, RCM, 6-14 Baud rate, setting for COM* ports, 451 B-cache, 3-5, 3-7 boot command, SRM, 3-8, 3-9, 3-11, 3-13 to 3-17, 3-21, 3-23, 4-3, 4-18, 4-32 passing information to command, 4-50 using in secure mode, 4-27 Boot screen, AlphaBIOS, 3-24, 5-2 boot_file environment variable, SRM, 3-9, 3-11, 3-13, 3-17, 3-19, 3-21, 4-27 boot_flags environment variable, SRM, 4-27 boot_osflags environment variable, SRM, 3-9, 3-11, 3-13, 3-17, 3-19, 3-21, 4-47, 4-50 Digital UNIX, 4-50 OpenVMS, 4-50, 4-51
passing information to command, 4-50 Windows NT, 3-24 C CDROM drive location, 1-12 clear envar command, SRM, 4-3 clear password command, SRM, 4-30 clear password command, SRM, 4-3 CMOS setup screen, AlphaBIOS, 530, 5-32 COM* ports, setting baud rate, 4-51 com*_baud environment variable, SRM, 4-47, 4-51 Command syntax, SRM console, 4-5 Configuration rules, DIMMs, 7-10 I/O cards, 7-13 Configuring parameters, AlphaBIOS console, 5-30 Configuring the system Digital UNIX system, 4-20 OpenVMS system, 4-20 Console
E edit command, SRM, 4-3, 4-38 EISA configuration screen, AlphaBIOS, 5-15 enable command, RCM, 6-13 Environment variables, SRM, 4-36 auto_action, 3-7 boot_file, 3-9, 3-11, 3-13, 3-17, 3-19, 3-21, 4-27 boot_flags, 4-27 boot_osflags, 3-9, 3-11, 3-13, 317, 3-19, 3-21 boot_reset, 3-17 bootdef_dev, 3-9, 3-11, 3-13, 317, 3-19, 3-21, 4-27 console, 3-5, 3-7 displaying the value or setting, 311, 4-37 graphics, 3-5 modifying, 4-37 os_type, 3-7 password, 4-30 serial, 3-5 setting, 4-37 summary, 4-47 Equipment installat
AlphaBIOS second-level help screen, 5-5 help command, LFU, 3-44, 3-45 help command, RCM, 6-14 help command, SRM, 4-3, 4-45 I Indicators front panel, 1-6 Initialization and answer strings default, 6-31 modifying for modem, 6-31 substitutions, 6-32 initialize command, SRM, 4-3, 4-17, 4-43, 4-44 Initializing the system, 4-43 Installing Digital UNIX, 3-14, 3-15 OpenVMS, 3-22 Windows NT, 3-26 Integrated peripherals screen, AlphaBIOS, 5-20 Interlock, 8-2 Interlock switch, 7-5 IOD, 3-7 ISA options, 1-12 K kbd_ha
determining extent of testing, SRM, 4-55 enabling and disabling settings in AlphaBIOS, 5-33 Memory tests, 3-5 memory_test environment variable, SRM, 4-48, 4-55 Modem Dial-in procedure, 6-6 dialog details, 6-31 usage in RCM, 6-3 Modifying an environment variable, SRM, 4-37 more command, SRM, 4-4, 4-42 Naming conventions, SRM, 4-11 Network protocols, enabling for booting and other functions, SRM, 4-53 installing OpenVMS, 3-22 installing Windows NT, 3-26 specifying default, 4-56 Operating system selection se
pk*0_fast environment variable, SRM, 4-48, 4-57 pk*0_host_id environment variable, SRM, 4-48, 4-58 pk*0_soft_term environment variable, SRM, 4-48, 4-58 Power system does not power up, 8-2 Power requirements, 2-3 poweroff command, RCM, 6-15 poweron command, RCM, 6-15 Power-up display, 3-4 Power-up, specifying console action, SRM, 4-49 prcache command, SRM, 4-4, 4-22 Primary operating system, AlphaBIOS, 5-44 Processor enabling and disabling specific CPUs, 4-52 Program mode, 1-3 Q quit command, RCM, 6-15 R R
set password command, SRM, 4-4, 426 set secure command, SRM, 4-4, 4-27 setesc command, RCM, 6-17 setpass command, RCM, 6-18 Setting an environment variable, 4-37 Setting up the hard disk, AlphaBIOS, 5-24 Setup screen, AlphaBIOS, 5-3 show config command, SRM, 4-4, 4-8 show cpu command, SRM, 4-4, 4-9 show device command, SRM, 3-8, 39, 3-16, 3-17, 3-19, 3-21, 44, 4-10, 4-32 show envar command, SRM, 3-16, 44, 4-36, 4-37 show fru command, SRM, 4-4, 4-12 show memory command, SRM, 4-4, 4-13 show network command, S
boot_osflags, OpenVMS, 4-50 bootdef_dev, 4-47 com*_baud, 4-47, 4-51 commands for displaying the value or setting, 4-37 commands for modifying, 4-37 commands for setting, 4-37 commands for using, 4-36 console, 4-52 console, 4-47 cpu_enabled, 4-47, 4-52 displaying the value or setting, 311 ew*0_mode, 4-47, 4-53 ew*0_protocols, 4-47, 4-53 kbd_hardware_type, 4-47, 4-54 kzpsa*_host_id, 4-47, 4-54 language, 4-47, 4-54 memory_test, 4-48, 4-55 ocp_text, 4-48, 4-55 os_type, 3-25, 4-56, 5-33 pci_parity, 4-48, 4-56, 4
installing, 3-26, 5-34 selecting version, 5-42 specifying as default operating system, 4-56 starting, 5-46 starting automatically, 5-31 Version selection, Windows NT, 5-42 W Windows NT auto start, 5-46 booting, 3-24 console for, 5-1 designating primary operating system, 5-44 X XSROM, 3-5 Index-9
