Manufacturing Part Number: HP Part No. A5990-90010
Edition E0600
Notice
The information contained in this document is subject to change without notice.
Restricted Rights Legend
Use, duplication, or disclosure by government is subject to restrictions as set forth in
subdivision (c) (1) (ii) of the Rights in Technical Data and Computer Software Clause at
DFARS 252.227.7013.
rights are reserved. No part of this document may be photocopied, reproduced or
translated to another language without the prior written consent of Hewlett-Packard
Company.
UNIX is a registered trademark in the United States and other countries, licensed
exclusively through X/Open Company Limited.
This software and documentation is based in part on the Fourth Berkeley Software
Distribution under license from the Regents of the University of California.
This Technical Reference provides instructions for installing and configuring hardware,
system specifications and characteristics, instructions for using the Boot Console Handler,
SCSI device information, error messages and troubleshooting hints for your HP
VISUALIZE J6000 workstation.
Safety and Regulatory Statements
See Appendix A for the safety and regulatory statements that apply to the J6000
workstation.
Installation Notice
Products designated in the Hewlett-Packard price list as customer installable can be
installed using the instructions provided with the product. If you have elected to have the
product installed by our field personnel, you will be charged for this service as covered
under the standard terms and conditions. For more information, please go to this web site:
www.hp.com/visualize/support
Related Manuals
For more information, refer to the following documents:
• Common Desktop Environment (CDE) User’s Guide
• Configuring HP-UX for Peripherals
• HP-UX System Administration Tasks
• HP CDE Getting Started Guide
• Managing Systems and Workgroups
• Using HP-UX.
• Using Your HP Workstation
• Getting Started Guide for the J6000
Note that the documents listed above can be viewed with a web browser using this URL:
http://www.docs.hp.com
9
Revision History
The revision history for each edition of the manual is listed below:
EditionRevision History
E0600First Printing
Problems, Questions, and Suggestions
If you have any problems or questions with our hardware, software, or documentation,
please contact either your HP Response Center or your local HP representative. If you
have access to a web browser, you can get the latest software and hardware patches at the
following URL:
http://www.hp.com/visualize/support/
Documentation Conventions
Unless otherwise noted in the text, this guide uses the following symbolic conventions.
Table 1. Documentation Conventions
user-supplied valuesItalic words or characters in syntax and command descriptions
represent values that you must supply. Italics are also used in text
for emphasis.
screen displayInformation that the system displays, commands that you must use
literally, and path names appear in this typeface.
EnterKeycaps are presented with a special keycap font as shown in the left
column. (In this document, we refer to the Enter key. On your
keyboard, the key may be labeled either Enter or Return.)
Electrostatic Discharge (ESD) Precautions
Electrostatic charges can damage the integrated circuits on printed circuit boards. To
prevent such damage from occurring, observe the following precautions during board
unpacking and installation:
• Work on a static-free mat.
• Wear a static strap to ensure that any accumulated electrostatic charge is discharged
from your body to ground.
• Create a common ground for the equipment you are working on by connecting the
static-free mat, static strap, and peripheral units to that piece of equipment.
• Keep uninstalled printed circuit boards in their protective antistatic bags.
• Handle printed circuit boards by their edges, once you have removed them from their
protective antistatic bags.
10
1LVD Product Information
This chapter provides general product information about the HP VISUALIZE J6000
workstation. This information is provided to help familiarize you with the main features
and components of the workstation.
11
LVD Product Information
Chapter Overview
Chapter Overview
This chapter contains the following main sections:
• Product Description
• Front Panel Components
• Rear Panel Components
• Internal Components
• Monitors
• Keyboard and Mouse
Product Description
The HP VISUALIZE J6000 workstation is a high-performance system capable of handling
the most complex problems in computational analysis, advanced 3-D design, and electronic
circuit design and verification.
The J6000 has two PA-8600 microprocessors and sixteen memory slots on its system
board. It has a 715 Watt power supply with no DC/DC converter units required.
Net Dimensions and Weights
The dimensions for the deskside system are listed below.
• Depth: 25.8 inches (65.5 cm)
• Width: 10.0 inches (25.4 cm)
• Height: 19.8 inches (53.3 cm)
The dimensions for the rack system are listed below.
• Depth: 24.5 inches (62.2 cm)
• Width: 16.7 inches (42.4 cm)
• Height: 3.4 inches (8.6 cm)
12Chapter1
. Table 1-1 lists the net weights for the J6000.
Table 1-1. Net Weights for the J6000 Workstations
Weight
Deskside ConfigurationMin. - 40lbs. (17 kg.)
Max. - 49 lbs (22 kg.)
LVD Product Information
Product Description
Maximum Configuration (Rack
Mount)
Maximum Configuration (Twenty
Fully Equipped Workstations and
the Rack)
1
1. The rails weigh approximately 10 lbs. (4 kg.). This weight is not included in these
figures.
Min. - 36lbs. (16 kg.)
Max. - 41 ls. (18 kg.)
1200 pounds (544 kg)
NOTEFor environmental and electrical requirements, see Appendix B.
Chapter 113
LVD Product Information
Product Description
Key Features
The J6000 workstations have the following key features.
• CPUs:
— Two 552MHz PA-8600 microprocessors, each with 0.5 MB instruction cache and 1.0
MB data cache.
• Operating System (Native HP-UX):
— 32-bit support requires HP-UX version 10.20 plus the June 1999 Workstation ACE
(Additional Core Enhancements)
— 64-bit support requires HP-UX version 11.0 plus ACE 9911
• User Interface: HP CDE (Common Desktop Environment) graphical user interface
• Compatibility: Source- and binary-code compatible with the B
-, C-, and J-Class
product families
• Main Memory: Using 512MB or 1 GB DIMMs
— Sixteen DIMM slots in pairs (from 1GB up to 16GB total)
• Power Supply:
— 500 Watt (output power), 715 Watt (input power) with two VRM modules
• Remote Power-On
— Remote power-on feature that allows you to power up and shut down your
workstation remotely through the RS232 port.
• Internal Storage Devices:
— Up to two Low-Voltage Differential (LVD) SCSI hard drives.
— One optional ATAPI Slim-line CD drive.
• Standard Networking: Ethernet IEEE 802.3 RJ45, Twisted Pair 10/100 Base T
• Standard I/O: Two GB/sec aggregate I/O bandwidth
— Two low-voltage differntial (LVD) SCSI buses. One dedicated to the two internal disk
drives and one for the external devices (multi-mode).
— Two USB (Universal Serial Bus) connectors (keyboard and mouse)
— Two serial interface connectors (RS-232C)
— Audio connectors (line input, line output, headphone, and microphone)
14Chapter1
LVD Product Information
Product Description
• I/O Expansion Capabilities: 64-bit PCI (Peripheral Connect Interface) slots
— Three PCI-4X slots at 3.3V, 66MHz
• Optional Graphics Cards Currently Supported:
— HP VISUALIZE-fx
10
— HP VISUALIZE-fxe
• Monitors Currently Supported:
— PC compatible monitors that support a minimum resolution of 1024×768 and a
frequency of 75Hz
• Standard Keyboard: The USB connector provides an interface for the keyboard to the
system. This keyboard provides the standard keys found on most PC keyboards.
• Mouse: The HP mouse (USB) has left, middle, and right buttons that function the same
as most mice. For general information on the various cursor shapes associated with
different areas of HP CDE while using a mouse, see the Using Your HP Workstation
document.
Chapter 115
LVD Product Information
Front Panel Components
Front Panel Components
Before powering on your system, you should become familiar with the system unit
controls.
Figure 1-1 shows the front panel components with the bezel attached.
Figure 1-1. System Unit Front Panel Controls With Bezel
CD ROM Bay
Hard Drive BaysPower Switch
System LCD
Figure 1-2. System Unit Front Panel Controls With Bezel Removed
approximately 36 to 49 pounds (16 to 22 kg), depending on the configuration.
Do not attempt to lift it by yourself, or injury may result.
Power Switch
This switch turns the system on and off. When you turn your workstation off, the operating
system automatically executes the shutdown -q command. This prevents any damage to
programs and data on your system disk. Turning the power switch back on again
automatically boots up the HP-UX operating system if your system has been configured to
auto boot.
16Chapter1
LVD Product Information
Front Panel Components
Thumbscrew on the Front Panel
There is one captive thumbscrew near the center of the front panel. Loosening and pulling
toward you with this screw allows the top panel to be removed. The top panel must be in
place or the system will not power up.
Between the LCD panel and the CD ROM drive, there is a threaded hole for an optional
locking screw. The locking screw is included in the bag of miscellaneous parts which comes
with the workstation. This locking screw allows the user to protect his/her workstation
form unwanted entry.
System LCD
The Liquid Crystal Display (LCD) indicator is located on the front panel. The LCD has two
16 characters lines. The LCD displays messages about the state of the system, including
chassis codes. The symbols in Figure 1-3 appear in the LCD if you have the HP-UX 10.20
or 11.0 operating system booted on your system. They represent the different system
activities.
Figure 1-3. LCD Symbols
Operating system running (Heart Beat)
Disk access in progress
Network receive in progress
Network transmit in progress
Chapter 117
LVD Product Information
Front Panel Components
Internal Storage Devices
The J6000 workstations support the following internal storage devices, which are also
located on the front panel, under the bezel:
• Up to two hot-pluggable, Low-Voltage Differential (LVD) hard disk drives
• One ATAPI (IDE) Slim-Line CD drive (optional)
The following subsections describe these internal storage devices.
Hard Disk Drive(s)
The J6000 workstations can support up to two hot-pluggable, Low-Voltage Differential
(LVD) hard disk drives. These hard disk drives are 3.5-inch form factor, 10K RPM devices
which connect to Ultra2 Wide LVD (Low Voltage Differential) SCSI interfaces on the disk
bay backplane. The hard disk drive bays are located on the lower left side of the front
panel, below the CD ROM drive. See Figure 1-1.
The two hard disk drive models currently supported are:
• 18 GB LVD 10K RPM disk drive (Product Number A4998A)
• 36 GB LVD 10K RPM disk drive (Product Number A6013A)
NOTEThe ability to hot plug the hard disk drive(s) requires MirrorDisk/UX
(Product Number B5403BA on HP-UX 10.20, or B2491BA on HP-UX 11.0
ACE 9911).
18Chapter1
LVD Product Information
Front Panel Components
The Hot-Plug Process
The physical aspect of inserting and removing a disk drive is discussed in the document
that comes with the drive. However, the operating system must be prepared for the
insertion or removal of a disk, or unexpected and harmful effects may occur.
There is a significant difference between the terms “hot-pluggable” and “hot-swappable”.
Hot swapping happens at the device level; that is, a hot-swappable device manages
insertion/removal on its own without assistance from HP-UX commands. The disk drive(s)in the J6000 are not hot-swappable; they are merely hot-pluggable. Thus, a manual
software procedure must be done in order to safely remove or insert disk drives while the
system is running.
The hot-plug process allows you to replace a defective disk drive in a high-available system
while it is running.
Replacing a Failed Disk Drive
In the context of replacing a failed disk drive, the system administrator must determine
which disk has failed. Depending on how the system was set up, the identity of the failed
drive may or may not be obvious. This determination may be done in either of two ways:
• Tracking the error message written by the LVM (Logical Volume Manager) to the
system console and/or a log file. For information on LVM commands, see the man pages
for vgchange, lvreduce, vgfgrestore, lvlnboot, lvextend, lvsync, etc.
• If installed, run the diagnostic utility Support Tool Manager (xstm) to determine disk
malfunction.
The removal of a defective disk drive from an active file system is supported through LVM
commands if hot-pluggable disks have been configured into the HP-UX file system with
LVM. To provide high availability, without impact to users, the disks must also be
configured as mirrored disks. Disk-mirroring is accomplished through use of the
MirrorDisk/UX software (HP part number B5403BA); for information on classes, see
http://www.hgp.com/education/courses/h628s.html.
No graphical user interface is currently offered through the System Administrator
Manager (SAM) for doing the required LVM commands because manipulation of the LVM
requires specialized knowledge that only experienced system administrators are expected
to have (see below for details).
Chapter 119
LVD Product Information
Front Panel Components
Hot-Plug Example
The following example describes a particular system problem where the solution is to
replace a hot-plug disk module.
Volume group /dev/vg00 contains the two disks, with the logical volume configuration as
shown:
The system problem for this example is that the disk at hardware address 10/0/13/0.0 has
a head crash, and as a result, is unusable. The steps described in the Hot-Plug Procedure
section below outline a method that can be used to recover from this state.
1. All of the replaced disk’s in-use extents must belong to mirrored logical volumes which
were created with the “strict” option (-s); see the documentation for MirrorDisk/UX.
2. You must have an up-to-date configuration backup file. This is done automatically each
time an LVM command changes LVM configuration.
The default backup file’s path is:
/etc/lvmconf/<
base_vg_name
>.conf
For example,
/etc/lvmconf/vg00.conf
3. The replacement disk must be the same product ID as the replaced one.
NOTEHP often uses different manufacturers for disks having the same product
number. The hot-plug manual procedure will not update the disk driver’s
internal information to that of the replaced disk.
The replacement disk will have the same capacity and block size as the defective disk
because they have the same product number. The only field that could be incorrect is the
string specifying the vendor’s name. This will not affect the behavior of the LVM. If it is
desired to update the manufacturer’s name, the disk’s volume group must be deactivated
and reactivated. See the HP-UX System Administration Tasks manual for details.
20Chapter1
LVD Product Information
Front Panel Components
The Hot-Plug Procedure
These are the steps required to properly hot-plug a disk drive:
Step 1
• Check if the LVM found the physical volume to be defective when the volume group was
activated.
• The “vgchange -a y” command would have printed the following message on the
console:
WARNING:
VGCHANGE:WARNING: COULDN’T ATTACH TP THE VOLUME GROUP
PHYSICAL VOLUME “/DEV/DSK/cXtXdX”
THE PATH OF THE PHYSICAL VOLUME REFERS TO A DEVICE THAT DOES NOT
EXIST, OR IS NOT CONFIGURED INTO THE KERNEL.
• If the status of the “vgchange -v vg02” is unknown, you may check if this occurred by
doing a vgdisplay command:
vgdisplay<
VG name
>
For our example:
vgdisplay /dev/vg00
• If the disk was defective at vgchange time, the following messages
will be printed one or more times:
“/DEV/DSK/cXtXdX”
THE SPECIFIED PATH DOES NOT CORRESPOND TO PHYSICAL VOLUME
ATTACHED TO THE VOLUME GROUP.
VGDISPLAY: WARNING: COULDN’T QUERY ALL OF THE PHYSICAL
VOLUMES
• If you see these messages, the disk was defective at the time the volume group was
activated.
Otherwise, your disk became defective after the vgchange and you must continue with
step 2 of this procedure.
Chapter 121
LVD Product Information
Front Panel Components
Step 2
• Reduce any logical volumes that have mirror copies on the faulty disk so that they no
longer mirror onto that disk (note the -A n option). This will take a several minutes.
lvreduce -m 0 -A n <
LV name
> /dev/dsk/<
hard drive
>
(for 1-way mirroring)
For example:
lvreduce -m 0 -A n /dev/vg00/stand /dev/dsk/c2t5d0
lvreduce -m 0 -A n /dev/vg00/swap /dev/dsk/c2t5d0
lvreduce -m 0 -A n /dev/vg00/ /dev/dsk/c2t5d0
The number of logical volumes that this step needs is variable. For instance, on a mirror
of a root disk you should have at least three logical volumes: /stand (islvol1), /swap (is lvol2), and / (is lvol3). Note that if your root mirror disk dies,
you need to do the following:
— Follow the procedure in the section “Initial System Loader (ISL) Environment” in
the chapter “Boot Console Handler” in this document. At the Main Menu prompt
boot from the good disk.
— Type y at the Interact with ISL prompt and press
— Type this command at the ISL prompt and press
Enter.
Enter: hpux -lq
The -lq option stands for loss of quorum. Once this procedure has been completed the
system will boot.
Step 3
• Replace the faulty disk.
•Doanioscan on the replaced disk to insure that it is accessible and also as a double
check that it is a proper replacement.
For example:
ioscan /dev/dsk/c2t5d0
Step 4
• Restore the LVM configuration/headers onto the replaced disk from your backup of the
LVM configuration:
vgcfgrestore -n <
volume group name
> /dev/rdsk/cxtxd
x
where x is the logical unit number of the disk that has been replaced.
For example:
vgcfgrestore -n /dev/vg00/dev/rdsk/c2t5d0
22Chapter1
LVD Product Information
Front Panel Components
Step 5
• Attach the new disk to the active volume group with the vgchange command.
vgchange -a y /dev/vg00
Step 6
• If the disk is not a mirror of a root disk, then skip this step.
• Run the mkboot command. For example:
mkboot /dev/rdsk/c2t5d0
• Run lvlnboot -R to relink the replaced disk into the Boot Data Reserved Area of all
the Physical volumes in the Volume group.
lvlnboot -R
Step 7
• Run the lvsync command to synchronize the physical extents of each logical volume
specified by logical volume path. Synchronization occurs only on physical extents that
are stale mirrors of the original logical extent.
At this stage, your system should be fully functioning. Use the xstm command to verify.
Chapter 123
LVD Product Information
Front Panel Components
CD ROM Drive (Optional)
As an optional component, the J6000 workstations support one slim-line CD ROM drive
with an ATAPI (IDE) interface.
Figure 1-4 shows the operating features of the CD ROM drive, and Table 1-3 describes
these features.
Figure 1-4. CD ROM Drive Features
Emergency Eject
Button
Disk Tray
Eject Button
Busy Indicator
Light
Table 1-3. CD ROM Drive Features
FeaturePurpose
Busy Indicator• Lights during a data access operation and during a data
transfer.
• Flashes at a one second rate when a disk is loaded.
• Continues to flash if a disk or hardware error is detected.
• Flashes at a three second rate while playing an audio disk.
Emergency
Eject Hole
Eject ButtonOpens the Disk Tray so that a CD ROM disk may be inserted
Disk TrayHolds the CD ROM disk. (Note that this style of CD ROM
Opens the Disk Tray when the end of a paper clip is inserted
into it. Used when the workstation does not have power and
the Disk Tray cannot be opened by pressing the Eject Button.
in it or removed from it. When the drive is in use, press the
Eject Button for more than one second to open the Disk Tray.
The Disk Tray does not open if the workstation power is off.
drive does not use a disk caddy.)
24Chapter1
LVD Product Information
Rear Panel Components
Rear Panel Components
This section describes the following components on the system unit’s rear panel. Figure 1-5
shows the locations of these rear panel components.
NOTETo maintain FCC/EMI compliance, verify that all cables are fully seated and
properly fastened.
Figure 1-5. System Unit Rear Panel Connectors
Power Connector
Serial Port 1
LAN Connector
Serial Port 2
SERIAL
IOIOI
1
LAN TP 10/100
2
USB
SELVD
SCSI
COMPATIBLE CABLE REQUIRED
TOC
USB Connectors
SE/LVD
Audio Connectors
SCSI
Connector
I/O Card Slots
1
2
3
15-Pin D-Sub
Connector
(optional graphics card)
slot 1
slot 2
slot 3
Chapter 125
LVD Product Information
Rear Panel Components
Connectors on the Rear Panel
Power Cord Connector
Plug the power cord into the power cord connector to provide AC power to the workstation.
The J6000 power cord is rated at 15A for a 100–120V source.
RS-232C Serial Connectors
You can attach a variety of pointing devices (such as a mouse or trackball) or peripheral
devices (such as printers, plotters, modems, and scanners) to the RS-232C Serial
Input/Output (SIO) portson this workstation.Consult the documentationthat
accompanies the device for specific information concerning its use.
LAN 10/100 BaseT RJ45 Connector
Your workstation has a built-in Twisted Pair (TP) connector for the 802.3 (ETHERNET) or
10 BaseT/100 BaseT network. Your workstation will automatically select the correct
network setting.
USB Connectors
The two Universal Serial Bus (USB) connectors support only the HP keyboard, mouse, or
hub (D6804A). You can connect the HP keyboard, mouse, or hub in either of the USB
connectors.
The USB mouse and keyboard were shipped with your system unit. The HP hub can be
ordered separately. Note that you should consult the documentation that accompanies
each input device for specific information concerning its use.
Formore information on the Universal Serial Bus, use your browser to access the following
URL:http://www.usb.org.
HP Hub for USB Devices
The HP USB hub provides you with the ability to connect more than two USB devices to
the workstation, as well as the ability to extend the USB device’s cable length. As an
example, you may desire to locate the workstation’s keyboard and mouse at a greater
distance from the workstation, but the keyboard and mouse cables are not long enough. To
increase the cable length, you must make use of the USB hub’s extra cable length and
connect the hub’s cable to one of the two connectors on the back of the workstation. You
then connect the keyboard and mouse into their separate connectors on the USB hub.
26Chapter1
LVD Product Information
Rear Panel Components
SCSI Connectors
There is one Single-Ended/Low-voltage Differential (SE/LVD) SCSI connector on the rear
panel. This connector will support SE SCSI and LVD SCSI, but not both at the same time.
Use the SCSI connector to connect external SCSI devices such as hard disk drives, optical
disk drives, DDS-format tape drives, and CD ROM drives.
Consult the documentation that accompanies each SCSI device for specific information
concerning its use. Also see Appendix C, “SCSI Connections,” for information about
connecting SCSI devices to the J6000 workstations.
CAUTIONDo not mix SE and LVD SCSI devices on the same SCSI bus as this can cause
reduction of device performance.
Audio Connectors
Your workstation has audio input and output capability through external input and output
connectors on the rear panel and through an internal speaker. The rear panel contains the
line input jack, line output jack, headphone jack, and microphone jack connectors.
Figure 1-6. Audio Connectors
Line Input
Line Output
HeadphoneMicrophone
The audio connectors are standard stereo audio mini-jacks. Hewlett-Packard recommends
using gold-plated plugs available through audio retailers for best quality recording and
playback through the external connectors. Table 1-4 on the next page provides a summary
of the audio electrical specifications.
Table 1-4. Audio Electrical Specifications
Frequency Response25 Hz to 20 kHz
Input Sensitivity/Impedance:
– Line in
– Microphone
Chapter 127
2.0 Vpk/47 Kohm
22 mVpk/1 Kohm
LVD Product Information
Rear Panel Components
Table 1-4. Audio Electrical Specifications
Maximum Output
Level/Impedance:
– Line out
– Headphones
– Speaker (internal)
Output Impedance:
– Line out
– Headphones
2.8 Vpp/47 Kohm
2.8 Vpp/50 ohm
5.9 Vpp/48 ohm
619 ohm
118 ohm
28Chapter1
LVD Product Information
Internal Components
Internal Components
This section describes the internal components of the J6000 workstations.
For instructions on how to remove the workstation’s top panel in order to access the PCI
cage, memory cards (DIMMs), CD ROM drive, and hard disk drive(s), as well as
instructions on how to install and remove them, see Chapter 4.
Figure 1-7. Internal Components of the J6000
Memory Slots
16
Processor 0
System Board
The system board in the J6000 contains the PA-RISC microprocessors, memory slots, and
PCI cage as well as connectors to other components.
Processor 1
VRMs
Chapter 129
LVD Product Information
Internal Components
Microprocessors
The J6000 has two PA-8600 microprocessors with operating frequencies of 552 MHz. Each
processor has 0.5 MB instruction cache and a 1.0 MB data cache. Each microprocessor is
cooled by a “turbocooler” which consists of a cylindrical heat sink and an integrated fan.
Power Supply
The power system is comprised of one apparent power factor 500W output power supply.
The maximum power needed by a fully-configured SPU is 715W input power. The
temperature sensor is located in the front of the power supply. The power supply weighs
approximately 8 lbs. (4 kg.). Please note that the system speaker is located in the power
supply.
CAUTIONHP does not recommend and does not support the use of “ferro-active” or
“ferro-resonant” power correction in conjunction with the J6000 workstation.
This type of line conditioner represents an older technology that is not
compatible with the most recent designs in active Power Factor Correction
(PFC) power supplies such as those in the HP J6000 workstations.
“Ferro-active” or “ferro-resonant” line conditioners may cause an increase in
total harmonic distortion and may produce significant and unpredictable
voltage regulation anomalies.
PCI Cage
The PCI (Peripheral Connect Interface) cage is located on the left side of the system board,
behind the CD ROM and hard disk drive bays. There are three PCI-4X, 64 bit, 3.3v, 66
MHz slots which provide I/O expansion capabilities for the workstation. There are no
primary and secondary card slots.
CD ROM and Hard Disk Drive Bays
The J6000 supports two Low-Voltage Differential (LVD) SCSI hard disk drives (one
standard and one optional) and one optional ATAPI slim-line CD ROM drive. The internal
SCSI Bus is independent of the external SCSI Bus.
The hard disk drives are hot-pluggable. More information on this was provided earlier in
this chapter in the Hard Disk Drive section.
Voltage Regulator Modules (VRMs)
NOTEThese VRMs are designed to function ONLY with the J6000 power supply.
The output is 2VDC. The maximum current is 52A.
30Chapter1
LVD Product Information
Monitors
Monitors
The J6000 workstations currently support the following HP monitors:
• 19-inch (18.3-inch viewable) VGA 1600×1200 color monitor (Product Number A4575A)
• 21-inch (19.9-inch viewable) VGA 1600×1200 color monitor (Product Number A4576A)
• 18.1-inch L1800 color flat panel display VGA up to 1280×1024 (Product Number
D5065W)
• 19-inch (18-inch viewable) display VGA 1600x1200 (Product Number D8910W)
• 21-inch (19.8-inch viewable) display VGA 1800x1440 (Product Number D2847A)
• 24-inch (22.5-inch viewable) display VGA 1920x1200 (Product Number A1295A)
Keyboard
The standard USB keyboard (Product Number A4983-604xx – the actual suffix number
depends on the localized version of the keyboard) with the J6000 workstations is a 104-key
input device. It is a PC-104 compatible keyboard.
Mouse
The USB mouse is either a scroll wheel type mouse (Product Number A4983-60101) where
the scroll wheel also serves as the middle button, or a true three-button type mouse
(Product Number A4983-60111).
Site Preparation and Installation
For information on:
• Preparing customers’ sites for the delivery and installation of J6000 workstations, refer
to the HP VISUALIZE J6000 Site Preparation Guide (www.docs.hp.com)
• Installing J6000 workstations, refer to the QuikInstall Poster which came with the
workstation (Part Number A5991-90000) and the Getting Started Guide - HPVISUALIZE J6000 Workstation (Part Number A5990-90020).
For a listing of documentation for the J6000 workstations, see Appendix D.
Chapter 131
LVD Product Information
Monitors
32Chapter1
2Troubleshooting
This chapter provides information about isolating a failing component, known as a Field
Replaceable Unit (FRU), in HP VISUALIZE J6000 workstations.
33
Troubleshooting
Chapter Overview
Chapter Overview
This chapter contains the following main sections:
• Introduction to Troubleshooting
• Flowcharts for Troubleshooting
• Dealing with a Boot Failure
• Identifying LCD-Indicated Conditions
• Running System Verification Tests
• Running ODE-Based Diagnostics
• LED Diagnostics
Introduction to Troubleshooting
To troubleshoot HP VISUALIZE J6000 workstations, you must be familiar with the
HP-UX operating system and be able to start and stop processes. You should also be
familiar with the boot ROM diagnostics, ISL diagnostics, and the Support Tools Manager
online tests, which are described in this chapter.
First note any error or status messages, and then run the power-up boot ROM diagnostics,
known as Selftest. If the Selftest diagnostics fail, replace the FRU that is indicated. If the
tests pass but you still suspect a problem, run the ISL diagnostics and the Support Tools
Manager online tests.
For a complete description of using ISL diagnostics and using the Support Tools Manager,
see the Support Media User’s Manual (Part Number B3782-90176).
Flowcharts for Troubleshooting
The following four figures contain troubleshooting flowcharts you can follow to isolate a
failing Field Replaceable Unit (FRU). Figure 3-1 on the next page contains the main
troubleshooting flowchart. Figures 3-2 through 3-4 on the following pages contain the
flowcharts for console, bootable device, and HP-UX troubleshooting, respectively.
This section contains information for searching for bootable media, stable storage, boot
command notations, supported boot paths and the Intermediate System Loader (ISL)
environment. Some of the examples in this section require the use of the Boot Console
Handler, which is discussed in Chapter 4 of this reference.
Special Considerations
When dealing with boot failures, you will need to consider the scenarios in this section.
• To boot from a known device containing a bootable operating system, type the following
at the prompt:
Main Menu: Enter command > boot
where
device
is the hardware path to the device, specified in Mnemonic Style
device
[Enter]
Notation.
Example: to boot an operating system stored on an IDE CD ROM, go to the Main Menu
of the Boot Console Handler and then type the following command at the prompt:
Main Menu: Enter command > boot ide [Enter]
The operating system on the specified device is used to start the workstation.
• To interact with the Initial System Loader (ISL) before booting the workstation, type
the following at the prompt:
Main Menu: Enter command > boot
device
[Enter]
You are prompted: Interact with ISL (Y or N) > y [Enter]
Answering yes (y) causes the ISL to be loaded from the specified device. After a short
time, the following prompt appears on the screen:
ISL>
ISL is the program that actually controls the loading of the operating system. By
interacting with ISL, you can choose to load an alternate version of the HP-UX
operating system.
For example, if the usual kernel (/stand/vmunix) on the root disk has become
corrupted, boot the workstation from the backup kernel (/stand/vmunix.prev)by
typing the following at the ISL> prompt:
ISL> hpux /stand/vmunix.prev [Enter]
• To find the location of the bootable operating systems on the various media in the file
system, use the searchiplcommand. See the next subsection, “Searching for
Bootable Media.”
Chapter 239
Troubleshooting
Dealing with a Boot Failure
Searching for Bootable Media
To list all devices that contain bootable media, go to the Main Menu of the Boot Console
Handler, and then type the following at the prompt:
Main Menu: Enter command > search ipl [Enter]
The search command searches all buses. The search may turn up more devices than there
are lines on the display. If you are using a text terminal, you can control the progress of the
search from the terminal’s keyboard by doing any of the following:
• To temporarily suspend the search, press [Ctrl]-[S].
• To continue the search, press [Ctrl]-[Q].
• To halt the search, press any other key.
These flow-control commands do not work with a bitmapped display, but such a display can
show more than forty lines of text, so you are unlikely to need them.
To search for devices of just one type that actually contain bootable media, go to the Main
Menu of the Boot Console Handler, and then type the following at the prompt:
Main Menu: Enter command > search ipl
where
device_type
is one of the following:
device_type
[Enter]
• fwscsi is the internal, Ultra2 Wide LVD (Low Voltage Differential) SCSI bus.
• scsi is the external SE/LVD SCSI bus.
• lan is all connections to the built-in LAN.
• ide is the built-in CD ROM drive.
n
• pci
is an optional SCSI interface in slot numbern.
Stable Storage
Stable Storage is non-volatile memory associated with the PA-RISC processor module.
Stable Storage is used by the processor (CPU) to store device path information, the state of
the boot flags, HPMC error information, and operating system initialization data.
Boot Command Notations
The boot command supports the following two notations:
• Mnemonic
• Path number
Type help scsi or help lan for more information on the boot path parameters.
Here are examples of mnemonic notation:
• boot with no parameters selects the primary boot path in stable storage.
• boot with the alternate or alt parameter selects the alternate boot path in stable
storage.
40Chapter2
Troubleshooting
Dealing with a Boot Failure
Here is an example of path number notation:
• boot p1[Enter] attempts to boot from the second path in a list generated by a
previous search command.
Supported Boot Paths
SCSI devices are bootable when connected to any SCSI port on the system. Workstations
can only boot from the built-in LAN port. The workstation can be booted from the CD ROM
drive for software installation.
Intermediate System Loader (ISL) Environment
The ISL environment provides the means to load the operating system (HP-UX)
environment. The ISL environment also provides an offline platform to execute diagnostic
and utility programs from a boot device when HP-UX does not load.
The ISL program is the first program loaded into main memory from an external media
(LAN, disk, or tape) and launched by the initial program loader (IPL) routine during the
Boot Administration environment.
The ISL environment provides the following capabilities:
• Execute user-entered commands to modify boot device paths and boot options in stable
storage.
• Run off-line diagnostic programs and utilities.
• Provide automatic booting of the HP-UX operating system after power-on or reset.
Chapter 241
Troubleshooting
Identifying LCD-Indicated Conditions
Identifying LCD-Indicated Conditions
This workstation uses a 2-line LCD, with up to 16-characters per line, to display
firmware/operating system progress codes. These codes are referred to as chassis codes.
The information displayed on the LCD has the following format:
XXX YYYY: ZZZZZZ(Line 1)
AAAAAAAAAAAAAAAA(Line 2)
Where:
XXXThree-character Operating Status
YYYYFour-digit hex code identifying the code module being executed
ZZZZZZSix-digit FRU descriptor
AAAAAAAAAAAAAAAADiagnostic message of up to 16 characters
The 3-character operating status can be one of the following:
FLT (fault)
TST (test)
INI (initialize)
SHU (shutdown)
WRN (warning)
RUN (running)
A hardware error has been detected
Hardware being tested
Hardware being initialized
System being shutdown
A non-optimal operating condition exists
The operating system is running
Selftest Failures
Chassis codes are the key to debugging selftest errors. If a failure is found during selftest,
chassis codes are displayed in the system LCD. To debug a failure:
1. In Table 3-1 starting on the next page, find the chassis code listed on the LCD.
2. In the Boot Console Handler, use the Service Menu’s pim, pdt, and ChassisCodes
commands to get additional information about the failure.
The FRU column in Table 3-1 shows messages printed on the LCD that refer to system
FRUs. All codes are listed in numeric order.
42Chapter2
Troubleshooting
Identifying LCD-Indicated Conditions
Memory Failures
The J6000 workstations require special Memory Page Deallocation to be implemented.
This feature allows the workstation to provide information to the operating system about
memory failures.
HP-UX uses this information to map out failing memory areas and continue normal
operation. You can check the Memory Page Deallocation Table (PDT) using the pdt
command in the Service menu of the Boot Console Handler (refer to Chapter 4). If a failing
DIMM is replaced, use the command pdt clear in the Service Menu to clear out the PDT.
Chapter 243
Troubleshooting
Identifying LCD-Indicated Conditions
Chassis Codes
Table 3-1 lists all of the chassis codes for the J6000 workstations.
Table 2-1. Chassis Codes for J6000 Workstations
OstatCodeFRUMessageDescription
FLT1n01SYS BDHPMC occurredCPU n detected an unexpected HPMC.
FLT1n02SYS BDpowerfail intrptCPU n detected an unexpected power fail
interrupt.
FLT1n03SYS BDrecvry cntr trapCPU n detected an unexpected recovery
counter trap.
FLT1n04SYS BDexternal intrrptCPU n detected an unexpected external
interrupt.
FLT1n05SYS BDLPMC occurredCPU n detected an unexpected LPMC.
FLT1n06SYS BDITLB mis/Ipg fltCPU n detected an unexpected ITLB miss
or instruction page fault.
FLT1n07SYS BDI mem prot trapCPU n detected anunexpected instruction
memory protection trap.
FLT1n08SYS BDillegal inst trpCPU n detected an unexpected illegal
instruction trap.
FLT1n09SYS BDbreak instr trapCPU n detected an unexpected break
instruction trap.
FLT1n0ASYS BDprivilgd op trapCPU n detected an unexpected privileged
operation trap.
FLT1n0BSYS BDprivlgd reg trapCPU n detected an unexpected privileged
register trap.
FLT1n0CSYS BDoverflow trapCPU n detected an unexpected overflow
trap.
FLT1n0DSYS BDconditional trapCPU n detected an unexpected conditional
trap.
FLT1n0ESYS BDassist exep trapCPU n detected an unexpected assist
exception trap.
FLT1n0FSYS BDDTLB mis/Dpg fltCPU n detected an unexpected DTLB
miss or data page fault.
FLT1n10SYS BDnon-acc ITLB misCPU n detected an unexpected non-access
ITLB miss fault.
FLT1n11SYS BDnon-acc DTLB misCPU n detected an unexpected non-access
DTLB miss or data page fault.
44Chapter2
Troubleshooting
Identifying LCD-Indicated Conditions
Table 2-1. Chassis Codes for J6000 Workstations
OstatCodeFRUMessageDescription
FLT1n12SYS BDdata mem prot trCPU n detected an unexpected data
memory protection trap.
FLT1n13SYS BDdata mem brk trpCPU n detected an unexpected data
memory break trap.
FLT1n14SYS BDTLB dirty bit trCPU n detected an unexpected TLB dirty
bit trap.
FLT1n15SYS BDpage refrnce trpCPU n detected an unexpected page
reference trap.
FLT1n16SYS BDassist emul trapCPU n detected an unexpected assist
emulation trap.
FLT1n17SYS BDhi-priv xfer trpCPU n detected an unexpected
higher-privilege transfer trap.
FLT1n18SYS BDlo-priv xfer trpCPU n detected an unexpected
lower-privilege transfer trap.
FLT1n19SYS BDtaken branch trpCPU n detected an unexpected
taken-branch trap.
FLT1n1ASYS BDdata mem acc rtsCPU n detected an unexpected data
memory access rights trap.
FLT1n1BSYS BDdata mem prot IDCPU n detected an unexpected data
memory protection ID trap.
FLT1n1CSYS BDunalign data refCPU n detected an unexpected unaligned
data reference trap.
FLT1n1DSYS BDperf mon intrrptCPU n detected an unexpected
performance monitor interrupt.
TST1n20SYS BDCPUn basic testCPU n is starting its basic operations
self-test.
TST1n21SYS BDCPUn alu testCPU n is starting its arithmetic and
logical unit self-test.
TST1n22SYS BDCPUn branch testCPU n is starting its branch instruction
self-test.
TST1n23SYS BDCPUn arith condCPU n is starting its arithmetic condition
self-test.
TST1n24SYS BDCPUn bit opersCPU n is starting its bit operation
instruction self-test.
TST1n25SYS BDCPUn cntrl regsCPU n is starting its control register
self-test.
Chapter 245
Troubleshooting
Identifying LCD-Indicated Conditions
Table 2-1. Chassis Codes for J6000 Workstations
OstatCodeFRUMessageDescription
TST1n26SYS BDCPUn ext intrptCPU n is starting its external interrupt
self-test.
TST1n27SYS BDCPUn itimer testCPU n is starting its interval timer
self-test.
TST1n28SYS BDCPUn multi-mediaCPU n is starting its multi-media
instructions self-test.
TST1n29SYS BDCPUn shadow regCPU n is starting its shadow register
self-test.
TST1n2ASYS BDCPUn diagnse regCPU n is starting its diagnose register
self-test.
TST1n2BSYS BDCPUn rdr testCPU n is starting its remote diagnose
register self-test.
TST1n2CSYS BDCPUn bypass testCPU n is starting its integer bypass
operation self-test.
TST1n30SYS BDCPUn start estCPU n is starting its early (pre-memory)
self-tests.
WRN1n31SYS BDCPUn skip estCPU n is bypassing its early self-tests to
save time.
FLT1n32SYS BDCPUn bad tst modCPU n detected an unsupported system
mode.
INI1n3CSYS BDCPUn initializeCPU n is initializing after self-tests.
TST1n3ESYS BDCPUn exit estCPU n finished its early self-tests.
TST1nA0SYS BDCPUn fpu testsCPU n is starting its floating-point unit
self-tests.
TST1nA1SYS BDCPUn fpu reg tstCPU n is starting its floating-point
register self-test.
TST1nA2SYS BDCPUn fpu instCPU n is starting its floating-point
instruction self-test.
TST1nA3SYS BDCPUn fpu trapsCPU n is starting its floating-point trap
self-test.
TST1nA4SYS BDCPUn fpu miscCPU n is starting its floating-point
miscellaneous operations self-test.
TST1nA5SYS BDCPUn fpu bypassCPU n is starting its floating-point
bypassing self-test.
TST1nB1SYS BDCPUn TLB RAM tstCPU n is starting its TLB register
self-test.
46Chapter2
Troubleshooting
Identifying LCD-Indicated Conditions
Table 2-1. Chassis Codes for J6000 Workstations
OstatCodeFRUMessageDescription
TST1nB2SYS BDCPUn TLB transCPU n is starting its TLB translation
self-test.
FLT1nBASYS BDmonarch CPU
FLT1nBBSYS BDbad CPUn numberThe CPU identifier was out of range.
FLT1nBFSYS BDCPUn halt bootBootstrap failure--machine halted.
INI1nCASYS BDCPUn sys bus arbMonarch CPU is initializing the system
WRN1nCDSYS BDCPUn deconfigCPU n deconfigured itself.
WRN1nCESYS BDCPUn extinguishPDC_PROC halted CPU n.
FLT1nCFSYS BDslaven failedSlave CPU n failed self-test.
WRN1mDsSYS BDslaves deconfigMonarch CPU m deconfigured slave CPU
WRN1nEFSYS BDCPUn slftst warnCPU n detected a non-fatal error during
WRN1mFsSYS BDmonm stop slave
INI1nFCSYS BDCPUn sync’ingCPU n is synchronizing with the rest of
INI1nFDSYS BDCPUn stat wd tstCPU n is testing the system status word.
FLT1nFFSYS BDmonarchn selftstMonarch CPU n failed self-test.
fail
The monarch CPU failed.
bus arbitration.
s.
its self-tests.
s
Monarch CPU m halted slave CPU s.
the system.
TST2n20SYS BDCPUn icache RAMCPU n is starting its instruction cache
RAM self-test.
FLT2n25SYS BDCPUn ic ld d errCPU n detected a data error during data
cache load.
FLT2n26SYS BDCPUn ic ld t errCPU n detected a tag error during data
cache load.
TST2n30SYS BDCPUn icache tagCPU n is starting its instruction cache tag
self-test.
TST2n40SYS BDCPUn icache parCPU n is starting its instruction cache
parity detection self-test.
TST2n50SYS BDCPUn dc stor queCPU n is starting its data cache store
queue self-test.
FLT2n51SYS BDCPUn dc st q errCPU n detected an error during its data
cache store queue self-test.
TST2n70SYS BDCPUn dcache RAMCPU n is starting its data cache RAM
self-test.
Chapter 247
Troubleshooting
Identifying LCD-Indicated Conditions
Table 2-1. Chassis Codes for J6000 Workstations
OstatCodeFRUMessageDescription
TST2n80SYS BDCPUn dcache tagCPU n is starting its data cache tag
self-test.
TST2n90SYS BDCPUn dcache ECCCPU n is starting its data cache ECC
self-test.
FLT2BADSYS BDassertion failA firmware assertion failed.
TST3n00SYS BDROM checksum tstMonarch CPU n is testing the boot ROM
integrity.
FLT3n00SYS BDROM checksum BADThe boot ROM failed checksum.
INI3n00SYS BDROM checksum okThe boot ROM passed checksum.
TST3n01SYS BDPDH control testMonarch CPU n is testing PDH control
register.
INI3n01SYS BDPDH control initMonarch CPU n is initializing the PDH
control register.
FLT3n01SYS BDPDH control errMonarch CPU n detected an error in the
PDH control register.
TST3n02SYS BDscratch RAM testMonarch CPU n is testing scratch RAM.
INI3n02SYS BDscratch RAM okThe scratch RAM test failed.
FLT3n02SYS BDscratch RAM badThe scratch RAM test passed.
WRN3n03SYS BDstbl st read errCPU n detected a non-fatal error reading
the stable store.
FLT3n03SYS BDstbl st read errCPU n detected a non-fatal error reading
the stable store.
INI3nC4SYS BDclearing EEPROMMonarch CPU n is clearing the EEPROM.
INI3nD4SYS BDdeflting EEPROM2Monarch CPU n is initializing the
EEPROM to system defaults.
WRN3n04SYS BDEEPROM write errCPU n detected a non-fatal error writing
the EEPROM.
FLT3n04SYS BDEEPROM write errCPU n detected a fatal error writing the
EEPROM.
FLT3n05SYS BDEEPROM wrt limitCPU n detected a fatal error writing the
EEPROM.
WRN3n06SYS BDEEPROM read errCPU n detected a non-fatal error reading
the EEPROM.
FLT3n06SYS BDEEPROM read errCPU n detected a fatal error reading the
EEPROM.
48Chapter2
Troubleshooting
Identifying LCD-Indicated Conditions
Table 2-1. Chassis Codes for J6000 Workstations
OstatCodeFRUMessageDescription
INI3n07SYS BDCPUn invoke LDBCPU n is starting the low-level debugger.
FLT3n09SYS BDbad sys mde byteCPU n detected an unsupported system
mode.
WRN3n1ASYS BDhversion mismtchStable store hardware version doesn’t
match system.
TST3n1BSYS BDchck model strngCheck model string with version in stable
store.
WRN3n1BSYS BDmodel str msmtchModel string doesn’t match that in stable
store.
FLT3n1BSYS BDfatal model strError reading model string from stable
TST3nBCIO BDtest sys clocksCPU n is verifying processor clocks with
INI3nBCSYS BDinit sys clocksCPU n has initialized the processor clocks.
FLT3nBCIO BDRTC tick timeoutThereal-time clock is ticking too slowly or
TST3nCDSYS BDcheck defaultsCPU n is initializing stable store values to
INI3nCDSYS BDinit defaultsCPU n finished initializing stable store
FLT3nCDSYS BDinit EEPROM errCPU n detected an error writing to stable
FLT3nECSYS BDbad sys configCPU n detected an illegal CPU board
FLT3nF4SYS BDEEPROM boot limtCPU n detected a fatal error writing the
s
CPU n is awaiting the low-level debugger
for s more seconds.
the real-time clock.
not at all.
system defaults.
values.
store.
configuration.
EEPROM.
FLT3nFCSYS BDbad sys bd idCPU n cannot identify CPU board.
TST4n00SYS BDCPUn start lstCPU n is starting its late (with memory)
self-tests.
Chapter 249
Troubleshooting
Identifying LCD-Indicated Conditions
Table 2-1. Chassis Codes for J6000 Workstations
OstatCodeFRUMessageDescription
WRN4n01SYS BDCPUn skip lstCPU n is bypassing its late self-tests to
save time.
TST4n0ESYS BDCPUn exit lstCPU n finished its late self-tests.
TST4n20SYS BDCPUn lst erly stCPU n is re-executing some of its early
self-tests from system memory.
TST4n21SYS BDCPUn lst basicCPU n is re-executing its basic operations
self-test.
TST4n22SYS BDCPUn lst aluCPU n is re-executing its arithmetic and
logic unit self-test.
TST4n23SYS BDCPUn lst branchCPU n is re-executing its branch
instruction self-test.
TST4n24SYS BDCPUn lst arth cdCPU n is re-executing its arithmetic
conditions self-test.
TST4n25SYS BDCPUn lst bit opsCPU n is re-executing its bit operations
self-test.
TST4n26SYS BDCPUn lst ctl regCPU n is re-executing its control register
self-test.
TST4n27SYS BDCPUn lst ext intCPU n is re-executing its external
interrupt self-test.
TST4n28SYS BDCPUn lst itimerCPU n is re-executing its interval timer
self-test.
TST4n29SYS BDCPUn lst mltimedCPU n is re-executing its multi-media
instructions self-test.
TST4n2ASYS BDCPUn lst shadowCPU n is re-executing its shadow register
self-test.
TST4n2BSYS BDCPUn lst dg regsCPU n is re-executing its diagnose
register self-test.
TST4n2CSYS BDCPUn lst rdrsCPU n is re-executing its remote diagnose
register self-test.
TST4n2DSYS BDCPUn lst bypassCPU n is re-executing its integer bypass
operation self-test.
TST4n30SYS BDCPUn cache byteCPU n is starting its data cache sub-word
operations self-test.
TST4n40SYS BDCPUn cache flushCPU n is starting its cache flush self-test.
TST4n50SYS BDCPUn icache missCPU n is starting its instruction cache
miss self-test.
50Chapter2
Troubleshooting
Identifying LCD-Indicated Conditions
Table 2-1. Chassis Codes for J6000 Workstations
OstatCodeFRUMessageDescription
TST4n60SYS BDCPUn dcache missCPU n is starting its data cache miss
self-test.
FLT5n00SYS BDunknown bus errCPU n detected an unknown error on the
system bus (Runway).
FLT5n02SYS BDpath err assertdCPU n detected a path error on the
system bus (Runway).
FLT5n04SYS BDdata parity errCPU n detected a data, address, or control
parity error on the system bus (Runway).
FLT5n07SYS BDRunway dir errorCPU n detected a directed error on the
system bus (Runway).
FLT5n08SYS BDRunway broad errCPU n detected a broadcast error on the
system bus (Runway).
FLT5n0ASYS BDillegal responseCPU n received data that did not match
any outstanding data request.
FLT5n0BSYS BDbus timeoutCPU n timed out before receiving
requested data. The responder is logged in
the system responder address.
FLT5n0CSYS BDCPU sync failureCPU n’s synchronizer detected a rule
violation on the system bus (Runway).
INI7000DIMMstart DIMM scanStart looking for installed DIMMs.
INI7002SYS BDinit mem tablesInitialize memory data structures.
FLT7004SYS BDmem plt upd failError updating memory platform data.
FLT7005DIMMinsufficient memInsufficient memory detected to continue.
TST7010DIMMcheck DIMM orderStart memory DIMM order check.
WRN7011DIMMskip DIMM ord ckBypass memory DIMM order check.
FLT7012DIMMDIMM order errorMemory DIMMs are not in the proper
order.
FLT7013DIMMDIMM order errorMemory DIMMs are not in the proper
order. As a result, the system cannot
access one or more DIMMs and has
deallocated all inaccessible DIMMs.
WRN7017DIMMskip mem pair ckBypass memory DIMM set check.
FLT701FDIMMno memory foundMemory scan couldn’t find any DIMMs.
Chapter 251
Troubleshooting
Identifying LCD-Indicated Conditions
Table 2-1. Chassis Codes for J6000 Workstations
OstatCodeFRUMessageDescription
TST7020SYS BDsearch for IMMTry to find a single memory bank to use
for the initial memory module.
TST703sDIMMDIMMs IMM vrfyDIMM s was the initial memory module
last boot. Verify it still works.
FLT704sDIMMDIMMs IMM failDIMM s failed the initial memory module
test.
TST705sDIMMDIMM
INI706sDIMMDIMMs is IMMDIMM s chosen as initial memory module.
INI70F0DIMMDIMM scan doneMemory DIMM scan complete.
TST7100SYS BDmem register tstStart testing registers in memory
WRN7101SYS BDskip mem reg tstBypass the memory controller register
FLT7102SYS BDmem addr reg tstFirmware detected an error in the
FLT7103SYS BDmem mbat reg tstFirmware detected an error in the
FLT7104SYS BDmem reg tst failFirmware detected an error in the
FLT7105SYS BDmem err reg testFirmware detected an error in the
FLT7106SYS BDmem err clr failFirmware was unable to clear the error
s IMM test
TestDIMM in slot s as the initial memory
module.
controller.
test.
memory controller address registers.
memory controller bank registers.
memory controller memory registers.
memory controller error registers.
registers after testing.
INI7200DIMMstrt DIMM detectStart the Serial Presence Detection (SPD)
to search for memory DIMMs.
INI7201DIMMDIMM detectx%SPD is x% finished.
WRN7202SYS BDskip DIMM detectBypass Serial Presence Detection.
FLT7203DIMMunsupp DIMM typeSPD found an unsupported DIMM type.
FLT7204DIMMSPD fatal errorSPD detected an unexpected, fatal error.
INI7205DIMMadd HP DIMM typeNew HP manufactured DIMM type added
to tables.
INI7206DIMMnon-HP DIMM typeNew non-HP DIMM type added to tables
(use at own risk).
52Chapter2
Troubleshooting
Identifying LCD-Indicated Conditions
Table 2-1. Chassis Codes for J6000 Workstations
OstatCodeFRUMessageDescription
FLT7207DIMMDIMM table fullThe DIMM table is full--cannot add new
type.
FLT7208DIMMno DIMMs foundSPD didn’t find any memory DIMMs.
INI721sDIMMis DIMMs inst?SPD is checking memory slot s.
INI722sDIMM???? DIMM in
INI723sDIMM128M DIMM in
INI724sDIMM256M DIMM in
INI725sDIMM512M DIMM in
FLT72AsDIMMDIMMs checksumDIMM in slot s failed SPD checksum and
FLT72CsDIMMDIMMs mismatchDIMM in slot s didn’t match the other in
FLT72DsDIMMDIMMs load errMemory DIMMs are not in the proper
INI7300SYS BDmem config startStarting main memory configuration.
TST7301SYS BDcheck mem configChecking for memory configuration
TST7600DIMMdest mem testStarting the destructive memory test.
WRN7601DIMMmem init onlySkip the test, just initialize memory to
save time.
TST7602DIMMtst 1st mem pageStarting 3-pass test of first memory page.
TST7603DIMMtst rest of memStarting 3-pass test of the rest of memory.
TST7604DIMMstart 1st passStarting 1st pass of memory test (write
pseudorandom sequence).
TST7605DIMM1st pass
TST7606DIMMstart 2nd passStarting 2nd pass of memory test (verify
TST7607DIMM2nd pass
TST7608DIMMstart 3rd passStarting 3rd pass of memory test (verify
TST7609DIMM3rd passx%Third pass is x% complete.
TST760ADIMMstart mem initStarting memory initialization. (Initialize
TST760BDIMMmem init
WRN760CDIMMrepeat dest testRe-execute destructive test for hardware
x%
x%
x%
First pass is x% complete.
pseudorandom sequence, write inverse).
Second pass is x% complete.
inverse sequence).
to zero to set ECC.)
Memory initialization is x% complete.
troubleshooting.
FLT760DDIMMmem code cpy errFirmware tried to copy code from ROM to
memory, but the copy didn’t match the
original.
FLT7610DIMMECC wrt/read errWriting and reading back good data
caused memory ECC error.
54Chapter2
Troubleshooting
Identifying LCD-Indicated Conditions
Table 2-1. Chassis Codes for J6000 Workstations
OstatCodeFRUMessageDescription
FLT7611DIMMECC single dataMemory ECC test failed to detect
single-bit data error.
FLT7612DIMMECC single ECCMemory ECC test failed to detect
single-bit ECC error.
FLT7613DIMMECC multipl dataMemory ECC test failed to detect
multiple-bit data error.
FLT7614DIMMECC multpl signlMemory ECC test failed to signal
multiple-bit error.
FLT7800SYS BDmem err summaryPrinting memory error summary word to
RS-232.
FLT7801SYS BDbus ctrl par errSystem bus (Runway) control parity error
detected.
FLT7802SYS BDbus addr par errSystem bus (Runway) address parity error
detected.
FLT7803SYS BDbus data par errSystem bus (Runway) data parity error
detected.
FLT7804SYS BDmem out of rangeMemory access outside configured
memory space.
FLT7805SYS BDbus broadcst errSystem bus (Runway) broadcast error
detected.
FLT7806SYS BDmem addr par errMemory bus address parity error
detected.
FLT7807SYS BDmem ctlr stat wdPrinting memory controller status word to
RS-232.
FLT781sDIMMDIMMs uncor errUncorrectable ECC error detected in
DIMM s.
FLT782sDIMMDIMMs corr errDIMM s is bad and needs replacing.
FLT783sDIMMReplace DIMM
FLT7840SYS BDunexpected HPMCUnexpected HPMC detected.
FLT7841SYS BDmem status invldMemory error status word is invalid.
FLT7842SYS BDmem summ invalidMemory summary word is invalid.
s
Correctable ECC error detected in DIMM
s.
FLT7843SYS BDfwd prog invalidMemory forward progress word is invalid.
FLT7844SYS BDmem HPMC summ wdPrinting memory error summary word to
RS-232.
Chapter 255
Troubleshooting
Identifying LCD-Indicated Conditions
Table 2-1. Chassis Codes for J6000 Workstations
OstatCodeFRUMessageDescription
FLT7845SYS BDmem ctlr stat wdPrinting memory controller status word to
WRN80F6EXT IOboot read errorCannot load IODC entry_io for boot
device.
WRN80F7EXT IOboot IO errorError detected during boot device I/O.
WRN80F8EXT IOinvalid boot devInvalid boot device class; bad IODC?
WRN80FCEXT IOinvalid boot devUnexpected error; bad IODC?
INI8800IOCARDPCI BusWlk startStarting PCI bus and device discovery.
INI88r1IOCARDPCI Rope r walkStarting PCI bus and device discovery on
Rope r.
INI8802IOCARDPCI BusWalk donePCI bus and device discovery complete.
INI8803SYS BDPCI alloc doneDone allocating address space for PCI
devices.
INI8804SYS BDPCI config doneDone configuring PCI devices.
FLT881rIO BDR2PCIr not foundRope-to-PCI bridge r not found.
WRN882
FLT883rIO BDRoper config errRope r configuration failed.
INI884
FLT884
INI8850SYS BDearly rope0 initInitializing rope 0 for early RS-232
WRN8A04EXT IONo USB keyboardCannot re-establish communications with
the USB keyboard.
TST8C06EXT IOPCI BIST testRunning PCI Built-In Self-Test
WRN8C07EXT IOPCI BIST errorPCI Built-In Self-Test failed.
WRN8C08SYS BDPCI alloc errorPCI address space allocation failed.
WRN8C09IO BDPCI mem mngr errMemory allocation for PCI device failed.
WRN8C0AEXT IOPCI mem type errPCI device requested invalid memory
type.
WRN8C0BIO BDPCI max bus dpthPCI bus depth exceeded maximum
supported depth.
WRN8C0CEXT IOPCI dev not cnfgUnable to configure PCI device.
WRN8C0FIO BDdev tree ovrflowData space for PCI devices is full.
WRN8DECIO BDinit LAN SROMInitializing the core LAN serial EPROM.
SHU8DECIO BDresetting systemRestarting system after core LAN
initialization.
FLT8E10IO BDPARALEL port cfgParallel port configuration failed.
FLT8E11IO BDSERIAL1 port cfgSerial 1 port configuration failed.
FLT8E12IO BDSERIAL2 port cfgSerial 2 port configuration failed.
FLT8E13IO BDFLOPPY drive cfgFloppy drive configuration failed.
FLT8E20IO BDbad USB port cfgUSB port configuration failed.
WRN9001EXT IOno console foundSearch for console display device failed.
INI9151IO BDinit SERIAL_1Initializing serial 1 port as console
display.
INI9152IO BDinit SERIAL_2Initializing serial 2 port as console
display.
INI915FIO BDinit unknown devInitializing unknown device as console
display.
INI916sEXT IOinit PCI slot
s
Initializing PCI device in slot s as console
display.
INI91DBIO BDinit SERIAL_LDBInitializing serial LDB port as console
display.
INI9C51IO BDconsol is SER_1Console display is on serial port 1.
58Chapter2
Troubleshooting
Identifying LCD-Indicated Conditions
Table 2-1. Chassis Codes for J6000 Workstations
OstatCodeFRUMessageDescription
WRN9C51IO BDbad init SERIAL1Serial port 1 failed to initialize as a
console device.
INI9C52IO BDconsol is SER_2Console display is on serial port 2.
INI9160EXT IObuiltin GRAPHICSInitializing built-in graphics as console
display.
INI9C52IO BRDconsol is SER_2Console display is on serial port 2.
WRN9C52IO BDbad init SERIAL2Serial port 2 failed to initialize as a
console device.
INI9C6sEXT IOconsol is GRAPH
WRN9C6sEXT IObad PCI slot
INI9C8tEXT IOcnfg mon type
WRN9C8tEXT IOmon type t failFailedto configure console to monitor type
INI9CDBIO BDconsl is SER_LDBConsole display is on serial LDB port.
WRN9CDBIO BDbad init SER_LDBSerial LDB port failed to initialize as a
FLTA088IO BDconsl path faultUnable to boot--no console device found.
WRNA008EXT IOno boot deviceUnable to boot--no bootable device found.
WRNA0BDEXT IOdevice not readyBoot device not ready--operation may be
FLTA0FFEXT IOunknown launchUnable to boot. Explanation may appear
WRNA50FEXT IOinit pri pth errUnable to boot from primary boot device.
s
Console display is on graphics card in PCI
slot s.
s
Graphics in PCI slot s failed to initialize
as a console device.
t
Set graphics console to monitor type t.
(Seen when cycling through types.)
t.
console device.
retried.
on console.
WRNA70FEXT IOinit otr pth errUnable to boot from non-primary boot
device.
INIC10mSYS BDCPUm is monarchCPU m was chosen as the monarch
processor. (All other CPUs are slaves.)
INIC30mSYS BDmonarchm testCPU m finished the monarch-only tests
and system initialization.
INIC30CSYS BDmnrch slv chckThe monarch CPU is checking whether
the slaves are in the correct rendezvous.
Chapter 259
Troubleshooting
Identifying LCD-Indicated Conditions
Table 2-1. Chassis Codes for J6000 Workstations
OstatCodeFRUMessageDescription
INIC3FFSYS/IOlate monarch tstThe monarch CPU is starting the late
(post-memory) monarch-only tests.
FLTC3FFSYS/IOlate monarch fltThe late (post-memory) monarch-only
INIC540EXT IOinit pri pathAutoboot is trying to boot from primary
boot device.
INIC580EXT IOload IPL pri pthLoading IPL from primary boot device.
WRNC5F0EXT IOerr read pri IPLError loading IPL from primary boot
device.
FLTC5F0EXT IOpri IPL faultError loading IPL from primary boot
device.
WRNC5F1EXT IOerr read pri IPLCannot load IPL from primary boot
device--load address invalid.
WRNC5F2EXT IOerr read pri IPLCannot load IPL from primary boot
device--file is not IPL image.
WRNC5F3EXT IOerr read pri IPLCannot load IPL from primary boot
device--IPL image size invalid.
WRNC5F4EXT IOerr read pri IPLCannot load IPL from primary boot
device--IPL entry point address invalid.
WRNC5F8EXT IOerr read pri IPLCannot load IPL from primary boot
device--IPL image checksum failed.
INIC5FF<blank>launch pri IPLBooting from primary boot path.
INIC642EXT IOinit kybrd conslTry to initialize USB keyboard.
FLTC642EXT IOkeyboard errorAn error was detected trying to access the
keyboard.
WRNC643EXT IOkeyboard reinitKeyboard was re-initialized.
WRNC64FEXT IOreset montr typeThe console device failed to initialize with
the given monitor type. Try again with
type 1.
60Chapter2
Identifying LCD-Indicated Conditions
Table 2-1. Chassis Codes for J6000 Workstations
OstatCodeFRUMessageDescription
TSTC680SYS BDbuiltin graphicsLook for built-in graphics card.
Troubleshooting
TSTC68sSYS BDtest graph in
INIC68sSYS BDinit graph in sSuccessfully initialized graphics card in
INIC68
WRNC68
WRNC68sSYS BDfail graph in
INIC740EXT IOinit other pathAutoboot is trying to boot from
INIC780EXT IOld IPL othr pathLoading IPL from non-primary boot
WRNC7F0EXT IOother IPL faultError loading IPL from non-primary boot
WRNC7F1EXT IObad alt IPL readCannot load IPL from non-primary boot
WRNC7F2EXT IObad alt IPL readCannot load IPL from non-primary boot
WRNCB73SYS BDTOC occurredA Transfer of Control caused entry to
PDCE_CHECK (the firmware trap
handler).
FLTCB9rIO BDError on roperAn error was detected on rope r.
FLTCB99SYS BDseed IVA handlerPDC_SEED_ERROR triggered an HPMC.
FLTCB9ASYS BDHPMC overwriteFirmware is overwriting PIM data from a
previous HPMC.
OFFCBA1SYS BDAIOC int dat errI/O controller internal error.
OFFCBA2IO BDEtoA rope perrParity error between I/O controller and
Rope-to-PCI bridge.
OFFCBA3SYS BDaccess invld TLBAn invalid I/O TLB entry was accessed.
OFFCBA4IO BDEtoA rp cmd perrCommand parity error between I/O
controller and Rope-to-PCI bridge.
OFFCBA5IO BDCDF timeoutRope Command/Data FIFO is backed up.
OFFCBA6IO BDR2PCI resp tmoutRope-to-PCI bridge timed out. Could be a
failure of the PCI card, rope, or R2PCI
bridge.
OFFCBA7IO BDUnknown AIOC errUnknown I/O controller error.
OFFCBB1IO BDPCI timeoutA PCI card requested the bus but failed to
use it.
OFFCBB2IO BDPCI timeout; OVMore than once aPCI card requested the
OFFCBB6IO BDPCI data req errPCI bus data requestor error: R2PCI
detected PERR# assertion.
OFFCBB8IO BDPCI D req err;OVRope-to-PCI bridge detected multiple
PERR# assertions.
OFFCBBAIO BDPCI data par errPCI bus data parity error.
OFFCBBCIO BDPCI Dpar err;OVMultiple PCI bus data parity errors.
OFFCBBEIO BDR2PCI intrnl errError in R2PCI internal data to PCI bus.
OFFCBC0IO BDR2PCI int err;OVMultiple R2PCI internal data to PCI bus
errors.
Chapter 263
Troubleshooting
Identifying LCD-Indicated Conditions
Table 2-1. Chassis Codes for J6000 Workstations
OstatCodeFRUMessageDescription
OFFCBC2IO BDPCI data parityPCI data parity error.I/O error log word 3
contains the error address.
OFFCBC4IO BDPCI data par; OVMultiple PCI data parity errors. I/O error
log word 3 contains the error address.
OFFCBC6IO BDR2PCI intrnl errRope-to-PCI bridge internal data error:
R2PCI detected PERR# assertion.
OFFCBC8IO BDR2PCI int err;OVMultiple R2PCI internal data errors:
R2PCI detected multiple PERR#
assertions.
OFFCBCAIO BDPCI data rs errPCI bus data responder error: R2PCI
detected PERR# assertion.
OFFCBCCIO BDPCI D rs err; OVMultiple PCI bus data responder errors:
INICC0nSYS BDCPUn OS rendezvsSlave CPU n entering the final
rendezvous, waiting for the operating
system to awaken it.
INICC1nSYS BDCPUn early rendSlave CPU n entering the early
rendezvous, waiting for the monarch CPU
to initialize scratch RAM and other
system state.
INICC2nSYS BDCPUn rendezvousSlave CPU n entering rendezvous. Slave
CPUs enter this rendezvous numerous
times during boot.
INICC3nSYS BDCPUn cache rendSlave CPU n entering cached rendezvous,
waiting for the monarch CPU to configure
the system bus.
INICC4nSYS BDCPUn mem rendezSlave CPU n entering memory
rendezvous, waiting for the monarch CPU
to select a boot device.
TSTD000SYS BDmicro controllerFirmware is initializing communications
with the system controller.
WRND004SYS BDmicro not respFirmware detected a communications
error with the system controller.
INID005SYS BDset dom1 fan spdFirmware is initializing communications
with the system controller.
INID006SYS BDset dom2 fan spdFirmware is initializing communications
with the system controller.
WRND007SYS BDbad microctl cmdFirmware detected a communications
error with the system controller.
FLTD01nSYS/IOfann: failure!Firmware detected system fan n stopped.
WRND02nSYS/IOfann: too slow!Firmware detected system fan n is
running too slowly.
66Chapter2
Troubleshooting
Running System Verification Tests
Running System Verification Tests
HP-UX uses an online diagnostics product called the Support Tools Manager that allows
system operation verification.
Three interfaces are available with the Support Tools Manager: a command line interface
(accessed through the cstm command), a menu-driven interface (accessed through the
mstm command), and the graphical user interface (accessed through the xstm command).
For more information on these user interfaces, see the online man pages by entering the
following at a command line prompt:
man cstm [Enter]
man mstm [Enter]
man xstm [Enter]
For information on the enhanced online diagnostics, see the Support Media User’s Manual
(HP Part Number B3782-90176).
To access the Support Tools Manager, perform the following steps:
1. In a terminal window, type the following at the # prompt to invoke the command line
interface:
# cstm [Enter]
2. The following message appears:
Support Tool ManagerVersion A.01.00
Type ‘help’ for a list of available commands.
CSTM>
3. To verify the system operation, type the following at the CSTM> prompt:
CSTM> verify all [Enter]
Messages similar to the following appear:
Verification has started on device (CPU).
Verification has started on device (FPU).
CSTM> Verification of (FPU) has completed.
CSTM> Verification of (CPU) has completed.
4. Press [Enter] to return to the CSTM> prompt after all test results are reported.
5. To exit the Support Tools Manager, enter the following:
CSTM> exit [Enter]
If any tests failed, run Selftest and ISL diagnostics to isolate the problem.
Chapter 267
Troubleshooting
Running ODE-Based Diagnostics
Running ODE-Based Diagnostics
The Offline Diagnostic Environment (ODE) consists of diagnostic modules for testing and
verifying system operation. ODE provides all the necessary functions for the user to load
specified tests and interact with those tests.
ODE is an ISL utility. To boot ODE:
1. Invoke the ISL environment from the system disk or a CD ROM.
2. Type ode [Enter] after the ISL> prompt to invoke ODE from the LIF directory on
the system disk. The prompt changes to ODE>.
Not all of the test modules are available on all systems. To see what test modules are
available to run on this system, type ls at the ODE> prompt. The available modules include
the following:
• astrodiag – tests and verifies the basic functionality of the Astro memory
controller/I/O chip.
• siodiag – tests and verifies the basic functionality of the SuperI/O multifunction I/O
chip, including serial, parallel, USB, and so forth.
• wdiag – tests and verifies the functionality of the PA-RISC chip.
• memtest – tests and verifies the memory arrays. If an error is detected, the diagnostic
reports the memory card and its slot number that needs replacement. It also provides a
map of the memory configuration so that the user can identify the type of memory and
its slot location.
• fupdate – updates the system’s Processor Dependent Code (PDC) firmware in the
EEPROM.
• mapper – identifies the configuration of HPPA systems. It displays path, identification,
and revision information of I/O components, configuration of memory controllers,
processors, co-processors, cache, and TLB, as well as processor board component
revisions and values of various HPPA system identifiers, revisions, and capabilities.
For further information on the various ODE commands and a complete listing of the
command set, type help [Enter] at the ODE> prompt or at the prompt of one of the test
modules.
68Chapter2
Troubleshooting
Using the System Board LEDs for Troubleshooting
Using the System Board LEDs for Troubleshooting
This section provides a description of the system board’s Light Emitting Diodes (LEDs)
and how to use them for troubleshooting. These LEDs are located inside of the workstation
on the system board’s left-back edge. See Figure 2-5.. Note that you will have to view these
LEDs through the airflow holes on the back of your workstation.
Figure 2-5. System Board LEDs
For those system problems that this section is not able to solve, you will have to call your
local HP Support Representative. Before you call, record the state (on, off or blinking) of
your LEDs and give this information to your local HP support representative. The
representative will use this information to determine the course of action to take.
Interpreting the LED Information
Table 2-2. explains how to interpret the information the system board LEDs provide. Note
that the SUPPLY LED is reserved for future functionality.
Table 2-2. Interpreting the System Board LEDs
LED NameLED’sColor
When On
VRM1GreenThis light, when on, indicates that the
Chapter 269
Description
voltage regulator module is working
correctly for processor one. The default
state for this light is on.
Troubleshooting
Using the System Board LEDs for Troubleshooting
Table 2-2. Interpreting the System Board LEDs
LED NameLED’sColor
When On
VRM0GreenThis light, when on, indicates that the
FETCHGreenThis light, when on, indicates that one
FANSYellow
(blinking)
Over CurrentRedThis light, when on, indicates there is
Description
voltage regulator module is working
correctly for processor zero. The
default state for this light is on.
or both processors is fetching code.The
default state for this light is on.
Note that the yellow light blinks a
heart beat when the system is working
correctly. See Table 2-3. for more
details for interpreting the blinks of
this light.
a short somewhere in the system. The
default state for this light is off.
There are six LED blink sequences supported by the System Controller. The LED blink
sequences are shown in Table 2-3. Note that each blink of the LED represents a tenth of a
second (0.1 sec.).
If the FANS LED is ever stuck either ON or OFF, a system problem has occurred. This
system problem is most likely an I2C bus hang. A potential fix may be to check that the
power supply cables are correctly plugged in. If this does not work, call you local HP
Support Representative.
LED Blink Sequence
(black dot represents 0.1 second LED on; white dot
is 0.1 second LED is off)
Description
shut off power to
the system because
the ambient
temperature
exceeded 60˚C or
140˚F.
detects a fan
failure. If this
happens you need
to read the message
in the LCD on the
front of the
workstation.
reporting an error.
Troubleshooting with System Board LEDs
This section explains what to do when you see the LEDs on your system board in a
non-default state, and when the yellow FANS LED displays certain blink sequences. For
the default states, see Table 2-2. Note that the non-default state is a state that should not
exist, and it is a state that requires a solution.
Table 2-4. Solutions for the Non-Default LED States
1
LED Name
VRM1OFFIf the following solutions do not bring this LED back
Non-Default
State
Solution
on, replace VRM1 board.
• Swap VRM cards to determine if VRM1 is bad
• Determine that the power cable to the system is
plugged in
• Check that the power button has been pressed on
• Re-seat the VRM1 board in its connector
• Check that the VRM1 connector cable is properly
plugged in
Chapter 271
Troubleshooting
Using the System Board LEDs for Troubleshooting
Table 2-4. Solutions for the Non-Default LED States
1
LED Name
Non-Default
State
VRM0OFFIf the following solutions do not bring this LED back
FETCHOFFIf the following solutions do not bring this LED back
Solution
on, replace VRM0 board.
• Swap VRM cards to determine if VRM0 is bad
• Determine that the power cable to the system is
plugged in
• Check that the power button has been pressed on
• Re-seat the VRM0 board in its connector
• Check that the VRM0 connector cable is properly
plugged in
on, replace the system board.
• Look at the system’s LCD to determine if the
firmware update process has been interrupted
• Determine that the power cable to the system is
plugged in
• Check that the power button has been pressed on
• Determine that all external peripheral devices are
turned on and that their cables are properly
connected
• Check that all internal devices are powered on and
that their cables are properly connected
72Chapter2
Using the System Board LEDs for Troubleshooting
Table 2-4. Solutions for the Non-Default LED States
1
LED Name
Non-Default
State
Solution
Troubleshooting
FANSOFF or
blink
sequence 4,
5 or 6
If the following solutions do not bring the LED back on
or cause it to properly blink, replace the system board.
OFFUnplug the system and replace the
system board
Blink Sequence 4 Unplug the system and operate the
unit when its environment gets
cooler
Blink Sequence 5 Replace the fan associated with the
message in your system LCD. If
power supply fans are bad, you have
to replace the power supply. If the
PCI fan is bad, replace it. If either
one of the processor fans are bad, you
must replace the system board. Note,
fans may still be spinning, but their
control signal may have failed.
Blink Sequence 6 Check that the 24-pin power supply
signal cable is properly connected
Press the power button off and
unplug the system and wait for two
minutes before turning the system
back on
SHORTONIf the following solutions do not turn this LED off,
replace the system board.
• Check that no pieces of metal are shorting
connections anywhere in the system
• Check that no pins on system connectors are bent
and touching each other
1. The LEDs are in the OFF state, or in the case of the FANS LED, the LED is
blinking sequence 1, 2, or 6 or it is not blinking.
Chapter 273
Troubleshooting
Using the System Board LEDs for Troubleshooting
74Chapter2
3System Upgrades
This chapter discusses the system upgrades for the HP VISUALIZE J6000 workstations,
and how to install and remove them. A system upgrade in this chapter is a hard disk drive,
CD ROM drive, I/O card or memory DIMMs.
75
System Upgrades
Chapter Overview
Chapter Overview
This chapter contains the following main sections:
• Tools Required
• Exchange and Nonexchange Part Numbers
• System Upgrades
—Electrostatic Discharge (ESD) Precautions
— Prerequisite for the System Upgrade Procedures
— Front Bezel and Top Panel
— Hard Disk Drives
— CD ROM Drive
— Memory DIMMs
— I/O Cards
WARNINGFor most of the installation and removal procedures in this chapter,
you must power off the workstation and unplug the workstation
power cord from the AC power outlet. The exceptions to this are the
installation and removal of DIMMs and the I/O cards. For these you
only need to power off the workstation.
NOTETo maintain FCC/EMI compliance, verify that all covers are replaced and
that all screws are properly seated.
Workstation Configurations
Refer to the HP Workstations web site for a complete list of supported accessories,
peripherals, and operating system versions for the J6000 workstations. The URL for the
web site is:
http://www.hp.com/visualize
76Chapter3
System Upgrades
Tools Required
Tools Required
Use the following tools to remove or replace system upgrades (for example, hard disk
drives):
• Light-duty flat blade screwdriver with 6-inch (150 mm) blade
• T-15 Torx and T-20 (for rack mounting) Torx drivers
• ESD equipment (see the “Electrostatic Discharge (ESD) Precautions” section later in
this chapter for detailed information)
Chapter 377
System Upgrades
System Upgrades
System Upgrades
The procedures in this section describe how to remove and replace J6000 workstation
system upgrades. Observe the electrostatic discharge (ESD) precautions and the
prerequisites for installing and removing system upgrades in the next two subsections, as
well as any NOTEs, CAUTIONs, and WARNINGs in each system upgrade procedure.
NOTEIf you need to install a new system upgrade, simply follow the procedures for
installing the upgrade in this chapter. (That is, replacement procedures are
the same as those for installing new system upgrades.)
Electrostatic Discharge (ESD) Precautions
To prevent damage to the J6000 workstation, observe all of the following ESD precautions
while performing the system upgrade procedures:
1. Remove all ESD-generating materials from the work area in which you will remove and
replace a workstation’s system upgrade(s).
2. Stand on an ESD (static-free) mat.
3. Wear a grounding wrist strap to ensure that any accumulated electrostatic charge
discharges from your body to ground.
4. Connect all equipment together, including the ESD mat, grounding wrist strap,
workstation, and peripherals.
5. Keep uninstalled printed circuit boards in their protective antistatic bags.
6. Once you have removed printed circuit boards from their protective antistatic bags,
handle the printed circuit boards by their edges only.
78Chapter3
System Upgrades
System Upgrades
Prerequisite for the System Upgrade Procedures
You must complete the following steps before performing any of the installation and
removal procedures in this chapter:
1. Power off the workstation (either by executing shutdown -h as root, or by simply
pressing the power switch on the front panel of the workstation, which accomplishes
the same thing), as well as the monitor and any attached peripheral devices.
2. Unplug the workstation power cord and all peripheral devices from AC power outlets.
3. Attach the static-grounding wrist strap by following the instructions on the package.
Attach the sticky end of the wrist strap to bare metal on the rear panel of the
workstation.
NOTETo make access to the internal components easier, you may want to place the
workstation on a table or workbench instead of leaving it on the floor.
CAUTIONThis workstation is designated for two-person lifting; it weighs approximately
36 to 49 pounds (12 to 22 kg), depending on the configuration. Do not attempt
to lift it by yourself, or injury may result.
Chapter 379
System Upgrades
System Upgrades
Front Bezel and Top Cover
This section describes how to install and remove the J6000 workstation’s front bezel and
top cover.
Note that you can perform certain operations, like installing and removing hard disk
drives, by removing the front bezel of the workstation. Other operations require more
access to the interior of the workstation, so you will need to remove the front bezel or top
panel to perform those procedures.
CAUTIONThe system will not operate with the top panel removed.
80Chapter3
Removing the Top Cover
Figure 3-1. Removing the Top Cover
System Upgrades
System Upgrades
- Remove all connectors from
1
back of workstation
- Remove workstation from
pedestal.
1
Hold down pedestal when
removing workstation
- Remove top cover
3
1. Unscrew captive screw
2. Pull cover forward
3. Lift cover up.
2
- Place workstation on a padded
surface
- Remove bezel
- Press in on both sides of bezel
and pull forward as shown.
2
- Attach anti-static strap
4
3
2
1
To replace the top cover or front bezel, perform the above steps in reverse.
NOTEThe graphics in these steps depict a desk side unit. If this is a rack mount
unit, the skins and pedestal will not be present. Rack mounted systems will
not have air louvres mounted in the front bezel. When replacing the bezel,
remove and discard the louvres from the new bezel unit.
Chapter 381
System Upgrades
System Upgrades
Installing and Removing the Hard Disk Drives
To install the hard disk drives, perform the following steps. You should make sure that the
disks are firmly seated. Reinstall the hard disk drive cover and optional locking
thumbscrew, if applicable.
Figure 3-2. Installing and Removing the Hard Disk Drives
1. Remove optional locking thumbscrew
1
2. Press HDD cover release tab to remove cover
Locking
Thumbscrew
2
1
Removing a HDD
2
- Pull out bracket
- Remove bracket and HDD
Adding a HDD
- Remove bracket and screws
Removing a HDD
3
- Install hard drive in bracket
- Insert in HDD cage till firmly seated
Adding a HDD
- Carefully remove bar
- Install HDD
Carefully
remove and
discard
To remove the hard disk drives, perform the above steps in reverse.
Hard Disk Drive Configuration
The SCSI IDs for hard disk drives are hard-wired into the SCA Ultra2 Wide LVD SCSI
interfaces in the backplane of the two disk bays within the J6000 workstations. Hence,
SCSI IDs do not need to be set for the hard disk drives installed in these workstations.
From top to bottom, the pre-set SCSI IDs for hard disk drives are: 6 and 5.
82Chapter3
Installing and Removing an Internal CD ROM Drive
To install the CD ROM drive, do the following:
Figure 3-3. Installing the CD ROM Drive
1. Slide CD in place
2. Screw in two screws
3. Connect the CD cable
3
1
System Upgrades
System Upgrades
2
To remove the CD ROM drive, perform the above steps in reverse.
Installing and Removing Memory DIMMs
To install memory DIMMs in the J6000, refer to the memory sequence label inside the
system or see Figure 3-4. Be sure to press the DIMMs into their slots until the tabs on each
end snap into place.
When removing the DIMMs, be sure to press the tabs at both ends of the DIMM slots to
release the DIMMs, then lift the DIMMs out of the slots.
J6000 Memory Configuration
The J6000 workstation has sixteen memory slots, labeled 0A, 0B to 7A, 7B. Memory
DIMMs must be installed in pairs in this workstation, and both DIMMs in each pair must
be of equal size. The DIMMs for this workstation currently come in 512 MB and 1 GB
sizes. This workstation comes with two 512 MB DIMMs as its standard configuration from
the factory. Thus, currently the minimum memory configuration for this workstation is
1GB, and the maximum is 16 GB.
DIMMs should be loaded in the order shown with 0A, 0B being the first pair of DIMMs
loaded, and 7A, 7B being the last pair loaded. Figure 2-1 shows the installation sequence.
Chapter 383
System Upgrades
System Upgrades
NOTEIf memory is installed improperly or it is bad and fastboot is not enabled, your
workstation’s operating system will not boot-up and a DIMM error will
appear in your workstation’s LCD. For more information see the section
“Displaying and Setting Fastboot Mode” in Chapter 4.
Figure 3-4. Memory Loading Sequence in the J6000
84Chapter3
Installing and Removing an I/O Card
To install an I/O card, do the following:
Figure 3-5. Installing an I/O Card
1
- Lift PCI handle to remove cage from workstation
System Upgrades
System Upgrades
1. Slide PCI retainer back
2
2. Lift off cage
- Insert I/O card in PCI slot as shown
3
- Insert bulkhead screw
2
1
PCI CARD
RETAINER
Bulkhead
screw
To remove an I/O card, perform the above steps in reverse.
Chapter 385
System Upgrades
System Upgrades
PCI Slot Information for I/O Cards
The three PCI slots located in the PCI cage area of the J6000 workstations are 64-bit, 4x,
3.3v, 66 MHz PCI (Peripheral Connect Interface) slots, providing I/O expansion
capabilities for the J6000 workstations.
CAUTIONThe J6000 workstations supply about 75 Watts of power to the PCI slots. Do
not insert I/O cards that together draw more than 75 Watts, or damage to the
workstation may result. Please look at the specifications that come with your
individual I/O cards for power requirements. Note that each PCI slot can
provide up to 25 watts.
86Chapter3
4Boot Console Handler
This chapter explains how to use the Boot Console Handler, which provides an interactive
environment after the power-on sequence in HP VISUALIZE J6000 workstations.
87
Boot Console Handler
Chapter Overview
Chapter Overview
This chapter contains the following main sections:
• Boot Console Handler Features
• Accessing the Boot Console Handler
• Boot Console Menus
• Booting the Workstation
• Searching for Bootable Media
• Resetting the Workstation
• Displaying and Setting Paths
• Displaying and Setting the Monitor Type
• Displaying the Current Memory Configuration
• Displaying the Status of the I/O Slots
• Setting the Auto Boot and Auto Search Flags
• Displaying and Setting the Security Mode
• Displaying and Setting Fastboot Mode
• Displaying the LAN Station Address
• Displaying System Information
• Displaying PIM Information
• Using Remote Power-On
• Setting the Fan Speed
• Stable Storage
• ISL Environment
88Chapter4
Boot Console Handler
Boot Console Handler Features
Boot Console Handler Features
There are times when you want to interact directly with the J6000 workstation before it
boots the operating system. These workstations provide a menu-driven Boot Console
Handler that allows you to perform special tasks, display information, and set certain
system parameters, even if the operating system is unavailable.
Here are some of the things you can do:
• Boot the workstation
• Search for bootable media
• Reset the workstation
• Display and set boot paths
• Display and set the monitor type
• Display memory configuration information
• Display the status of the I/O slots
• Set Auto Boot, Auto Search, and Auto Start
• Display and set Security mode
• Set Fastboot
• Display LAN information
• Display system information
• Display PIM information
• Using Remote Power-On
• Setting the Fan Speed
NOTEAll of the tasks in the Boot Console Handler should be performed by a system
administrator with superuser (root) login permissions.
Chapter 489
Boot Console Handler
Accessing the Boot Console Handler
Accessing the Boot Console Handler
To access the Boot Console Handler, follow these steps:
1. Close any files and applications on the workstation.
2. Press the power switch on the front panel of the workstation to power it off.
NOTEThere is no need to manually shut down the HP-UX operating system on the
workstation before powering it off. When you press the power switch, the
workstationautomaticallyshutsdowntheoperatingsystembefore
terminating the power.
Make sure you do not unplug the workstation’s power cord or otherwise interrupt power
to the workstation at this time.
3. Power on the workstation after the system has completely shut down.
If auto boot is turned off, the boot sequence automatically stops at the boot console
Main Menu.
If auto boot is turned on, you will see the following message:
Processor is starting auto boot process. To discontinue, press any key
within 10 seconds.
If auto boot and auto search are both turned on, you will see the following message:
Processor is booting from first available device. To discontinue, press
any key within 10 seconds.
NOTEIf you are using a power-saving monitor, you will have less than 10 seconds
from the time this message appears to press a key.
4. Press a key. You will then see the following message:
Boot terminated
The Main Menu of the Boot Console Handler appears.
90Chapter4
Boot Console Handler
Boot Console Menus
Boot Console Menus
The boot console menus follow, showing the various tasks you can perform and the
available information.
The shortened version of each command is indicated by the uppercase letters.
Help is available for all the menus and commands by using either help, he, or ? and the
menu or command for which you want help.
------ Main Menu -------------------------------------CommandDescription
-----------------BOot [PRI|ALT|<path>]Boot from specified path
PAth [PRI|ALT|CON|KEY [<path>]]Display or modify a path
SEArch [DIsplay|[[IPL] [<path>]]] Search for boot devices
COnfiguration [<command>] Access Configuration menu/commands
INformation [<command>]Access Information menu/commands
SERvice [<command>]Access Service menu/commands
DIsplayRedisplay the current menu
HElp [<menu>|<commands>]Display help for menu or command
RESET Restart the system
Main Menu: Enter command >
Chapter 491
Boot Console Handler
Boot Console Menus
------ Configuration Menu -----------------------------
CommandDescription
------------------
AUto [BOot|SEArch] [ON|OFF]Display or set specified flag
BootID [<proc> [<boot ID>]]Display or modify processor boot ID
BootINfoDisplay boot-related information
CPUconfig [<proc>[ON|OFF]] Config/deconfig processor
DEfaultSet the system to predefined values
FanChoice [DeskSide|RackMount] Display or set the fan preference
FastBoot [ON|OFF]Display or set boot tests execution
LanConfig [<config_type>]Display or set LAN configuration
MOnitor [LIST|[<path> <type>]]Change the current monitor type
PAth [PRI|ALT|CON|KEY [<path>]] Display or modify a path
PreviousPower [ON|OFF]Set previous power state
SEArch [DIsplay|[[IPL][<path>]] Search for boot devices
SECure [ON|OFF]Set/show security mode
TIme [c:y:m:d:h:m:s]Read or set real time clock in GMT
BOot [PRI|ALT|<path>]Boot from specified path
DIsplayRedisplay the current menu
HElp [<menu>|<command>]Display help for menu or command
RESETRestart the system
MAinReturn to Main Menu
-----
Configuration Menu: Enter command >
92Chapter4
Boot Console Handler
Boot Console Menus
------ Information Menu -------------------------------
CommandDescription
------------------
ALLDisplay all system information
BootINfoDisplay boot-related information
CAcheDisplay cache information
ChipRevisionsDisplay revisions of VLSI and firmware
COprocessorDisplay coprocessor information
FwrVersionDisplay firmware version
IODisplay I/O interface information
LanAddressDisplay built-in system LAN address
MEmoryDisplay memory information
PRocessorDisplay processor information
SysConfigDisplay the system configuration
WArningsDisplay selftest warning messages
BOot [PRI|ALT|<path>] Boot from specified path
DIsplay Redisplay the current menu
HElp [<menu>|<command>] Display help for menu or command
RESETRestart the system
MAinReturn to Main Menu
-----Information Menu: Enter command >
Chapter 493
Boot Console Handler
Boot Console Menus
------ Service Menu -----------------------------------
CommandDescription
------------------
ChassisCodes [<proc>|ON|OFF]Display/enable/disable chassis codes
CLEARPIMClear (zero) the contents of PIM
EepromRead [<addr> [<len>]]Read EEPROM locations
MemRead <addr>[<len>] [<type>]Read memory locations
PciDelay [<value>]Display or set PCI delay value
PDT [CLEAR]Display or clear the Page
Deallocation Table
PIM [<proc>] [HPMC|LPMC|TOC]Display PIM information
RemotePower [ON|OFF] Display/enable/disable remote power
ScRoll [ON|OFF] Display or change scrolling ability
BOot [PRI|ALT|<path>] Boot from specified path
DIsplay Redisplay the current menu
HElp [<menu>|<command>]Display help for menu or command
RESETRestart the system
MAinReturn to Main Menu
-----
Service Menu: Enter command >
94Chapter4
Boot Console Handler
Booting the Workstation
Booting the Workstation
You usually start a workstation by turning it on and waiting for HP-UX to boot
automatically. However, you may not always want the usual boot sequence to occur.
For example, you may want to start the workstation from an operating system that is
stored on a device that is different from the usual boot device. If the normal operating
system kernel or the disk on which it resides becomes damaged or unusable, you may wish
to boot from a different disk or perhaps from another type of device, such as a CD ROM
drive.
Here are some possible booting scenarios you may encounter:
• If you know which device you want to boot from, and you know that it contains a
bootable operating system, follow the directions in “Accessing the Boot Console
Handler” on, and then type the following at the prompt:
Main Menu: Enter command > boot device [Enter]
where device is the hardware path to the device, specified in Mnemonic Style Notation.
For example, if you wish to boot an operating system that is stored on an IDE CD ROM
drive, you would type the following command at the prompt:
Main Menu: Enter command > boot IDE [Enter]
• If you do not know which device you want to boot from, then type the following at the
prompt:
Main Menu: Enter command > search [Enter]
A message similar to the following will be displayed:
Path Number Device PathDevice Type
-------------------------- ------------
P0IDETEAC CD-532E-B
P1FWSCSI.6.0SEAGATE ST39102LC
At the prompt, you might type the following:
Main Menu: Enter command > boot P1 [Enter]
Note that the operating system on the specified device (P1) is used to boot the system
(also see the next section, “Searching for Bootable Media”).
Chapter 495
Boot Console Handler
Booting the Workstation
• If you wish to interact with the Initial System Loader (ISL) before booting the
workstation, follow the directions in the section “Accessing the Boot Console Interface”
found in this chapter, and type the following at the prompt:
Main Menu: Enter command > boot device [Enter]
The following prompt will appear:
Interact with ISL (Y,N,Q)>
Answering yes (Y) causes the ISL to be loaded from the specified device. After a short
time, the following prompt appears on the screen:
ISL>
ISL is the program that actually controls the loading of the operating system. By
interacting with ISL, you can choose to load an alternate version of the HP-UX
operating system. If you do not want to interact with ISL, you must enter no (N).
For example, if the usual kernel (/stand/vmunix) on the root disk (fwscsi.6.0) has
become corrupted, and you wish to boot the workstation from the backup kernel
(/stand/vmunix.prev), type the following at the ISL> prompt:
ISL> hpux /stand/vmunix.prev [Enter]
• If you do not know which media in the file systems have bootable operating systems,
you can find them with the search ipl command. See the next section, “Searching for
Bootable Media.”
96Chapter4
Boot Console Handler
Searching for Bootable Media
Searching for Bootable Media
To list all devices that contain bootable media, follow the directions in the section
“Accessing the Boot Console Handler” found in this chapter, and type the following at the
prompt:
Main Menu: Enter command > search ipl [Enter]
The search command searches all buses. The search may turn up more devices than there
are lines on the display. If you are using a text terminal, you can control the progress of the
search from the terminal’s keyboard by doing any of the following:
• To temporarily suspend the search, press [Ctrl]-[S].
• To continue the search, press [Ctrl]-[Q].
• To halt the search, press any other key.
These flow-control commands do not work with a bit-mapped display, but such a display
can show more than forty lines of text, so you are unlikely to need them.
To search for devices of just one type that actually contain bootable media, follow the
directions in the section “Accessing the Boot Console Handler” found in this chapter, and
then type the following at the prompt:
Main Menu: Enter command > search ipl device_type [Enter]
where
device_type
is one of the following:
• fwscsi is the internal, Wide LVD (Low Voltage Differential) SCSI bus.
• scsi is the external, SE/LVD ( Single-Ended/Low-Voltage Differential) SCSI bus.
• lan is all connections to the built-in LAN.
• ide is the built-in CD ROM drive.
n
• pci
is an optional SCSI interface in slot numbern.
For more information about the search command, type the following at the prompt:
Main Menu: Enter command > help search [Enter]
Chapter 497
Boot Console Handler
Resetting the Workstation
Resetting the Workstation
To reset the workstation to its predefined values, follow the directions in the section
“Accessing the Boot Console Handler” found in this chapter, and type the following at the
prompt to access the Configuration Menu:
Main Menu: Enter command > co [Enter]
When the Configuration Menu appears, type the following at the prompt:
Configuration Menu: Enter command > default [Enter]
Then type the following at the prompt:
Configuration Menu: Enter command > reset [Enter]
98Chapter4
Boot Console Handler
Displaying and Setting Paths
Displaying and Setting Paths
A path is the hardware address of a device that is attached to the I/O system of a
workstation. The path command sets the system paths shown in Table 5-1.
The path command sets and displays the hardware address of a specified device attached
to the I/O bus of the workstation.
Table 4-1. System Paths
Path TypeDevice
primary or priThe workstation’s default boot device (usually the root disk)
alternate or altThe workstation’s alternate boot device (usually a DDS-format tape device)
console or conThe workstation’s primary display device
keyboard or keyThe workstation’s primary ASCII input device
To display the current settings for the system paths, type the following at the prompt:
Main Menu: Enter command > path [Enter]
The paths are displayed in Mnemonic Style Notation, as shown in Table 5-2.
To display the current setting for a particular system path, follow the directions in the
section “Accessing the Boot Console Handler” found in this chapter, and type the following
at the prompt:
Main Menu: Enter command > path path_type [Enter]
where
path_type
is one of the path types listed in Table 5-1.
For example, to get the path to the primary boot device, follow the directions in the section
“Accessing the Boot Console Handler” found in this chapter, and type the following at the
prompt:
Main Menu: Enter command > path primary [Enter]
Chapter 499
Boot Console Handler
Displaying and Setting Paths
Toset a system path to a new value, follow the directions in the section “Accessing the Boot
Console Handler” found in this chapter, and type the following at the prompt:
Main Menu: Enter command > path
where
path_type
is one of the path types listed in Table 5-1 and
path_type path
[Enter]
path
is the specification of
the path in Mnemonic Style Notation (as described in Table 5-2). For example, to set the
primary boot path to a SCSI disk with an ID of 6.0, follow the directions in “Accessing the
Boot Console Handler” on, and then type the following at the prompt:
Main Menu: Enter command > path pri scsi.6.0 [Enter]
100Chapter4
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.