GOC3-4-5 T/S guide.

DARC / IG’s troubleshooting

Table of Contents {TOC}

1- Introduction.
2- How to check basic function of the IG’s ?
3- What are the basic ‘connections’ to an IG ?
4- Serial Over Lan [SOL] useful commands / resets
5- ipmitool : a ‘shell’ for the SOL connection
6- How to identify what DARC/IG/VIG you have ? (Westville or Jarrell)
7- How to reflash the VRAC of VIG Boards independently ?
8- How to check if the DIP/RAC VDIP/VRAC are ‘responding’ [lspci] ?
9- How to check if the DARC / IG’s hardware config ?
10 - How to test the VDIP Board (VCT’s) ?
11- How to test the VRAC Board (VCT’s) ?
12 - How to exercise in deep the VIG’s (VCT’s) ?
13 - How to test the DIP Board (non-VCT’s)
14 - How to test the RAC / IG Boards (non-VCT’s)
15 - Test / verify the RAC flash code (non VCT IG’s)
Appendix 1
Appendix 2

1- Introduction.

The purpose of this document is to regroup tools & diags that can be used on-site or remote to evaluate
possible issues with the DARC / VDARC / IG’s / VIG’s components of a GOC3-4-5 console. This
concerns LightSpeed, LS Pro, BrightSpeed, VCT all types. However, main focus is VCT therefore all
examples provided are from VCT configurations (except few specific to non-VCT consoles).
The host HP 8000/8200, SCSI tower, SDDA, Intercom & few other components are NOT covered here.

This covers the basic functions of the Motherboards, connections with the PCI devices on board, diags
available, Serial Over Lan [SOL] connections & utilities, and some ways to reflash / reconfigure some
components.

The Console Diagnostics of course can also be used to launch many of these diags, I do not describe
Console Diagnostics in details here (see Appendix 2). The purpose of the present doc is to list & describe
tools 1 by 1 and related to the troubleshooting needs.
Color codes :
Bold : highlights, keywords.
Blue : whatever has to be typed
Green : good responses, or items of interest.
Red : errors or important warning.
{TOC} : link brings you back to the Table Of Contents

2- How to check basic function of the IG’s ? {TOC}

One of the common problems seen is that one of the IG’s is ‘dropping’ the Recon process that it should
normally run. Several root causes can produce this : hardware Pbs, network Pbs, Motherboard Pbs or mis-
configuration of IG’s firmware, most being covered in further sections.
In normal conditions, all 3 IG’s should run a process image_generation. The check consists of listing
those 3 processes on the DARC :
[ctuser@darc log]$ ps -lef | grep image_g
4 S ctuser 18919 18913 0 75 0 - 446 - May14 ? 00:00:00 rsh ig1 image_generation -bp
0 -host darc -node 1 -th 2
4 S ctuser 18922 18913 0 75 0 - 446 - May14 ? 00:00:00 rsh ig2 image_generation -bp
0 -host darc -node 2 -th 2
4 S ctuser 18925 18913 0 75 0 - 446 - May14 ? 00:00:00 rsh ig3 image_generation -bp
0 -host darc -node 3 -th 2
GE Proprietary – May 2007 – Ph.Giudici - rev.0 p1
 GOC3-4-5 T/S guide.

0 S ctuser 24126 22312 0 77 0- 940 pipe_w 11:40 pts/0 00:00:00 grep image_g
[ctuser@darc log]$

Here, the 3 processes are running, which is good. However, this does not prove that hardware on each IG
is fully functional. See below for more hardware checks & diags.
If one of the 3 processes is not running, then you have a problem : either 1 IG did not start, or
encountered severe error leading to process crash.

3- What are the basic ‘connections’ to an IG ? {TOC}

The ONLY physical link between DARC & IG’s is the RJ45 cable which carries both :
• the Ethernet connection (Linux processes, scan data, images…) when IG has successfully booted
-AND-
• the Serial Over Lan connection, which should be active & alive at all times ! It is used to remotely
‘start’ the IG boot. Even if Linux is not running on the IG, the RJ45 cable goes to a control chip
called BMC (Board Monitor Ctrl) which essentially deals with the hardware (CPU, fans,
temperatures, power…)
We ‘talk’ to this chip when using the SOL {telnet localhost 623} and get the DPCCLI> prompt.
To check connections :
1. ping ig1, ig2, ig3 from the DARC. It is possible that a failing IG still replies to the ping, but does not
properly execute Recon. If all 3 replies, try reboot the failing IG using SOL (see below)
2. if one IG is not replying to ping, it is likely NOT running Linux. However, the SOL should still be
available.
3. Launch ‘telnet localhost 623’ on the failing IG. If it replies with DPCCLI>, at least the hardware is
still active. Try to run basic hardware checks on the IG then reboot the board (see below).
4. If the SOL connection looks ‘dead’ (not connected) then you should check if the software service
driving the SOL is active :
a. Try first to open an SOL connection on another IG. If it fails, go to [b] ; if it works, go to [5]
b. On the DARC, type [ctuser@darc ~]$ ps -elf|grep dpcproxy
1 S root 2735 1 0 75 0 - 916 - May14 ? 00:00:00 /usr/local/cli/dpcproxy
0 S ctuser 8757 8736 0 76 0 - 941 pipe_w 10:23 pts/0 00:00:00 grep dpcproxy

If the process (green) is not running : try restart it with command :

[root@darc]# service cliservice start
then restart at step 3 above.
5. If after ‘repair’ tentative in step 4, you still have a dead SOL, you have either an RJ45
cable/connection issue, OR a dead component on the IG. In such case, it’s good to cycle the power
from the IG main switch with Applications UP, to reconfigure [maybe] the BMC chip with proper IP
address.
6. If that last action does not bring the SOL alive on the IG, you need to swap the unit.

4- Serial Over Lan [SOL] useful commands / resets {TOC}

IMPORTANT NOTICE : all details given in this chapter apply the same way to the SOL connections
from the OC to the DARC
–AND-
from the DARC to the IG’s

The SOL prompt DPCCLI> offers a help ; most used commands are in bold.
dpccli> help
alarm -q { -g <id> [ -o <id> ] [-a <id> ] } | { -l <severity> } | -p
alarm -s -a <id> -l <severity>
alarm -c { -g <id> [ -o <id> ] [-a <id> ] } | { -l <severity> } | all
boot -s normal | service [-f] [-console]
clear
clearlog
commit
console
displaylog [-F csv|hex|dsv] [-O filename] [-n <num>]
exit
GE Proprietary – May 2007 – Ph.Giudici - rev.0 p2
 GOC3-4-5 T/S guide.

quit
get -T <target> <options>
help [-C <command>]
id
identify [-on [<seconds>]] [-off]
identify -s
interrupt -i nonmask [-console]
power { -on [-console] } | -off
power -state
reset [-console]
sensors [-v] [-F csv|dsv] [-f ok|nc|cr|nr|us] [-T volt|temp|power|fan]
service { console | exit | ftp { start | stop } }
set -T <target> <options>
shutdown [-f] [-r]
version
dpccli>
The 1st thing is to run the sensors –v command which will report all power supplies, fans, voltages, CPU…
on the motherboard. All MUST be OK as shown below :
dpccli> sensors -v
05/16/2007 | 04:04:42 | BB +1.2V Vtt | ok | 1.21 | Volts
05/16/2007 | 04:04:43 | +1.5V NIC Core | ok | 1.54 | Volts
05/16/2007 | 04:04:44 | BB +1.5v | ok | 1.51 | Volts
05/16/2007 | 04:04:45 | Memory Voltage | ok | 1.81 | Volts
05/16/2007 | 04:04:45 | BB +3.3V | ok | 3.37 | Volts
05/16/2007 | 04:04:46 | STBY +3.3V | ok | 3.32 | Volts
05/16/2007 | 04:04:47 | AUX +3.3V | ok | 3.25 | Volts
05/16/2007 | 04:04:48 | BB +5V | ok | 4.97 | Volts
05/16/2007 | 04:04:48 | STBY +5V | ok | 4.88 | Volts
05/16/2007 | 04:04:49 | BB +12V | ok | 11.97 | Volts
05/16/2007 | 04:04:50 | BB -12V | ok | -11.73 | Volts
05/16/2007 | 04:04:52 | Baseboard Temp | ok | 30.00 | Celsius
05/16/2007 | 04:04:52 | CPU 1 Blower | ok | 2485.00 | RPM
05/16/2007 | 04:04:53 | CPU 2 Blower | ok | 2414.00 | RPM
05/16/2007 | 04:04:54 | Add-in Blower | ok | 1917.00 | RPM
05/16/2007 | 04:04:55 | Exhst Fan | ok | 7171.00 | RPM
05/16/2007 | 04:05:00 | CPU 1 Temp | ok | 36.00 | Celsius
05/16/2007 | 04:05:01 | CPU 2 Temp | ok | 36.00 | Celsius
05/16/2007 | 04:05:02 | CPU 1 VRM | ok | 12.03 | Volts
05/16/2007 | 04:05:02 | CPU 2 VRM | ok | 12.03 | Volts
05/16/2007 | 04:05:10 | Proc 1 Vccp | ok | 1.25 | Volts
05/16/2007 | 04:05:11 | Proc 2 Vccp | ok | 1.25 | Volts
dpccli>

You may use the displaylog command to post on the screen the on-board log file of motherboard activity.
This will likely scroll slowly and for 3~5 minutes as this log is huge. It rarely contains relevant information,
few occurrences of IERR (interrupt error) or POST (PowerOn SelfTest error) can be of some use. Use e.g.
displaylog –n 50 to display the last 50 lines or the log.

The commands power –state, power –off, power –on allow to see if the board is ON, also to turn it
OFF or turn it ON from the DPPCLI> prompt. This is equivalent to push the On/Off switch on the front
panel, but NOT the back panel switch : this one also removes power to the BMC chip, which is not the
case for the front switch or the SOL command.

One of the common actions via SOL connection is to reboot the unit.
This is done by typing :
dppcli> reset [enter]
dpplci > console [enter]

The previous command reset –c does not work properly anymore due to DPCCLI versions change
coming with MW29.7 release. You need now to type 2 distinct commands as described above. Expect ~30
sec. Before you see the start of the reboot script. Characters can look scrambled on screen, depending on
the type of connection used for this reboot (Xterm, VOLC…)
GE Proprietary – May 2007 – Ph.Giudici - rev.0 p3
 GOC3-4-5 T/S guide.

WARNING : these reset actions can be done via VOLC or ISD remote connection, but our Telnet
application will not handle properly the characters flow during the boot process, and it WILL HANG.
Don’t be surprised, the boot will actually happen in the background. Disconnect/close the Telnet
application, and reconnect to the site.

5- ipmitool : a ‘shell’ for the SOL connection {TOC}

A utility called ipmitool can be used as a ‘shell’ using the SOL connection to control the IG’s, and perform
all same operations than the DPCCLI> prompt (and even more), but this tool is far from user-friendly, so
we’ll limit here to the basic checks and readings that seem of interest, with reasonable typing…
You’ll see in the help that the range of possibility is large, including options that can put you in trouble.
Use only what is described here !

Let’s see the help first ; items of interest in bold.

[ctuser@darc ~]$ ipmitool -h
ipmitool version 1.8.7

usage: ipmitool [options...] <command>

-h This help
-V Show version information
-v Verbose (can use multiple times)
-c Display output in comma separated format
-I intf Interface to use
-H hostname Remote host name for LAN interface
-p port Remote RMCP port [default=623]
-U username Remote session username
-f file Read remote session password from file
-S sdr Use local file for remote SDR cache
-a Prompt for remote password
-e char Set SOL escape character
-C ciphersuite Cipher suite to be used by lanplus interface
-k key Use Kg key for IPMIv2 authentication
-L level Remote session privilege level [default=ADMINISTRATOR]
-A authtype Force use of auth type NONE, PASSWORD, MD2, MD5 or OEM
-P password Remote session password
-E Read password from IPMI_PASSWORD environment variable
-m address Set local IPMB address
-b channel Set destination channel for bridged request
-l lun Set destination lun for raw commands
-t address Bridge request to remote target address
-o oemtype Setup for OEM (use 'list' to see available OEM types)
-O seloem Use file for OEM SEL event descriptions

Interfaces:
open Linux OpenIPMI Interface [default]
imb Intel IMB Interface
lan IPMI v1.5 LAN Interface
lanplus IPMI v2.0 RMCP+ LAN Interface

Commands:
raw Send a RAW IPMI request and print response
i2c Send an I2C Master Write-Read command and print response
lan Configure LAN Channels
chassis Get chassis status and set power state
power Shortcut to chassis power commands
event Send pre-defined events to MC
mc Management Controller status and global enables
GE Proprietary – May 2007 – Ph.Giudici - rev.0 p4
 GOC3-4-5 T/S guide.

sdr Print Sensor Data Repository entries and readings

sensor Print detailed sensor information
fru Print built-in FRU and scan SDR for FRU locators
sel Print System Event Log (SEL)
pef Configure Platform Event Filtering (PEF)
sol Configure and connect IPMIv2.0 Serial-over-LAN
tsol Configure and connect with Tyan IPMIv1.5 Serial-over-LAN
isol Configure IPMIv1.5 Serial-over-LAN
user Configure Management Controller users
channel Configure Management Controller channels
session Print session information
firewall Configure firmware firewall (IPMIv2.0)
sunoem OEM Commands for Sun servers
picmg Run a PICMG/ATCA extended cmd
fwum Update IPMC using Kontron OEM Firmware Update Manager
shell Launch interactive IPMI shell
exec Run list of commands from file
set Set runtime variable for shell and exec

The syntax used is : ipmitool –I [interface] –H [host] –P [password] {command}

{interface} = lan
{host} = ig1, ig2, ig3
{password} = ‘simple’ or “double” quotes, “’’ for empty (no password ever)
Typical commands are given below, see the Appendix 1 for samples printout results on a VCT.

ipmitool -I lan -H ig1 -P “” sel : basic comm. over SOL, and log status
ipmitool -H ig1 -P '' chassis power status : check chassis power behaviour at boot
ipmitool -H ig1 -P '' fru : lists board components
ipmitool -H ig1 -P '' sdr type temp : components temperature checks
ipmitool -H ig1 -P '' sel list last 15 : lists last 15 lines of the on-board log
ipmitool -H ig1 -P '' sensor : lists all board sensors... many details. Look for OK’s
ipmitool -H ig1 -P '' sdr : simplified board sensors. Again, look for OK’s

6- How to identify what DARC/IG/VIG you have ? (Westville or Jarrell) {TOC}

The command dmidecode (as root) reads Board type. It returns a Version string which contains WV for
Westville, JR for Jarrell. This works for all IG’s, VIG’s and DARC types we use nowadays.
Notice the same tool on HP host will also give you the BIOS version of the Motherboard.

[ctuser@ig1 ctuser]# dmidecode|grep -i vers

Version: SE7520JR23.86B.P.10.00.0087.120820051348
Version:
Version: FRU Ver 0.01
Version:
Version: Intel(R) Xeon(TM) CPU 3.20GHz
Version: Intel(R) Xeon(TM) CPU 3.20GHz
Specification Version: 2.0

[ctuser@ig1 ctuser]# exit

7- How to reflash the VRAC of VIG Boards independently ? {TOC}

The vrac_flash_update command can be run either from the OC or from the DARC. It needs of course to
have Applications down.
From the OC : it will reflash all IG’s without further confirmation.
From the DARC : you will need to specify which IG you whish to reflash, like example below.

GE Proprietary – May 2007 – Ph.Giudici - rev.0 p5

 GOC3-4-5 T/S guide.

Note : in this case, the reflash failed due to defective VRAC module. In such case, a swap of IG is
required.

[ctuser@darc ~]$ vrac_flash_update ig1

Xlib: connection to "oc:0.0" refused by server
Xlib: No protocol specified

This tool will check the FLASH versions of the VRAC on all
IGs in the system. If any version is not up to date the
VRAC will be updated at this time. APPLICATIONS MUST NOT BE
RUNNING WHEN THIS STARTS. YOU MUST NOT ABORT THIS PROCEDURE
ONCE STARTED. Are you sure you want to continue?
enter 'y' to continue
y
vrac_flash_update[5965]: started check of VRAC FLASH; argv=['ig1']
args= ['/usr/bin/vrac_popup', '-t', 'Updating VRAC FLASH
DO NOT INTERRUPT!']
Xlib: connection to "oc:0.0" refused by server
Xlib: No protocol specified

Updating VRAC FLASH DO NOT INTERRUPT!

Set chassis power restore policy to always-off

vrac_flash_update[5965]: ig1: IPMI status 0
Set ISOL Baud Rate to 57600
vrac_flash_update[5965]: ig1: set SOL baud rate to 57600
vrac_flash_update[5965]: checking/updating FLASH ig1
vrac_flash_update[5965]: ig1:
vrac_flash_update[5965]: ig1: *** ERROR: FLASH procedure was unsuccessful
vrac_flash_update[5965]: ig1: /dev/gemsvrac: No such file or directory
vrac_flash_update[5965]: ig1:
vrac_flash_update[5965]: ig1: error executing flash_vrac -e -l0 -R -FBOTH /etc/vrac.elf
vrac_flash_update[5965]: ig1:
vrac_flash_update[5965]: ig1: *** ERROR: FLASH procedure was unsuccessful
vrac_flash_update[5965]: ig1: /dev/gemsvrac: No such file or directory
vrac_flash_update[5965]: ig1:
vrac_flash_update[5965]: ig1: error executing flash_vrac -e -l1 -R -FBOTH /etc/vrac_thin.elf
vrac_flash_update[5965]: could not update flash on ig1
kill pid 5968
vrac_flash_update[5965]: FLASHed 0 of 1 IGs
vrac_flash_update[5965]: Unable to FLASH all Igs

8- How to check if the DIP/RAC VDIP/VRAC are ‘responding’ [lspci] ? {TOC}

On DARC & IG's, lspci allows to verify that the PCI devices [DIP / VDIP / RAC / VRAC]
are responding and correctly detected from the Motherboard side.
Note : the 2 commands suggested here do the same, the 2nd one is easier to use.
This is run either from the DARC prompt to detect DIP/VDIP, or from each IG’s prompt to detect RAC /
VRAC. The GE components are those which appear ‘unknown’ !!
Notice you also see here all other components attached to the Motherboard (Eth. controllers, VGA cards…)
Good responses on these tests mean the PCI device is detected, not necessary they work properly. For
sure, if a device is not listed, system will not work. In such case, it can be productive to open the box
(DARC, IG) and reseat all PCI connections, cables, etc… ESD equipment needed !

[root@ig1 ~]# lspci -nd 17b6

03:08.0 Class ff00: 17b6:5084 (rev 80)
[root@ig1 ~]#

GE Proprietary – May 2007 – Ph.Giudici - rev.0 p6

 GOC3-4-5 T/S guide.

[root@ig1 ~]# lspci

00:00.0 Host bridge: Intel Corp. E7501 Memory Controller Hub (rev 01)
00:00.1 Class ff00: Intel Corp. E7000 Series Host RASUM Controller (rev 01)
00:03.0 PCI bridge: Intel Corp. E7000 Series Hub Interface C PCI-to-PCI Bridge (rev 01)
00:03.1 Class ff00: Intel Corp. E7000 Series Hub Interface C RASUM Controller (rev 01)
00:1d.0 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #1) (rev 02)
00:1d.1 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #2) (rev 02)
00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB/ER Hub interface to PCI Bridge (rev 42)
00:1f.0 ISA bridge: Intel Corp. 82801CA LPC Interface Controller (rev 02)
00:1f.1 IDE interface: Intel Corp. 82801CA Ultra ATA Storage Controller (rev 02)
00:1f.3 SMBus: Intel Corp. 82801CA/CAM SMBus Controller (rev 02)
01:0c.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
02:1c.0 PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (rev 04)
02:1d.0 PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (rev 04)
02:1e.0 PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (rev 04)
02:1f.0 PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (rev 04)
03:07.0 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01)
03:07.1 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01)
03:08.0 Class ff00: Unknown device 17b6:5084 (rev 80)

>>> last line lists the VRAC device.

======================================================

[root@darc ~]# lspci -nd 17b6

03:0a.0 Class ff00: 17b6:2000 (rev c0)
[root@darc ~]#

[root@darc ~]# lspci

00:00.0 Host bridge: Intel Corp. E7501 Memory Controller Hub (rev 01)
00:00.1 Class ff00: Intel Corp. E7000 Series Host RASUM Controller (rev 01)
00:03.0 PCI bridge: Intel Corp. E7000 Series Hub Interface C PCI-to-PCI Bridge (rev 01)
00:03.1 Class ff00: Intel Corp. E7000 Series Hub Interface C RASUM Controller (rev 01)
00:1d.0 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #1) (rev 02)
00:1d.1 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #2) (rev 02)
00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB/ER Hub interface to PCI Bridge (rev 42)
00:1f.0 ISA bridge: Intel Corp. 82801CA LPC Interface Controller (rev 02)
00:1f.1 IDE interface: Intel Corp. 82801CA Ultra ATA Storage Controller (rev 02)
00:1f.3 SMBus: Intel Corp. 82801CA/CAM SMBus Controller (rev 02)
01:0c.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
02:1c.0 PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (rev 04)
02:1d.0 PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (rev 04)
02:1e.0 PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (rev 04)
02:1f.0 PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (rev 04)
03:07.0 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01)
03:07.1 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01)
03:0a.0 Class ff00: Unknown device 17b6:2000 (rev c0)
04:07.0 SCSI storage controller: Adaptec AIC-7902 U320 (rev 03)
04:07.1 SCSI storage controller: Adaptec AIC-7902 U320 (rev 03)
04:09.0 Ethernet controller: Intel Corp. 82546GB Gigabit Ethernet Controller (rev 03)
04:09.1 Ethernet controller: Intel Corp. 82546GB Gigabit Ethernet Controller (rev 03)
04:0a.0 Ethernet controller: Intel Corp. 82546GB Gigabit Ethernet Controller (rev 03)
04:0a.1 Ethernet controller: Intel Corp. 82546GB Gigabit Ethernet Controller (rev 03)

>>> green line lists the VDIP device.

9- How to check if the DARC / IG’s hardware config ? {TOC}

GE Proprietary – May 2007 – Ph.Giudici - rev.0 p7

 GOC3-4-5 T/S guide.

The ‘hinv’ OC command is not implemented on DARC nor IG’s software, however a generic Linux
command lhinv does exactly the same job. See below examples on a VIG. Notice this is a convenient way
to check the amount of memory detected on the Motherboard, which is critical to proper operation.

[ctuser@ig1 ~]$ lhinv

CPU: GenuineIntel Intel(R) Xeon(TM) CPU 3.20GHz
4 3194 MHz i686 Processors
Secondary cache: 16 KB
FPU: GenuineIntel Intel(R) Xeon(TM) CPU 3.20GHz Floating Point
Main memory size: 6656 Mbytes
1 Graphics board: VGA detected at 03c0-03df
Ethernet interface configured: eth0
Ethernet interface configured: eth1
[ctuser@ig3 ~]$

10 - How to test the VDIP Board (VCT’s) ? {TOC}

A diag is available from the DARC prompt : vdip_menu. If launched without option it will post a menu,
where you can choose from a list of tests. Use the –h to see options. Most likely use the –A option which is
the most convenient, as it chains all tests w/o loopback optical fiber. It takes ~ 30 sec.
Execute the test as root, otherwise it will fail the bandwidth test.

[ctuser@darc ~]$ vdip_menu -h

fd is 5 in vdip.cvar.fd
usage:
/usr/bin/vdip_menu.py [-h |-l |-v] | [-r |-R <# of reps>] & [-a |-t <test #'s>]

where:
-h displays this text
-l lists the tests
-v verbose mode
-r sets the number of times to run each test
-a executes all of the menu selections (Require loopback cables)
-A executes all of the menu selections except serial loopback tests
-t runs the test or tests that follow

[root@darc ~]# vdip_menu -A

fd is 5 in vdip.cvar.fd

Loop 1:
PASSED - 1 - Read Configuration Space Header
PASSED - 2 - Read contents of Board ID and PCI Rev.
PASSED - 3 - Read contents of Registers
PASSED - 4 - Data Pattern Test of SRAM A
PASSED - 5 - Data Pattern Test of SRAM B
PASSED - 6 - Walking Bit Test of SRAM A
PASSED - 7 - Walking Bit Test of SRAM B
PASSED - 8 - Address Pattern Test of SRAM A
PASSED - 9 - Address Pattern Test of SRAM B
PASSED - 10 - Read Test of FLASH
PASSED - 11 - Relay Loopback Test

Loop 1:
PASSED - 14 - DMA Test
PASSED - 15 - DMA Band Width Test
PASSED - 16 - Memory Test
PASSED - 17 - Interrupt Test
***********************************************************
GE Proprietary – May 2007 – Ph.Giudici - rev.0 p8
 GOC3-4-5 T/S guide.

RESULTS
0 of 2 Loops Contain Failures
ALL TESTS PASSED
***********************************************************
[root@darc ~]#

11- How to test the VRAC Board (VCT’s) ? {TOC}

A diag is available from the IG’s prompt : vrac_menu. If launched without option it will post a menu,
where you can choose from a list of tests. Use the –h to see options. Most likely use the –a option which is
the most convenient, as it chains all tests. It takes ~ 2 min.
This test will exercise the VRAC with various Recon modes. A successful test means the VRAC is
performing back-projection tasks properly, however, the IG itself can generate problems like ‘dropping’
the Recon process, which is described in another chapter.

[root@darc ~]# rsh ig2

connect to address 10.0.2.2 port 543: Connection refused
Trying krb4 rlogin...
connect to address 10.0.2.2 port 543: Connection refused
trying normal rlogin (/usr/bin/rlogin)
[root@ig2 ~]# vrac_menu -h
usage: /usr/bin/vrac_menu.py [-h | -l | -v ] | [-r <# of reps>] & [-a|-t <test #'s>]
where:
-h displays this text
-l lists the tests
-v verbose mode
-r sets the number of times to run each test
-a executes all of the menu selections in order
-t runs the test or tests that follow
-cb set the bp mode to cone beam
-ts set the bp mode to thin slice
[root@ig2 ~]# vrac_menu -a
----------------
Cone Beam Tests
----------------
Loop 1:
PASSED - 0 - Reset VRAC
device 0x17b6 vendor 0x5084 : VRAC1
PASSED - 1 - Read Configuration Space Header
PASSED - 2 - Read contents of Board IP, Assembly Version, PBC VHDL and BPP VHDL Registers
PASSED - 3 - Read contents of the Instruction Stack, Execution and Status Registers
PASSED - 4 - Read contents of Control and Interrupt Registers
PASSED - 5 - Read contents of Test Registers
…
PASSED - 10.2.3 - BPP3 PJM Data Shift Tests (83 Inst)
0x86 Instruction Complete
…
0x87 Instruction Complete
PASSED - 11.1 - Image Memory Tests (86 and 87 Inst)
PASSED - 11.2.1 - BPP1 LUT Tests
…
Beam)
PASSED - 12.4.2 - 25 x 48 x 1710 - 512 x 512 - 4 Images (Cosine Data Cone Beam)
PASSED - 12.4.3 - 984 x 48 x 64 - 512 x 512 - 4 Images (Cosine Data Cone Beam)
----------------
Thin Slice Tests
----------------
Loop 1:
PASSED - 0 - Reset VRAC
GE Proprietary – May 2007 – Ph.Giudici - rev.0 p9
 GOC3-4-5 T/S guide.

device 0x17b6 vendor 0x5084 : VRAC1

PASSED - 1 - Read Configuration Space Header
…
PASSED - 10.2.3 - BPP3 PJM Data Shift Tests (83 Inst)
0x86 Instruction Complete
…
PASSED - 11.3.3 - BPP3 DMA Tests
PASSED - 12.5.1 - 2 x 4 x 64 - 32 x 32 - (Cosine Input Thin Slice)
########## The test will cost about 90 seconds ##########
Aligned 1710 channels to 1712 channels
PASSED - 12.5.2 - 2612 x 64 x 1710 - 512 x 512 (Cosine Input Thin Slice)
***********************************************************
RESULTS
***********************************************************
--CONE BEAM--
ALL CONE BEAM TESTS PASSED
***********************************************************
--THIN SLICE--
ALL THIN SLICE TESTS PASSED
***********************************************************
0 Total Failures
[root@ig2 ~]#

12 - How to exercise in deep the VIG’s (VCT’s) ? {TOC}

We have a diagnostic on the DARC called test_igs which will go to each IG in sequence and run many
Recon tasks, in various Recon modes (thin slice, cone beam, cardiac..). This is a complete test for the
Recon hardware. It takes ~ 20 minutes for 3 IG’s.
Notice the tests also gives you details about the type of VRAC, firmware rev, etc.

[ctuser@darc~]$test_igs
###########################################
IG-1
rsh ig1 OK
ig1 has a VRAC
2395084 G [FPGA LOAD 1] PCI Rev 128 PBC Rev 452 BPP Rev 355
1. VRAC Board Level Diagnostics
..............
ALL TESTS PASSED
2. VRAC Backprojection Tests
....
ALL TESTS PASSED
3. Helical Backprojection Stess Test
Successfully sent LUTs to the VRAC
In cone beam mode
Aligned 1710 channels to 1712 channels
Image 0 : 8bcee099
Image 1 : 80514510
Image 2 : 743daa46
Image 3 : 67e7f940
Image 4 : 5b7ce5da
.........................
PASSED - Run Helical Simulation Cone Beam
4. Cardiac Backprojection Stess Test
Successfully sent LUTs to the VRAC
In cone beam mode
Aligned 1710 channels to 1712 channels
Image 0 : 8bcee099 88effbca 86214b64 83317960
GE Proprietary – May 2007 – Ph.Giudici - rev.0 p10
 GOC3-4-5 T/S guide.

Image 1 : 80514510 7d4f02a6 7a56cdff 7750cc28

Image 2 : 743daa46 7135bba4 6e1cb0dd 6afea19c
Image 3 : 67e7f940 64ce7238 61ae3609 5e9d532a
Image 4 : 5b7ce5da 587278de 556fe853 52688c85
.........................
PASSED - Cardiac Stress Test Cone Beam
#######################################

… then does same for IG2, IG3.

13 - How to test the DIP Board (non-VCT’s) {TOC}

The DIP board on LS / LS Pro / BrightSpeed… systems is attached to the DARC as a PCI device. See 1st the
lspci command description. Then, to run diags on the DIP, use DipDiag utility :
[ctuser@darc ~]$ DipDiag -h
usage: DipDiag [options]
options:
-a, --all,
-x, --execute, 1,2,3,...
-n, --do-not-execute, 1,2,3,...
-i, --iterations, N
-q, --quiet,
-p, --stop-on-error,
-h, --help,
Test numbers are as follows
1 - X-ray Enable Relay
2 - Test FEC Bit
3 - Test EDDR Bit
4 - Test Magic Number Register
5 - Memory Test
6 - Interrupt Test
7 - External LoopBack Test
8 - DMA Test
Without options the test is run in interactive mode.
Use the DipDiag –a option which will chain all tests automatically.
WARNING : as you won’t probably have the loopback Optical Fiber installed, tests 7 & 8 WILL FAIL.
This is normal. These tests MUST PASS when the loopback fiber is installed.

[ctuser@darc ~]$ DipDiag -a

15:48:14 opening LINUX device /dev/dip
creating H16 dip interface
DIP PN : 2326523 B
test 1 Passed X-ray Enable Relay
test 2 Passed Test FEC Bit
test 3 Passed Test EDDR Bit
test 4 Passed Test Magic Number Register
fill mem
write to dip took 4.715 sec
verifying memory
read from dip took 19.543 sec
test 5 Passed Memory Test
test 6 Passed Interrupt Test
error - failed in select
test 7 Failed External LoopBack Test
gdip_dma_test(3,8388608,1,2048,0)
error - Timeout waiting for DMA interrupt
GE Proprietary – May 2007 – Ph.Giudici - rev.0 p11
 GOC3-4-5 T/S guide.

test 8 Failed DMA Test

1 loops 2 failures
2 tests failed
[ctuser@darc ~]$

14 - How to test the RAC / IG Boards (non-VCT’s) {TOC}

The RAC is the PCI device on top of IG’s Motherboard in charge of Recon backprojection, etc. See 1st the
lspci command description. Previous software releases had a ‘racdiag’ utility on the IG’s, not user-
friendly. On current releases (06MW03.x, 06MW29.7 & beyond), a macro is now available on the OC host:
racdiags. This diag needs to shutdown Application. Notice the macro will try to run diags on all IG’s,
therefore will send failing messages on IG2 & IG3 if they are not here (as below). You can also run as
many loops of this diag with racdiags –i3 for e.g. 3 loops.

{ctuser@msec5x2}[9] racdiags -i3

executing diagnostics on DARC
Running 3 loops of racdiags on ig1
2
0 SRAM A Incr Pat PASSED 3 loops
1 SRAM A Walking Pat PASSED 3 loops
2 SRAM A Address Pat PASSED 3 loops
3 SRAM B Incr Pat PASSED 3 loops
4 SRAM B Walking Pat PASSED 3 loops
5 SRAM B Address Pat PASSED 3 loops
6 FLASH Region 0 PASSED 3 loops
7 FLASH Region 1 PASSED 3 loops
13 DMA host<-image mem PASSED 3 loops
14 DMA host->projection mem PASSED 3 loops

3 Loops: All tests passed

Running 3 loops of racdiags on ig2
ig2: No route to host
Running 3 loops of racdiags on ig3
ig3: No route to host
{ctuser@msec5x2}[10]

15 - Test / verify the RAC flash code (non VCT IG’s) {TOC}

The ‘flash_rac’ utility is used on the IG's to check the integrity of the RAC flash memory.
This is valid with releases 06MW03.5, 06MW29.7 & beyond.

Last login: Fri May 26 12:54:07 from darc

[ctuser@ig1 ~]$ flash_rac -v -l0 /usr/local/gemsrac/power_up_cfg.hexout

*** Warning!!!!!!
*** You are about to reprogram the main FPGA load.
*** If you program the wrong image here or if the load fails,
*** you may not be able to FLASH the device again from the driver.
Are you sure you want to continue? (y/n) y
Really sure? (y/n) y
Board ID: 2316826 C
done reading file '/usr/local/gemsrac/power_up_cfg.hexout'
1305558 bytes
Calculated checksum byte is 0x9e
image size is padded to 1310720
verify OK

[ctuser@ig1 ~]$ flash_rac -v -l1 /usr/local/gemsrac/fan_para.hexout

Board ID: 2316826 C
GE Proprietary – May 2007 – Ph.Giudici - rev.0 p12
 GOC3-4-5 T/S guide.

done reading file '/usr/local/gemsrac/fan_para.hexout'

1305558 bytes
Calculated checksum byte is 0xe8
image size is padded to 1310720
verify OK
[ctuser@ig1 ~]$

GE Proprietary – May 2007 – Ph.Giudici - rev.0 p13

 GOC3-4-5 T/S guide.

Appendix 1 - ipmitool samples : {TOC}

[ctuser@darc ~]$ ipmitool -I lan -H ig1 -P "" sel

SEL Information
Version : 2.0 (v1.5, v2 compliant)
Entries :1
Free Space : 65512 bytes
Percent Used : 0%
Last Add Time : 05/16/2007 00:27:13
Last Del Time : 05/16/2007 00:27:13
Overflow : false
Supported Cmds : 'Delete' 'Partial Add' 'Reserve' 'Get Alloc Info'
# of Alloc Units : 3276
Alloc Unit Size : 20
# Free Units : 3275
Largest Free Blk : 3275
Max Record Size : 12
[ctuser@darc ~]$ ipmitool -H ig1 -P '' chassis power status
Chassis Power is on

[ctuser@darc ~]$ ipmitool -H ig1 -P '' fru

FRU Device Description : Builtin FRU Device (ID 0)
Chassis Type : Main Server Chassis
Chassis Serial : 1544730
Chassis Extra : SR2400
Board Mfg : Intel
Board Product : SE7520JR23
Board Serial : BZJR64500014
Board Part Number : C53659-450
Product Manufacturer : Intel

FRU Device Description : IMM Module FRU (ID 1)

Board Mfg : Intel
Board Product : Intel(R) Management Module - Professional Edition
Board Serial : 641IMFM03893
Board Part Number : C46194-450

FRU Device Description : DIMM 1A SPD (ID 6)

Memory Size : 384 MB
Memory Type : Unknown (0x8)
Voltage Intf : Unknown (0x5)
Error Detect/Cor : ECC
Manufacturer : Micron Technology
Part Number : 18HTF12872Y-40ED6

FRU Device Description : DIMM 1B SPD (ID 7)

Memory Size : 384 MB
Memory Type : Unknown (0x8)
Voltage Intf : Unknown (0x5)
Error Detect/Cor : ECC
Manufacturer : Micron Technology
Part Number : 18HTF12872Y-40ED6

FRU Device Description : DIMM 2A SPD (ID 8)

Memory Size : 384 MB
Memory Type : Unknown (0x8)
Voltage Intf : Unknown (0x5)
Error Detect/Cor : ECC
Manufacturer : Micron Technology
GE Proprietary – May 2007 – Ph.Giudici - rev.0 p14
 GOC3-4-5 T/S guide.

Part Number : 18HTF12872Y-40ED6

FRU Device Description : DIMM 2B SPD (ID 9)

Memory Size : 384 MB
Memory Type : Unknown (0x8)
Voltage Intf : Unknown (0x5)
Error Detect/Cor : ECC
Manufacturer : Micron Technology
Part Number : 18HTF12872Y-40ED6

FRU Device Description : DIMM 3A SPD (ID 10)

Memory Size : 384 MB
Memory Type : Unknown (0x8)
Voltage Intf : Unknown (0x5)
Error Detect/Cor : ECC
Manufacturer : Micron Technology
Part Number : 18HTF12872Y-40ED6

FRU Device Description : DIMM 3B SPD (ID 11)

Memory Size : 384 MB
Memory Type : Unknown (0x8)
Voltage Intf : Unknown (0x5)
Error Detect/Cor : ECC
Manufacturer : Micron Technology
Part Number : 18HTF12872Y-40ED6

[ctuser@darc ~]$ ipmitool -H ig1 -P '' sdr type temp

Baseboard Temp | 30h | ok | 7.1 | 30 degrees C
CPU 1 Temp | 98h | ok | 3.1 | 36 degrees C
CPU 2 Temp | 99h | ok | 3.2 | 36 degrees C
Proc1 ThermCtrl | C0h | ok | 3.1 | Transition to OK
Proc2 ThermCtrl | C1h | ok | 3.2 | Transition to OK
CPU1 VRD Temp | C8h | ok | 3.1 | Transition to OK
CPU2 VRD Temp | C9h | ok | 3.1 | Transition to OK

[ctuser@darc ~]$ ipmitool -H ig1 -P '' sel list last 15

8c54 | 05/15/2007 | 09:46:14 | System Event #0x83 | Timestamp Clock Sync | Asserted
8c68 | 05/15/2007 | 09:46:19 | System Event #0x83 | OEM System boot event | Asserted
8c7c | 05/16/2007 | 11:29:47 | Physical Security #0x05 | System unplugged from LAN | Asserted
8c90 | 05/16/2007 | 11:30:13 | Physical Security #0x05 | System unplugged from LAN | Deasserted
8ca4 | 05/16/2007 | 11:31:53 | System Event #0x83 | Timestamp Clock Sync | Asserted
8cb8 | 05/16/2007 | 11:31:53 | System Event #0x83 | Timestamp Clock Sync | Asserted
8ccc | 05/16/2007 | 11:31:58 | System Event #0x83 | OEM System boot event | Asserted
8ce0 | Pre-Init Time-stamp | Power Unit #0x01 | AC lost | Asserted
8cf4 | Pre-Init Time-stamp | System Event #0x83 | Timestamp Clock Sync | Asserted
8d08 | 05/17/2007 | 04:04:26 | System Event #0x83 | Timestamp Clock Sync | Asserted
8d1c | 05/17/2007 | 04:04:31 | System Event #0x83 | OEM System boot event | Asserted
8d30 | 05/17/2007 | 11:37:15 | Physical Security #0x05 | System unplugged from LAN | Asserted
8d44 | 05/17/2007 | 11:37:23 | Physical Security #0x05 | System unplugged from LAN | Deasserted
8d58 | 05/17/2007 | 11:37:45 | Physical Security #0x05 | System unplugged from LAN | Asserted
8d6c | 05/17/2007 | 11:37:51 | Physical Security #0x05 | System unplugged from LAN | Deasserted

[ctuser@darc ~]$ ipmitool -H ig1 -P '' sensor

Power Unit | 0x0 | discrete | 0x0000| na | na | na | na | na | na
BMC Watchdog | 0x0 | discrete | 0x0000| na | na | na | na | na | na
POST Error | 0x0 | discrete | 0x0000| na | na | na | na | na | na
Critical Int | 0x0 | discrete | 0x0000| na | na | na | na | na | na
Memory | 0x0 | discrete | 0x0000| na | na | na | na | na | na
Logging Disabled | 0x0 | discrete | 0x0000| na | na | na | na | na | na
Session Audit | 0x0 | discrete | 0x0000| na | na | na | na | na | na
BB +1.2V Vtt | 1.210 | Volts | ok | na | 1.090 | 1.109 | 1.292 | 1.317 | na
+1.5V NIC Core | 1.537 | Volts | ok | na | 1.357 | 1.388 | 1.615 | 1.646 | na
BB +1.5v | 1.505 | Volts | ok | na | 1.357 | 1.388 | 1.615 | 1.646 | na

GE Proprietary – May 2007 – Ph.Giudici - rev.0 p15

 GOC3-4-5 T/S guide.

Memory Voltage | 1.813 | Volts | ok | na | 1.627 | 1.669 | 1.936 | 1.978 | na

BB +3.3V | 3.371 | Volts | ok | na | 2.993 | 3.062 | 3.543 | 3.629 | na
STBY +3.3V | 3.320 | Volts | ok | na | 2.993 | 3.062 | 3.543 | 3.629 | na
AUX +3.3V | 3.264 | Volts | ok | na | 2.992 | 3.060 | 3.553 | 3.621 | na
BB +5V | 4.966 | Volts | ok | na | 4.524 | 4.628 | 5.382 | 5.486 | na
STBY +5V | 4.883 | Volts | ok | na | 4.549 | 4.626 | 5.371 | 5.500 | na
BB +12V | 11.966 | Volts | ok | na | 10.912 | 11.098 | 12.896 | 13.144 | na
BB -12V | -11.733 | Volts | ok | na | -13.119 | -12.842 | -11.178 | -10.952 | na
BB Vbat | 0x0 | discrete | 0x0400| na | na | na | na | na | na
Baseboard Temp | 30.000 | degrees C | ok | na | 5.000 | 10.000 | 60.000 | 66.000 | na
CPU 1 Blower | 2485.000 | RPM | ok | na | 0.000 | 0.000 | na | na | na
CPU 2 Blower | 2414.000 | RPM | ok | na | 0.000 | 0.000 | na | na | na
Add-in Blower | 1846.000 | RPM | ok | na | 0.000 | 0.000 | na | na | na
Exhst Fan | 7242.000 | RPM | ok | na | 0.000 | 0.000 | na | na | na
SCSI 1 Term Flt | 0x0 | discrete | 0x0000| na | na | na | na | na | na
SCSI 2 Term Flt | 0x0 | discrete | 0x0000| na | na | na | na | na | na
Proc Missing | 0x0 | discrete | 0x0000| na | na | na | na | na | na
System Event | 0x0 | discrete | 0x0000| na | na | na | na | na | na
Button | 0x0 | discrete | 0x0000| na | na | na | na | na | na
SMI Timeout | 0x0 | discrete | 0x0000| na | na | na | na | na | na
NMI State | 0x0 | discrete | 0x0000| na | na | na | na | na | na
SMI State | 0x0 | discrete | 0x0000| na | na | na | na | na | na
CPU 1 Status | 0x0 | discrete | 0x8000| na | na | na | na | na | na
CPU 2 Status | 0x0 | discrete | 0x8000| na | na | na | na | na | na
CPU 1 Temp | 36.000 | degrees C | ok | na | 5.000 | 10.000 | 91.000 | 99.000 | na
CPU 2 Temp | 36.000 | degrees C | ok | na | 5.000 | 10.000 | 91.000 | 99.000 | na
CPU 1 VRM | 12.028 | Volts | ok | na | 10.912 | 11.098 | 12.896 | 13.144 | na
CPU 2 VRM | 12.028 | Volts | ok | na | 10.912 | 11.098 | 12.896 | 13.144 | na
Proc1 ThermCtrl | 0x0 | discrete | 0x0100| na | na | na | na | na | na
Proc2 ThermCtrl | 0x0 | discrete | 0x0100| na | na | na | na | na | na
CPU1 VRD Temp | 0x0 | discrete | 0x0100| na | na | na | na | na | na
CPU2 VRD Temp | 0x0 | discrete | 0x0100| na | na | na | na | na | na
Proc 1 Vccp | 1.254 | Volts | ok | na | 0.813 | 0.838 | 1.436 | 1.481 | na
Proc 2 Vccp | 1.247 | Volts | ok | na | 0.813 | 0.838 | 1.436 | 1.481 | na
CPU Config Error | 0x0 | discrete | 0x0000| na | na | na | na | na | na
DIMM 1B | 0x0 | discrete | 0x0400| na | na | na | na | na | na
DIMM 1A | 0x0 | discrete | 0x0400| na | na | na | na | na | na
DIMM 2B | 0x0 | discrete | 0x0400| na | na | na | na | na | na
DIMM 2A | 0x0 | discrete | 0x0400| na | na | na | na | na | na
DIMM 3B | 0x0 | discrete | 0x0400| na | na | na | na | na | na
DIMM 3A | 0x0 | discrete | 0x0400| na | na | na | na | na | na
D1 Sparing Enb | na | discrete | na | na | na | na | na | na | na
D1 Spare Redun | na | discrete | na | na | na | na | na | na | na
D2 Sparing Enb | na | discrete | na | na | na | na | na | na | na
D2 Spare Redun | na | discrete | na | na | na | na | na | na | na
D1 Mirror Enbl | na | discrete | na | na | na | na | na | na | na
D1 MirrorRedun | na | discrete | na | na | na | na | na | na | na

[ctuser@darc ~]$ ipmitool -H ig1 -P '' sdr

Power Unit | 0x00 | ok
BMC Watchdog | 0x00 | ok
POST Error | 0x00 | ok
Critical Int | 0x00 | ok
Memory | 0x00 | ok
Logging Disabled | 0x00 | ok
Session Audit | 0x00 | ok
BB +1.2V Vtt | 1.21 Volts | ok
+1.5V NIC Core | 1.54 Volts | ok
BB +1.5v | 1.51 Volts | ok
Memory Voltage | 1.81 Volts | ok
BB +3.3V | 3.37 Volts | ok
STBY +3.3V | 3.32 Volts | ok
AUX +3.3V | 3.26 Volts | ok
BB +5V | 4.97 Volts | ok
STBY +5V | 4.88 Volts | ok
BB +12V | 11.97 Volts | ok
BB -12V | -11.73 Volts | ok
BB Vbat | 0x04 | ok
Baseboard Temp | 30 degrees C | ok
CPU 1 Blower | 2485 RPM | ok
CPU 2 Blower | 2414 RPM | ok
Add-in Blower | 1846 RPM | ok
Exhst Fan | 7242 RPM | ok
SCSI 1 Term Flt | Not Readable | ns
GE Proprietary – May 2007 – Ph.Giudici - rev.0 p16
 GOC3-4-5 T/S guide.

SCSI 2 Term Flt | Not Readable | ns

Proc Missing | 0x00 | ok
System Event | 0x00 | ok
Button | 0x00 | ok
SMI Timeout | 0x00 | ok
NMI State | 0x00 | ok
SMI State | 0x00 | ok
CPU 1 Status | 0x80 | ok
CPU 2 Status | 0x80 | ok
CPU 1 Temp | 36 degrees C | ok
CPU 2 Temp | 36 degrees C | ok
CPU 1 VRM | 12.03 Volts | ok
CPU 2 VRM | 12.03 Volts | ok
Proc1 ThermCtrl | 0x01 | ok
Proc2 ThermCtrl | 0x01 | ok
CPU1 VRD Temp | 0x01 | ok
CPU2 VRD Temp | 0x01 | ok
Proc 1 Vccp | 1.25 Volts | ok
Proc 2 Vccp | 1.25 Volts | ok
CPU Config Error | 0x00 | ok
DIMM 1B | 0x04 | ok
DIMM 1A | 0x04 | ok
DIMM 2B | 0x04 | ok
DIMM 2A | 0x04 | ok
DIMM 3B | 0x04 | ok
DIMM 3A | 0x04 | ok
D1 Sparing Enb | Not Readable | ns
D1 Spare Redun | Not Readable | ns
D2 Sparing Enb | Not Readable | ns
D2 Spare Redun | Not Readable | ns
D1 Mirror Enbl | Not Readable | ns
D1 MirrorRedun | Not Readable | ns
[ctuser@darc ~]$

Appendix 2 – Console Diagnostics. {TOC}

Console Diags run many diags & tests simultaneously, on the HP, SCSI Tower, DARC, IG… and is
configurable as what tests to run, number of loops, etc…. It uses graphical Xwindows interface, and
therefore is not primarily oriented to remote operations, even if it is possible.
To run the diags : 2 ways :
• From the CSD page, with Proprietary key : click on the Console Diags link.
• From a Linux shell with Apps down, as root : type diagsSetup.sh
• With releases 07MW11.x, from From a Linux shell with Apps down, as root : type ConsoleDiags
The tool will open as many Xterm windows as tests made, and you will see the execution & results in each
window.
WARNING : if SCSI tower diags are selected, you need MOD & DVD media inserted, and they will be
overwritten !

GE Proprietary – May 2007 – Ph.Giudici - rev.0 p17