Digital Equipment AlphaServer 800 Service Manual
  1. Manuals
  2. Brands
  3. Digital Equipment Manuals
  4. Server
  5. AlphaServer 800
  6. Service manual

Digital Equipment AlphaServer 800 Service Manual

Hide thumbs Also See for AlphaServer 800:
Table of Contents

Advertisement

Quick Links

Download this manual See also: User Manual
AlphaServer 800
Service Guide
Order Number:
EK–ASV80–SG. A01
This guide describes diagnostics used in troubleshooting system
failures, as well as the procedures for replacing field-replaceable
units (FRUs).
Digital Equipment Corporation
Maynard, Massachusetts

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the AlphaServer 800 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Digital Equipment AlphaServer 800

Summary of Contents for Digital Equipment AlphaServer 800

  • Page 1 AlphaServer 800 Service Guide Order Number: EK–ASV80–SG. A01 This guide describes diagnostics used in troubleshooting system failures, as well as the procedures for replacing field-replaceable units (FRUs). Digital Equipment Corporation Maynard, Massachusetts...
  • Page 2 The software, if any, described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software or equipment that is not supplied by Digital Equipment Corporation or its affiliated companies.

  • Page 3: Table Of Contents

    Contents Preface ....................ix Chapter 1 Troubleshooting Strategy Questions to Consider................1-1 Problem Categories.................. 1-2 Service Tools and Utilities..............1-10 Information Services................1-12 Chapter 2 Power-Up Diagnostics and Display Interpreting Error Beep Codes ..............2-2 Power-Up Display ................... 2-5 2.2.2 Console Event Log ................2-9 Mass Storage Problems................
  • Page 4 Chapter 3 Running System Diagnostics Command Summary ................3-2 Command Reference ................3-3 3.2.1 test....................3-3 3.2.2 sys_exer.................... 3-6 3.2.3 cat el and more el................3-8 3.2.4 crash ....................3-9 3.2.5 memexer..................3-10 3.2.6 net -s....................3-13 3.2.7 net -ic ..................... 3-14 3.2.8 kill and kill_diags ................
  • Page 5 6.7.5 Using a VGA Controller Other Than the Standard On-Board VGA................6-38 Chapter 7 FRU Removal and Replacement AlphaServer 800 FRUs ................7-1 Removal and Replacement ..............7-5 7.2.1 Accessing FRUs, Pedestal Systems ........... 7-5 7.2.2 Accessing FRUs, Rackmount Systems ..........7-8 7.2.3...
  • Page 6 Hard Disk Drive LEDs..............2-15 Floppy Drive Activity LED............. 2-16 CD-ROM Drive Activity LED ............2-17 Control Panel LEDs ................ 2-17 AlphaServer 800 Memory Layout ........... 3-12 Remote Management Console Block Diagram........4-2 System Architecture: AlphaServer 800 Systems........ 6-2 Device Name Convention ..............6-8 Motherboard Connectors..............
  • Page 7 Control Panel LEDs ................ 2-18 PCI Troubleshooting............... 2-19 EISA Troubleshooting ..............2-21 Summary of Diagnostic and Related Commands....... 3-2 Dial and Alert String Elements ............4-6 RMC Troubleshooting ..............4-19 AlphaServer 800 Fault Detection and Connection......5-2 Environment Variables Set During System Configuration....6-11...
  • Page 8 (EISA Options Only) ..............6-24 Summary of Procedure for for Configuring ISA Options....6-25 Serial Line Keyboard Commands............ 6-38 AlphaServer 800 FRUs ..............7-2 Power Cord Order Numbers (Pedestal Systems)......7-13 Power Cord Order Numbers (Rackmount Systems)......7-13 Appendix A...

  • Page 9: Preface

    Preface Intended Audience This guide describes the procedures and tests used to service AlphaServer 800 systems and is intended for use by Digital Equipment Corporation service personnel and qualified self-maintenance customers. The material is presented as follows: • Chapter 1, Troubleshooting Strategy, describes the troubleshooting strategy for AlphaServer 800 systems.
  • Page 10 Conventions The following conventions are used in this guide: Convention Meaning WARNING: A warning contains information to prevent injury. CAUTION: A caution contains information essential to avoid damage to equipment or software. NOTE: A note calls the reader’s attention to important information. In command format descriptions, brackets indicate optional elements.
  • Page 11 Related Documentation Table 1 lists the documentation kits and related documentation for AlphaServer 800 systems. Table 1 AlphaServer 800 Documentation Title Order Number AlphaServer 800 System Information Kit QZ–00XAA–GZ AlphaServer 800 User's Guide EK–ASV80–UG AlphaServer 800 Basic Installation EK–ASV80–IG AlphaServer 800 Maintenance Kit QZ–00XAB–GZ...

  • Page 13: Chapter 1 Troubleshooting Strategy

    Chapter 1 Troubleshooting Strategy This chapter describes the troubleshooting strategy for AlphaServer 800 systems. • Questions to consider before you begin troubleshooting • Diagnostics flows for each problem category • List of service tools and utilities • List of information services 1.1 Questions to Consider...

  • Page 14: Problem Categories

    1. Power problems (Table 1-1) 2. No access to console mode (Table 1-2) 3. Console-reported failures (Table 1-3) 4. Boot failures (Table 1-4) 5. Operating system-reported failures (Table 1-5) AlphaServer 800 Service Guide...

  • Page 15: Power Problems

    Table 1-1 Power Problems Symptom Action • System does not power on. Check the power source and power cord. • Check the On/Off setting on the operator control panel. Toggle the On/Off button to off, then back to the On position to clear a remote power disable.

  • Page 16: Problems Getting To Console Mode

    VGA controller is being used, refer to Section 6.7 for more information. If console is set to serial, the power-up screen is routed to the COM1 serial communication port (Section 6.7) and cannot be viewed from the VGA monitor. AlphaServer 800 Service Guide...
  • Page 17 Table 1-2 Problems Getting to Console Mode (continued) Symptom Action Try connecting a console terminal to the COM1 serial communication port (Section 6.7). Check the baud rate setting for the console terminal and the system. The system baud rate setting is 9600. When using the COM1 port, you must set the console environment variable to serial.

  • Page 18: Problems Reported By The Console

    Use the troubleshooting tables in Section 2.6 to event log indicates problems determine the problem. with EISA devices. • PCI devices are missing from Use the troubleshooting tables in Section 2.6 to the show config display. determine the problem. AlphaServer 800 Service Guide...
  • Page 19 Table 1-3 Problems Reported by the Console (continued) Symptom Action • Power-up screen or console Use the troubleshooting table in Section 2.7 to event log indicates problems determine the problem. with EISA devices. • EISA devices are missing Use the troubleshooting table in Section 2.7 to from the show config determine the problem.

  • Page 20: Boot Problems

    Systems booting from a DIGITAL UNIX server should be set to bootp; systems booting from an OpenVMS server should be set to mop (Section 6.1.4.4). Run the device tests (Chapter 3) to check that the boot device is operating. AlphaServer 800 Service Guide...

  • Page 21: Errors Reported By The Operating System

    Table 1-5 Errors Reported by the Operating System Symptom Action System is hung or has crashed. Press the Halt button and enter the crash command to provide a crash dump file for analysis. Refer to OpenVMS Alpha System Dump Analyzer Utility Manual for information on how to interpret OpenVMS crash dump files.

  • Page 22: Service Tools And Utilities

    The loopback tests are a subset of the ROM-based diagnostics. RECOMMENDED USE: Use loopback tests to isolate problems with the COM2 serial port, the parallel port, and Ethernet controllers. Refer to Chapter 3 for instructions on performing loopback tests. 1-10 AlphaServer 800 Service Guide...
  • Page 23 Firmware Console Commands Console commands are used to set and examine environment variables and device parameters, as well as to invoke ROM-based diagnostics and exercisers. For example, the show memory, show configuration, and show device commands are used to examine the configuration; the set bootdef_dev, set auto_action, and set boot_osflags commands are used to set environment variables;...

  • Page 24: Information Services

    (FRU) procedures and illustrations, is available in online format. You can download the hypertext file (AS800.HLP) or order a self-extracting .HLP on diskette (AK–R2MAA–CA) or the AlphaServer 800 Maintenance Kit (QZ–00XAB–GZ). The maintenance kit includes hardcopy service guide, diskette, and illustrated parts breakdown.
  • Page 25 AlphaServer systems. Systems are shipped with an ECU kit, which includes the ECU license. Customers who already have the ECU and license, but need the latest ECU revision (a minimum revision of 1.10 for AlphaServer 800 systems), can order a separate kit. Call 1-800-DIGITAL to order.
  • Page 26 Supported Options A list of options supported on AlphaServer 800 systems is available on the Internet: FTP address: ftp://ftp.digital.com/pub/Digital/Alpha/systems/as800/ World Wide Web address: http://www.digital.com/info/alphaserver/tech_docs/alphasrv800/ You can obtain information about hardware configurations for the AlphaServer 800 from the DIGITAL Systems and Options Catalog. The catalog can be used to order and configure systems and hardware options.

  • Page 27: Chapter 2 Power-Up Diagnostics And Display

    Chapter 2 Power-Up Diagnostics and Display This chapter provides information on how to interpret error beep codes and the power-up display on the console screen. In addition, a description of the power-up and firmware power-up diagnostics is provided as a resource to aid in troubleshooting.

  • Page 28: Interpreting Error Beep Codes

    The beep codes are the primary diagnostic tool for troubleshooting problems when console mode cannot be accessed. Refer to Table 2-1 for information on interpreting error beep codes. AlphaServer 800 Service Guide...

  • Page 29: Interpreting Error Beep Codes

    Table 2-1 Interpreting Error Beep Codes Beep Code Problem Corrective Action A single beep is emitted when Not applicable. No error. the SROM code has successfully completed. VGA monitor is not plugged in. Plug in the graphics monitor. If you do not want the graphics monitor, disable the VGA jumper (J27) on the motherboard.
  • Page 30 If replacing the TOY NVRAM chip bridge chipset (Intel 82375EB). does not solve the problem, replace the motherboard (Chapter 7). 3-3-3 Failure of the native SCSI Replace the motherboard controller (Qlogic) on the system (Chapter 7). motherboard. AlphaServer 800 Service Guide...

  • Page 31: Power-Up Display

    2.2 Power-Up Display During power-up self-tests, test status and results are displayed on the console terminal. Information similar to that in Example 2-1 is displayed on the screen. Example 2-1 Sample Power-Up Display ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5.ef.df.ee.f4. probing hose 0, PCI probing PCI-to-EISA bridge, bus 1 bus 0, slot 5 -- pka -- QLogic ISP1020 bus 0, slot...

  • Page 32: Console Power-Up Countdown Description And Frus

    Start phase 2 drivers: Non-specific/Status message Start phase 3 drivers (console Keyboard, VGA or TGA select): tt serial line class, option, or backplane TGA graphics, VGA graphics, and keyboard drivers Run power-up memory test DIMM memory AlphaServer 800 Service Guide...
  • Page 33 Table 2-2 Console Power-Up Countdown Description and FRUs (continued) Countdown Number Description Likely FRU Start phase 4 drivers: console Non-specific/Status message support drivers. Build HWRPB CPU Non-specific/Status message information Initialize environment Non-specific/Status message variables Start SCSI class driver Backplane (onboard Qlogic) Start phase 5 drivers: I/O PCI or EISA option drivers...

  • Page 34: Alphabios Boot Menu

    Please select the operating system to start: Windows NT Server 4.00 to move the highlight to your choice. Press Enter to choose. Alpha Press <F2> to enter SETUP PK-0728A-96 Refer to the AlphaServer 800 User’s Guide for information on the AlphaBIOS firmware. AlphaServer 800 Service Guide...

  • Page 35: Console Event Log

    2.2.2 Console Event Log A console event log consists of status messages received during power-up self-tests. If problems occur during power-up, standard error messages indicated by asterisks (***) may be embedded in the console event log. To display a console event log, use the more el or cat el command.

  • Page 36: Mass Storage Problems

    Table 2-4 provides troubleshooting tips for AlphaServer systems that use a RAID array subsystem. • Section 2.4 provides information on storage device LEDs. Use Table 2-3 and Table 2-4 to diagnose the likely cause of the problem. 2-10 AlphaServer 800 Service Guide...

  • Page 37: Mass Storage Problems

    Table 2-3 Mass Storage Problems Symptom Problem Corrective Action Drives are missing Drives have Correct SCSI IDs. from the show duplicate SCSI IDs. Note: Internal hard disk drives are config display. automatically assigned SCSI IDs 0, 1, 2, and 3 (from left to right for pedestal systems;...
  • Page 38 The entire SCSI bus length, from intermittently from exceeded. terminator to terminator, must not the show config exceed 6 meters for fast double- and show device ended SCSI-2, or 3 meters for fast displays. single-ended SCSI-2. 2-12 AlphaServer 800 Service Guide...
  • Page 39 Table 2-3 Mass Storage Problems (continued) Symptom Problem Corrective Action Read/write errors Terminator Check the following jumpers and in the console missing or terminator to ensure that proper event log; storage wrong termination is provided for all internal adapter port fails. terminator SCSI devices.

  • Page 40: Troubleshooting Raid Problems

    6 seconds. This is the default setting if you are using the default configuration files for the controller. If the settings are different, adjust them as needed. 2-14 AlphaServer 800 Service Guide...

  • Page 41: Storage Device Leds

    2.4 Storage Device LEDs Storage device LEDs indicate the status of the device. • Figure 2-2 shows the hard disk drive LEDs for disk drives in the system enclosure. • Figure 2-3 shows the Activity LED for the floppy drive. This LED is on when the drive is in use.

  • Page 42: Floppy Drive Activity Led

    At product introduction, this LED has no function, it may be used with future enhancements. Disk Present When lit indicates that a disk drive is installed for that position (green) in the hard disk drive backplane. Figure 2-3 Floppy Drive Activity LED Activity LED IP00081 2-16 AlphaServer 800 Service Guide...

  • Page 43: Control Panel Leds

    Figure 2-4 CD-ROM Drive Activity LED Activity LED IP00082 2.5 Control Panel LEDs Control panel LEDs (Figure 2-5) indicate the status of the system. Table 2-6 describes the LEDs. Figure 2-5 Control Panel LEDs Power Halt Reset Reset Halt Power IP00039B Power-Up Diagnostics and Display 2-17...

  • Page 44: Control Panel Leds

    NOTE: To power up or reset without executing the NVRAM script or initiating an automatic operating system boot, power up or reset with the Halt button depressed. 2-18 AlphaServer 800 Service Guide...

  • Page 45: Pci Bus Problems

    2.6 PCI Bus Problems PCI bus failures at power-up are usually indicated by the inability of the system to see the device. Table 2-7 provides steps for troubleshooting PCI bus problems. Use the table to diagnose the likely cause of the problem. NOTE: Some PCI devices do not implement PCI parity, and some have a parity- generating scheme in which parity is sometimes incorrect or is not compliant with the PCI Specification.

  • Page 46: Eisa Bus Problems

    Run the EISA Configuration Utility (ECU) when this message is displayed. Other EISA bus problems are indicated by the absence of EISA devices from the show config display. Table 2-8 provides steps for troubleshooting EISA bus problems that persist after you run the ECU. 2-20 AlphaServer 800 Service Guide...

  • Page 47: Eisa Troubleshooting

    Table 2-8 EISA Troubleshooting Step Action Confirm that the EISA module and any cabling are properly seated. Run the ECU to: • Confirm that the system has been configured with the most recently installed controller. • See what the hardware jumper and switch setting should be for each ISA controller.
  • Page 48 UNIX and OpenVMS, use ECU diskette DECpc AXP (AK-Q2CR*-CA). The CFG files supplied with the option you want to install may not work on AlphaServer 800 systems. Some CFG files call overlay files that are not required on this system or may reference inappropriate system resources, for example, BIOS addresses.

  • Page 49: Fail-Safe Loader

    2.8 Fail-Safe Loader The fail-safe loader (FSL) allows you to boot an SRM console from a diskette at power-up. This allows you to power up without running power-up diagnostics and load new SRM and FSL console firmware from the firmware diskette. NOTE: The fail-safe loader should be used only when a failure at power-up prohibits you from getting to the console program.

  • Page 50: Power-Up Sequence

    DC power is applied to the system with the DC On/Off button on the control panel. A summary of the DC power-up sequence follows: 1. When the DC On/Off button is pressed, the power supply checks for a POK_H condition. 2-24 AlphaServer 800 Service Guide...

  • Page 51: Firmware Power-Up Diagnostics

    2. 12V, 5V, 3.3V, and –12V outputs are energized and stabilized. If the outputs do not come into regulation, the power-up is aborted and the power supply enters the latching-shutdown mode. 2.10 Firmware Power-Up Diagnostics After successful completion of AC and DC power-up sequences, the processor performs diagnostics to verify system operation, loads the system console, and tests the core system (CPU, memory, and system board), including all boot path devices.

  • Page 52: Console Firmware Diagnostics

    5. Enter console mode or boot the operating system. This action is determined by the auto_action environment variable. If the os_type environment variable is set to NT, the AlphaBIOS console is loaded into memory and control is passed to the AlphaBIOS console. 2-26 AlphaServer 800 Service Guide...

  • Page 53: Chapter 3 Running System Diagnostics

    AlphaServer 800 system RBDs rely on exerciser modules to isolate errors. The exercisers run concurrently, providing maximum bus interaction between the console drivers and the target devices.

  • Page 54: Command Summary

    The tests are run in the background. net -ic Initializes the MOP counters for the specified Ethernet 3.2.7 port. net -s Displays the MOP counters for the specified Ethernet 3.2.6 port. sys_exer Exercises core system. Tests run concurrently. 3.2.2 AlphaServer 800 Service Guide...

  • Page 55: Command Reference

    Table 3-1 Summary of Diagnostic and Related Commands (continued) Command Function Section Loopback Testing sys_exer -lb Conducts loopback tests for COM2 and the parallel port 3.2.2 in addition to core system tests. test -lb Conducts loopback tests for COM2 and the parallel port 3.2.1 in addition to quick core system tests.
  • Page 56 NOTE: Because traffic on live networks is unpredictable, loopback timeouts are considered soft errors. Syntax test [-lb] Argument: [-lb] The loopback option includes console loopback tests for the COM2 serial port and the parallel port during the test sequence. AlphaServer 800 Service Guide...
  • Page 57 Examples In the following example, the tests complete successfully. NOTE: Examine the console event log after running tests. >>> test Testing the Memory Testing the DK* Disks(read only) No DU* Disks available for testing No DR* Disks available for testing No MK* Tapes available for testing No MU* Tapes available for testing Testing the DV* Floppy Disks(read only)

  • Page 58: Sys_Exer

    COM2 (9-pin loopback connector, 12-27351-01) port and parallel port (25- pin loopback connector) when the -lb argument is used. Syntax sys_exer [-lb] Argument: [-lb] The loopback option includes console loopback tests for the COM2 serial port and the parallel port during the test sequence. AlphaServer 800 Service Guide...
  • Page 59 Example >>> sys_exer Default zone extended at the expense of memzone. Use INIT before booting Exercising the Memory Exercising the DK* Disks(read only) Exercising the Floppy(read only) Testing the VGA (Alphanumeric Mode only) Exercising the EWA0 Network Exercising the EWB0 Network Type "init"...

  • Page 60: Cat El And More El

    The following example shows an abbreviated console event log with an error message that indicates the keyboard is not plugged in or is not working. >>> more el *** keyboard not plugged in... ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5.ef.df.ee.f4. probing hose 0, PCI probing PCI-to-EISA bridge, bus 1 >>> AlphaServer 800 Service Guide...

  • Page 61: Crash

    3.2.4 crash The crash command forces a crash dump to the selected device for DIGITAL UNIX and OpenVMS systems. Use this command when an error has caused the system to hang and can be halted by the Halt button or the RMC halt command. The crash command restarts the operating system and forces a crash dump to the selected device.

  • Page 62: Memexer

    --- ------------ ------------ ------ --------- ---------- 00000001 idle system 000000c7 memtest memory 0 635651584 62565154 000000cc memtest memory 0 635651584 62565154 000000d0 memtest memory 0 635651584 62565154 000000d1 memtest memory 0 635651584 62565154 >>> kill_diags >>> 3-10 AlphaServer 800 Service Guide...
  • Page 63 The following is an example with a memory compare error indicating bad DIMMs. In most cases, the failing bank and DIMM position (Figure 3-1) are specified in the error message. If the failing DIMM information is not provided, use the procedure that follows to isolate a failing DIMM.

  • Page 64: Alphaserver 800 Memory Layout

    In the example, the lowest five bits (represented by the last or rightmost character in the address) in the failing address is 8 (a11848). Therefore, the failing DIMM is DIMM 1. Figure 3-1 AlphaServer 800 Memory Layout DIMM 3 DIMM 2...

  • Page 65: Net -S

    3.2.6 net -s The net -s command displays the MOP counters for the specified Ethernet port. Syntax net -s ewa0 Example >>> net -s ewa0 Status counts: ti: 72 tps: 0 tu: 47 tjt: 0 unf: 0 ri: 70 ru: 0 rps: 0 rwt: 0 at: 0 fd: 0 lnf: 0 se: 0 tbf: 0 tto: 1 lkf: 1 ato: 1 nc: 71 oc: 0 MOP BLOCK:...

  • Page 66: Net -Ic

    Bytes: 0 Frames: 0 Multicast bytes: 0 Multicast frames: 0 RX Failures: Block check: 0 Framing error: 0 Long frame: 0 Unknown destination: 0 Data overrun: 0 No system buffer: 0 No user buffers: 0 >>> 3-14 AlphaServer 800 Service Guide...

  • Page 67: Kill And Kill_Diags

    3.2.8 kill and kill_diags The kill and kill_diags commands terminate diagnostics that are currently executing. NOTE: A serial loopback connector (12-27351-01) must be installed on the COM2 serial port for the kill_diags command to successfully terminate system tests. • The kill command terminates a specified process. •...

  • Page 68: Show_Status

    Error count (hard and soft): soft errors are not usually fatal; hard errors halt  the system or prevent completion of the diagnostics. ž Bytes successfully written by the diagnostic. Bytes successfully read by the diagnostic. Ÿ 3-16 AlphaServer 800 Service Guide...

  • Page 69: Chapter 4 Server Management Console

    Chapter 4 Server Management Console This chapter describes the function and operation of the integrated server management console. • Section 4.1 describes how the remote management console (RMC) allows you to remotely monitor and control the system. • Section 4.2 describes the first-time setup procedures for using the RMC modem port and enabling the system to call out to a remote operator.

  • Page 70: Operating The System Remotely

    Figure 4-1 Remote Management Console Block Diagram System SRM/Alpha BIOS Consoles COM1 Operating System Remote >>>set com1_baud Management UART Console RCM>set baud Microprocessor RMC Modem Port 9600 Baud Modem Modem >>> >>> RCM> RCM> Script Console (MMJ) Port IP00086 AlphaServer 800 Service Guide...
  • Page 71 You can access the RMC through either of two serial lines: the standard console terminal COM1 (MMJ) port or the RMC modem port (9-pin DIN). • To enter the RMC console remotely, dial in through a modem, enter a password, and then type a special escape sequence that invokes the RMC command mode.
  • Page 72 RMC recognizes an alert and dials the remote operator. (This assumes that dial-out alerts have been enabled using the commands enable remote, set dial, and enable alert). The watchdog timer alert also causes the RMC to reboot the system automatically, if the enable reboot command has been issued. AlphaServer 800 Service Guide...

  • Page 73: First-Time Setup

    4.2 First-Time Setup Before you can dial in remotely through the RMC modem port or enable the system to call out to a remote operator in response to system alerts, several RMC strings and parameters must be set. Use the following procedure to set up RMC strings, password and parameters;...

  • Page 74: Dial And Alert String Elements

    This also allows the RMC to automatically dial the phone number set by the dial string upon detection of an alert condition and to send the modem initialization string to the modem. 6. Using the RMC command enable alert, enable alert condition to page an external operator. AlphaServer 800 Service Guide...
  • Page 75 7. Using the RMC command send alert, force an alert condition in order to test the dial out function and verify proper setup of the modem initialization, dial, and alert strings. 8. Once the alert is received successfully, use the RMC command clear alert, to clear the current alert condition and cause the RMC to stop paging the remote operator.

  • Page 76: Resetting The Rmc To Factory Defaults

    7. Close the system side panel. 8. Plug the system line cord into the AC power line NOTE: After resetting to default settings, you should complete the first-time setup procedures to enable remote dial in and call out alerts. AlphaServer 800 Service Guide...

  • Page 77: Remote Management Console Commands

    4.4 Remote Management Console Commands The remote management console supports the following commands: clear {alert, port} disable {alert, reboot, remote} enable {alert, reboot, remote} halt {in, out} hangup help or ? power {off, on} quit reset send alert set {alert, baud, dial, escape, init, password, wdt} status Explanations and examples of the RMC command set follow.
  • Page 78 The disable remote command disables the remote access to the RMC modem port and disables the automatic dialing on alert condition detection. Example: RCM>disable remote RCM> enable alert The enable alert command enables alert conditions to page an external operator. Example: RCM> enable alert RCM> 4-10 AlphaServer 800 Service Guide...
  • Page 79 enable reboot The enable reboot command enables automatic reboot of the system when the watchdog timer expires. The watchdog timer is enabled and operated by the operating system. It periodically interrupts the server management microcontroller and assists in clearing a hung state in the operating system. If the microcontroller does not receive a watchdog timer interrupt for a specified period of time, it will reset the system.
  • Page 80 RCM>help clear {alert, port} disable {alert, reboot, remote} enable {alert, reboot, remote} halt {in, out} hangup help or ? power {off, on} quit reset send alert set {alert, baud, dial, escape, init, password, wdt} status 4-12 AlphaServer 800 Service Guide...
  • Page 81 power off The power off command is the equivalent of turning off the system power from the operator control panel. If the system is already powered off this command will have no effect. The system can be powered back on by either issuing a power on command or by toggling the power button on the system front panel.
  • Page 82 Example: RCM> set alert alert> ,,,,,,,5085551212#; RCM> “,” is used to cause a 2-second delay, which may be helpful when sending data to numeric paging services. “#;” must be used to terminate the alert string. 4-14 AlphaServer 800 Service Guide...
  • Page 83 set baud The set baud command sets the baud rate on the RMC modem port and on the COM1 to microcontroller port. Allowed values are 1, 2, and 3. Note that the microcontroller port that is connected to the 6-pin MMJ connector for the local console terminal is not affected.
  • Page 84 31 characters and may be modified depending on the type of modem used. Some typical initialization strings are: Modem Initialization String Motorola 3400 Lifestyle 28.8 at&f0e0v0x0s0=2 AT &T Dataport 14.4/FAX at&f0e0v0x0s0=2 Hayes Smartmodem Optima 288 at&fe0v0x0s0=2 V-34/V.FC + FAX 4-16 AlphaServer 800 Service Guide...
  • Page 85 Example: RCM> set init init> at&f0e0v0x0s0=2 RCM> set password The set password command allows the user to change the password that is prompted at the beginning of a modem session. The password is stored in nonvolatile memory. The maximum password length is 14 characters. The password is not echoed on the user’s terminal.
  • Page 86 Remote Access: Enabled and connected Alert Enable: Disabled Alert Pending: NO Init String: At&f0e0v0x0s0=2 Dial String: atxdt815085551212 Alert String: ,,,,,,,5085551234#; Modem and COM1 baud: 9600 Last Alert: Watchdog Timer: 60 seconds Autoreboot : ON RCM> 4-18 AlphaServer 800 Service Guide...

  • Page 87: Rmc Troubleshooting Tips

    4.5 RMC Troubleshooting Tips Table 4-2 lists a number of possible causes and suggested solutions for symptoms you might see. Table 4-2 RMC Troubleshooting Symptom Possible Cause Suggested Solution The local terminal will System, terminal, or RMC Set the baud rates for the not communicate with the baud rate set incorrectly.
  • Page 88 Cannot enable modem or The modem is not Modify the modem modem will not answer. configured correctly to initialization string work with the RMC. according to your modem documentation. 4-20 AlphaServer 800 Service Guide...

  • Page 89: Chapter 5 Error Log Analysis

    This chapter tells how to interpret error logs reported by the operating system. • Section 5.1 provides the fault detection and correcton compontents of AlphaServer 800 systems. • Section 5.2 describes machine checks/interrupts and how these errors are detected and reported.

  • Page 90: Fault Detection And Reporting

    • If error/event logging is required, control is passed through the system control block (SCB) to the appropriate exception handler. Table 5-1 AlphaServer 800 Fault Detection and Correction Component Fault Detection/Correction Capability CPU Daughter Board...

  • Page 91: Machine Checks/Interrupts

    5.2 Machine Checks/Interrupts The exceptions that result from hardware system errors are called machine checks/interrupts. They occur when a system error is detected during the processing of a data request. Four types of machine checks/interrupts are related to system events: •...
  • Page 92 Single-bit I-stream ECC error • Single-bit D-stream ECC error System-Detected Nonfatal Error (SCB: 620) These nonfatal errors are AlphaServer 800-specific correctable errors. The following conditions cause the PALcode to invoke the operating system 620 error handler: • DMA read errors •...

  • Page 93: Error Logging And Event Log Entry Format

    5.2.1 Error Logging and Event Log Entry Format The DIGITAL UNIX and OpenVMS error handlers generate several entry types. Error entries, except for correctable memory errors, are logged immediately. Entries can be of variable length based on the number of registers within the entry. Each entry consists of an operating system header, several device frames, and an end frame.

  • Page 94: Openvms Alpha Translation Using Decevent

    System faults can be isolated by examining translated system error logs or using the DECevent Analysis and Notification Utility. Refer to the DECevent Analysis and Notification Utility for DIGITAL UNIX, User and Reference Guide for more information. AlphaServer 800 Service Guide...

  • Page 95: Chapter 6 System Configuration And Setup

    Chapter 6 System Configuration and Setup This chapter provides configuration and setup information for AlphaServer 800 systems and system options. • Section 6.1 describes how to examine the system configuration using the console firmware. —Section 6.1.1 describes the function of the two firmware interfaces used with AlphaServer systems.

  • Page 96: Verifying System Configuration

    Alpha System Reference Manual (SRM). • Microsoft Windows NT is supported under the AlphaBIOS console. Refer to the AlphaServer 800 User's Guide for more information on AlphaBIOS screens and menus. The console firmware provides the data structures and callbacks available to booted programs defined in the SRM and AlphaBIOS standards.
  • Page 97 SRM Interface Systems running DIGITAL UNIX or OpenVMS access the SRM firmware through a command-line interface, a UNIX style shell that provides a set of commands and operators, as well as a scripting facility. The SRM console allows you to configure and test the system, examine and alter system state, and boot the operating system.

  • Page 98: Switching Between Interfaces

    4. When the “Power cycle the system to implement change” message is displayed, press the Reset button. Once the console firmware is loaded and device drivers are initialized, you can boot the operating system. NOTE: For information on AlphaBIOS, refer to the AlphaServer 800 User's Guide. AlphaServer 800 Service Guide...

  • Page 99: Verifying Configuration: Alphabios Menu Options For Windows Nt

    6.1.3 Verifying Configuration: AlphaBIOS Menu Options for Windows NT The following AlphaBIOS menu options are used for verifying system configuration on Windows NT systems: • Display System Configuration menu—Provides 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 requisite information.
  • Page 100 For each option that contains a PCI-to-PCI bridge, the bus number increments by 1, and the logical slot numbers start anew at 0. For more information on device names, refer to Figure 6-2. Refer to Figure 6-3 for the location of physical slots. AlphaServer 800 Service Guide...
  • Page 101 Syntax show config Example >>> show config Digital Equipment Corporation AlphaServer 800 5/400 Firmware ™ SRM Console: V4.8-29 ARC Console: v5.8 PALcode: VMS PALcode V1.19-3, OSF PALcode V1.21-5 Serial Rom: X0.4 Processor DECchip (tm) 21164A-1 400MHz System š Motherboard Revision: 0 Memory ›...

  • Page 102: Device Name Convention

    The device name convention is shown in Figure 6-2. Figure 6-2 Device Name Convention dka0.0.0.0.0 Hose Number: 0 For AlphaServer 800 Systems Logical Slot Number: For EISA options---Correspond to EISA option physical slot numbers (1 - 3) For PCI options:...
  • Page 103 Example >>> show device ™ š › œ dka100.1.0.5.0 DKA100 RZ28M-S 0021 dka200.2.0.5.0 DKA200 RZ28M-S 0526 dka400.4.0.5.0 DKA400 RRD45 1645 dkc0.0.0.2003 DKC9 RZ25 0900 dva0.0.0.1000.0 DVA0 ewa0.0.0.1001.0 EWA0 08-00-2B-3E-BC-B5 ewb0.0.0.12.0 EWB0 00-00-C0-33-E0-0D ewc0.0.0.13.0 EWC0 08-00-2B-E6-4B-F3 pka0.7.0.5.0 PKA0 SCSI Bus ID 7 2.10 pka0.7.0.2002.0 PKB0...
  • Page 104 Restores variable to its default value. -integer Creates variable as an integer. -string Creates variable as a string (default). Examples >>> set bootdef_dev dka200 >>> show bootdef_dev bootdef_dev dka200.2.0.5.0 >>> show auto_action boot >>> set boot_osflags 0,1 >>> 6-10 AlphaServer 800 Service Guide...

  • Page 105: Environment Variables Set During System Configuration

    Table 6-1 Environment Variables Set During System Configuration Variable Attributes Description auto_action NV,W The action the console should take following an error halt or power failure. Defined values are: BOOT — Attempt bootstrap. HALT — Halt, enter console I/O mode. RESTART —...
  • Page 106 Common settings are a, autoboot, and Da, autoboot and create full dumps if the system crashes. bus_probe_ Specifies a bus probe algorithm for the system. algorithm This setting is fixed and cannot be altered. 6-12 AlphaServer 800 Service Guide...
  • Page 107 Variable Attributes Description com1_baud NV,W Sets the baud rate of the COM1 (MMJ) port. The default baud rate is 9600. Baud rate values are 9600, 19200, 38400. If you change com1_baud to a setting other than 9600, you need to change the RMC baud rate to match.
  • Page 108 Enables fast SCSI devices on a SCSI controller to perform in standard or fast mode. 0—Sets the default speed for devices on the controller to standard SCSI. 6-14 AlphaServer 800 Service Guide...
  • Page 109 Variable Attributes Description pk*0_fast If a controller is set to standard SCSI mode, both (continued) standard and fast SCSI devices will perform in standard mode. 1—Sets the default speed for devices on the controller to fast SCSI mode. Devices on a controller that connect to both standard and Fast SCSI devices will automatically perform at the appropriate rate for the device, either fast or standard mode.
  • Page 110 NOTE: Whenever you use the set command to reset an environment variable, you must initialize the system to put the new setting into effect. Initialize the system by entering the init command or pressing the Reset button. 6-16 AlphaServer 800 Service Guide...

  • Page 111: Cpu, Memory, And Motherboard

    SROM code 6.2.2 Memory Modules AlphaServer 800 system architecture supports from 32 Mbytes to 2 Gbytes of memory, although at product introduction, 1 Gbyte of memory is supported. Memory options consist of four dual in-line memory modules (DIMMs) and are available in the following variations: •...

  • Page 112: Motherboard

    —EISA bus connectors (Slots 1, 2, and 3) —PCI bus connectors (32-bit: Slots 11, 12, and 13) —PCI bus connector (64-bit: Slot 14) —Memory module connectors (8 DIMM connectors) —CPU daughter board connector Figure 6-3 shows the motherboard and its connectors. 6-18 AlphaServer 800 Service Guide...

  • Page 113: Motherboard Connectors

    Figure 6-3 Motherboard Connectors RMC PIC Processor Power Supply Connectors Bank 1 Memory Module Connectors Bank 0 Daughter Board Removable Media Narrow SCSI PCI 11 Connector BIOS Chip PCI 12 Hard Disk PCI Option Wide SCSI Slots Connector PCI 13 E14 E78 PCI 14 (64-bit) Shared PCI...

  • Page 114: Eisa Bus Options

    ISA boards have one row of contacts and no more than one gap. • EISA boards have two interlocking rows of contacts with several gaps. Figure 6-4 EISA and ISA Boards EISA M A 0 0 1 1 1 6-20 AlphaServer 800 Service Guide...

  • Page 115: Eisa Configuration Utility

    Before you install an option, check that the system supports the option. The version of the ECU that ships with AlphaServer 800 systems accommodates eight EISA slots. However, AlphaServer 800 systems have only three EISA slots, slots 1, 2, and 3.

  • Page 116: Before You Run The Ecu

    “In” position. When the console prompt >>> is displayed, set the Halt button to the “Out” position. 2. Start the ECU as follows: NOTE: Make sure the ECU diskette is not write-protected. 6-22 AlphaServer 800 Service Guide...
  • Page 117 • For systems running Windows NT—Select the following menus: From the AlphaBIOS Setup menu, select Utilities. b. From submenu, select Run Maintenance Program. Insert the ECU diskette for Windows NT (AK-PYCJ*-CA) into the diskette drive and select Run ECU from floppy. •...

  • Page 118: Configuring Eisa Options

    Return to the SRM console Refer to step 4 of Section 6.6.2 for operating- (DIGITAL UNIX and system-specific instructions. OpenVMS systems only) and restart the system. 6-24 AlphaServer 800 Service Guide...

  • Page 119: Configuring Isa Options

    6.4.4 Configuring ISA Options ISA boards are configured manually, whereas EISA boards are configured through the ECU software. See Table 6-3 for a summary of steps to configure an EISA bus that contains both EISA and ISA options. Review Section 6.6.1. Then run the ECU as described in Section 6.6.2.
  • Page 120 Refer to step 4 of Section 6.6.2 for information (DIGITAL UNIX and about returning to the console. OpenVMS systems only) and turn off the system. Install ISA board and turn on Use the instructions provided with the ISA option. the system. 6-26 AlphaServer 800 Service Guide...

  • Page 121: Pci Bus Options

    6.5 PCI Bus Options PCI (Peripheral Component Interconnect) is an industry-standard expansion I/O bus that is the preferred bus for high-performance I/O options. The AlphaServer 800 provides three slots for 32-bit PCI options and one slot for 64-bit PCI options. A PCI board is shown in Figure 6-5.

  • Page 122: Configuring Internal Storage Devices

    6.6.1 Configuring Internal Storage Devices The AlphaServer 800 system supports up to seven internal SCSI storage devices. The hard disk drive backplane automatically supplies the SCSI IDs for the hard disk drives as shown in Figure 6-6. The CD-ROM drive is assigned SCSI ID 4 at the factory.
  • Page 123 When configuring the SCSI bus, note the following: • If you plan to connect the internal hard disk drives to a RAID controller option or a SCSI controller other than the onboard controller, you need to use cable PB8HA-DA. This cable provides additional length needed to reach the connector on the controller option.

  • Page 124: Raid/Scsi Cable For Internal Disk Drive Backplane

    Figure 6-7 RAID/SCSI Cable for Internal Disk Drive Backplane IP00015A 6-30 AlphaServer 800 Service Guide...

  • Page 125: Wide Scsi Cable For Breakouts At Rear Of Enclosure

    Figure 6-8 Wide SCSI Cable for Breakouts at Rear of Enclosure IP00015B System Configuration and Setup 6-31...

  • Page 126: Wide Scsi Dual Connector Cable For Standard

    Figure 6-9 Wide SCSI Dual Connector Cable for Standard Bulkhead Connector IP00049A 6-32 AlphaServer 800 Service Guide...

  • Page 127: External Scsi Expansion

    Figure 6-10 Removing Divider to Allow for Full-Height Device IP00037 6.6.2 External SCSI Expansion External SCSI devices, such as tabletop or rackmounted storage devices, can be connected to the system using EISA- or PCI-based SCSI adapters. Use the following rules to determine if a particular device can be used: •...

  • Page 128: Console Port Configurations

    (PBXGA). A serial terminal can also be configured to run the ECU or interface with the AlphaBIOS console (Section 6.7.4). When using a VGA controller other than the standard onboard VGA, refer to Section 6.7.5. 6-34 AlphaServer 800 Service Guide...

  • Page 129: Set Console

    6.7.1 set console The setting of the console environment variable determines where the system will display power-up output. Power-up information is typically displayed on the console terminal. The console terminal can be either a graphics monitor or a serial terminal. Set this environment variable according to the console terminal that you are using.

  • Page 130: Set Tt_Allow_Login

    Disables login on alternative console ports. Whenever you change the value of this environment variable, you must initialize the system with the init command. Example >>> set console serial >>> set tt_allow_login 1 >>> init 6-36 AlphaServer 800 Service Guide...

  • Page 131: Set Tga_Sync_Green

    6.7.3 set tga_sync_green The tga_sync_green environment variable sets the location of the SYNC signal generated by the ZLXp-E PCI graphics accelerator card. The correct setting, displayed with the show command, is: >>> show tga_sync_green tga_sync_green If the monitor does not synchronize, set the parameter as follows: >>>...

  • Page 132: Using A Vga Controller Other Than The Standard On-Board Vga

    The VGA jumper (J27) on the motherboard must be set to disable (off). • The console environment variable should be set to graphics. • With multiple VGA controllers, the system will direct console output to the first controller it finds. 6-38 AlphaServer 800 Service Guide...

  • Page 133: Chapter 7 Fru Removal And Replacement

    Chapter 7 FRU Removal and Replacement This chapter describes the field-replaceable unit (FRU) removal and replacement procedures for AlphaServer 800 systems, pedestal and rackmount. • Section 7.1 lists the FRUs. • Section 7.2 provides the removal and replacement procedures for the FRUs.

  • Page 134: Alphaserver 800 Frus

    Table 7-1 AlphaServer 800 FRUs Part # Description Reference Cables 17-03970-03 Floppy drive cable Figure 7-5 17-03971-04 Control panel module cable Figure 7-6 Power cord (pedestal systems) Table 7-2 Power cord (rackmount systems) Table 7-3 17-01476-02 Hard disk drive status cable, 20-pin...
  • Page 135 Table 7-1 AlphaServer 800 FRUs (continued) Part # Description Reference CPU Modules 54-24801-01 333 MHz CPU daughter board (EV5.6) Figure 7-14 54-24801-02 400 MHz CPU daughter board (EV5.6) Figure 7-14 12-23609-24 Fan, 4.75-inch with 3-pin cable Figure 7-16 Fixed-Disks RZ28M-S 2.1 GB SCA2 disk drive...
  • Page 136 Table 7-1 AlphaServer 800 FRUs (continued) Part # Description Reference Memory Modules (continued) 20-47170-D7 Alternate for 54-24352-DA Section 7.2.8 20-47083-D7 Alternate for 54-24329-DA Section 7.2.8 20-47167-D7 Alternate for 54-24344-DA Section 7.2.8 20-47137-D7 Alternate for 54-24823-DA Section 7.2.8 NOTE: Alternate and standard DIMM options cannot be mixed. Determine DIMM type before ordering.

  • Page 137: Removal And Replacement

    7.2 Removal and Replacement This section describes the procedures for removing and replacing FRUs. CAUTION: Static electricity can damage integrated circuits. Always use a grounded wrist strap (29-26246) and grounded work surface when working with internal parts of a computer system. Unless otherwise specified, you can install a FRU by reversing the steps shown in the removal procedure.

  • Page 138: Opening Front Door, Pedestal Systems

    Figure 7-1 Opening Front Door, Pedestal Systems IP00046A AlphaServer 800 Service Guide...

  • Page 139: Removing Top Cover And Side Panels, Pedestal Systems

    Figure 7-2 Removing Top Cover and Side Panels (Pedestal Systems) IP00006F FRU Removal and Replacement...

  • Page 140: Accessing Frus, Rackmount Systems

    6. Slide the enclosure out on its rails. 7. Remove the retaining screw indicated by the yellow label on the upper left side of the front of the system. 8. Slide back and remove the top cover. AlphaServer 800 Service Guide...

  • Page 141: Accessing Frus, Rackmount Systems

    Figure 7-3 Accessing FRUs, Rackmount Systems IP00065D FRU Removal and Replacement...

  • Page 142: Frus, Pedestal And Rackmount Enclosure

    Control Panel Cable Control Panel DIMM Memory Hard Disk Drive Disk Status Module Daughter Board Disk Status Cable Speaker SCSI Disk Cable Motherboard NVRAM Chip (E14) SCSI Removable NVRAM Toy Clock Chip (E78) Media Cable IP00010F 7-10 AlphaServer 800 Service Guide...

  • Page 143: Cables

    7.2.3 Cables This section shows the routing for each cable in the system. Figure 7-5 Floppy Drive Cable (34-Pin) IP00014 Figure 7-6 Control Panel Module Cable IP00013 FRU Removal and Replacement 7-11...

  • Page 144: Power Cords

    Figure 7-7 Power Cords 115V 230V 220-240 100-120 100-120 220-240 100-120VAC 7.0A 50/60 Hz 220-240VAC 3.0A 50/60 HZ IP00092A 7-12 AlphaServer 800 Service Guide...

  • Page 145: Power Cord Order Numbers (Pedestal Systems)

    Table 7-2 lists the country-specific power cords for pedestal systems. Table 7-3 lists the country-specific power cords for rackmount systems. Table 7-2 Power Cord Order Numbers (Pedestal Systems) Country Power Cord BN Number DIGITAL Number U.S., Japan, Canada BN09-1K 17-00083-09 Australia, New Zealand BN019H-2E 17-00198-14...

  • Page 146: Hard Disk Drive Status Cable (20-Pin)

    Figure 7-8 Hard Disk Drive Status Cable (20-Pin) IP00019 7-14 AlphaServer 800 Service Guide...

  • Page 147: Scsi (Embedded 16-Bit) Disk Drive Cable (68-Pin)

    Figure 7-9 SCSI (Embedded 16-Bit) Disk Drive Cable (68-Pin) IP00015 FRU Removal and Replacement 7-15...

  • Page 148: Scsi (Embedded 8-Bit) Removable Media Cable (50-Pin)

    Figure 7-10 SCSI (Embedded 8-Bit) Removable-Media Cable (50-Pin) IP00016 7-16 AlphaServer 800 Service Guide...

  • Page 149: Scsi (16-Bit) Raid Option To Disk Drive Backplane (68-Pin)

    Figure 7-11 SCSI (16-Bit)/RAID Option to Disk Drive Backplane (68-Pin) IP00015A FRU Removal and Replacement 7-17...

  • Page 150: Wide Scsi Cable For Breakouts At Rear Of Enclosure

    Figure 7-12 Wide SCSI Cable for Breakouts at Rear of Enclosure IP00015B 7-18 AlphaServer 800 Service Guide...

  • Page 151: Wide Scsi Dual Connector Cable For Standard Pci/Eisa

    Figure 7-13 Wide SCSI Dual Connector Cable for Standard PCI/EISA Bulkhead Connector IP00049A FRU Removal and Replacement 7-19...

  • Page 152: Cpu Daughter Board

    When installing the CPU daughter board, be sure to insert it straight and square, so as not to damage the connector pins. Once the levers are in place and screwed closed, press in on the front of the module to ensure that it is properly seated. 7-20 AlphaServer 800 Service Guide...

  • Page 153: Control Panel Module

    7.2.5 Control Panel Module Disconnect the control panel cable and remove the control panel module. Figure 7-15 Removing the Control Panel Module IP00035 FRU Removal and Replacement 7-21...

  • Page 154: Fan

    7.2.6 Fan Figure 7-16 Removing Fan AIRFLOW IP00031 7-22 AlphaServer 800 Service Guide...

  • Page 155: Hard Disk Drives

    7.2.7 Hard Disk Drives NOTE: If the drives are plugged into a RAID controller, you can “hot swap” drives; that is, you can add or replace drives without first shutting down the operating system or powering down the server hardware. For more information, see the StorageWorks RAID Array Subsystem Family Installation and Configuration Guide.

  • Page 156: Memory Modules

    WARNING: CPU and memory modules have parts that operate at high temperatures. Wait 2 minutes after power is removed before handling these modules. CAUTION: Do not use any metallic tools or implements including pencils to release DIMM latches. Static discharge can damage the DIMMs. 7-24 AlphaServer 800 Service Guide...

  • Page 157: Removing Dimms From Motherboard

    Figure 7-19 Removing DIMMs from Motherboard IP00100 Figure 7-10 Installing DIMMs on Motherboard IP00100A NOTE: When installing DIMMs, make sure that the DIMMs are fully seated. The two latches on each DIMM connector should lock around the edges of the DIMMs. FRU Removal and Replacement 7-25...

  • Page 158: Disk Status Module

    7.2.9 Disk Status Module Figure 7-21 Removing Disk Status Module IP00038 7-26 AlphaServer 800 Service Guide...

  • Page 159: System Motherboard

    7.2.10 System Motherboard STEP 1: RECORD THE POSITION OF EISA AND PCI OPTIONS. STEP 2: REMOVE EISA AND PCI OPTIONS. STEP 3: REMOVE THE CPU DAUGHTER BOARD. Figure 7-22 Removing EISA and PCI Options IP00049 FRU Removal and Replacement 7-27...

  • Page 160: Removing Cpu Daughter Board

    Once the levers are in place and screwed closed, press in on the front of the module to ensure that it is properly seated. STEP 4: REMOVE AIRFLOW BAFFLE FROM THE MOTHERBOARD. STEP 5: DETACH MOTHERBOARD CABLES, REMOVE SCREWS, AND MOTHERBOARD. 7-28 AlphaServer 800 Service Guide...

  • Page 161: Removing Air Flow Baffle And Motherboard

    Figure 7-24 Removing Airflow Baffle and Motherboard (12X) IP00034A STEP 6: MOVE THE NVRAM CHIP (E14) AND NVRAM TOY CHIP (E78) TO THE NEW MOTHERBOARD. FRU Removal and Replacement 7-29...

  • Page 162: Nvram Chip (E14) And Nvram Toy Clock Chip (E78)

    7.2.11 NVRAM Chip (E14) and NVRAM TOY Clock Chip (E78) See Figure 7-24 for the motherboard layout. NOTE: The NVRAM TOY chip contains the os_type environment variable. This environment variable may need to be reset (Section 6.1.4.4). 7-30 AlphaServer 800 Service Guide...

  • Page 163: Pci/Eisa Options

    7.2.12 PCI/EISA Options STEP 1: RECORD THE POSITION OF FAILING EISA OR PCI OPTION. STEP 2: REMOVE FAILING OPTION. Figure 7-26 Removing PCI or EISA Option IP00049 FRU Removal and Replacement 7-31...

  • Page 164: Scsi Disk Drive Backplane

    7.2.13 SCSI Disk Drive Backplane STEP 1: REMOVE HARD DISK DRIVES. Figure 7-27 Removing Hard Disk Drives IP00040A STEP 2: DISCONNECT DISK POWER, DISK STATUS, AND SCSI DATA CABLES FROM THE DISK DRIVE BACKPLANE AND REMOVE BACKPLANE. 7-32 AlphaServer 800 Service Guide...

  • Page 165: Removing Disk Drive Backplane

    Figure 7-28 Removing Disk Drive Backplane Disk Power SCSI Data Disk Status (6X) IP00033A FRU Removal and Replacement 7-33...

  • Page 166: Power Supply

    STEP 1: DISCONNECT POWER SUPPLY CABLES AND REMOVE POWER SUPPLY. Figure 7-29 Removing Power Supply 115V 230V IP00012A WARNING: Hazardous voltages are contained within the power supply. Do not attempt to service. Return to factory for service. 7-34 AlphaServer 800 Service Guide...
  • Page 167 STEP 2: SET VOLTAGE SELECT SWITCH ON REPLACEMENT POWER SUPPLY AND INSTALL POWER SUPPLY. CAUTION: Incorrectly setting the voltage select switch can destroy the power supply. FRU Removal and Replacement 7-35...

  • Page 168: Speaker

    7.2.15 Speaker Figure 7-30 Removing Speaker and Its Cable IP00036 7-36 AlphaServer 800 Service Guide...

  • Page 169: Removable Media

    7.2.16 Removable Media Figure 7-31 Removing the Floppy Drive IP00042 FRU Removal and Replacement 7-37...

  • Page 170: Removing The Cd-Rom Drive

    Figure 7-32 Removing the CD-ROM Drive IP00041 NOTE: When removing a 5.25-inch device from the upper two 5.25-inch storage slots, you must first remove the diskette drive in order to access the screws that retain the 5.25-inch device. 7-38 AlphaServer 800 Service Guide...

  • Page 171: Default Jumper Settings

    Appendix A Default Jumper Settings This appendix provides the location and default setting for all jumpers in AlphaServer 800 systems. • Section A-1 provides location and default settings for jumpers on the motherboard. • Section A-2 provides the location and supported settings for the J3 jumper on the CPU daughter board.

  • Page 172: Motherboard Jumpers (Default Settings

    A.1 Motherboard Jumpers Figure A-1 shows the location and default settings for jumpers on the motherboard. Figure A-1 Motherboard Jumpers (Default Settings) 1 2 3 1 2 3 IP00071B A-2 AlphaServer 800 Service Guide...
  • Page 173 Figure A-1.) disabled. A.2 CPU Daughter Board (J3) Supported Settings Figure A-2 shows the supported AlphaServer 800 5/400 settings for the J3 jumper on the CPU daughter board. This jumper affects the clock speed and other critical system settings. Default Jumper Settings A-3...

  • Page 174: A-2 Alphaserver 8005/400 And 5/333 Cpu Daughter Board (Jumper J3)

    Figure A-2 AlphaServer 800 5/400 and 5/333 CPU Daughter Board (Jumper J3) 400 MHz 0 1 2 3 4 333 MHz 0 1 2 3 4 5 6 7 0 1 2 3 4 IP00070D A.3 CPU Daughter Board (J1 Jumper) Figure A-3 shows the system default setting for the J1 jumper on the CPU daughter board.

  • Page 175: Jumper J1 On The Cpu Daughter Board

    Figure A-3 Jumper J1 on the CPU Daughter Board 0 1 2 3 4 5 6 7 IP00070C Bank Jumper Setting Function Standard boot setting Power up with backup cache disabled: Allows the system to run despite bad B-cache until a replacement CPU board is available. Power up to the fail-safe loader with backup cache disabled.

  • Page 176: A-4 Scsi Hard Disk Backplane Jumper Settings (J5)

    Figure A-4 shows the supported setting for the J5 jumper on the SCSI hard disk backplane. Figure A-4 SCSI Hard Disk Backplane Jumper Setting (J5) Storage Backplane (Rear) Storage Jumpers Backplane (Front) Storage Shelf IP00073 A-6 AlphaServer 800 Service Guide...

  • Page 177: Connector Pin Layout

    Appendix B Connector Pin Layout This appendix provides the pin layout for AlphaServer 800 internal and external connectors. • Section B-1 provides the layout for internal connectors. • Section B-2 provides the layout for external connectors.

  • Page 178: Internal Connectors

    B.1 Internal Connectors OCP Connector SYS_DC_OK HALT RESET POWER_SWITCH 10 = FAN Connector TACH FROM FAN TO FAN CIRCUIT FILTERED_PLUS12V...

  • Page 179: External Connectors

    B.2 External Connectors COM1 (MMJ) Connector ~TXD CHAS GND ~RXRTN ~RXD 6 = DSR Remote Management Modem Connector ~DCD ~DSR ~RTS ~CTS ~DTR CHAS GND COM2 Connector ~DCD ~DSR ~RTS SOUT ~CTS ~DTR CHAS GND Mouse and Keyboard Connectors DATA CHAS 6 = NC...
  • Page 180 Parallel Port Connector ~STRB 14 = ~AUTOFD DAT0 15 = ~ERROR DAT1 16 = ~INIT DAT2 17 = ~SLCTIN DAT3 18 = CHAS DAT4 19 = CHAS DAT5 20 = CHAS DAT6 21 = CHAS DAT7 22 = CHAS 10 = ~ACK 23 = CHAS...
  • Page 181 Index cat el, 3-8 crash, 3-9 AC power-up sequence, 2-24 diagnostic and related, AlphaBIOS interface, 6-3 summarized, 3-2 switching to SRM from, 6-4 kill, 3-15 alphabios command, 6-4 kill_diags, 3-15 memexer, 3-10 more el, 3-8 Beep codes, 2-2 net -ic, 3-14 Boot diagnostic flow, 1-8 net -s, 3-13 boot problems, 1-8...
  • Page 182 problems at power-up, 2-20 troubleshooting, 2-20 DC power-up sequence, 2-24 troubleshooting tips, 2-22 DEC VET, 1-11 Environment variables DECevent, 1-10 configuring, 6-10 Device naming convention setting and examining, 6-10 SRM, 6-8 Environment variables set during dia command, 5-6 systems configuration, 6-10 DIAGNOSE command, 5-6 Diagnostic flows Error...
  • Page 183 memexer command, 3-10 Memory layout, 3-12 Hard disk drives, 2-15 Memory module internal, 6-28 configuration, 6-17 displaying information for, 6-9 Memory, main I/O bus, EISA features, 6-20 exercising, 3-10 Information resources, 1-12 isolating failing DIMM, 3-11 Interfaces Modem initialization strings, 4-5 switching between, 6-4 Modules Internet files...
  • Page 184 power-up display, interpreting, 2- RAID System diagnostics, 3-1 diagnostic flow, 2-14 System machine check, 5-4 problems, 2-14 System power-up display, 2-5 Remote console monitor. See RMC System-detected nonfatal error, 5-4 Removable media, storage problems, 2-10 RMC, 4-2 accessing, 4-3 test command, 3-3 alert string, 4-6 Testing console commands, 4-9...
  • Page 185 with ROM-based diagnostics, 1- PCI problems, 2-19 storage LEDs, 2-15 Troubleshooting Troubleshooting strategy control panel LEDs, 2-17 categories of system problems, 1- EISA problems, 2-20 mass storage, 2-10 questions before you begin, 1-1 Index-5...

Table of Contents