Copyright: Copyright ® Digital Equipment Corp. 1997
Citation: Copyright ® Digital Equipment Corp. 1997


Troubleshooting Menu


Troubleshooting
Overview

Troubleshooting Overview

Before troubleshooting any system problem, first check the site maintenance log for the system's service history.  Be sure to ask the system manager the following questions:

1.	Has the system been used and did it work correctly?

2.	Have changes to hardware or updates to firmware or software been made to the system recently?  If so, are the revision numbers compatible for the system? (Refer to the hardware and operating system release notes).

3.	What is the state of the system -- is the operating system running?

If the operating system is down and you are not able to bring it up, use the diagnostic beep codes and console environment diagnostic tools, such as the power-up display on the VGA terminal and ROM-based diagnostics (RBDs).

If the operating system is running, use the operating system environment diagnostic tools, such as the DECevent management utility (to translate and interpret error logs), crash dumps, and exercisers (DEC VET).

System problems can be classified into the categories listed on the troubleshooting menu.  Using these categories, you can quickly determine a starting point for diagnosis and eliminate the unlikely sources of the problem.

AlphaServer 800 system architecture


System Architecture

AlphaServer 800 System Architecture


Power Problems

Troubleshooting
Power Problems

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.
	Check the indicator lights on the control panel.  If the green Power OK light is off and amber Halt/Remote Power Off light is on, the system may be powered off by one of the following:
	-- a remote management console command
	-- system software
	-- fan failure
	-- overtemperature condition
	-- power supply failure
	-- power select switch on power supply is set to 120V for a 220V power source
	Check that the ambient room temperature is within environmental specifications (10-40ºC, 50-104ºF).
	Check that internal power supply cables are plugged in at both the system motherboard.
Power supply shuts down after a few seconds (fan failure).	Listen to hear if the fan is spinning at power-up.  A failure of the fan causes the system to shut down after a few seconds.   Enter the remote management console (RMC) and query system status/alerts (using the status command) for an indication of fan failure or overtemperature condition.
More information on power-up


Power Supply Cable Connections


Problems Getting to Console Mode

Troubleshooting
No Access to Console Mode

Problems Getting to Console Mode

Symptom	Action
Power-up screen is not displayed.	Interpret the error beep codes at power up for a failure detected during self-tests. Check that keyboard and monitor are properly connected and powered on.   If the power-up screen is not displayed, yet the system enters console mode when you press the Return key, check that the console environment variableis set correctly.   If you are using a VGA monitor as the console terminal, the console environment variable should be set to graphics.  If you are using a serial console terminal, the console environment variable should be set to serial.   If you are using the standard onboard VGA controller, the VGA enable (J27) jumper on the motherboard must be enabled.  If a VGA controller other than the standard onboard VGA controller is being used, make sure the VGA enable (J27) jumper is disabled.  If console is set to serial, the power-up screen is routed to the COM1 serial communication port and cannot be viewed from the VGA monitor. Try connecting a console terminal to the COM1 serial communication port.  Check the baud rate setting for the console terminal and system.  The system baud rate setting is 9600.  When using the COM1 port, you must set the console environment variable to serial. If none of the above considerations solve the problem, check that the J1 jumper on the CPU daughter board  is not missing.   If the system has a customized NVRAM file, try powering up or resetting the system with the Halt button set to the In position.  The NVRAM script will not be executed when powering up or resetting the system with the Halt button depressed.  For certain situations, power up using the fail-safe loader to load new console firmware from a diskette.


Disabling on-board VGA controller

Troubleshooting
No Access to Console Mode

Using a VGA Controller Other than the Standard, Onboard VGA

When the system is configured to use a PCI- or EISA-based VGA controller instead of the standard onboard VGA (Trio64 PCI), consider the following:

The VGA jumper (J27) on the motherboard must then 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 that finds it.


Fail-Safe Loader

Troubleshooting
No Access to Console Mode

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.  You cannot boot an operating system from the fail-safe loader.

If a checksum error is detected when the console is loading at power-up (error beep code 1-1-2 or 1-1-4), the fail-safe loader is automatically activated so that you can reinstall the firmware.

The fail-safe loader (FSL) allows you to attempt to recover when one of the following is the cause of a problem getting to the console program under normal power-up:

A hardware or power failure, or accidental power-down during a firmware upgrade occurred.

A configuration error, such as an incorrect environment variable setting or an inappropriate NVRAM script.

A driver error at power-up.

A checksum error is detected when the SRM console is loading at power-up (corrupted firmware).

From the FSL program, you can update or load new SRM/AlphaBIOS console firmware and FSL console firmware.

The fail-safe loader program is available on diskette (AK-R4VLA-CA) or can be downloaded from the Internet to create your own diskette.

http://ftp.digital.com/pub/Digital/Alpha/firmware/readme.html

Activating the Fail-Safe Loader


Activating the Fail-Safe Loader

Troubleshooting
No Access to Console Mode

Activating the Fail-Safe Loader

Note:  When installing new console firmware, the flash ROM VPP enable jumper (J50) on the motherboard must be enabled.

To activate the FSL:

1.	Move the jumper at bank 7 of the J1 jumper on the CPU daughter board.  The jumper is normally installed in the standard boot setting (position 0).

2.	Insert the console firmware diskette and turn on the system.

3.	Reinstall the console firmware from a firmware diskette.

4.	Power down and return the J1 jumper to the standard boot setting (position 0).


Fail-Safe Loader Jumper

Troubleshooting
No Access to Console Mode

Jumper J1 on the CPU Daughter Board

Bank	Jumper Setting
0	Standard boot setting
1	Power up with backup cache disabled:  Allows the system to run despite bad B-cache until a replacement CPU board is available.
2	Power up to the fail-safe loader with backup cache disabled.
3	Mini console setting (Internal use only)
4	Mini console setting (Internal use only)
5	Mini console setting (Internal use only)
6	Mini console setting (Internal use only)
7	Fail-Safe Loader setting: Attempt to boot from the fail-safe loader diskette at power-up.


Console Event Log

Troubleshooting
Console-Reported Failures

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.

Note:  To stop the screen display from scrolling, enter Ctrl/S.  To resume scrolling, enter Ctrl/Q.  You can also use the command, more el, to display the console event log one screen at a time.

Note:  Click on the [image] icon to view an example.


Console Event Log Example

Troubleshooting
Console-Reported Failures

Console Event Log Example

The following example shows a console event log that contains two standard error messages.

(1) Indicates that the mouse is not plugged in or is not working.

(2) Indicates that SROM tests detected a bad DIMM (bank 1, DIMM3).

>>> cat el

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 6 -- vga -- S3 Trio64/Trio32

bus 1, slot 1 -- ewa -- DECchip 21040-AA

bus 0, slot 11 --ewb -- DECchip 21040-AA

bus 0, slot 13 --ewc -- DECchip 21040-AA

ed.ec.

** mouse error **(1)

*** Bad memory detected by serial rom

*** SROM failing Bank 1, DIMM 3 (2)

eb.....ea.e9.e8.e7.e6.resetting the SCSI bus on

pka0.7.0.5.0 e5.e4.e3.e2.e1.e0.

>>>


Boot Problems

Troubleshooting
Boot Failures

Boot Problems

Symptom	Action
System cannot find boot device.	Check system configuration for correct device parameters (node ID, device name, and so on).  For DIGITAL UNIX and OpenVMS:      show config      show device For Windows NT:      AlphaBIOS menus Check the system configuration for correct environment variable settings.  For DIGITAL UNIX and OpenVMS:     auto_action     bootdef_dev     boot_osflags     os_type For problems booting over a network, check the ew*0_protocols environment variable settings: Systems booting from a DIGITAL UNIX server should be set to bootp; systems booting from an OpenVMS server should be set to mop. For Windows NT: Auto Start and Auto Start Count CMOS Setup Menu Options
Device does not boot.	For problems booting over a network, check the ew*0_protocols environment variable setting: Systems booting from a DIGITAL UNIX server should be set to bootp; systems booting from an OpenVMS server should be set to mop. Run device tests to check that boot device is operating.


Operating System Reported Problems

Troubleshooting
Operating System-Reported Failures

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 (AA-PV6UB-TE) for information on how to interpret OpenVMS crash dump files. Refer to the Guide to Kernel Debugging (AA-PS2TD-TE) for information on using the DIGITAL UNIX Krash Utility.
Errors have been logged and the operating system is up.	Examine the operating system error log files to isolate the problem.   If the problem occurs intermittently, run an operating system exerciser, such as DEC VET, to stress the system. Refer to the DEC Verifier and Exerciser Tool User's Guide (AA-PTTMD-TE) for instructions on running DEC VET.


Mass Storage Problems at Power-Up

Troubleshooting
Console-Reported Failures

Mass Storage Problems Indicated at Power-Up

Mass storage failures at power-up are usually indicated by read fail messages.  Other problems are indicated by storage devices missing from the show config display.  The mass storage troubleshooting table can help you diagnose the likely cause of the problem.

Mass Storage Troubleshooting Table

Troubleshooting tips for AlphaServer systems using a RAID Array Subsystem

Mass Storage Device LEDs


Mass Storage Troubleshooting Table

Troubleshooting
Console-Reported Failures

Mass Storage Troubleshooting Table

Symptom	Problem	Corrective Action
Drives are missing from the show config display.	Drives have duplicate SCSI IDs.	Correct SCSI IDs.  Note: Internal hard disk drives are automatically assigned SCSI IDs 0, 1, 2, and 3 (from left to right for pedestal systems;  and bottom to top for rackmount systems).  The onboard controller is assigned SCSI ID 7, and the CD-ROM, SCSI ID 4.
	SCSI bus not properly terminated.	Check the following jumpers and terminator to ensure that the proper termination is provided for all internal SCSI devices.
		The SCSI terminator jumper (J51) on the motherboard should be set to On.
		The J5 jumper on the hard disk drive backplane should be set to the default setting.
		The cable terminator at the end of the SCSI removable media cable should be properly seated.
		For controllers other than the onboard controller, the pk*0_soft_term environment variable  is used to enable/disable SCSI terminators.
Drives are missing from the show config display/One drive may appear seven times on the show config display.	Drive SCSI ID set to 7 (reserved for host ID) or Duplicate host IDs on a shared bus.	Correct SCSI IDs or Change host ID through the pk*0_host_id envirionment variable (set pk*0_host_id) through the SRM console.
LEDs do not come on.  Drive missing from the show config display.	Missing or loose cables.  Drives not properly seated on the hard disk backplane.	Remove device and inspect cable connections. Reseat drive.
Drives disappear intermittently from the show config and show device displays.	SCSI bus length exceeded.	The entire SCSI bus length, from terminator to terminator, must not exceed 6 meters for fast double-ended SCSI, or 3 meters for fast single-ended SCSI.
Read/write errors in the console event log; storage adapter port fails.	Terminator missing or wrong terminator used.	Check the following jumpers and terminator to ensure that the proper termination is provided for all internal SCSI devices.
		The SCSI terminator jumper (J51) on the motherboard should be set to on.
		The J5 jumper on the hard disk drive backplane should be set to the default setting.
		The cable terminator at the end of the SCSI removable media cable should be properly seated.
		For controllers other than the onboard controller, the pk*0_soft_term environment variable  is used to enable/disable SCSI terminators.
Devices produce errors or device IDs are dropped.	Extra terminator.	Check that bus is terminated only at beginning and end.  Remove unnecessary terminators.  Removable media devices should disable termination (check devices jumpers or SIPs).  For controllers other than the onboard controller, the pk*0_soft_term environment variable  is used to enable/disable SCSI terminators.
Problems persist after eliminating the problem sources.	SCSI storage controller failure	Replace the failing EISA or PCI storage adapter module (or motherboard for the native SCSI controller).


pk*0_soft_term

pk*0_soft_term Environment Variable

Enables or disables SCSI terminators for optional SCSI controllers.  This environment variable applies to systems using the Qlogic SCSI controller, though it does not affect the onboard controller.

The Qlogic SCSI controller implements the 16-bit wide SCSI bus.  The Qlogic module has two terminators, one for the 8 low bits and one for the high 8 bits. There are five possible values:

off--Turns off both low 8 bits and high 8 bits.

low--Turns on low 8 bits and turns off high 8 bits.

high--Turns on high 8 bits and turns off low 8 bits.

on--Turns on both low 8 bits and high 8 bits.

diff--Place the bus in differential mode.


Hard disk drive LEDs

Troubleshooting
Console-Reported Failures

Hard Disk Drive LEDs

LED	Meaning
Activity (green)	When lit, indicates disk activity
Fault (amber)	At product introduction, this LED has no function, it may be used with future enhancements.
Disk Present (green)	When lit, indicates that a disk drive is installed for that position in the hard disk drive backplane.


Control Panel LEDs

Troubleshooting
Power Problems

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.

Power OK (green)	Halt (amber)	Status
Off	Off	System powered off using control panel Power button, or no AC power is present.
Off	On	System power is enabled using the control panel Power button, but the system has been powered off by one of the following:  --Remote management console command --System software --Fan failure --Overtemperature condition --Power supply failure
On	Off	System is powered-on and is not in a halt state.
On	On	System is powered-on and the Halt button is pressed or a halt in command has been issued at the remote management console.


Power-Up Sequence

Troubleshooting
Console-Reported Failures

Power-Up Sequence

During the system power-up sequence, the power supplies are stabilized and the system is initialized and tested.

The power-up sequence includes the following:

Power supply power-up:

AC power-up

DC power-up

Two sets of diagnostics:

Serial ROM diagnostics

Console firmware diagnostics


AC Power-Up Sequence

Troubleshooting
Console-Reported Failures

AC Power-Up Sequence

The following power-up sequence occurs when AC power is applied to the system (systems is plugged in) or when electricity is restored after a power outage:

1.	The front end of the power supply begins operation and energizes.  A minimal set of remote server management logic is powered off the auxiliary 5V power output.

2.	The power supply then waits for the DC power to be enabled.


DC Power-Up Sequence

Troubleshooting
Console-Reported Failures

DC Power-Up Sequence

DC power is applied to the system with the DC On/Off button on the operator 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.	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.


Firmware Power-Up Diagnostics

Troubleshooting
Power Problems

Firmware Power-Up Diagnostics

Serial-ROM Diagnostics

Console Firmware 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 motherboard), including all boot path devices.  These tests are performed as two distinct sets of diagnostics:

1.	Serial ROM diagnostics --These tests check the basic functionality of the system and load the console code from the FEPROM on the motherboard into system memory.

Failures during these tests are indicated by audible error beep codes  and messages in the console event log.

2.	Console firmware diagnostics --These tests are executed by the console code.  They test the core system, including all boot path devices.

Failures during these tests are reported to the console terminal through the power-up screen or console event log.


Serial ROM Diagnostics

Troubleshooting
Power Problems

Serial ROM Diagnostics

The serial ROM diagnostics are loaded into the CPU's instruction cache from the serial ROM on the CPU daughter board.  The diagnostics test the system in the following order:

1.	The CPU and backup cache on the CPU daughter board.

2.	The CPU module's system bus interface.

3.	The system bus to PCI bus bridge and system bus to EISA bus bridge. If the PCI bridge or EISA bridge fails, an error beep code (3-3-1) sounds.  Testing continues despite these errors.

4.	The onboard SCSI controller.  If the controller fails, an error beep code (3-3-3) sounds.

5.	First 32 Mbytes of memory.  If the memory test fails, the failing bank is mapped out and memory is reconfigured and retested.  Testing continues until good memory is found.  If good memory is not found, an error beep code (1-3-3) is generated and the power-up tests are terminated.

6.	The data path to the FEPROM on the motherboard.

7.	The console program is loaded into memory from the FEPROM on the motherboard.  A checksum test is executed for the console image.  If the checksum test fails, an error beep code (1-1-4) is generated, the power-up tests are terminated, and the fail-safe loader is activated.

If the checksum test passes, a single audible beep is issued, and control is passed to the console code, and the console firmware diagnostics are run.


Console Firmware-Based Diagnostics

Troubleshooting
Power Problems

Console Firmware-Based Diagnostics

Console firmware tests are executed once control is passed to the console code in memory.  The console firmware is loaded from the FEPROM on the motherboard during power-up.  They check the system in the following order:

1.	Perform a complete check of system memory.

Steps 2--5 may be completed in parallel.

2.	Start the I/O drivers for mass storage devices and tapes. A complete check of the machine is made.  After the I/O drivers are started, the console program continuously polls the bus for devices (approximately every 20 or 30 seconds).

3.	Check that EISA configuration information is present in NVRAM for each EISA module detected and that no information is present for modules that have been removed.

4.	Run exercisers on the drives seen by the system.

Note:  This step does not ensure that all disks in the system will be tested or that any device drivers will be completely tested.  Spin-up time varies for different drives, so not all disks may be on line at this point in the power-up.  To ensure complete testing of disk devices, use the test command.

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.


Troubleshooting Table for Console Reported Problems

Troubleshooting
Console-Reported Failures

Problems Reported by the Console Program

Symptom	Action
Power-up tests do not complete.	Interpret the error beep codes at power-up and check the power-up screen for a failure detected during self-tests.
The system attempts to boot from a floppy drive after a checksum error is reported (error beep code 1-1-2 or 1-1-4).	Reinstall firmware by inserting a fail-safe loader diskette.  Refer to the procedure provided with the firmware update documentation.
Console program reports error: Error beep codes report an error at power-up. Power-up screen includes error messages.	Use the error beep codes and/or console terminal to determine error. Examine the console event log (enter the more el command) or power-up screen to check for errors detected during power-up.
Power-up screen or console event log indicates problems with mass storage devices.	Use the mass storage troubleshooting table to determine the problem.
Storage devices are missing from the show config display.	Use the mass storage troubleshooting table to determine the problem.
PCI devices are missing from the show config display.	Use the PCI troubleshooting table to determine the problem.
Power-up screen or console event log indicates problems with EISA devices.	Use the EISA troubleshooting table to determine the problem.
EISA devices are missing from the show config display.	Use the EISA troubleshooting table to determine the problem.
	Run the ROM-based diagnostic (RBD tests) to verify problem.

More information on firmware power-up diagnostics


EISA Bus Problems

Troubleshooting
Console-Reported Failures

EISA Bus Problems Indicated at Power-Up

EISA bus failures at power-up may be indicated by the following messages:

EISA Configuration Error. Run the EISA Configuration Utility.

Run the EISA Configuration Utility (ECU) when this message is displayed.  Other problems are indicated by the absence of EISA devices from the show config display.

Use the table below to troubleshoot EISA bus problems that persist after you run the ECU.

Step	Action
1	Confirm that the EISA module and any cabling are properly seated.
2	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. See what the software setting should be for each ISA and EISA controller. See if the ECU deactivated (<>) any controllers to prevent conflict. See if any controllers are locked (!), which limits the ECU's ability to change resource assignments.
3	Confirm that hardware jumpers and switches on ISA controllers reflect the settings indicated by the ECU.  Start with the last ISA module installed.
4	Run ROM-based diagnostics for the type of option: Storage adapter -- Run test to exercise the storage devices off the EISA controller option. Ethernet adapter -- Run test to exercise an Ethernet adapter.
5	Check for bad slot by moving the last installed controller to a different slot.
6	Call option manufacturer or support for help.
Additional EISA Troubleshooting Tips


Additional EISA Troubleshooting Tips

Troubleshooting
Console-Reported Failures

Additional EISA Troubleshooting Tips

The following tips can aid in isolating EISA bus problems.

Peripheral device controllers need to be seated firmly in their slots to make all necessary contacts.  Improper seating is a common source of problems.

Be sure you run the correct version of ECU for the operating system. For Windows NT, use ECU diskette DECpc AXP (AK-PYCJ*-CA); for DIGITAL 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.  Contact the option vendor to obtain the proper CFG file.

Peripherals cannot share direct memory access (DMA) channels.  Assignment of more than one peripheral to the same DMA channel can cause unpredictable results or even loss of function of the EISA module.

Not all EISA products work together.  EISA is an open standard, and not every EISA product or combination of products can be tested.  Violations of specifications may matter in some configurations, but not in others.

Manufacturers of EISA options may have a list of ISA and EISA options that do not function in combination with particular systems.  Be sure to check the documentation or contact the option vendor for the most up-to-date information.

EISA systems will not function unless they are first configured using the ECU.

The ECU will not notify you if the configuration program diskette is write-protected when it attempts to write the system configuration file (system.sci) to the diskette.


PCI Problems at Power-Up

Troubleshooting
Console-Reported Failures

PCI Bus Problems Indicated at Power-Up

PCI bus failures at power-up are usually indicated by the inability of the system to see the device. Use the PCI troubleshooting table below 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.  In such cases, the device functions properly as long as parity is not checked.

The pci_parity environment variable for the SRM console, or the PCI Parity Checking option on the Advanced CMOS Setup Menu for the AlphaBIOS console, allow you to turn off parity checking so that false PCI parity errors do not result in machine check errors.

When you disable PCI parity, no parity checking is implemented for any PCI device.  The default setting is off, no parity checking.

Step	Action
1	Confirm that the PCI module and any cabling are properly seated.
2	Run ROM-based diagnostics for the type of option: Storage adapter -- Run test to exercise the storage devices off the PCI controller option. Ethernet adapter -- Run test to exercise an Ethernet adapter.
3	Check for bad slot by moving the last installed controller to a different slot.
4	Call option manufacturer or support for help.


Interpreting error beep codes

Troubleshooting
No Access to Console Mode

Interpreting Error Beep Codes

If errors are detected at power-up, audible beep codes are emitted from the system.  For example, if the SROM code could not find any good memory, you would hear a 1-3-3 beep code (one beep, a pause, a burst of three beeps, a pause, and another burst of three beeps).

Be sure to check that the CPU daughter board is properly seated in its connector if errors are reported.

Note: A single beep is emitted when the SROM code completes successfully.  The console firmware then continues with its power-up tests.

The beep codes are the primary diagnostic tool for troubleshooting problems when console mode cannot be accessed. Use the table below to interpret error beep codes.

Beep Code	Problem	Corrective Action
1	A single beep is emitted when the SROM code has successfully completed.	Not applicable.  No error.
1-3	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.
1-1-2	ROM data path error detected while loading the AlphaBIOS/SRM console code.  System automatically attempts to boot a fail-safe loader diskette from the floppy drive.	1. Insert the fail-safe loader diskette into the floppy drive to load new AlphaBIOS/SRM console code. 2. If loading new console firmware does not solve the problem, replace the motherboard.
1-1-4	The SROM code is unable to load the console code:  Flash ROM header area or checksum error detected.  System automatically attempts to boot a fail-safe loader diskette from the floppy drive.	1. Insert the fail-safe loader to load new AlphaBIOS/SRM console code. 2. If loading new console firmware does not solve the problem, replace the motherboard.
1-1-7	Floppy read error.  System could not locate a valid boot block on the diskette.	Make sure floppy diskette is inserted, or try another diskette.
1-2-1	TOY NVRAM failure.	Replace the TOY NVRAM chip (E78) on motherboard.
1-2-4	Backup cache error.	Replace the CPU daughter board.   The system can be operated with the B-cache disabled until a replacement CPU daughter board is available.  Bank 1 of the J1 jumper on the CPU daughter board is used to disable the B-cache.
1-3-3	No usable memory detected.	1. Verify that the memory modules are properly seated and try powering up again. 2. Swap memory with known good memory and power up. 3. If populating with known good memory does not solve the problem, replace the CPU daughter board. 4. If replacing the CPU daughter board does not solve the problem, replace the motherboard.
3-3-1	Generic system failure. Possible problem sources include the TOY NVRAM chip (Dallas DS1287A) or PCI-to-EISA bridge chipset (Intel 82375EB).	1. Replace the TOY NVRAM chip (E78) on system motherboard.  2. If replacing the TOY NVRAM chip does not solve the problem, replace the motherboard.
3-3-3	Failure of the native SCSI controller (Qlogic) on the motherboard.	Replace the motherboard.


Memory Layout

AlphaServer 800 Memory Layout


Startup Action (set auto_action)

Troubleshooting
Boot Failures

Startup Action (set auto_action)

Synopsis

Set the console action at power-up and restart.

Command

set auto_action  value

Note:  Click on the [image] icon to view an example.


Value	Description
halt	Causes the system to remain in console mode after the system is powered up (default).
boot	Causes the system to boot automatically when it is turned on.  Causes the system to halt after a system failure.
restart	Causes the system to boot automatically when it is turned on or after it fails.


Startup Action -- Description

Sets the action the console should take any time the system is powered up, fails, or the Reset button is pressed.  When the setting involves autobooting, the system boots from the default boot device that is specified by the value of the bootdef_dev environment variable.

Whenever you change the value of this environment variable, you must initialize the firmware with the init command.


Startup Action - Example

Troubleshooting
Boot Failures

Example

In the following example, the system's default console action following error, halt, or power-up is changed from halt to boot.

>>> show auto_action

auto_action	halt

>>> set auto_action boot

>>> init

 .

 .

 .

>>> show auto_action

auto_action	boot


Boot Device (set bootdef_dev)

Troubleshooting
Boot Failures

Boot Device (set bootdef_dev)

Synopsis

Set the default boot device

Command

set bootdef_dev boot device

Note:  Click on the [image] icon to view an example.


Qualifier	Description
boot_device	Name of a boot device.  See the show device command for device naming conventions.


Boot Device -- Description

Troubleshooting
Boot Failures

Boot Device -- Description

Specifies the default boot device to the system.  The default boot device is the device from which the bootstrap system software is loaded.  In most cases, the default boot device has already been identified on your system as the device on which Factory Installed Software (FIS) was loaded.

Setting the default boot device simplifies the process of booting the operating system as follows:

You can enter b and press Return at the console prompt and the system will find and boot operating system software.

Assuming the default startup action is set to boot or restart (using the set auto_action command), the system will automatically boot the operating system at power-up.

Before identifying the boot device, consider the following:

Your boot device may already be set.  (Enter the command show bootdef_dev to display the current default boot device).

You can identify multiple boot devices to the system.  By doing so, when you enter b or boot at the console prompt, the system searches for a bootable device from the list of devices that you specify.  The system then automatically boots from the first device on which it finds software.

Whenever you boot the operating system, you can override the default boot device by specifying an alternative device name on the boot command line.


Default Boot Device - Example

Troubleshooting
Boot Failures

Example

In the following example, the default device from which the system attempts to boot is set to dka0.

>>> set bootdef_dev dka0

In the next example, the default devices are set to dub0 and dka0.

>>> set bootdef_dev dub0,dka0

>>> show bootdef_dev

bootdef_dev dub0,dka0


Boot Flags (set boot_osflags)

Troubleshooting
Boot Failures

Boot Flags (set boot_osflags)

Synopsis

Set the default boot flags, and in OpenVMS, a root number.

DIGITAL UNIX Command:

set boot_osflags bootflag

OpenVMS Command:

set boot_osflags root number,bootflag

Note:  Click on the [image] icon to view examples.


Boot Flags (DIGITAL UNIX)

Possible boot flag settings and their meanings for DIGITAL UNIX systems are:

Flag Setting	Meaning
a	Autoboot.  Boots/vmunix from bootdef_dev, and goes to multi-user mode.  Use this for a system that should come up automatically after a power failure.
i	Interactive boot.  Requests the name of the image to boot from the specified boot device.  Other flags, such as -kdebug (to enable the kernel debugger), may be entered using this option.
s	Stop in single-user mode. Boots /vmunix to single-user mode and stops at the # (root) prompt.
D	Full dump, implies "s" as well. By default, if DIGITAL UNIX crashes, it completes a partial memory dump. Specifying "D" forces a full dump at system crash.


Root Number Settings (OpenVMS)

The root number is the directory number on the system disk on which OpenVMS files are located.  For instance:

File Location	Corresponding Root Number
[SYS0.SYSEXE]	0 (default)
[SYS1.SYSEXE]	1
[SYS2.SYSEXE]	2
[SYS3.SYSEXE]	3


Boot Flags (OpenVMS)

Possible boot flags settings and their meanings for OpenVMS systems are:

Flag Setting	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 breakpoints.
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.
10000	16	Display debug messages during booting.
20000	17	Display user messages during booting.

Note:  You can specify multiple boot flags by adding the flag values together (logical Oring).  For example, the flag value 10080 executes both the 80 and 10000 flag settings.


Boot Flags -- Description

Boot flags contain information used by the operating system to determine some aspects of a system bootstrap.  Under normal circumstances, you can use the default boot flag settings.

To change the boot flags for the current boot only, you can use the flags_value option with the boot command.

The argument flags_value is specific to the operating system.

The DIGITAL UNIX operating system takes a single ASCII character as an argument.

The OpenVMS operating system expects an ordered pair: root_number and boot_flags.  If you specify only one argument, the argument designates the boot flag.


Default Boot Flags - Example

Troubleshooting
Boot Failures

Example 1 -- DIGITAL UNIX

The boot flags are set to autoboot:

>>> set boot_osflags a

Example 2-- OpenVMS

The root_number is set to 2 and boot_flags is set to 1:

>>> set boot_osflags 2,1

With this setting, the system will boot from root directory SYS2.SYSEXE to the SYSBOOT prompt.

Example 3 -- OpenVMS

The root_number is set to 0 and boot_flags is set to 80:

>>> set boot_osflags 1

With this setting, the operator will be prompted for the name of the secondary bootstrap file.


Operating System (set os_type)

Troubleshooting
Boot Failures

Operating System (set os_type)

Synopsis

Set the default operating system

Command

set os_type os type

Note:  Click on the [image] icon to view an example.


Operating Systems (set os_type) - Example

Troubleshooting
Boot Failures

Example

The default operating system is reset from OpenVMS to Microsoft Windows NT.  After the system is initialized, the Windows NT Boot menu will be displayed.

>>> set os_type nt

>>> init

 .

 .

 .


os type	Description
UNIX	Sets the default operating system to DIGITAL UNIX; starts SRM firmware
VMS	Sets the default operating system to OpenVMS; starts SRM firmware
NT	Sets the default operating system to Microsoft Windows NT; starts AlphaBIOS firmware


Operating System -- Description

The operating system is set at the factory to DIGITAL UNIX, OpenVMS, or Windows NT, depending on the operating system purchased.  The set os_type command is used to change the factory default setting to the operating system you specify.  The os_type environment variable also sets the firmware environment variable that will be started whenever the system powers up, is halted or restarted, or the operating systems is shut down.

If os_type is set to OpenVMS, the system starts the SRM firmware, and OpenVMS is the default operating system.

If os_type is set to DIGITAL UNIX, the system starts the SRM firmware, and DIGITAL UNIX is the default operating system.

If os_type is set to Windows NT, the systems starts the AlphaBIOS firmware, and Windows NT is the default operating system.

If you decide to change operating systems, from DIGITAL UNIX or OpenVMS to Windows NT or from Windows NT to DIGITAL UNIX or OpenVMS, you must reset the os_type environment variable in order to activate the appropriate firmware for the operating system.  If you change to Windows NT, you must also use the appropriate EISA Configuration Utility diskette.

Whenever you change the value of this environment variable, you must initialize the firmware with the init command.


Controller Host Bus Node ID (set pk*0_host_id)

Troubleshooting
Console Reported Failures

set pk*0_host_id (Controller Host Bus Node ID)

Synopsis

Set the controller host bus node ID to a value between 0 and 7.

Command

set pk*0_host_id scsi controller bus node id

Note:  Replace the asterisk (*) with the adapter ID for the SCSI controller for which you are setting the default.

Whenever you change the value of this environment variable, you must initialize the firmware with the init command.

To get a list of the controllers on your system, enter the show config command. A list of all system devices is displayed.  The third letter is the adapter ID for the controller.

Note:  Click on the [image] icon to view an example.


Controller Bus Node ID - Example

Troubleshooting
Console Reported Failures

Example

The default bus node ID for a SCSI controller with an adapter ID of "b" is set to bus node ID 6.

>>> set pkb0_host_id 6

>>> init

 .

 .

 .

>>> show pkb0_host_id

pkb0_host_id 	6


Bus Node ID	Description
0-7	Indicates the bus node ID.


Controller Host Bus Node ID --- Description

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.  You should not need to change the controller bus node ID unless you place two or more controllers on the same bus.

To get a list of the controllers on your system, enter the show device command.  SCSI devices begin with the letters pk, for example pka0.  The third letter is the adapter ID for the controller.  When entering the set pk*_host_id command, replace the asterisk (*) with the adapter ID letter.


Displaying System Configuration: AlphaBIOS

Troubleshooting
Boot Failures

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 systems installed processor, memory, attached devices, and option boards.

From the AlphaBIOS Setup screen, select Display System Configuration..., then the category for the requisite information.

CMOS Setup menu--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.


show config

Troubleshooting
Boot Failures

show config

The show config command displays all devices found on the system, including PCI and EISA devices.  You can use the information in the display to identify target devices for commands such as boot and test, as well as to verify that the system sees all the installed devices.

The configuration display includes the following:

Firmware

System motherboard revision

Memory

Hose 0, Bus 0, PCI

Hose 0, Bus 1, EISA

Hose 0, Bus 2, PCI

Note:  Click on the [image] icon to view an example.


show config

Firmware:

The version numbers for the firmware code, PALcode, SROM chip, and CPU are displayed, along with the CPU clock speed.


show config

System Motherboard Revision:

The hardware revision number of the system motherboard is displayed.


show config

Memory:

The memory size and configuration for each bank of memory is displayed.


show config

Hose 0, Bus 0, PCI Bus:

All controllers on Hose 0, Bus 0, of the primary PCI bus.  The logical slot numbers are listed in the left column of the display.

---Slot 5 = SCSI controller on the system backplane, along with storage drives on the bus

---Slot 6 = Onbard VGA video adapter

---Slot 7 = PCI to EISA bridge chip

Slots 11--14 correspond to physical PCI card cage slots on the PCI bus:

Slot 11 = PCI11

Slot 12 = PCI12

Slot 13 = PCI13

Slot 14 = PCI14 (64-bit PCI option)

In the case of storage controllers, the devices off the controller are also displayed.

Motherboard Connectors and Layout


show config

Hose 0, Bus 1, EISA Bus:

All controllers on Hose 0, Bus 1 of the EISA bus.  The logical slot numbers in the left column of the display correspond to physical EISA card cage slots (1---3).

In the case of storage controllers, the devices off the controller are also displayed.


show config

Hose 0, Bus 2, PCI Bus:

If PCI options contain a PCI-to-PCI bridge, such as the DECchip 21050-AA in the PCI bus, slot 11, in the show configuration example, the additional bus is represented in the display.

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.


Physical Slot Locations

Motherboard Connectors


show config - Example

Troubleshooting
Boot Failures

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) 21064A-1    400MHz

System Motherboard Revision:  0

Memory

     64 Meg of System Memory

     Bank 0 = 64 Mbytes(16 MB Per DIMM) Starting at 0x00000000

     Bank 1 = No Memory Detected

Slot Option                Hose 0, Bus 0, PCI

  5  Qlogic ISP1020        pka0.7.0.5.0       SCSI Bus ID 7

                           dka100.1.0.5.0     RZ28M-S

                           dka200.2.0.5.0     RZ28M-S

                           dka400.4.0.5.0     RRD46

  6  S3 Trio64/Trio32

  7  Intel 82375EB                        Bridge to Bus1, EISA

 11  DECchip 21050-AA                     Bridge to Bus 2, PCI

 12  DECchip 21040-AA      ewb0.0.0.12.0  08-00-2B-3E-BC-B5

 13  NCR 53C825            pkd0.7.0.13.0  SCSI Bus ID 7

Slot Option                Hose 0, Bus 1, EISA

  1  DE425                 ewa0.0.0.1001.0  08-00-2B-3E-BC-B5

Slot Option                Hose 0, Bus 2, PCI

  0  DECchip 21040-AA      ewa0.0.0.2000.0  08-00-2B-E5-CC-B1

  2  Qlogic ISP1020        pkb0.7.0.2002.0  SCSI Bus ID 7

  3  Qlogic ISP1020        pkc0.0.0.2003.0  SCSI Bus ID 7

                           dkc0.0.0.2003.0  RZ26

>>>

Note: The onboard SCSI controller is always device pka.


show device

Troubleshooting
Boot Failures

show device

The show device command displays the console bootable devices and controllers in the system.

Driver ID

Adapter ID

Device Unit Number

Bus Node Number

Channel Number

Logical Slot Number

Hose Number

Note:  Click on the [image] icon to view an example.


show device - Example

Troubleshooting
Boot Failures

Examples

>>> 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                    RRD46   1645

dkc0.0.0.1000.0        DKC9                       RZ26   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               SCSI Bus ID 7   2.10

pka0.7.0.2003.0        PKC0               SCSI Bus ID 7   2.10

>>>


Console device name


Node name (alphanumeric, up to 6 characters)


Device type


Firmware version (if know)


Storage Adapter ID

One-letter adapter designator (A,B,C. . .)


Device Unit Number

Unique device unit number; SCSI unit numbers are forced to 100 X Node ID.


Bus Node Number

Bus Node ID


Channel Number

Used for multi-channel devices.


Hose Number

0 for AlphaServer 800 Systems


show device

Two-letter port or class driver designator

DR-RAID set device

DV-Floppy drive

EW-Ethernet port (TULIP chip, DECchip 21040)

PK-SCSI port, DK-SCSI disk, MK-SCSI tape

PU-DSSI port, DU-DSSI disk, MU-DSSI tape


show device
For EISA options -- Correspond to EISA option physical slot numbers (1----3)

For PCI options:

Slot 5 = SCSI controller on system backplane

Slot 6 = Onboard graphics adapter

Slot 7 = PCI to EISA bridge chip

Slots 11-14 = Correspond to physical PCI options slots: PCI11, PCI12, PCI13, and PCI14 (64-bit)

      --Bus 1 (EISA devices) are reported as 1000. 1001, and 1002

      --Bus 2 (PCI devices) are reported as 2000, 2001, 2002, and so on


SWXCR-XX controller

Troubleshooting
Console-Reported Failures

Troubleshooting RAID Problems

Symptom	Action
Some RAID drives do not appear on the show device display.	Valid configured RAID logical drives will appear as DRA0-DRAn, not as DKn.  Configure the drives by running the RAID Configuration Utility (RCU), following the instructions provided with the StorageWorks RAID Array subsystem. Reminder: several physical disks can be grouped as a single logical DRAn device.
Drives on the SWXCR controller power up with the amber Fault light on.	Whenever you move drives onto or off the controller, run the RAID configuration Utility to set up the drives and logical units.  Follow the instructions provided with the StorageWorks RAID Array Subsystem.
Cannot access disks connected to the RAID subsystems on Windows NT systems.	On Windows NT systems, disks connected to the controller must be spun up before they can be accessed.   While running the ECU, verify that the controller is set to spin up two disks every 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.


ew*0_protocols, er*0_protocols

Troubleshooting
Boot Failures

ew*0_protocols

Synopsis

Enable network protocols are enabled for booting and other functions. These environment variables apply to systems with a DIGITAL Ethernet controller (ew* for the TULIP chip, DECchip 21040).

set ew*0_protocols qualifier

When entering this command, replace  *  with the adapter ID for the Ethernet controller for which you are setting the default.

To get a list of Ethernet controllers on the system, enter the show device command.  A list of all system devices is displayed.  The Ethernet controllers for which this command setting is pertinent start with the letters "ew".  The third letter is the adapter ID for the Ethernet controller.

Note:  Click on the [image] icon to view examples.


ew*0_protocols: Qualifiers

Qualifier	Meaning
mop	Sets the network protocol to mop (Maintenance Operations Protocol): the setting typically used for systems using the OpenVMS operating system (default setting).
bootp	Sets the network protocol to bootp: the setting typically used for systems using the DIGITAL UNIX operating system.
bootp,mop	The bootp and mop qualifiers can be used in a list, separated by a comma.  When the settings are used in a list, the systems attempts to use the mop protocol first, regardless of which protocol is listed first.  If not successful, it then attempts to use the bootp protocol.


Default Boot Flags - Example

Troubleshooting
Boot Failures

Example 1

The network protocol is set to mop for the devices ewa0.

>>> set ewa0_protocols mop

>>> show ewa0_protocols

ewa0_protocols          MOP

Example 2

The network protocol is set to bootp for device ewa0.

>>> set ewa0_protocols bootp

>>> show ewa0_protocols

ewa0_protocols          BOOTP

Example 3

The network protocol is set to mop or bootp for device ewa0.

>>> set ewa0_protocols bootp,mop

>>> show ewa0_protocols

ewa0_protocols          BOOTP,MOP


Power-up Screen

Troubleshooting
Boot Failures

Power-Up Screen

During power-up self-tests, the test status and results are displayed on the console terminal.  Information similar to the following should be displayed on the screen.

ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5.f4

probing hose 0, PCI

probing PCI-to-EISA bridge, bus 1

bus 0, slot 5 -- pka -- Qlogic ISP1020

bus 0, slot 6 -- vga -- S3 Trio64/Trio32

bus 1, slot 1 -- ewa -- DE425

bus 0, slot 11 -- ewb -- DECchip 21040-AA

bus 0, slot 13 -- ewc -- DECchip 21040-AA

ed.ec.eb......ea.e9.e8.e7.e6.e5.e4.e3.e2.e1.e0.

T4.7-72, built on Oct 22 1996 at 09:26:04

Memory Testing and Configuration Status

   64 Meg of System Memory

   Bank 0 = 64 Mbytes (16 MB Per DIMM) Starting at 0x00000000

   Bank 1 = No Memory Detected

Testing the System

Testing the Disks (read only)

Testing the Network

Change mode to Internal loopback.

Change to Normal Operating Mode.

Change mode to Internal loopback.

Change to Normal Operating Mode.

Change mode to Interal loopback.

Change to Normal Operating Mode.

If the power-up display stops, use the error beep codes and a description of the power-up countdown to isolate the likely field-replaceable unit (FRU).

DIGITAL UNIX or OpenVMS Systems

DIGITAL UNIX and OpenVMS operating systems are supported by the SRM firmware.  The SRM console prompt, >>>, is available using SRM console firmware.

Windows NT Systems

The Windows NT operating system is supported by the AlphaBIOS firmware.  Systems using Windows NT power up to the AlphaBIOS boot menu as follows:


Power-up countdown description and Field Replaceable Units (FRUs)

Troubleshooting
Boot Failures

Console Power-Up Countdown Description for Output to the Serial Console Port and Field Replaceable Units (FRUs)

Countdown Number	Description	Likely FRU
ff	Console initiation  started	Non-specific/Status message
fe	Initialized idel PCB	Non-specific/Status message
fd	Initializing semaphores	Non-specific/Status message
fc,fb,fa	Initializing heap	Non-specific/Status message
f9	Initializing driver structures	Non-specific/Status message
f8	Initializing idle process PID	Non-specific/Status message
f7	Initializing file system	NVRAM TOY chip (E78)
f6	Initializing timer data structures	Non-specific/Status message
f5	Lowering IPL	Non-specific/Status message
f4	Entering idle loop	NVRAM TOY chip (E78)
ef	Start memory configuration (heap)	DIMM memory or backplane
df	Configure PCI and EISA bus	PCI or EISA bridge chips
ee	Start phase 1 drivers: NVRAM driver.  Probe EISA and PCI bus for option modules.	NVRAM chip (E14), PCI or EISA option
ed	Start phase 2 drivers:	Non-specific/Status message
ec	Start phase 3 drivers (console selct): tt serial line class, TGA graphics, VGA graphics, and keyboard drivers	Keyboard, VGA or TGA option, or backplane
eb	Run power-up memory test	DIMM memory
ea	Start phase 4 drivers: console support drivers.	Non-specific/Status message
e9	Build HWRPB CPU information.	Non-specific/Status message
e8	Initialize environment variables.	Non-specific/Status message
e7	Start SCSI class driver	Backplane (onboard Qlogic)
e6	Start phase 5 drivers: I/O drivers	PCI or EISA option
e5	Restore timers	NVRAM TOY chip (E78)


Console port configurations

Troubleshooting
No Access to Console Mode

Console Port Configurations

Power-up information is typically displayed on the systems console terminal.  The console terminal may be either a graphics monitor or a serial terminal (connected through the COM1 (MMJ) serial port).

Several SRM console environment variables are used to configuring console ports:

Environment Variable	Description
console	Determines where the system will display power-up output.  Set this environment variable according to the console terminal that you are using.
tt_allow_login	Enables or disables login to the SRM console firmware on alternative console ports.

In addition, the tga_sync_green environment variable is used to synchronize monitors using the high-performance turbo graphics adapter card (PBXGA).

A serial terminal can also be configured to run the ECU.

Using a VGA controller other than the standard onboard VGA.


set console

Troubleshooting
No Access to Console Mode

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 either be a graphics monitor or a serial terminal.  Set this environment variable to the console terminal that you are using.

Whenever you change the value of this environment variable, you must initialize the firmware with the init command.

Syntax:

set console output_device

Arguments:

graphics	Sets the power-up output to be displayed at a graphics monitor or a device that is connected to the VGA port (default setting).
serial	Sets the power-up output to be displayed on the device that is connected to the COM1 (MMJ) port.

Example:

>>> set console serial

>>> init

 .

 .

 . !Now switch to the serial terminal.

>>> show console

Console      serial


set tt_allow_login

Troubleshooting
No Access to Console Mode

set tt_allow_login

The setting of the tt_allow_login environment variable enables or disables login to the SRM console firmware on alternative console ports.

Whenever you change the value of this environment variable, you must initialize the firmware with the init command.

Syntax:

set tt_allow_login [0,1]

Arguments:

1	Enables login on alternative ports (default setting). If the console output device is set to serial, allows you to log in on the COM1 (MMJ) port, COM2 port, or the graphics monitor. If the console output device is set to graphics, allows you to log in through either the primary graphics monitor or the COM1 (MMJ) or COM2 console port.
0	Disables login on alternative console ports.
Example:

>>> set console serial

>>> set tt_allow_login 1

>>> init

 .

 .

 .


set tga_sync_green

The tga_sync_green environment variable set the location of the SYNC signal generated by the ZLX-p-E PCI graphics accelerator card.

The correct setting, displayed with the show command, is:

>>> show tga_sync_green

tga_sync_green   0

If the monitor does not synchronize, set the parameter as follows:

>>> set tga_sync_green 00

This command sets all graphics cards to synchronize on a separate vertical SYNC line, as required by some monitors.  See the monitor documentation for all other information.


Running AlphaBIOS on a Serial Terminal

Troubleshooting
No Access to Console Mode

Setting Up a Serial Terminal to Run the AlphaBIOS Console and the ECU

You can run the ECU and interface with the AlphaBIOS console from either a VGA-compatible graphics monitor or from a serial terminal (VT320 or higher, or equivalent).  Graphics is the default.  If you use the serial line, use serial line equivalents to the graphics line keyboard commands.  To use a serial terminal with the ECU, do the following:

1.	Invoke the terminal setup utility as described in the documentation for the serial terminal and change settings as follows:

  From the General menu, set the terminal mode to Vtxxx, 8-bit controls.

  From the Comm menu, set the character format to 8 bit, no parity, and set receive XOFF to 128 or greater.

  From the Keyboard menu, set the keyboard so that the tilde (~) key sends the escape (ESC) signal.

2.	Enter the following commands at the SRM console prompt to set the console terminal to receive in serial mode.

>>> set console serial

>>> init

 .

 .

 .  !Now switch to the serial terminal.

>>> show console

console   serial


Serial Line Keyboard Commands

Graphics Line Commands	Serial Line Commands
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
ESC	CTRL +[


Removal and Replacement: Guidelines and Static Electricity Precautions

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 field-replaceable unit (FRU) by reversing the steps shown in the removal procedure.

Continue. . .


FRU List

Removal and Replacement -
Field-Replaceable Units for AlphaServer 800 Systems

Part #	Description

Cables
17-03970-03	Floppy drive cable (34-pin)
17-03971-04	Control panel module cable (10-pin)
	Power cord (pedestal systems)
	Power cord (rackmount systems)
17-01476-02	Hard disk drive status cable (20-pin)
17-04400-01	SCSI (embedded 16-bit) disk drive cable (68-pin)
17-04399-01	SCSI (embedded 8-bit) removable-media cable (50-pin)
PB8HA-DA	SCSI (16-bit) option to hard disk backplane cable (68-pin)
BC25V-1H	SCSI option to 68-pin breakouts at rear of enclosure
KZPAC-SB	SCSI option to 68-pin dual connector for standard PCI/EISA bulkhead connector
CPU Modules
54-24801-01	333 MHz CPU daughter board (EV5.6)
54-24801-02	400 MHz CPU daughter board (EV5.6)
Fan
12-23609-24	Fan, 4.75-inch with 3-pin cable
Fixed-Disks
RZ28M-S	2.1 GB SCA2 disk drive
For a complete listing of supported disk options, refer to the DIGITAL Systems and Options Catalog (ftp://ftp.digital.com/pub/Digital/info/SOC/).

Memory Modules
54-24354-DA	1 M x 72, 60 NS, 8 MB DIMM
54-24352-DA	2 M x 72, 60 NS, 16 MB  DIMM
54-24329-DA	4 M x 72, 60 NS, 32MB DIMM
54-24344-DA	8 M x 72, 60 NS, 64 MB DIMM
54-24823-DA	16 M x 72, 60 NS, 128 MB DIMM
20-47480-D7	32 M x 72, 60 NS, 256 MB DIMM
54-24821-DA	Alternate for 54-24344-DA
20-47166-D7	Alternate for 54-24354-DA
20-47170-D7	Alternate for 54-24352-DA
20-47083-D7	Alternate for 54-24344-DA
54-24821-DA	Alternate for 54-24344-DA
20-47137-D7	Alternate for 54-24823-DA
Note:  Alternate and standard DIMM options cannot be mixed.  Determine DIMM type before ordering.

Other Modules and Components
54-24978-01	Control panel module
54-24960-01	Disk status module
54-24945-01	SCSI disk drive backplane
54-24803-01	Motherboard
21-29631-02	NVRAM chip (E14)
54-32423-01	NVRAM TOY clock chip (E78)
	PCI/EISA Options
30-47661-02	Power supply
70-31349-01	Speaker with 2-pin cable
30-46117-02	Mouse, 3 button
LK46W-A2	OpenVMS style keyboard (108 key)
LK97W-A2	Windows NT/DIGITAL UNIX style keyboard (104 key)
12-37977-02	Key for door
Removable Media
RRD46 -AB	CD-ROM drive, half-height
RX23L MB	Floppy drive


Motherboard Removal: Steps 1, 2

Removal and Replacement
Motherboard, AlphaServer 800

Step 1:  Record the position of the EISA and PCI options.

Step 2:  Remove the EISA and PCI options.

Note:  Click on the [image] icon to go to next step.


Motherboard Removal: Step 3

Removal and Replacement
Motherboard, AlphaServer 800

Step 3:  Remove CPU daughter board.

Warning: CPU and memory modules have parts that operate at high temperatures.  Wait 2 minutes after power is removed before handling these modules.

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.

Note:  Click on the [image] icon to go to next step.


Motherboard Removal: Steps 4, 5

Removal and Replacement
Motherboard, AlphaServer 800

Step 4: Remove the airflow baffle from the motherboard.

Step 5: Detach motherboard cables, remove screws, and motherboard.

Note:  Click on the [image] icon to go to next step.


Motherboard Removal: Step 6

Removal and Replacement
Motherboard, AlphaServer 800

Step 6:  Move the socketed NVRAM chip (position E14) and NVRAM TOY chip (E78) to the replacement motherboard and set jumpers to match previous settings.


NVRAM Chip and NVRAM TOY Chip

Removal and Replacement
NVRAM Chip (E14) and NVRAM TOY Chip (E78), AlphaServer 800

NVRAM Chip (E14) and NVRAM TOY Chip (E78)

Note:  The NVRAM TOY clock chip contains the os_type environment variable.  This environment variable may need to be reset.


Disk Status Module


OCP Cable Removal

Control Panel Module Cable (10-pin)


Wide SCSI Cable for Breakouts at Rear of Enclosure


Wide SCSI Dual Connector Cable for Standard PCI/EISA Bulkhead Connector


Floppy Cable Removal

Floppy Drive Cable (34-pin)


SCSI Disk Drive Backplane: Step 1

Removal and Replacement
SCSI Disk Drive Backplane, AlphaServer 800

Step 1:  Remove hard disk drives.

Note:  Click on the [image] icon to go to next step.


SCSI Disk Drive Backplane: Step 2

Removal and Replacement
SCSI Disk Drive Backplane, AlphaServer 800

Step 2:  Disconnect disk power, disk status, and SCSI data cables from the disk drive backplane and remove backplane.


Pedestal Systems

Rackmount Systems


Power Cord (Rackmount Systems)

Removal and Replacement
Power Cord (Rackmount Systems), AlphaServer 800

Power Cord Order Numbers (Rackmount Systems)

Country	Power Cord Description	DIGITAL Number
U.S., Japan, Canada	120V NEMA	17-00083-58
U.S., Japan, Canada	240V NEMA	17-00083-61
Europe	230V IEC	17-04285-04


Power Cord (Pedestal Systems)

Removal and Replacement
Power Cord (Pedestal Systems), AlphaServer 800

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
Central Europe (Aus, Bel, Fra, Ger, Fin, Hol, Nor, Swe, Por, Spa)	BN19C-2E	17-00199-21
U.K., Ireland	BN19A-2E	17-00209-15
Switzerland	BN19E-2E	17-00210-13
Denmark	BN19K-2E	17-00310-08
Italy	BN19M-2E	17-00364-18
India, South Africa	BN19S-2E	17-00456-16
Israel	BN18L-2E	17-00457-16


Power Cords


Hard Disk Drive Status Cable (20-pin)


SCSI (Embedded 8-Bit) Removable-Media Cable (50-pin)

SCSI (Embedded 16-Bit) Disk Drive Cable (68-pin)


SCSI (Embedded 8-Bit) Removable-Media Cable (50-pin)


SCSI (16-Bit) RAID Option to Disk Drive Backplane (68-pin)


Control Panel Module Removal: Step 1,2

Removal and Replacement
Control Panel Module, AlphaServer 800

Step 1:  Disconnect the control panel cable.

Step 2:  Remove the control panel module.


CPU Daughter Board, Removal

CPU Daughter Board

Warning: CPU and memory modules have parts that operate at high temperatures.  Wait 2 minutes after power is removed before handling these modules.

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.


Memory Removal

Removal and Replacement
Memory Modules, AlphaServer 800

DIMM Memory Modules

The position of failing dual-inline memory modules (SIMMs) is

reported by the SROM power-up scripts or can be determined using the procedures described with the memexer command.

AlphaServer 800 system memory configuration rules

Note:  Click on the [image] icon to go to next step.


AlphaServer 800 Memory Configuration Rules

AlphaServer 800 System Memory Configuration Rules

At least one memory bank must contain a memory option.

The memory option consists of four DIMMs (0, 1, 2, and 3).

All DIMMs in a bank must be of the same capacity and part number.


Memory Module Removal: Steps 1 and 2

Removal and Replacement
Memory Modules, AlphaServer 800

Step 1: Record the position of the failing DIMMs.

Step 2: Locate the failing DIMM on the motherboard.

Note:  Click on the [image] icon to go to next step.


Memory Module Removal: Step 3

Removal and Replacement
Memory Modules, AlphaServer 800

Step 3: Replace the failing DIMM(s).

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 note use any metallic tools or implements including pencils to release DIMM latches.  Static discharge can damage the DIMMs.

Removing DIMMs from Motherboard

Installing DIMMs on Motherboard


DIMM Memory Removal

Removing DIMMs


DIMM Memory Installation

Installing DIMMs

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 DIMM.


Fan


Hard Disk Drives

Removal and Replacement
Hard Disk Drive, AlphaServer 800

Hard Disk Drive

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 Subsystems Family Installation and Configuration Guide.

If the drives are not plugged into a RAID controller, you will need to shut down the operating system before swapping a drive. However, you will not need to power down the server before installing the drives.

Warning:  When removing the right-most (or top-most for rackmount systems), remove the disk drive door to avoid the possibility of hitting your hand against the door.


Floppy Drive Removal

Floppy Drive


Speaker


CD-ROM Drive

Floppy Drive


CD-ROM Drive, Removing

CD-ROM Drive

Note:  When removing a 5.25-inch device from the upper 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.


Removing PCI/EISA Options: Steps 1, 2

Removal and Replacement
PCI/EISA Options, AlphaServer 800

Step 1:  Record the position of the failing EISA or PCI option.

Step 2:  Record the position of the failing EISA or PCI option.

PCI and EISA slots


Motherboard Layout


Power Supply: Steps 1, 2

Removal and Replacement
Power Supply, AlphaServer 800

Step 1:  Disconnect power supply cables and remove power supply.

Step 2:  Set voltage select switch on replacement power supply and install power supply.

Warning:  Hazardous voltages are contained within the power supply.  Do not attempt to service.  Return to factory for service.

Caution:  Incorrectly setting the voltage select switch can destroy the power supply.


Pedestal Systems

Rackmount Systems


Accessing FRUs, Pedestal Systems

Removal and Replacement
Accessing FRUs, AlphaServer 800 Pedestal Systems

Caution:  Before removing the top cover and side panels:

1. Perform an orderly shutdown of the operating system.

2. Set the On/Off button on the operator control panel to off.

3. Unplug the AC power cord.

4. Unlock and open the front door.

5. Remove the retaining screw indicated by the yellow label on the lower left side of the front of the system.

6. Slide back and remove the left side panel.

7. Slide back and remove the top and right side panel.


Opening Front Door (Pedestal Systems)

Opening the Front Door, Pedestal Systems


Accessing FRUs, Rackmount Systems

Removal and Replacement
Accessing FRUs, AlphaServer 800 Rackmount Systems

Access rackmount FRUs as follows:

Warning: The system can weigh 27.45 kg (61 lb).  To prevent injury and equipment damage, ensure that only one system is extended out of the cabinet at any one time and that the cabinet is stabilized before pulling the system out on its slides.

The adjustable leveling feet should be down and the cabinets stabilizing bar fully extended before any component is extended out of the cabinet on slides.

Do not extend more than one slide assembly at a time; cabinet instability may result.

1. Perform an orderly shutdown of the operating system.

2. Set the On/Off button on the operator control panel to off.

3. Unplug the AC power cord.

4. Pull off the front bezel using the two finger holds.

5. Remove the two front  screws.

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.


FRUs, Pedestal and Rackmount Enclosure, AlphaServer 800 Systems

Removal and Replacement
FRUs, Pedestal and Rackmount Enclosure, AlphaServer 800


Running ROM-Based Diagnostics

Troubleshooting
ROM-Based Diagnostics (RBDs)

Running ROM-Based Diagnostics

ROM-based diagnostics (RBDs), which are part of the console firmware, offer many powerful diagnostic utilities, including the ability to examine error logs from the console environment and run system- or device-specific exercisers.

AlphaServer 800 RBDs rely on exerciser modules to isolate errors. The exercisers are designed to run concurrently, providing maximum bus interaction between the console drivers and the target devices.  The console firmware allows you to run diagnostics in the background (using the background operator & at the end of the command).  You run diagnostics by using console commands.

Note:  ROM-based diagnostics, including the test command, are run from the SRM console (firmware used by OpenVMS and DIGITAL UNIX operating  systems).  If you are running a Windows NT system, you will need to switch consoles.

RBDs report errors to the console terminal and/or the console event log.

Acceptance Testing and Initialization


Acceptance Testing and Initialization

Perform the acceptance testing procedure listed below after installing a system or whenever adding or replacing the following:

CPU daughter board

Memory modules

Motherboard

Storage devices

EISA or PCI options

1.  Run the RBD acceptance tests using the test command.

2.  If you have added, moved, or removed an EISA or ISA option, run the EISA    Configuration Utility (ECU).

3.  Bring up the operating system.

4.  Run DEC VET to test that the operating system is correctly installed.


DEC VET

Digital's DEC Verifier and Exerciser Tool (DEC VET) software is a multipurpose system maintenance tool that performs exerciser-oriented maintenance testing.  DEC VET runs on OpenVMS, DIGITAL UNIX, and Windows NT operating systems. DEC VET consists of a manager and exercisers.  The DEC VET manager controls the exercisers.  The exercisers test system hardware and the operating system.

DEC VET supports various exerciser configurations, ranging from a single device exerciser to full system loading, that is, simultaneous exercising of multiple devices.

Refer to the DEC Verifier and Exerciser Tool Users Guide (AA-PTTMD-TE) for instructions on running DEC VET.


Diagnostic Commands

Troubleshooting
ROM-Based Diagnostics (RBDs)

Running System Diagnostics

Summary of Diagnostic and Related Commands

Command	Function
Acceptance Testing
test	Quickly tests the core system.  The test command is the primary diagnostic for acceptance testing and console environment diagnosis. The test command runs one pass of the tests.  To run tests concurrently and indefinitely, use the sys_exer command.
Error Reporting
cat el	Displays the console event log.
more el	Displays the console event log one screen at a time.
Extended Testing/Troubleshooting

crash	Forces a crash dump at the operating system level.
memexer	Exercises memory by running a specified number of memory tests.  The tests are run in the background.
net -ic	Initializes the MOP counters for the specified Ethernet port.
net -s	Displays the MOP counters for the specified Ethernet port.
sys_exer	Exercises core system.  Tests run concurrently.
Loopback Testing
sys_exer -lb	Conducts loopback tests for COM2 and the parallel port in addition to core system tests.
test_-lb	Conducts loopback tests for COM2 and the parallel port in addition to quick core system tests.
Diagnostic-Related Commands

kill	Terminates a specified process.
kill_diags	Terminates all executing diagnostics.
show_status	Reports the status of executing test/exercisers.


Command Reference --- crash

Troubleshooting
ROM-Based Diagnostics (RBDs)

crash

Synopsis

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.

Refer to OpenVMS Alpha System Dump Analyzer Utility Manual for information on how to interpret OpenVMS crash dump files.

Refer to the Guide to Kernel Debugging for information on using the DIGITAL UNIX Krash Utility.

Command

crash ([device])

Example

Note:  Click on the [image] icon to view an example.


Argument	Description
[device]	The device name of the device to which the crash dump is written.


clear_error - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example

>>> crash dka100

CPU restarting

DUMP:  401408 blocks available for dumping.

DUMP:  38535 required for partial dump.

DUMP:  0x805001 is the primary swap with 401407, start our last 38534

    : of sump at 362873, going to end (real end is one more, for header)

DUMP.prom: dev SCSI 100 1 0 5 0 0, block 131072

.

.

.

succeeded

halted CPU

halt code = 5

Halt instruction executed

PC = fffffc00004e2d64

>>>


Command Reference --- cat el and more el

Troubleshooting
ROM-Based Diagnostics (RBDs)

cat el and more el

Command

The cat el and more el commands display the contents of the console event log.  Status and error messages are logged to the console event log at power-up, during normal system operation, and while running system tests.  Standard error messages are indicated by asterisks (***).

When cat el is used, the contents of the console event log scroll by. You can use the Ctrl/S combination to stop the screen from scrolling, Ctrl/Q to resume scrolling.

The more el command allows you to view the console event log one screen at a time.

Synopsis

cat el

or

more el

Note:  Click on the [image] icon to view an example.


more el, cat el - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example

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.

>>> cat 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

.

.

.

>>>


Command Reference --- memexer

Troubleshooting
ROM-Based Diagnostics (RBDs)

memexer

Synopsis

The memexer command tests memory by running a specified number of memory exercisers.  The exercisers are run in the background and nothing is displayed unless an error occurs.  Each exerciser tests all available memory in twice the backup cache size blocks for each pass.

To terminate the memory tests, use the kill command to terminate an individual diagnostic or the kill_diags command to terminate all diagnostics.  Use the show_status display to determine the process ID when terminating an individual diagnostic test.

Command

memexer [number]

Note:  Click on the [image] icon to view examples.


Argument	Description
[number]	The number of exercisers to start.  The default  is 1. The number of exercisers, as well as the length of time for testing, depends on the context of the testing.  Generally, running three to five exercisers for 15 minutes to 1 hour is sufficient for troubleshooting most memory problems.


memexer - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example with no errors

>>> memexer 4

>>> show_status

ID --------	Program -------	Device -----------	Pass ----	Hard/Soft -----	Bytes Written -------	Bytes Read -------
00000001	idle	system	0	0    0	0	0
0000006b	memtest	memory	3	0    0	63565158	62565154
00000071	memtest	memory	2	0    0	63565158	62565154
000000d1	memtest	memory	3	0    0	63565158	62565154
00000077	memtest	memory	1	0    0	63565158	62565154
>>> kill_diags

>>>

Example with a memory compare error indicating bad DIMMs

>>> memexer 3

*** Hard Error - Error #41 - Memory compare error

Diagnostic Name	ID	Device	Pass	Test	Hard/Soft	7-NOV-1997
memtest	00000193	brd0	114	1	1     0	12:00:01
Expected value:	25c07
Received value:	35c07
Failing addr:	a11848

*** End of Error ***

>>> kill diags

>>>

To find the failing bank, compare the failing address (a11848 in this example) with the show memory display or memory portion of the show config command display:

1.	Banks with no memory present are eliminated as possible failing banks.

2.	If the failing address is greater than the bank starting address, but less than the starting address for the next bank, then the failing DIMM is within this bank. (Bank 0 in the example using failing address a11848 and the following memory display.)

>>> show memory

Memory

  128 Meg of System Memory

  Bank 0 = 64 Mbytes (16MB per DIMM) Starting at 0x00000000

  Bank 1 = 64 Mbytes (16MB per DIMM) Starting at 0x01000000

>>>

To determine the failing DIMM, match the lowest five bits of the failing address in which the bad data is received to the failing DIMM using the following table:

Failing Address Lowest  Five Bits	Failing DIMM
0	0
8	1
10	2
18	3

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.


Command Reference --- net-s

Troubleshooting
ROM-Based Diagnostics (RBDs)

net  -s

Synopsis

The net -s command displays the MOP counters for the specified Ethernet port.

Command

net -s ewa0

Note:  Click on the [image] icon to view an example.


net-s - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

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:

 Network list size: 0

MOP COUNTERS:

Time since zeroed (Secs): 42

TX:

 Bytes: 0 Frames: 0

 Deferred: 1 One collision: 0 Multi collisions: 0

TX Failures:

 Excessive collisions: 0 Carrier check: 0 Short circuit: 71

 Open circuit: 0 Long frame: 0 Remote defer: 0

 Collision detect: 71

RX:

 Bytes: 49972 Frames: 70

 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

>>>


Command Reference --- net -ic

Troubleshooting
ROM-Based Diagnostics (RBDs)

net  -ic

Synopsis

The net -ic command initializes the MOP counters for the specified Ethernet port.

Command

net -ic ewa0

Note:  Click on the [image] icon to view an example.


net -ic - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example

>>> net -ic ewa0

>>> 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:

 Network list size: 0

MOP COUNTERS:

Time since zeroed (Secs): 3

TX:

 Bytes: 0 Frames: 0

 Deferred: 0 One collision: 0 Multi collisions: 0

TX Failures:

 Excessive collisions: 0 Carrier check: 0 Short circuit: 0

 Open circuit: 0 Long frame: 0 Remote defer: 0

 Collision detect: 0

RX:

 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

>>>


Command Reference --- kill and kill_diags

Troubleshooting
ROM-Based Diagnostics (RBDs)

kill and kill_diags

Synopsis

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.

Command

kill_diags

kill [PID . . . ]


kill --- Description

The kill command terminates a specified process.


kill_diags --- Description

The kill_diags command terminates all diagnostics.


PID	Description
[PID. . .]	The process ID of the diagnostic to terminate.  Use the show_status command to determine the process ID.


Command Reference --- show_status

Troubleshooting
ROM-Based Diagnostics (RBDs)

show_status

Synopsis

Reports the status of currently executing test/exercisers.

Command

show_status

Note:  Click on the [image] icon to view an example.


show_status -- Description

The show_status command reports one line of information per executing diagnostic.  The information includes ID, diagnostic program, device under test, error counts, passes completed, bytes written and read.

Many of the diagnostics run in the background and provide information only if an error occurs.  Use the show_status command to display the progress of diagnostics.

The following command string is useful for periodically displaying diagnostic status information for diagnostics running in the background:

>>> while true;show_status;sleep n;done

Where n is the number of seconds between show_status displays.


show_status - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example

>>>show_status

ID -------	Program -------	Device ------	Pass ----	Hard/Soft -----	Bytes Written -------	Bytes Read -------
00000001	idle	system	0	0    0	0	0
0000006f	memtest	memory	1	0    0	35651584	35651584
00000070	memtest	memory	1	0    0	35651584	35651584
00000077	memtest	memory	1	0    0	37748736	37748736
0000007e	exer_kid	dka0.0.0.1.0	0	0    0	0	69120
0000007f	exer_kid	dka600.6.0.1	0	0    0	0	66560
00000093	exer_kid	dva0.0.0.0.1	0	0    0	0	0
000000d5	nettest	era0.0.0.2.1	13	0    0	308672	308672


ID

Process ID.


Program

Program module name.


Device

Device under test.


Pass

Diagnostic pass count.


Hard/Soft

Error count (hard and soft):  Soft errors are not usually fatal; hard errors halt the system or prevent completion of the diagnostics.


Bytes Written

Bytes successfully written by diagnostic.


Bytes Read

Bytes successfully read by diagnostic.


Exit

Do you want to exit this application?


Testing the System (test)

Console Firmware
ROM-Based Diagnostics (RBDs)

test

Synopsis

The test command runs one pass of diagnostics for the system.  To run test concurrently and indefinitely, use the sys_exer command.  Fatal errors are reported to the console terminal.

The more el command should be used in conjunction with the test command to examine test/error information reported to the console event log.

Note:  By default, no write tests are performed on disk and tape drives.  Media must be installed to test the floppy drive and tape drives.  A loopback connector is required for the COM2 (9-pin loopback connector, 12-27351-01) port and parallel port (25-pin loopback connector) when the -lb argument is used.

The test command does not test the DNSES, TGA card, MEMORY CHANNEL options, or third-party options.

When using the test command after shutting down an operating system, you must initialize the system to a quiescent state.  Enter the following command at the SRM console:

>>> init

 .

 .

 .

>>> test

Command

test ([-lb])

Note:  If you are running the Windows NT operating system, you need to switch to the AlphaBIOS console in order to enter the test command.

To examine test/error information, examine the console event log using the more el command.

Note:  Click on the [image] icon to view examples.


Testing the system (test)- Example

Console Firmware
ROM-Based Diagnostics (RBDs)

Example 1

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)

file open failed for dva0.0.0.1000.0

Testing the VGA (Alphanumeric Mode only)

Testing the EWA0 Network

Testing the EWB0 Network

Testing the EWC0 Network

Example 2

In the following example, the system is tested and the system reports a fatal  error message.  No network server responded to a loopback message.  Ethernet connectivity on this system should be checked.

>>> 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)

file open failed for dva0.0.0.1000.0

Testing the VGA (Alphanumeric Mode only)

Testing the EWA0 Network

*** Error (ewa0), Mop loop message timed out from: 08-00-2b-3b-42-fd

*** List index: 7 received count: 0 expected count 2

Testing the EWB0 Network

Testing the EWC0 Network

>>>


Test Command --Description

The tests are run in the following order:

1.	Memory tests (one pass).

2.	Read-only tests:  DK* disks, DR* disks, DU* disks, MK* tapes, DV* floppy.

3.	Console loopback tests if -lb argument is specified: COM2 serial port and parallel port.

4.	VGA/TGA console tests.  These tests are run only if the console environment variable is set to serial.  The VGA/TGA console test displays rows of the word "digital. "

5.	Network external loopback tests for E*A0.  This test requires that the Ethernet port be terminated or connected to a live network or the test will fail.

Note:  Because traffic on live networks is unpredictable, loopback timeouts are considered soft errors.


Argument	Description
[-lb]	The loopback option includes console loopback tests for the COM2 serial port and the parallel port during the test sequence.


sys_exer

Console Firmware
ROM-Based Diagnostics (RBDs)

sys_exer

Synopsis

The sys_exer command runs diagnostics for the system.  The same tests that are run using the test command are run with sys_exer, only these tests are run concurrently and in the background.  Nothing is displayed, after the initial test startup messages, unless an error occurs.

The diagnostics started by the sys_exer command automatically reallocate memory resources, as these tests require additional resources. The init command must be used to reconfigure memory before booting an operating system.

Because the sys_exer tests are run concurrently and indefinitely (until you stop them with the init  command), they are useful in flushing out intermittent hardware problems.

When using the sys_exer command after shutting down an operating system, you must initialize the system to a quiescent state.  Enter the following command at the SRM console:

>>> init

 .

 .

 .

>>> sys_exer

Note:  By default, no write tests are performed on disk and tape drives.  Media must be installed to test the floppy drive and tape drives.  A loopback connector is required for the COM2 (9-pin loopback connector, 12-27351-01) port and parallel port (25-pin loopback connector) when the -lb argument is used.

Command

sys_exer ([-lb])

Note:  If you are running the Windows NT operating system, you need to switch to the AlphaBIOS console in order to enter the sys_exe r command.

Note:  Click on the [image] icon to view example.


Testing the system (sys_exer)- Example

Console Firmware
ROM-Based Diagnostics (RBDs)

Example

In the following example, the tests complete successfully.

Note:  Examine the console event log after running tests.

>>> 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)

Exercising the VGA (Alphanumeric Mode only)

Exercising the EWA0 Network

Exercising the EWB0 Network

Type init in order to boot the operating system

Type show_status to display testing progress

Type cat el to redisplay recent errors

>>> show_status

ID ----	Program -------	Device ------	Pass ----	Hard/ Soft -----	Bytes Written -------	Bytes Read -------
00000001	idle	system	0	0  0	0	0
0000550b	memtest	memory	193	0  0	7243563008	7243563008
0000003d	memtest	memory	192	0  0	7222591488	7222591488
00005514	exer_kid	dka100.1.0.2.0	7	0  0	0	2461184
0000551d	exer_kid	dka400.4.0.2.0	0	0  0	0	2311168
0000551e	exer_kid	dva0.0.0.100.0	0	0  0	0	922624
00005533	nettest	ewa0.0.0.200		0  1	12160512	12159632
00005608	nettest	ewb0.0.0.13		0  2	12116624	12115280
>>> init

ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5.ef.df.ee.f4

.

.

.

>>>


Argument	Description
[-lb]	The loopback option includes console loopback tests for the COM2 serial port and the parallel port during the test sequence.


Switching Between Interfaces

Console Firmware
ROM-Based Diagnostics (RBDs)

Switching Between Interfaces

For a few procedures it is necessary to switch from one console interface to the other.

The test command is run from the SRM interface.

The EISA Configuration Utility (ECU) and the RAID Configuration Utility (RCU) are run from the AlphaBIOS interface, as are some option-specific configuration utilities.

Switching from SRM to AlphaBIOS

Switching from AlphaBIOS to SRM


Switching from SRM to ARC

Switching from SRM to AlphaBIOS

Two SRM console commands are used to temporarily switch to the AlphaBIOS console:

The alphabios command loads the AlphaBIOS firmware and displays the AlphaBIOS menu interface.

The ecu command loads the AlphaBIOS firmware and then loads and starts the EISA configuration utility from diskette.

The console environment variable determines where the AlphaBIOS firmware is displayed.  To force the AlphaBIOS output to the graphics display, use the -g qualifier with the alphabios or ecu command.

For systems that boot the Windows NT operating system, return to the AlphaBIOS console by setting the os_type environment variable to NT, then enter the init command:

>>> set os_type NT

>>> init


Switching from ARC to SRM

Switching from AlphaBIOS to SRM

Switch from the AlphaBIOS console to the SRM console as follows:

1.  From the CMOS Setup menu, press F6 to enter Advanced CMOS setup.

2.  From the Advanced CMOS Setup menu, select OpenVMS (SRM).

3.  Press F10 to save the change.

4.  When the "Power-cycle the system to implement the change" message is displayed, press the Reset button.  Once the console firmware is loaded and the device drivers are loaded, you can boot the operating system.

Note:  For information on AlphaBIOS, refer to the AlphaServer 800 Users Guide.


Error Log Analysis

Troubleshooting
Error Log Analysis

Fault Detection and Reporting

Machine Check/Interrupts

Error Logging and Event Log Entry Format

Event Record Translation

Open VMS Alpha Translation Using DECevent

DIGITAL UNIX Translation Using DECevent


Fault Detection and Reporting

Troubleshooting
Error Log Analysis

Fault Detection and Reporting

PALcode Exception Handling

Component	Fault Detection/Correction Capability
CPU Daughter Board
Alpha 21164 microprocessor	Contains error detection and correction (EDC) logic for data cycles. There are check bits associated with all data entering and exiting the microprocessor.  A single-bit error on any of the four longwords being read can be corrected (per cycle).  A double-bit error on any of the four longwords being read can be detected (per cycle).
Backup cache (B-cache)	EDC check bits on the data store; and parity on the tag address store and tag control store.
Memory Subsystem
Memory DIMMs	EDC logic protects data by detecting and correcting data cycle errors.  A single-bit error on any of the four longwords can be corrected (per cycle).  A double-bit error on any of the four longwords being read can be detected (per cycle).
System Motherboard
SCSI controller EISA-to-PCI bridge chip	SCSI data parity is generated. PCI data parity is generated.


PALcode Exception Handling

Generally, PALcode handles exceptions as follows:

The PALcode determines the cause of the exception.

If possible, it corrects the problem and passes control to the operating system for reporting before returning the system to normal operation.

If error/event logging is required, control is passed through the system control block (SCB) to the appropriate exception handler.


Machine Checks/Interrupts; Processor machine check; system machine check; processor-detected correctable error; system-detected

Troubleshooting
Error Log Analysis

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.  There are four types of machine checks/interrupts related to system events:

1.	Processor Machine Check (SCB 670)

2.	System Machine Check (SCB 660)

3.	Processor-Detected Correctable Error (SCB 630)

4.	System-Detected Nonfatal Error (SCB 620)

Note:  A fan failure is a fatal, noncorrectable error, but is reported as nonfatal to allow the operating system to perform shutdown.

During the error-handling process, errors are first handled by the appropriate PALcode error routine and then by the associated operating system error handler.  Click on the type of machine check/interrupt for information on the possible causes of each. The system control block (SCB) vector through which PALcode transfers controls to the operating system is shown in parentheses.


Processor Machine Check

Processor Machine Check (SCB: 670)

Processor machine check errors are fatal system errors that result in a system crash.  The error-handling code for these errors is common across all platforms using the Alpha 21164 microprocessor.

I-cache data or tag parity error

S-cache data parity error--I-stream

S-cache tag parity error--I-stream

S-cache data parity error--D-stream Read/Read, READ_DIRTY

S-cache tag parity error--D-stream or system commands

D-cache data parity error

D-cache tag parity error

I-stream uncorrectable ECC data parity errors (B-cache or memory)

D-stream uncorrectable ECC data parity errors (B-cache or memory)

B-cache tag parity errors--I-stream

B-cache tag parity error--D-stream

System command/address parity error


System Machine Check

Troubleshooting
Error Log Analysis

System Machine Check (SCB: 660)

A system machine check is a system- or processor-detected error that occurred as a result of an off-chip request to the system.  The following conditions cause PALcode to build the 660/670 machine check logout frame and invoke the 660 error handler.

CIA-detected noncorrectable ECC error

CIA-detected command/address parity error

CIA-detected nonexistent memory reference

PCI bus parity error

PCI command/address parity error

PCI master abort

PCI target abort

Scatter/gather invalid translations table entry

I/O timeout

System overtemperature (event)

Unexpected IPL 23 interrupt request


Processor-Detected Correctable Errors

Processor-Detected Correctable Errors (SCB: 630)

Processor-detected correctable errors are generic Alpha 21164 microprocessor correctable errors.  The error handling code should be common across all platforms that use the Alpha 21164.  The following conditions cause PALcode to invoke the operating system 630 error handler:

Single-bit I-stream ECC error

Single-bit D-stream ECC error


System-Detected Nonfatal Errors

System-Detected Nonfatal Errors (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

High temperature warning (event)

Fan warning/failure (event)---This event is fatal and noncorrectable, though reported as nonfatal.  The OS then shuts the system down.


Error Log Format

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.  Most entries have a PAL-generated logout frame, and may contain frames for CPU, memory, and I/O.


Event Record Translation

Troubleshooting
Error Log Analysis

Event Record Translation

Systems running DIGITAL UNIX and OpenVMS operating systems use the DECevent management utility to translate events into ASCII reports derived from system event entries (bit-to-text translations).

The DECevent utility has the following features relating to the translation of events:

Translating event log entries into readable reports

Selecting input and output sources

Filtering input events

Selecting alternate reports

Translating events as they occur

Maintaining and customizing the user environment with the interactive shell commands

OpenVMS Alpha Translation Using DECevent

DIGITAL UNIX Translation Using DECevent

Note:  Microsoft Windows NT does not currently provide bit-to-text translation of system errors.


OpenVMS Translation Using DECevent

OpenVMS Alpha Translation Using DECevent

The kernel error log entries are translated from binary to ASCII using the DIAGNOSE command. To invoke the error log utility, enter the DCL command DIAGNOSE.

Format:

DIAGNOSE/TRANSLATE [qualifier] [,...] [infile[,...]]

Example:

$ DIAGNOSE/TRANSLATE/SINCE=14-jun-1997

For more information on generating error log reports using DECevent, refer to the DECevent Translation and Reporting Utility for OpenVMS Alpha, User and Reference Guide, AA-Q73KC-TE.

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 OpenVMS Alpha, User and Reference Guide, AA-Q73LC-TE, for more information.


DIGITAL UNIX Translation Using DECevent

The kernel error log entries are translated from binary to ASCII using the dia command.  To invoke the DECevent utility, enter the dia command.

Format:

dia [-a -f infile[...]]

Example:

% dia -t s:14-jun-1997:10:00

For more information on generating error log reports using DECevent, refer to the DECevent Translation and Reporting Utility for DIGITAL UNIX, User and Reference Guide, AA-QAA3-TE.

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, AA-QAA4A-TE, for more information.


SCSI Bus

SCSI Buses
Configuring Internal Storage Devices

SCSI Bus

The embedded SCSI controller on the motherboard:

Supports up to seven drives.

Provides 8-bit fast narrow SCSI for up to three 5.25-inch internal, half-height removable-media devices.

Provides 16-bit fast wide SCSI support for up to four 3.5-inch, internal hard disk drives.

Note:  Two half-height removable-media devices can be substituted for one 5.25-inch full-height device.

For Windows NT, adding or removing drives may require rebooting the operating system.  Certain RAID controllers may permit hotswapping of drives without deallocating drives and rebooting the operating system.

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.

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 need to reach the connector on the controller option.

If you plan to extend a SCSI bus from a controller through either of the wide SCSI breakouts at the rear of the enclosure, cable BC25V-1H provides a wide 68-pin connector.

If you plan to extend a SCSI bus from a multi-channel controller to external devices through a vacant PCI/EISA slot bulkhead connector, cable KZPAC-SB provides two 68-pin (Honda miniature) connectors on a bulkhead connector.

Two of the three 5.25-inch half-height removable-media device slots can be used to provide room for one 5.25-inch full-height device.  Remove the divider to convert from two half-height to one full-height slot.

External SCSI expansion


SCSI Configuration Rules for External SCSI Expansion

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:

The device must be supported by the operating system. Consult the software product description or contact the hardware vendor.

A maximum seven devices can be attached on any one SCSI controller.

Each device on the bus must have a unique SCSI ID.  You may need to change a devices default SCSI ID in order to make it unique.  For information about setting a devices ID, refer to the guide for that device.

The entire SCSI bus length, from terminator to terminator, must not exceed 6 meters for fast double-ended SCSI, or 3 meters for fast single-ended SCSI.

Ensure that the SCSI bus is properly terminated and that no devices in the middle of the bus are terminated.

For best performance, wide devices should be operated in wide SCSI mode.


SCSI Bus IDs


RAID/SCSI Cable for Internal Disk Drive Backplane


Wide SCSI Cable for Breakouts at Rear of Enclosure


Wide SCSI Dual Connector Cable for Standard Bulkhead Connector


Removing Divider to Allow for Full-Height Device


Exit

Do you want to exit this application?


Notices

V1 April 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.

The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation.

Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document.

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.

Copyright  1997 by Digital Equipment Corporation. All rights reserved.

The following are trademarks of Digital Equipment Corporation: AlphaServer, OpenVMS, StorageWorks, and the DIGITAL logo.

The following are third-party trademarks:  Lifestyle 28.8 DATA/FAX Modem is a trademark of Motorola, Inc.  UNIX is a registered trademark in the U.S. and other countries, licensed exclusively through X/Open Company Ltd.  U.S.  Robotics and Sportster are registered trademarks of U.S. Robotics.  Windows NT is a trademark of Microsoft Corp.  All other trademarks and registered trademarks are the property of their respective holders.

Information Services

Contributors


Contributors

Oleg Klimowicz - Illustrator

Andrea Thurber - Interface /Graphic Designer

Rich Trubey - Writer/Designer


Information Services

Alpha Firmware Updates

ECU Revisions

OpenVMS Patches

Late-Breaking Technical Information

Supported Options

Training

Digital Assisted Services


Alpha Firmware Updates

Under certain circumstances, such as a CPU upgrade or replacement of the system motherboard, you may need to update the system firmware.  An Alpha Firmware CD-ROM is available with DIGITAL UNIX, OpenVMS, and Windows NT operating systems.  The Alpha firmware files can also be downloaded from the Internet as follows:

ftp://ftp.digital.com/pub/Digital/Alpha/firmware/readme.html

The above README file describes the firmware directory structure, and how the files can be downloaded and used.

New versions of firmware released between shipments of the Alpha Firmware CD-ROM are available in an interim directory:

ftp://ftp.digital.com/pub/Digital/Alpha/firmware/interim/


ECU Revisions

The EISA Configuration Utility (ECU) is used for configuring EISA options on 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 revision of the ECU, can order a separate kit.  Call 1-800-DIGITAL to order.

If the customer plans to migrate from DIGITAL UNIX or OpenVMS to Windows NT, you must re-run the appropriate ECU.  Failure to run the operating-specific ECU will result in system failure.


OpenVMS Patches

Software patches for the OpenVMS operating system are available from the World Wide Web as follows:

http://www.service.digital.com/html/patch_service.html

Choose the Contract Access option if you have a valid software contract with DIGITAL or you wish to become a software contract customer.  Choose the Public Access options if you do not have a software service contract.


Late Breaking Technical Information

Late-Breaking Technical Information

You can download up-to-date files and late-breaking technical information from the Internet.

The information includes firmware updates, the latest configuration utilities, software patches, lists of supported options, Wide SCSI information, and more.

FTP Address:

ftp.digital.com

cd /pub/Digital/Alpha/systems/as800/

World Wide Web address:

http://www.service.digital.com/info/alphaserver/tech_docs/alphasrv800/


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.  The catalog presents all products that are announced, actively marketed, and available for ordering.

Access printable postscript files of any section of the catalog from the Internet as follows (be sure to check the Readme file):

ftp://ftp.digital.com/pub/Digital/info/SOC/


Training

Computer Based Training (CBT) and lecture lab courses are available from the DIGITAL training center:

Alpha Concepts

DSSI Concepts: EY-9823E

ISA and EISA Bus Concepts: EY-I113E-P0

RAID Concepts: EY-N935E

SCSI Concepts and Troubleshooting: EY-P841E, EY-N838E


Fail-safe loader

Fail-Safe Floppy Loader

The fail-safe floppy loader diskette (AK-R4VLA-CA) can be ordered.  Call 1-800-DIGITAL, or download the firmware from the Internet to create your own fail-safe loader diskette.

ftp://ftp.digital.com/pub/Digital/Alpha/firmware/readme.html

The above README file describes the firmware directory structure, and how the files can be downloaded and used.


Assisted Services

Digital Assisted Services

DIGITAL Assisted Services (DAS) offers products, services, and programs to customers who participate in the maintenance of DIGITAL computer equipment. Components of DIGITAL assisted services include:

Spare parts and kits

Diagnostics and service information/documentation

Tools and test equipment

Parts repair services, including Field Change Orders


Navigating Hints

Looking Up Topics in the Index

To look up a topic using the index:

1	Choose the Index button in the application window.

2	Type the word you want to search for or select the word from the list.

You can press a key on your keyboard to move quickly to different parts of the list.  For example, type "S" to move to words beginning with the letter "S" and then type "O" to see words beginning with "So."

3	Choose the Show Topics button.

The application lists the topics that are linked to the word you entered or selected.

4	Double-click on the topic you want to view or select the topic and choose the Go To button.

Use the vertical scroll bar to see topics not visible in the list.

Tip:  Double-click on a word to list the related topics automatically.


Navigating Hints

Search Menu

Searching for a Word or Phrase


The hand symbol indicates there is more information in the topic.  Click on the hand symbol pointing right to browse forward in the topic.


The hand symbol indicates there is more information in the topic.  Click on the hand symbol pointing left to browse backward in the topic.


Using "file folder" Tabs

Navigating Hints

Using "Folder" Tabs

Folder tabs allow you to quickly navigate between sections.


Using the Map

Navigating Hints

Using the Map

The map allows you to quickly navigate between sections.


Using the Scroll Bar

Navigating Hints

Using the Scroll Bar

A scroll bar to the right of the screen indicates that there is more information for that topic. Click and drag the scroll bar down to see the additional information.  Click and drag the scroll bar up to backtrack.


Default Jumpers

Default Jumper Settings
Motherboard, CPU Daughter Board, and Hard Disk Backplane

Jumper Settings:

Motherboard jumpers

Supported setting for jumper J3 on the CPU daughter board

J1 jumper on the CPU daughter board

J5 jumper on the hard disk backplane


CPU Daughter Board, J3 and J4 Jumpers

CPU Daughter Board, J3 Supported Settings

Note: : These jumpers affect the clock speed and other critical system settings.


Motherboard Jumpers

Default Jumper Settings
Motherboard

Motherboard Jumpers (Default Settings)


Motherboard Jumper J27
Jumper	Name	Description	Default Setting
J27	VGA Enable	When enabled (as shown), the onboard VGA logic is activated.	Enabled for onboard VGA; Disabled if an EISA- or PCI-based VGA option is installed.


Motherboard Jumper J51
Jumper	Name	Description	Default Setting
J51	SCSI Termination	Allows the internal SCSI terminator to be disabled.	Enabled (as shown).


Motherboard Jumper J16
Jumper	Name	Description	Default Setting
J16	Fan fail override	Allows the fan failure detection logic to be disabled to accommodate alternative enclosures	This jumper is not installed on AlphaServer 800 Systems.


Motherboard Jumper J50
Jumper	Name	Description	Default Setting
J50	Flash ROM VPP Enable	Permits the 12V voltage needed to update the Flash ROMS.	Jumper installed (enabled).


Motherboard Jumper J22
Jumper	Name	Description	Default Setting
J22	Remote Management Console (RMC)	Sets default values to the RMC NVRAM.	Disabled (as shown).


CPU Daughter Board, Jumper J1

Default Jumper Settings
CPU Daughter Board (J1 Jumper)

CPU Daughter Board (Jumper J1)

Bank	Jumper Setting
0	Standard boot setting
1	Power up with backup cache disabled:  Allows the system to run despite bad B-cache until a replacement CPU board is available.
2	Power up to the fail-safe loader with backup cache disabled.
3	Mini console setting (Internal use only)
4	Mini console setting (Internal use only)
5	Mini console setting (Internal use only)
6	Mini console setting (Internal use only)
7	Fail-Safe Loader setting: Attempt to boot from the fail-safe loader diskette at power-up.


SCSI Hard Disk Backplane Jumper (J5)

Default Jumper Settings
SCSI Hard Disk Backplane Jumper (J5)

SCSI Hard Disk Backplane Jumper Setting (J5)


Remote Server Management

Troubleshooting
Remote Server Management

The remote management console (RMC) allows you to remotely monitor and control the system

First-time setup procedures for using the RMC modem port and enabling the system to call out to a remote operator

Procedure to reset the RMC to its factory settings

RMC commands

Troubleshooting tips and suggestions for using the RMC


Operating the System Remotely

Troubleshooting
Remote Server Management

Operating the System Remotely

The remote management console (RMC) enables the user to monitor and control the system remotely.  The RMC resides on the system backplane and allows a remote operator to connect to the system through a modem, using a serial terminal or terminal emulator.

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

 To enter the RMC console locally

Once connected to the RMC, the operator can use a special set of remote console commands, distinct from the standard SRM and AlphaBIOS consoles.  The RMC firmware is implemented in a dedicated microprocessor (RMC PIC processor).  The RMC commands allow the operator to remotely monitor power supply status, system temperature, and fan status.

RMC commands also allow the remote operator to exercise control over the system, equivalent to using the system control panel: Power off/on, Reset, and Halt (in/out).

The RMC logic can dial a preset telephone number when it detects system alarm conditions.  A typical scenario might be:

1.	RMC detects an alarm condition due to excessive temperature.

2.	RMC dials the operators pager and sends a message identifying the system.

3.	Operator dials the system from a remote serial terminal.

4.	Logging into the RMC, the operator checks system status and powers down the system.

5.	Later the operator powers up the system and reboots.

The remote operator can disconnect (using the quit command) from the RMC and connect to the systems COM1 port.  Through the remote terminal, the operator can then communicate with the software and firmware that normally use the local serial terminal:

 SRM and AlphaBIOS firmware consoles

 ECU and RCU configuration utilities

 Operating systems

The RMC also provides a watchdog timer, whose interval is set using the RMC set wdt command.  If the system fails to respond within the watchdog timer interval, the 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.


Entering 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.  The default escape sequence is ^[^[rcm.  This is equivalent to <Esc><Esc>rcm, where <Esc> is the escape key on a PC keyboard.  The default string can be changed using the set escape command.  Before you can dial in remotely, you must set up the RMC initialization and dial strings.


Entering the RMC Console Locally

Type the escape sequence at the SRM console prompt on the local serial console terminal.  The default escape sequence is ^[^[rcm.  This is equivalent to <Esc><Esc>rcm, where <Esc> is the escape key on a PC keyboard.

You can also enter the RMC console from the local graphics monitor by entering the RMC command at the SRM console prompt, and then entering the escape sequence.   When finished accessing the RMC console from the graphics monitor, enter the reset command to restore the RMC and SRM consoles.


Remote Management Console Block Diagram


RMC First-Time Setup

Troubleshooting
Remote Server Management

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; and to send out a test alert to verify the modem strings are set correctly.

1.	From the local console terminal, enter the RMC escape sequence at the SRM prompt.  The default escape sequence is ^[^[rcm.  This is equivalent to <Esc><Esc>rcm, where <Esc> is the escape key on a PC keyboard.

You can also enter the RMC from the local graphics monitor by entering the rcm command at the SRM console prompt, and then entering the escape sequence.   When finished accessing the RMC from the graphics monitor, enter the reset command to restore the RMC and SRM consoles.

2.	Using the RMC command set init, assign the modem initialization string appropriate for your modem.  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  V-34/V.FC + FAX	at&fe0v0x0s0=2
Refer to your modem documentation for more information on its initialization strings.

3.	Using the RMC commands set dial and set alert, assign a dial string to be called when the RMC detects an alert condition, as well as a string to be used with a paging service, usually a call-back number for the paging service.

When an alert is sent, the dial string and alert string are concatenated and sent to the modem.  Note that the dial and alert strings must be in the correct string format for the attached modem.  If a paging service is to be contacted, then the dial and alert strings must include the appropriate modem commands to dial the number, wait for the line to connect, and send the appropriate touch tones to leave a pager message.

4.	Using the RMC command set password, assign a password of up to 14 characters that will be stored in nonvolatile memory.  This password must be set before access through the modem port can be enabled.

5.  Using the RMC command enable remote, enable access to the to RMC modem port.  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.

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.  If the alert is not cleared, the RMC continues to page the remote operator approximately every 30 minutes.

First-Time Setup Example


RMC First-Time Setup, Example

Troubleshooting
Remote Server Management

First-Time Setup (Example)

RCM> status

              Platform Status:

Firmware Revision:  V1.0
Server Power:  OFF
Fanstate:
System Halt:
Temperature: 29.0C (warnings at 46C, power-off at 52C)
RCM Power Control:  ON
Escape sequence: ^[^[RCM
Remote Access:  Disabled
Alert Enable: Disabled
Alert Pending: NO
Init String:
Dial String:
Alert String:
Modem and COM1 baud:  9600
Last Alert:
Watchdog Timer: 60 seconds
Autoreboot : ON

RCM> set init

init> at&f0e0v0x0s0=2

RCM> set dial

dial> atxdt9,15085553333

RCM> set alert

alert> ,,,,,,5085553332#;

RCM> set password

new pass> *********

RCM> enable remote

RCM> enable alert

RCM> send alert

RCM> clear alert

RCM> status

Platform Status:

Firmware Revision:  V1.0
Server Power:  OFF
Fanstate:
System Halt:
Temperature: 29.0C (warnings at 46C, power-off at 52C)
RCM Power Control:  ON
Escape sequence: ^[^[RCM
Remote Access:  Enabled
Alert Enable:  Enabled
Alert Pending: NO
Init String:  at&f0e0v0x0s0=2
Dial String:  atxdt9,15085553333
Alert String:  ,,,,,,5085553332#;
Modem and COM1 baud:  9600
Last Alert:  RCM User Requested
Watchdog Timer: 60 seconds
Autoreboot : ON


Resetting the RMC to Factory Defaults

Troubleshooting
Remote Server Management

Resetting the RMC to Factory Defaults

If you have forgotten the password, or have changed and forgotten the RMC escape sequence, you can reset the RMC to its factory settings.  Use the following procedure  to restore the default settings:

1.	Unplug the system line cord from the AC power line.

2.	Open the system side panel.

3.	Install jumper J22 on the system motherboard.

4.	Plug the system line cord into the AC power line for approximately 15 seconds.

5.	Unplug the system line cord from the AC power line.

6.	Remove jumper J22.

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.


Remote Management Console Commands

Troubleshooting
Remote Server Management

Remote Management Console Commands

The remote management console supports the following commands

clear alert

clear port

disable alert

disable reboot

disable remote

enable alert

enable reboot

enable remote

halt in

halt out

hangup

help or ?

power off

power on

quit

reset

send alert

set alert

set baud

set dial

set escape

set init

set password

set wdt

status


clear alert

The clear alert command clears the current alert condition and causes the RMC to stop paging the remote operator. If the alert is not cleared, the RMC continues to page the remote operator every 30 minutes, assuming both remote access and alerts are enabled.

Example:

RCM> clear alert

RCM>


clear port

The clear port command uses the console port modem control signals to clear any stuck conditions on the systems COM1 port.  The object is to attempt to free the port using the COM1 port modem control lines if it is currently locked by some application program without resetting the entire system.

Example:

RCM> clear port

RCM>


disable port

disable alert

The disable alert command disables alert conditions from paging an external operator.  Monitoring continues and alerts are still logged in the last alert field; however, alerts are not sent to the remote user.

Example:

RCM> disable alert

RCM>


disable reboot

The disable reboot command disables automatic reboot of  the system when the watchdog timer expires.

Example:

RCM> disable reboot

RCM>


disable remote

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>


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.

Example:

RCM> enable reboot

RCM>


enable remote

The enable remote command enables access to the RMC modem port. This command also allows the RMC to automatically dial the phone number set with the set dial command upon detection of alert conditions.  The enable remote command causes the modem initialization string to be sent to the modem (see set init command).

Note: The RMC password must be set for the enable remote command to succeed.

Example:

RCM>enable remote

RCM>


halt in

The halt in command is the equivalent of setting the Halt button on the server front panel to the latching in position.  After executing the halt in command, the user is switched from the RMC monitor to the servers COM1 port.  Note that a local operator physically powering off the system through the system front panel will override this command and reset the halt command to the out condition.

Example:

RCM>halt in

Returning to COM  port.


halt out

The halt out command is the equivalent of setting the Halt button on the server front panel to the out position.  After executing the halt out command, the user is switched from the RMC monitor to the servers COM1 port.  Note that a local operator physically placing the front panel Halt button to the In position takes precedence over the setting of this command.

Example:

RCM>halt out

Returning to  COM  port.


hangup

The hangup command terminates the modem session.  Once issued, the user will no longer be connected to the server.

Example:

RCM>hangup

RCM>


help or ?

The help or ? command displays the command set.

Example:

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


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.

Example:

RCM>power off

RCM>


power on

The power on command is the equivalent of turning on the system power from the operator control panel.  If the system is already powered on or if the system is powered off through the system power button, this command has no effect.  After executing the power on command from the RMC monitor, the user is switched back to the servers COM1 port.

Example:

RCM>power on

Returning to COM port.


quit

The quit command is used to exit console monitor mode and return to pass-through mode.

Example:

RCM>quit

Returning to COM  port.


reset

The reset command is the equivalent of pushing the Reset button from the operator control panel.  It causes a full re-initialization of the system firmware.  When the reset command is executed, the users terminal exits console monitor mode and reconnects to the servers COM1 port.

Example:

RCM>reset

Returning to COM  port.


send alert

The send alert command forces an alert condition. This command can be used to test the setup of the alert dial out function or to send an alert condition when a system application program is connected to the RMC monitor program.

Example:

RCM> send alert

RCM>


set alert

The set alert command sets the alert string that is transmitted through the modem when an alert condition is detected.  This string should be set to some meaningful value such as the system remote access phone number.  An application on the remote system could monitor incoming alert strings and take appropriate action. The maximum string length is 47 characters.  When the alert is sent, the dial string and alert string are concatenated and sent to the modem.

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.


set baud

Troubleshooting
Remote Server Management

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. This port is fixed at 9600 baud.

It is important that the baud rate being used by the operating system or console (com1_baud) be changed before using this command; otherwise the remote operator will not be able to communicate with the system.

Consider the following before changing the baud rate:

 The value of the SRM com1_baud environment variable is saved in nonvolatile memory, while the value of the RMC set baud command is not.  If you have changed the baud rate and the power fails, the RMC modem baud rate will return to the default value (9600) and the com1_baud rate would have to be changed locally before a remote dial in could be reestablished.

 The ECU and RCU configuration utilities only run at the 9600 baud rate setting.

 DIGITAL UNIX requires that a file be edited to match the new baud rate, or the operating system will not reboot successfully.

The following example uses the SRM console.

Note: If a modem is being used, the enable remote command must be issued following the  set baud command in order to set the modem to the new baud rate.

Example:

>>> show com1_baud

com1_baud           9600

>>> set com1_baud 38400

^[^[RCM

RCM> set baud

baud (1=9600, 2=19200, 3=38400)>3

RCM> quit

Returning to COM port

>>> show com1_baud

com1_baud           38400

>>>


set dial

The set dial command sets the dial string to be used when the RMC detects an alert condition.  Note that this string must be in the correct dial string format for the attached modem.  If a paging service is to be contacted, then the dial string must include the appropriate modem commands to dial the number, wait for the line to connect, and send the appropriate touch tones to leave a pager message.  The dial string is limited to 31 characters.

Example:

RCM> set dial

dial> ATXDT15085551234

RCM>


set escape

The set escape command allows the user to change the escape sequence used for exiting pass-through mode and entering console monitor mode.  The escape sequence can be any character string.  A typical sequence consists of two or more control characters for a maximum of 14 characters.  It is recommended that control characters be used in preference of ASCII characters.

Example:

RCM> set escape

new esc> ^[^[rcm

RCM>


set init

The set init command sets the modem initialization string.  This string is limited to 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 V-34/V.FC + FAX	at&fe0v0x0s0=2

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 users terminal.  The password must be set before access through the modem can be enabled.

Example:

RCM> set pass

new pass> **************

RCM>


set wdt

The set wdt command sets the time-out period for the system watchdog timer. Allowable values are:

0    (disabled)
1    (10 seconds)
2    (20 seconds)

.

.

.

9    (90 seconds)

Example:

RCM> set wdt

time (0-9 tens of seconds)> 3

RCM>


status

The status command displays the current state of the servers sensors, as well as the current escape sequence and alarm information.

Example:

RCM> status

              Platform Status:

Firmware Revision:  V1.0
Server Power:  ON
Fanstate:  OK
System Halt:  Deasserted
Temperature: 29.0C (warnings at 46C, power-off at 52C)
RCM Power Control:  ON
Escape sequence: ^[^[RCM
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>


Dial and Alert String Elements, RMC

Troubleshooting
Remote Server Management

Dial and Alert String Elements

String Elements	Description
Dial String
ATXDT	(Enter characters either in all uppercase or all lowercase). AT = Attention X = Forces the modem to dial blindly (not look for the dial tone).  Enter this character if the dial-out line modifies its dial tone when used for services such as voice mail.  D = Dial T = Tone (for touch-tone) , = 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.
Alert String

,,,,,,	Pause for 12 seconds for paging service to answer (each comma (,) provides a two second delay.
5085553332#	Message, usually a call-back number for the paging service.  The alert string must be terminated by the # character.
;	Return to console command (;) character must be used to terminate the string.


RMC Troubleshooting

Troubleshooting
Remote Server Management

RMC Troubleshooting Tips

Symptom	Possible Cause	Suggested Solution
The local terminal will not communicate with the system or RMC console.	System, terminal, or RMC baud rate set incorrectly.	Set the baud rates for the system, RMC, and terminal to 9600 baud.  For first-time setup, suspect the console terminal, since the RMC and system default is 9600.
RMC will not answer when the modem is called.	Modem cables may be incorrectly installed.	Check modem phone lines and connections.
	RMC remote access is disabled.	Enable remote access.
	RMC does not have a valid password set.	Set password and enable remote access.
	On power-up, the RMC defers initializing the modem for 30 seconds to allow the modem to complete its internal diagnostics and initializations.	Wait 30 seconds after powering up the system and RMC before attempting to dial in.
	Modem may have had power cycled since last being initialized or modem is not set up correctly.	Enter enable remote command from RMC console.
After the system is powered up, the COM1 port seems to hang and then starts working after a few seconds.	This delay is normal behavior due to initialization.	Wait a few seconds for the COM1 port to start working.
New password and escape sequence are forgotten.		Reset the RMC to its factory default settings.
The remote user sees a +++ string on the screen.	The modem is confirming whether the modem has really lost carrier.  This occurs when the modem sees an idle time, followed by a 3, followed by a carriage return, with no subsequent traffic.  If the modem is still connected, it will remain so.	This is normal behavior.
The message unknown command is displayed when the user enters a carriage return by itself.	The terminal or terminal emulator is including a line feed character with the carriage return.	Change the terminal or terminal emulator setting so that new line is not selected.
Cannot enable modem or modem will not answer.	The modem is not configured correctly to work with the RMC.	Modify the modem initialization string according to your modem documentation.