Superdome 扩容

8/10/2019 Superdome

1/42

DISCLAIMER:

This PDF was generated on February 14, 2001. There may be

a newer version of this PDF at http://superdome.hp.com

8/10/2019 Superdome

2/42

System Hardware>Support Management Station H

Overview: Support Management Station

unctions

Two "big pipe" applications: SCAN and FWUU'

Repository for files and functions needed for SuperDome

nstallation

Rack: IOX or other rack

Table

Up to 8 SuperDomes per Support Management Station (approx.) need one TS for SCAN/FWU

if more than one: need to reset IPs

Challenge in site prep: get IP for each TS on customer's LAN

AN

Private LAN: the "big pipe"

Customer LAN: access to the rest of the net

latform Comparison

A180 A500

taccato Crescendo

8 Gig HD 18 Gig HD

56 M mem 256 M mem

wo LANs two LANs

80 MHz 360 MHz

ingle proc single/dual proc

arly release all other shipments (different SCSI cables needed)

oftware

Big two (loaded from CD along with diagnostics)


ttp://superdome-test.fc.hp.com/sd_epss_cdrom/content/00/00/M7/idd/106.html (1 of 2) [2/14/2001 2:45:58 PM]
http://superdome-test.fc.hp.com/sd_epss_cdrom/content/hrdwr/130.htmlhttp://superdome-test.fc.hp.com/sd_epss_cdrom/content/hrdwr/hrdwr/115.htmlhttp://superdome-test.fc.hp.com/sd_epss_cdrom/content/hrdwr/hrdwr/115.htmlhttp://superdome-test.fc.hp.com/sd_epss_cdrom/content/hrdwr/130.html

8/10/2019 Superdome

3/42

Several others including tsinstall and a chassis code capture program

Support Management Station Hardware Finding More System Management Station Informati


http://superdome-test.fc.hp.com/sd_epss_cdrom/content/hrdwr/hrdwr/115.htmlhttp://superdome-test.fc.hp.com/sd_epss_cdrom/content/hrdwr/hrdwr/115.htmlhttp://superdome-test.fc.hp.com/sd_epss_cdrom/content/hrdwr/hrdwr/115.html

8/10/2019 Superdome

4/42

8/10/2019 Superdome

5/42


nstalling Firmware Update Utility (FWUU)

nstalling FWUU from CD-ROM

he Firmware Update Utility (fwuu) is a tool to aid in updating firmware files on the superdome famcomputers. It resides on the Support Management Station (SMS) in the /opt/fwuu directory. For m

formation on using fwuu, see Using the Firmware Update Utility.

o install fwuu from the Support + Media CD-ROM: (assuming already logged in to SMS)

Insert the Support + media in the SMS DVD drive.1.

Mount the drive. The dirnamecan be anything you like, but typicais something easy like /CD, /SDROM, /CD-ROM. Names like that. The /deviceis the HPUX n

for the CD or DVD drive. It will typically have a name like /dev/dsk/c0t1d2 or something sim

To find the proper name, use the HPUX command ioscan -fnC disk. You must be root

use the ioscan command.

2.

Type swinstall -s /CD (for example) In the window that appears for the software you should se

FWUU and Scan-Released. There may be other files, too, but these two should be there. Selec

FWUU by highlighting it, then marking it for selection. Then start the install.

3.

After the file install is complete, check the SMS directory, /opt/fwuu. There should be one

executable file, called fwuu and one README or Release Notes file.

4.

If you are finished with the CD, unmount the drive (umount /CD) and remove the media.5.

nstalling FWUU from Depothere are different ways to obtain needed software from the various depots at HP. How we retrieve i

pends upon the host we are using to retrieve the software and where it is located. If we are outside

e HP firewall, there are various depots around the world for customers to download patches and

rmware files. If we are inside the HP firewall, we can use swinstall or swcopy to retrieve the neededes, archive them to tape and carry the tape to the customer site. This section will not attempt to list

mes of the various depots. It is a procedural listing for retrieving the needed files, getting them to t

propriate system and loading them into the proper directory.

Example 1 Obtaining FWUU from external depot directly to customer's SMS


ttp://superdome-test.fc.hp.com/sd_epss_cdrom/content/00/00/MI/idd/108.html (1 of 2) [2/14/2001 2:46:12 PM]
http://superdome-test.fc.hp.com/sd_epss_cdrom/content/hrdwr/130.htmlhttp://superdome-test.fc.hp.com/sd_epss_cdrom/content/hrdwr/hrdwr/115.htmlhttp://superdome-test.fc.hp.com/sd_epss_cdrom/content/00/01/8M/idd/128.htmlhttp://superdome-test.fc.hp.com/sd_epss_cdrom/content/00/01/8M/idd/128.htmlhttp://superdome-test.fc.hp.com/sd_epss_cdrom/content/hrdwr/hrdwr/115.htmlhttp://superdome-test.fc.hp.com/sd_epss_cdrom/content/hrdwr/130.html

8/10/2019 Superdome

6/42

The swinstall command is probably easiest. As root, type swinstall -s 1.

Once the swinstall / depot screen is displayed, one the the selections should be Fwuu. Select

and mark Fwuu for install. You should be able to select the directory for install.

2.

Start the install process from the Actionheading, selecting Install.3.

When download is complete, exit the program.4.

Verify the fwuu executable file is in the proper directory. The absolute path is /opt/fwuu/fwu5.

Loading and / or updating the firmware files used by fwuu is covered in Updating SuperdomFirmware.

6.

Example 2 Obtaining FWUU from internal HP depot to an alternate host

This section is still under test. It will be completed soon.1.

Finding More System Management Station Information Updating Superdome Firmwa


ttp://superdome-test.fc.hp.com/sd_epss_cdrom/content/00/00/MI/idd/108.html (2 of 2) [2/14/2001 2:46:12 PM]

8/10/2019 Superdome

7/42

8/10/2019 Superdome

8/42


Using the Firmware Update Utility

eneral Description

e Firmware Update Utility (FWUU) is a tool developed by the System Supportability Lab / Diagnostic and Su

ols team for verifying the revisions of firmware on the various entities in the superdome system and updating mware files, if needed. At superdome first release, it will be available only in HPUX and will reside in the

pt/fwuudirectory on the Support Management Station. Later FWUU will be ported to the Microsoft Windo

vironment for inclusion on the CE Toolkit.

wo Versions of FWUUthe early stages of superdome release, there are two versions of the Firmware Update Utility. One is fwuu_3

e other is fwuu_44. There are many different versions of the superdome firmware during the pre-release stage

e product. The version of fwuu needed is dependent upon the revision of firmware installed.

this time, fwuu_30 can always be used to update the superdome firmware. It has a drawback, though. Fwuu_3

ll update the files one at a time. Even if you input multiple flash handles on the command line, fwuu will updatities singly. If you were to try to update all the PDC files in a 32way machine with one command you would e

wuu>update 1152-1159 hd.bin.6.0.frm. With fwuu_30, all eight cells would have the PDC files

dated, but one at a time. This will take about 30 minutes or more.

ith fwuu_44, the command executes the download in parallel. The same command as the one above would exe

d load all of the cell boards at the same time reducing the download time to about 5 minutes. There is a warnin

th fwuu_44, however. GSP firmware version 6.4, dated 8/15/00 or later is required to run fwuu_44. If you hav

rlier version of GSP firmware, update the GSP file first, then you can use fwuu_44 to update the rest of the

achine.

GSP firmware 6.4, dated 8/15/00, is required to run fwuu_44. Serious problems could occur iffwuu_44 is used with any firmware earlier than 8/15/00

WUU Commands

e Firmware Update Utility has five commands to aid the user in successfully performing a firmware update ta

ey are:

DISPMAP--Displays a map of the remote/target superdome system

DISPFILES--Displays firmware files residing on local/source system

UPDATE--Updates firmware on an entity specified by its flash handle Usage: update

8/10/2019 Superdome

9/42

ep 1. Log in to the Support Management Station as hduser.

ep 2. Change the working directory to /opt/fwuu (cd /opt/fwuu).

ep 3.Start FWUU with the command ./fwuu. FWUU then asks for the IP address of the GSP on the system

be updated.

ep 4.

Type the IP address of the Private port. FWUU responds with the following:

A "successfully connected" message

An partial output of the Group A Complex Profile

An output of the DISPFILES command (automatic)

An output of the DISPMAP command (automatic)

A fwuu>prompt waiting for a user command

Example 1 Successful Connection - FWUU_30

feshd1-t% ./fwuu

********************************************************************

***** ****

***** Firmware Update Utility ****

***** ****

***** (C) Copyright Hewlett-Packard Co 1999 ****

***** All Rights Reserved ****

***** ****

***** THIS PROGRAM IS NOT LICENSED TO CUSTOMERS ****

***** ****

***** This program is intended for use by trained HP support ****

***** personnel only. HP shall not be liable for any damages ****

***** resulting from unauthorized use of this program. This ****

***** program is the property of HP. ****

***** ****

***** Version A.00.30 ****

***** **** ********************************************************************

Please enter address of Halfdome system: 15.99.111.101

System successfully connected to "15.99.111.101"

System Utilities Board Firmware Update - header version 0.1

Maximum USB transfer size is 4100

Retrieving Complex Profile Information......


ttp://superdome-test.fc.hp.com/sd_epss_cdrom/content/00/01/8M/idd/110.html (2 of 6) [2/14/2001 2:46:20 PM]

8/10/2019 Superdome

10/42

Complex Name:

Model Number:

Model String:

Original Product Number:

Current Product Number:

Serial Number:

Complex Revision Number: 0000

Firmware files found in "." directory:

Firmware

Filename Entity Type Revision Hversion

________________________ ___________ ________ _________

cio.4.14.frm PDI 4.14 0x42

clu.4.6.frm CLU 4.6 0x42

pm3.4.6.frm PM3 4.6 0x42

sinc.4.10.frm SINC 4.10 0x42

sub.4.16.frm GSP 4.16 0x42

hd.bin.04.00.frm PDC 4.0 0x5c7

Listing flash handle map of remote system "15.99.49.131":

Flash Firmware

Cabinet Entity Type Handle Cell# PDI# Revision Hversion

_______ ___________ ______ _____ ____ ________ __________

0 GSP 576 N/A N/A 4.16 0x42

0 PM3 640 N/A N/A 4.6 0x42

0 CLU 704 N/A N/A 4.6 0x42

0 PDI 775 4 7 4.14 0x42 0 SINC 1088 0 N/A 4.10 0x41

0 PDC 1152 0 N/A 4.0 0x05C7

0 SINC 1092 4 N/A 4.10 0x41

0 PDC 1156 4 N/A 4.0 0x05C7

Type HELP for command information.

FWUU>

dentifying the Entities to Update

e example above shows the different columns and the values associated with them. These values uniquely iden

FRU that contains firmware capable of field updates and are defined below:

Cabinet--The cabinet number in which the entity is contained

Entity Type--The category or name of the entity



8/10/2019 Superdome

11/42

Flash Handle--A unique number based on a mapping algorithm whereby no two entities within a complex

have the same number

This number is part of the UPDATE command line where different checks are made to ensure success.

Cell number--A number that is combined with the cabinet number to point to a physical location

PDI number--The physical location of the Core IO card where PDI resides

In the example above, the PDI number is 7. It maps to IO Bay 1, IO Chassis 3.

Firmware Revision--The revision of firmware currently installed on that entity

Hversion--A reference to the hardware version of the entity

It is a calculated number rather than a number extracted from the FRUID.

pdating Firmware

update the firmware on an entity or entities, use the UPDATE command. The format of the command is as

lows:

DATE

multiple entities are being updated with the same command line, they must all be the same type. For example,

ere is more than one cell board to be updated, the PDC on every cell board in a cabinet could be updated with o

mmand line as shown below:

DATE 1152 1153 1154 1155 1156 1157 1158 1159 pdc.4.11.frm

stead of entering all of the Flash Handles separately, they can be entered as a range (provided that they all are

cluded). The following is an example:

DATE 1152-1159 pdc.4.11.frm

l entities of a type within a partition must have the same firmware revision. As an example, suppose one cabin

th eight cells divided equally into two partitions, and the four cells in the first partition have PDC firmware rev

hile the four cells in second partition are running PDC 4.22. This is an acceptable configuration. To replace a c

e of the partitions, you would have to check the revision of the firmware (PDC and PDHC) on the new cell bo

fore allowing the cell to join the partition.

Save all firmware files (.frm) in a sub-directory of /opt/fwuu just in case you need to down-rev a firmwa

file.

There will be a table of compatible hardware and firmware revisions published. Always check for the laversion of the compatibility document before updating firmware to a new revision.

rtain rules about the state of the hardware apply to Firmware Update Utility. These are listed below by the typ

mware being updated:

PDC, PDHC, and CIO--The partitions must be shut down and the cell boards must be at BIB. The GSP

command RR insures this. The cabinet must be powered on (the +5HKP and +48VDC must be on).

CLU--The cabinet must be powered down (+5HKP and +48VDC must be off).



8/10/2019 Superdome

12/42

PM--The cabinet must be powered down (+5HKP and +48VDC must be off).

GSP--The GSP can be updated while everything is up and running without affecting the cabinet or operati

partitions.

Because the GSP must be reset upon completion, the connection from the Support Management Station to

GSP will be lost and all consoles, VFPs, and other connections to the GSP will be disconnected. Once the

has completed rebooting, the connections can be re-established.

Do not interrupt or disturb the firmware update process in any way, even if you have made a mist

and selected the wrong revision of the firmware file. The firmware file will be incomplete, corrupt

and the board will have to be replaced.

Once the fwuu> prompt has returned, you can immediately do another update with the proper file

As long as the entity doesn't reset, you can reload the proper firmware file. If the entity does reset

corrupted firmware file will load from Flash to RAM and the board will be inoperable. The only t

in this case is to replace the affected board.

Example 2 Example of Successful Update

FWUU>update 576 sub.4.16.frm

Updating firmware................

Percentage Complete

100 %

Flash Update

Cabinet Entity Type Handle Firmware File Status

_______ ___________ ______ ______________________ _________

0 GSP 576 sub.4.16.frm PASSED

Resetting entity(s) requested for update.....

Continue (yes/no)? [Y]:

Successful reset of all entity(s).

Warning: FWUU must abort execution, communication with

the remote system is lost after the GSP is reset.

Exiting Program

feshd1-t%



8/10/2019 Superdome

13/42

e above example appears to have had problems because of the Warning: statement. In this case, it is a successf

date. As mentioned previously, when the GSP is updated, it will reset, dropping all connections to it. As a user

ve the GSP enough time to reset and reboot, then re-establish the connection.

Example 3 Example of a Refused Update

FWUU>update 704 clu.4.6.frm

Checking power state of cabinet 0 .......

ERROR: Cabinet 0 was not shutdown, illegal UPDATE!

UPDATE was NOT successful

FWUU>

stated in the last line of the above example, the update of CLU firmware was not successful. However, the Up

ility was successful in that it determined the cabinet was in a powered up state. The utility requires the +48 V

f before it will update the CLU or PM firmware. The rules for machine state before updating firmware are enfo

FWUU but not explained beforehand.

xiting FWUUhen the update task has been completed, exit FWUU and log off of the Support Management Station. Type ex

r>to get back to the Support Management Station HPUX prompt. Type exitagain to disconnect from t

pport Management Station.

Updating Superdome Firmware Installing SCAN



8/10/2019 Superdome

14/42


nstalling SCAN Tools

efore Installation

fore you install the scan tools, there is a check that should be made. There are two tunables in the kernel that

checked and modified, if necessary. Using SAM, go to Kernel Configuration, then select Configurablerameters, then set maxdsizto at least 128 MB (0x08000000) and maxuprc to 200. Select kernel rebuild aboot the SMS to put the changes into effect. When the SMS has finished rebooting you may install the Scan

ftware by either Support + media (CD), from a self-built tape, or directly from the depot (internal only). Ther

ctions below detailing how to install Scan by each of the methods mentioned.

nstalling SCAN Tools from Support + Media (CD-ROM)

e files needed to run scan on a superdome system are contained on the Support + media and on various depo

thin the HP firewall.

install Scan tools from the Support + media CD-ROM (assuming already logged in as root to SMS):

ep 1. Insert the Support + media in the SMS DVD drive.

ep 2.

Mount the drive. The dirnamecan be anything, but typically it is somethin

easy to remember as /CD, /SDROM, /CD-ROM. The /deviceis the HPUX name for the CD or DVD d

It will typically have a name such as /dev/dsk/c0t1d2or something similar. To find the proper

name, use the HPUX command ioscan -fnC disk. You must be root to use the ioscan comman

ep 3.Enter swinstall -s /CD(for example). FWUU and Scan-Released should appear the softwarewindow. There may be other files, too, but these two should be there.

ep 4. Select Scan-Released by highlighting it and then marking it for selection.

ep 5. Start the install by selecting Action / Install.

ep 6.After the file install is complete, check the SMS directory, /opt/scansw. There should be three

directories: bin, data, and scripts. The swinstallprocess also creates the hduser username and passwor

setup.

ep 7. When finished with the CD, unmount the drive (umount /CD) and remove the media.

ep 8.Test the process. Log out as root and log back in as hduser (password: hduser). You should be

able to run the/opt/scansw/bin/cmdcommand, which builds the configuration files for the Superdom

nstalling SCAN Tools From a Self Built Tape

e Scan executable and its associated files will not be placed on an external depot server. Because Scan is

nsidered a diagnostic tool, it must remain confidential. Therefore, files needed for scan will only be obtainabl

om the Support + media or from an internal software depot. Since customer sites are outside of the HP firewa

wnload the files to a local server via swcopyand transfer the files to tape. You can then carry the tape to the

stomer site and install the files on the Support Management Station with the swinstallcommand.

e Scan software can be retrieved from an internal depot,

nstalling SCAN

ttp://superdome-test.fc.hp.com/sd_epss_cdrom/content/00/00/MH/idd/111.html (1 of 4) [2/14/2001 2:46:25 PM]

8/10/2019 Superdome

15/42

pdst123.cup.hp.com/scan/depots/released/IPR0103. The basic name should stay the same,

PR0103" changes periodically (usually quarterly). The following procedure retrieves the scan software to a lo

PUX machine, transfers the bundle to tape, and installs the files from tape to the Superdome Support Manage

ation.

e items needed are:

HPUX based workstation or server with a DDS tape drive attached and available

Blank or scratch tape that can be left at the customer's site, if security requires

Superdome Support Management Station at the Customer's site

ep 1. Insert the blank or scratch tape into the DDS drive.

ep 2.

Log on to the HPUX machine as root.

The default directory for SD to use is /var/usr/spool/.

If you want a different directory, create it at this time. It will be specified later after starting the swcopprocess.

Whatever directory is specified, it will become registered with SD. In the future, whenever you use a command (swinstall, swcopy, swpackage, swremove, etc.), the directories you have used will appear

the list of depots.

ep 3.

At the # prompt enter the following:

swcopy -s hpdst123.cup.hp.com:/scan/depots/released/IPR0103

The current depot for scan software is listed above. However, it will change periodically. Check with

WWSIT or WTEC for the latest depot site. Be sure to substitute the latest depot site (IPR0112, IPR02

etc.). When the swcopy window comes up, point the target path to the directory you want the software

installed. You can set up your own temporary directory for files and delete them when finished. For

example, /tmp/scanfor scan software would keep it separate from all of the patch bundles that arecopied by this same process.

ep 4.

When the files are copied to the specified directory, close the swcopywindow.

The files will now be moved to tape in a way that swinstallunderstands. This will facilitate the

installation at the customer's site.

ep 5.

Enter the swcommand.

There are a lot of arguments available to this command, being part of the SD command family. Use th

HPUX man pages for the specific command, or, enterman 5 sd. This gives a generic listing of the

commands, their arguments and options. The command for this example is:

/usr/sbin/swpackage -s /tmp/scan -x target_type=tape -d /dev/rmt/0m.

You may have to include some other optional arguments on the command line, depending on how you

particular system is set up. The above swpackagecommand example uses the /tmp/scandepot to

the files we wish to package, the target is a tape, and the specific device is/dev/rmt/0m. The output fr

the above command is shown in Example 1 below.

ep 6.Take the tape (can be done with a CD, also) to the customer's site and load into the Superdome SMS D

drive.

nstalling SCAN


8/10/2019 Superdome

16/42

ep 7.

Install the Scan software package by entering the following command:

/usr/sbin/swinstall -s /dev/rmt/0m

The DDS drive on the SMS should be this name. The tape built in the earlier steps contains an SD ima

of the files on the depot. The swinstall screens operate normally. The install takes a little longer, since

files are on tape and not coming over the network.

ep 8.When the installation is complete, check the files under /opt/scanswfor error. Log out as root and

in as hduser (password: hduser), run the ./bin/scan_setupscript., and then run the cmdcomm

and you are ready to go. For more information on scan_setupand cmd.

Example 1 Typical swpackage Output

# /usr/sbin/swpackage -s /tmp/scan -x target_type=tape -d /dev/rmt/0m

======= 10/30/00 10:10:17 CST BEGIN swpackage SESSION

* Session started for user "[email protected]".

* Source: gromit1:/tmp/scan

* Target: gromit1:/dev/rmt/0m * Software selections:*

* Beginning Selection Phase.

* Reading the source depot "/tmp/scan".

* Reading the contained files information for each selected

product.

NOTE: The temporary target depot "/var/tmp/pkgAAAa07854" has bee

created.

* Selection Phase succeeded.

* Beginning Analysis Phase.

* Analysis Phase succeeded.

* Beginning Package Phase.

* Packaging the bundle

"Fwuu,r=B.11.00.01.03,a=HP-UX_B.11.00_32/64,v=HP".

* Packaging the bundle

"Scan-Released,r=B.11.00.01.04,a=HP-UX_B.11.00_32/64,v=HP".

* Packaging the product "Fwuu-SW".

* Packaging the fileset "Fwuu-SW.FWUU".

* Packaging the product "Scan-SW".

* Packaging the fileset "Scan-SW.BIN".

* Packaging the fileset "Scan-SW.DATA".

* Packaging the fileset "Scan-SW.DOC". * Packaging the fileset "Scan-SW.SCRIPTS".

* Package Phase succeeded.

* Beginning Tapemaker Phase.

* Copying the temporary depot to the tape "/dev/rmt/0m".

* Calculating the tape blocks required to copy the temporary

depot to the tape "/dev/rmt/0m".

NOTE: The temporary depot requires 16250 Kbytes on the tape

"/dev/rmt/0m".

* Writing the tape "/dev/rmt/0m" (tape 1 of 1).

nstalling SCAN


8/10/2019 Superdome

17/42

8/10/2019 Superdome

18/42

System Hardware>Support Management Station

onfiguring Scan Software (JUST)

he Importance of cmdhen testing the Superdome machine the Scan software, JUST and its libraries, use configuration files to determine what

present and are to be tested. The cmdcommand builds the configuration files. Every time a board configuration chang

de to a Superdome cabinet, cmdmust be re-run to update the configuration files. If cmdis not run after a change, any plonger present may still be in the configuration file. This will produce errors during test. If cmdis not run after a new ptalled, the new part will not be tested, since it is not in the configuration file.

ch part that can be scanned, either a board or an ASIC, has a data or definition file associated with it that tells JUST howal with that part. These definition files are automatically included in the Scan software bundle and placed in the properectories for JUST. (See Installing Scan)

r scan, each cabinet is considered a node. In a Superdome complex, there can be up to four nodes. When cmdis run agah a complex, it creates a directory under the /opt/scansw/datadirectory called cplx-name. Where name is the n

the Private GSP LAN name. This directory contains configuration files for each node called node_x.cfg, wherexeq

cabinet number set on the UGUY board for each cabinet. cmdalso creates and/or modifies the complex.cfgfile. Th

e contains the information about each complex served by this Support Management Station (SMS).

xample 1 Example of Multiple Systems in complex.cfg

% cat complex.cfg

Complex

Hostname priv-04

Architecture 48

IP_Address 15.99.111.104

Port_Number 5151

Nodes

# Keyword Node SDP Queue Queue

# Num Version depth Size bytes

# -----------------------------------------------------

Node_Reference 0 1.0 1 96768

End_Of_Nodes

End_Of_Complex

Complex

Hostname priv-05

Architecture 32

IP_Address 15.99.111.105 Port_Number 5151

Nodes



# -----------------------------------------------------



Node_Reference 8 1.0@ 1 96768

End_Of_Nodes

Configuring SCAN

ttp://superdome-test.fc.hp.com/sd_epss_cdrom/content/00/00/C8/idd/112.html (1 of 13) [2/14/2001 2:46:33 PM]

8/10/2019 Superdome

19/42

8/10/2019 Superdome

20/42

# This is the part number of the board as

# specified in the boards serial eprom.

#

# This is the scan revision of the board as specified

# in the boards serial eprom.

#-----------------------------------------------------------------

##########################################################################

#Node Num: 0 Family: BACKPLANE Type: MAIN BACKPLANE Number: 0

##########################################################################

Board 02100000 DLB A6113-60001_0001

##########################################################################

#Node Num: 0 Family: BACKPLANE Type: HMIOB Number: 0

##########################################################################

Board 02200000 HMIOB A5201-60005_0001

##########################################################################

#Node Num: 0 Family: BACKPLANE Type: HMIOB Number: 1

##########################################################################

Board 02210000 HMIOB A5201-60005_0001

##########################################################################

#Node Num: 0 Family: BACKPLANE Type: HIOB Number: 1

##########################################################################

Board 02310000 HIOB2 A4856-60101_0001

##########################################################################


##########################################################################

Board 02350000 HIOB2 A4856-60101_0001

##########################################################################

#Node Num: 0 Family: PROCESSOR Type: CELL Number: 0

##########################################################################

Board 03100000 HCBW2 A5205-60001_0001

##########################################################################


##########################################################################

Board 03130000 HCBW2 A5205-60001_0001

##########################################################################

#Node Num: 0 Family: IO Type: CORE IO Number: 1

##########################################################################Board 05110000 CIO A5210-60001_0001

##########################################################################


##########################################################################

Board 05150000 CIO A5210-60001_0001

#-----------------------------------------------------------------

# Each path entry in the node has the following format:

Configuring SCAN


8/10/2019 Superdome

21/42

#

# Path

# Device _

# .

# .

# Device _

# End

#

# Path, Device, and End are all keywords used to parse this file.

#

# is a unique number identifying this path.

#

# Within each path is a list of devices present on that path.

#

# This field identifies which board the device is on.

#

# This field gives the device a unique name and comes from

# a user generated file.

#

# This field is the reference designator of the device.

#

# This field is the jtag id of the device.#

# This is the part number of the device.

#

# This is the revision of the part from the jtag id.

#-----------------------------------------------------------------

Path 0

##########################################################################


##########################################################################

Device 02100000 XBC00 U67 0x24071049 togo

##########################################################################


##########################################################################

Device 02100000 XBC01 U4 0x24071049 togo

End

Path 2

##########################################################################


##########################################################################

Device 02100000 FPGA0 U32 0x010400dd fpga

End

Path 3

Configuring SCAN


8/10/2019 Superdome

22/42

##########################################################################


##########################################################################

Device 03100000 cc U44 0x14076049 dna

##########################################################################


##########################################################################

Device 03100000 dillon U7 0x11250005 dillon

End

Path 4

##########################################################################


##########################################################################

Device 03100000 cpu0 U35 1QM1-000A pcxw

########################################################################## #Node Num: 0 Family: PROCESSOR Type: CELL Number: 0

##########################################################################

Device 03100000 m2y U10 0x14091049 m2

##########################################################################


##########################################################################

Device 03100000 m3y U11 0x14091049 m2

##########################################################################


##########################################################################

Device 03100000 m3x U38 0x14091049 m2

##########################################################################


##########################################################################

Device 03100000 m2x U37 0x14091049 m2

End

Path 5

##########################################################################


##########################################################################

Device 03100000 m0x U71 0x14091049 m2

##########################################################################


##########################################################################

Device 03100000 m1x U72 0x14091049 m2

Configuring SCAN


8/10/2019 Superdome

23/42

##########################################################################


##########################################################################

Device 03100000 m1y U51 0x14091049 m2

##########################################################################


##########################################################################

Device 03100000 m0y U50 0x14091049 m2

##########################################################################


##########################################################################


End

Path 12

##########################################################################

#Node Num: 0 Family: PROCESSOR Type: CELL Number: 3 ##########################################################################

Device 03130000 cc U44 0x14076049 dna

##########################################################################


##########################################################################

Device 03130000 dillon U7 0x11250005 dillon

End

Path 13

##########################################################################


##########################################################################


##########################################################################


##########################################################################

Device 03130000 m2y U10 0x14091049 m2

##########################################################################


##########################################################################

Device 03130000 m3y U11 0x14091049 m2

##########################################################################


##########################################################################

Device 03130000 m3x U38 0x14091049 m2

Configuring SCAN


8/10/2019 Superdome

24/42

##########################################################################


##########################################################################

Device 03130000 m2x U37 0x14091049 m2

End

Path 14

##########################################################################


##########################################################################

Device 03130000 m0x U71 0x14091049 m2

##########################################################################


##########################################################################

Device 03130000 m1x U72 0x14091049 m2

##########################################################################

#Node Num: 0 Family: PROCESSOR Type: CELL Number: 3 ##########################################################################

Device 03130000 m1y U51 0x14091049 m2

##########################################################################


##########################################################################

Device 03130000 m0y U50 0x14091049 m2

##########################################################################


##########################################################################


End

Path 30

##########################################################################


##########################################################################

Device 02310000 p00 U5001 0x582360a9 elroy

##########################################################################


##########################################################################


##########################################################################


##########################################################################


##########################################################################

Configuring SCAN


8/10/2019 Superdome

25/42


##########################################################################


##########################################################################


##########################################################################


##########################################################################


##########################################################################


End

Path 31

##########################################################################


########################################################################## Device 02310000 p06 U5007 0x582360a9 elroy

##########################################################################


##########################################################################


##########################################################################


##########################################################################


##########################################################################


##########################################################################


##########################################################################


##########################################################################


########################################################################## #Node Num: 0 Family: BACKPLANE Type: HIOB Number: 1

##########################################################################


End

Path 32

##########################################################################

Configuring SCAN


8/10/2019 Superdome

26/42


##########################################################################

Device 05110000 diva U18 1821-3440 diva

##########################################################################


##########################################################################

Device 05110000 cio_lan U8 1821-3749 cio_lan

##########################################################################


##########################################################################

Device 02310000 reo U5000 0x14081049 reo

End

Path 42

##########################################################################


########################################################################## Device 02350000 p00 U5001 0x582360a9 elroy

##########################################################################


##########################################################################


##########################################################################


##########################################################################


##########################################################################


##########################################################################


##########################################################################


##########################################################################


########################################################################## #Node Num: 0 Family: BACKPLANE Type: HIOB Number: 5

##########################################################################


End

Path 43

##########################################################################


Configuring SCAN


8/10/2019 Superdome

27/42

8/10/2019 Superdome

28/42

show examples and explain the most common error(s) encountered with cmd.

enario: You've just installed a Superdome complex and its Support Management Station. You've installed the Scan-Rele

ndle on the SMS and are now ready to configure the Scan software to Scan test the Superdome complex before releasingcustomer. You run the command/opt/scansw/bin/cmdand then/opt/scansw/bin/just -s priv-yywhere yy equals the

mplex (priv-01, priv-02, etc). Just fails. Can't find complex information.

hat happened?: The cmd command failed without informing you. To be more precise, the cmdcommand never really go

n, as shown in the example below.

xample 3 cmd error

feshd5-t% cmd

INFORMATIONAL: Using default settings.

feshd5-t% cd ../data

feshd5-t% ll

total 702

-rw-rw-rw- 1 hduser users 64 Jan 9 13:10 1

drwxr-xr-x 7 hduser users 1024 Dec 29 13:14 arch_0020

drwxr-xr-x 3 hduser users 1024 Jan 8 15:25 arch_0030

-rw-r--r-- 1 hduser users 1042 Nov 7 22:00 arch_code.map

-rw-r--r-- 1 hduser users 4838 Nov 7 22:00 cmd.cfg

-rw-rw-rw- 1 hduser users 892 Jan 10 08:41 cmd.log

-rw-rw-rw- 1 hduser users 201 Jan 10 08:41 complex.cfg

-rw-rw-rw- 1 hduser users 1823 Jan 8 15:27 cplx.ini

-rw-rw-rw- 1 root sys 1781 Jan 8 15:27 cplx.ini.old

drwxrwxrwx 2 hduser users 24 Jan 10 08:38 cplx_priv-05

drwxrwxrwx 2 hduser users 1024 Dec 29 11:44 cplx_spudome

-rw-rw-rw- 1 hduser users 2775 Jan 9 13:12 just.log

-rw-rw-rw- 1 hduser users 297 Jan 9 13:12 just.log.old

-rw-rw-rw- 1 hduser users 16 Dec 29 10:42 justconfig

-rw-rw-rw- 1 hduser users 325126 Jan 9 13:12 justerrorfilefeshd5-t% cat cmd.log

Wed Jan 10 08:40:58 2001

INFORMATIONAL : Message Log now using this file:

Wed Jan 10 08:41:03 2001

WARNING : CMD_Complex::process_Node_Mask - Initializing resend of com

Wed Jan 10 08:41:08 2001


Wed Jan 10 08:41:13 2001


Wed Jan 10 08:41:18 2001


Wed Jan 10 08:41:23 2001


Configuring SCAN


8/10/2019 Superdome

29/42

Wed Jan 10 08:41:28 2001

WARNING : CMD_Complex::process_Node_Mask - Max Retries Exceeded.

Wed Jan 10 08:41:28 2001

NON-FATAL ERROR : CMD_Manager::main_Loop - Recieved CMD_Exception id: 4 Sever

feshd5-t% cat complex.cfg

#------------------------------------------------------

# No Valid complexes identified. See the CMD log file

# for more detailed information.

#------------------------------------------------------

feshd5-t% cd cplx_priv-05

feshd5-t% ll

total 0

feshd5-t%

ove, the warning, "Initializing resend of com." points to the fact that cmd couldn't communicate with the complex. We c

this is the content of the complex.cfgfile. Also, the cplx_priv-yydirectory that gets created by the cmdcommempty.

oblem: Network Diagnostics was disabled on the GSP of the complex being polled. This is a very typical problem

ution: Access the GSP of the complex, enter Command Mode (cm), execute the GSP command nd, and enable Networagnostics. Exit the Command Mode, then exit the GSP. Now try the cmdcommand again. It should execute properly. Y

l see valid contents in the complex.cfgfile and there will be node_xx.cfgentries in the cplx_priv_yydirectis is shown in the example below.

xample 4 output and files after proper cmd execution

feshd5-t% ./cmd

INFORMATIONAL: Using default settings.

feshd5-t% cd ../data

feshd5-t% cat cmd.log

Wed Jan 10 08:46:43 2001

INFORMATIONAL : Message Log now using this file:

feshd5-t% cat complex.cfg

Complex

Hostname priv-05

Architecture 32

IP_Address 15.99.111.105

Port_Number 5151

Nodes



# -----------------------------------------------------

Configuring SCAN


8/10/2019 Superdome

30/42

8/10/2019 Superdome

31/42

System Hardware>Support Management Station

unning Scan Tool (JUST)

bout JUST

e JTAG Utility and Scan Tool (JUST) is a set of software tools and libraries that performs the following:

Inserts data packets into chips designed to JTAG (Joint Test Action Group) standards for testability

Clocks the data through the chip

Reads the output

Compares the output with the expected output and report the error(s), if needed

e JUST programs, libraries, configuration files, data files, and scripts reside on the Superdome Support Management Sta

MS) in the /opt/scanswdirectory.

onfiguring JUST

ter installing the Scan software (See Installing Scan), the Private network between the SMS and the Superdome GSP mu

ted and the Scan software configured to support the complex.

configure JUST for use on the Superdome complex, see Configuring Scan (JUST).

esting the Private Networkfore running JUST, test the Private network connection (SMS to GSP). If the SMS has been properly installed andnfigured,/usr/sbin/ping priv-01should respond without error.

he Private network has not been installed and/or configured, refer to Chapter 3 of the Superdome Installation Manual. IST has not been run on the complex, scannable hardware has been added to the complex, or a new system is being instaConfiguring Scanto make sure the files needed for scan have been set up.

member that the hostname, priv-01, applies to the first GSP attached to the Private network, priv-02 for the second, privthe third, and so forth.

ethods of Running JUST

ere are two methods of running JUST: as a command-line program that kills all of its related processes and removes themmand line when exited and as a daemon argument that keeps JUST running to watch for other processes that may need

e the JUST interface.

mmand Line Style

e actual JUST executable resides in /opt/scansw/bin. To invoke JUST in command-line style, change directories pt/scanswand enter the following:

bin/just -s .

here xx equals the private LAN name such as priv-01, priv-02, and so forth.

ST needs to be invoked in this manner because it is dependent upon finding its library, configuration, and data files withb-directory structure. It can be invoked with an argument to alter its behavior from the default. The arguments are:

-nodenode_x.cfg--Used to test just one node of a multi-node complex. Substitute the number of the node to be t

for the x.

-daemon -jp 2222 --Invokes JUST to run as a daemon. This is needed when running SOTF (Scan on the Fly) or ACscripts. The -jp 2222argument tells JUST to listen on port 2222 for commands.

Running SCAN


8/10/2019 Superdome

32/42

8/10/2019 Superdome

33/42

........................................................

just>> idv

Performing MakeSafe-> ..........................................

ID verify successful on Complex priv-04 Node 0 Path 0














JUST: Test Passed

just>>

Example 1, JUST prints out the version number of the JUST executable, displays the general JUST commands with a br

cription of each, connects to the host/node specified, and stops at the JUST prompt. The example executes the id_verif

mmand.

ST is now waiting for a command/argument string to begin test execution. Commands, arguments and a brief descriptioat is being tested is listed below. The commands invoked without arguments will take the default action, which is usual

erything.

ST commands

JUST and JUST commands affect components within a cabinet.NEVERrun JUST or JUST commands on cabinethas a partition running. All partitions contained wholly or in part within the cabinet being tested should be at BIB

e following section contains a description of each JUST command. Entering the command followed by a -hat the JUSTompt displays the usage information for that command.

: Make Safe ms[-complexcomplex] [-nodenode] [-pathpath]

complexrefers to the name of a given complex; the default is all complexes currently in memory.

noderefers to the number of a given node; the default is all nodes currently in memory.

pathrefers to the given scan path; the default is all scan paths._verify (idv): JTAG ID Verify Ring Test id_verify (idv) [-node node] [-pathpath]

noderefers to the number of a given node; the default is all nodes currently in memory.

pathrefers to the number of a given scan path; the default is all paths.

The id_verifytest verifies the configuration stored in memory against the real hardware configuration JTAG IDs

scan.

ble: Cable Test cable [-cable ] [-pattern ] [-wireinfo] [-untested] [-step]

Running SCAN


8/10/2019 Superdome

34/42

-cablespecifies the cable to be tested.

cable namerefers to which cable to use. Cables are listed in the flex.mtefile. The default is all cables.

-patternruns only specific patterns.

refers to the pattern number(s) to use - default is all patterns (first pattern is 0).

-wireinfodisplays some wire information.

-untesteddisplays untested wire information. Not needed if -wis set. Displays wires not fully tested. A fully testedwire has been set to 0 and 1. Displays all wires if -poption is used.

-stepis the step mode for debug pruposes.

DC Connectivity Test d [-pattern number] [-wireinfo] [-untested]

-patternruns only a specific pattern.numberrefers to which specific pattern number to use. The default is allgenerated patterns. First pattern is 0.

-wireinfodisplays some wire information

-untesteddisplays untested wire information.This is not needed if -wis set. Displays wires not fully tested. A fully

tested wire has been set to a 0 AND 1. It displays all wires if -poption is used.

v: Driver Test drv [-wireinfo] [-step]

-wireinfodisplays some wire information

-stepis the step mode for debug purposesHelp Help function for JUST commands.

o: Information Command info type [-ppath] [-DdeviceIndex]

typerefers to the type of information requested as follows:nodedisplays node information

pathdisplays path information.

devicedisplays device information.

envdisplays ist environment information

wiredisplays wire information.

pathrefers to the number of a given scan path.

deviceIndexrefers to which device in path (relative to 0)

e info nodeto get:

deviceIndexwirealso accepts [-tstargetstring] [-pin name] [-dctest] [-spn] [-smi]

targetstringis complex:node:path:part

nameis pin name or pin number.

-dctest shows only dc testable wires. The default is to show both dc and non dc testable wires.

-spnshows wires with pin names. The default is to show wires with pin numbers.

-smishows more info on wires.

Quit Exit JUST and return to the HP-UX prompt.

The following commands, while valid JUST commands, are considered Expert level commands. The Exper

level commands are potentially destructive to the hadware if not executed properly.

c: Test Bus Controller Test tbc [-complexcomplex] [-nodenode] [-pathpath] [-modemode] [-submodesub-mode]atadata]

complexrefers to the name of the complex. The default is all complexes in memory.

noderefers to the number of a given node. The default is all nodes in memory.

Running SCAN


8/10/2019 Superdome

35/42

pathrefers to the number of a given scan path. The default is all paths

moderefers to a JTAG mode to set all parts to. The default is all available modes. Potential modes are:bypass,sample, id,internal

sub-moderefers to an integer index into the mode

datarefers to a 16-bit hes format to scan in/out. The default is the following set of patterns: 0x0000, 0xffff, 0xaaaa,0x5555, 0x3333, 0xcafe

Gate Array Test g [options]

By default, all arrays that can be tested, will be tested.

The options are:

-refdestest arrays with a matching reference designator value.

-boardtest arrays on a given board. boardis a name or slot number.

-jtag_idtest arrays matching a JTAG id (e.g. 0x12345678)

-typetest arrays mathcing a type (e.g. dna)

-startnumberindicates the start with a given pattern number

-endnumberindicates the end on a certain pattern number

-maxnumberruns a maximum of number patterns per file

-optmaps a device to an index number numberis the index number to map device to. boardis name or slot number

of board. refdesis the reference designator of device. Only tests device number 0 unless pattern specifies a changeto a different device.

-vectorfilefilenamespecifies the vector file to use.

-patternfilefilenamespecifies the pattern file to use.

-nomakesafeindicates not to perform makesafe steps. This could be VERYdangerous.Do notdo this unlessspecifically told by support personnel.

o: Scan In Scan Out siso [-pathpath] [-modemode[:sub-mode]] [-submodesub-mode] [-datadata][-errorcountmber]

pathrefers to the number of a specific scan path to test. The default is to test all paths.

moderefers to a specific JTAG mode to test. The default is to test all testable modes. Valid modes are:sampleinternal. sub-mode refers to an integer index into the mode.

datarefers to a specific 16-bit hex number (i.e. 0xffff) to scan. The default is to use all of a set of patterns:0x00000xffff 0xaaaa 0x5555 0x3333 0xcafe

numberrefers to the number of errors to display. The default is 3.

bc: Multiple Mode tbc Test mtbc [-mode mode1[:sub-mode1] -mode mode2[:sub-mode2] [-complex complex] [

de] [-pathpath] [-data data] [-node number]

mode1and mode2refer to a JTAG mode to put all parts into.mode1is applied to a single part per scan testoperation. mode2is applied to the rest of the parts. Potential modes are:bypass, sample id, and internal.sub-mode1and sub-mode2refer to an integer index into the respective mode.

complexrefers to the name of a given complex. The default is all complexes in memory.

noderefers to the number of a given node.The default is all nodes in memory.

pathrefers to the number of a given scan path. The default is all paths.

datarefers to a 16-bit hex format to scan in/out. The default is the following set of patterns:0x0000 0xffff 0xaaaa

0x5555 0x3333 0xcafe

-nodenumberrefers to the number of errors to display.

Running SCAN


8/10/2019 Superdome

36/42

mtbc -m sample -m bypass -d 0xcafe -node 1

This puts one device at a time in sampleand all the other devices into bypass. It will use 0xcafefor the data and display

nly one error (even though there may be more). It does this for all devices of all paths.

get [-i on|off -errors on|off -fieldpath [0-2] -h]target_stringtarget_string= complex:node:path:device:ring:field

complexnames that is defined in complex.cfg.

node node name that is defined in complex.cfg.

pathscan path number that is defined in node_x.cfg.

devicedevice name that is defined in node_x.cfg.

ringring name that is defined in field.maporjtag.def.

fieldfield name that is defined in field.mapfile.

-i on|off: specifies whether or not an instruction write is done before a data read. This is useful if multiple scans areneeded on the same part. By default, this option is on.

-fieldpath [0-2]: specifies how much of the target string to print out to the screen.0: print all terms and return value(default)1: print field name and return value only2: print return value only

-errors on|off: specifies whether errors are reported to the screen. By default, this option is on.

t put [-i on|off -data_read on|off -e [END_STATE] -errors on|off-h]target_stringvaluetarget_string=mplex:node:path:device:ring:field :

complexcomplex name defined in complex.cfg.

nodenode name defined in complex.cfg



ringring name that is defined in field.maporjtag.def.


valuehex value of data to put in the field(e.g. 0xf1b).on|off: specifies whether or not an instruction write is done before a data read. This is useful if multiple scans are

eded on the same part. By default, this option is on. -data_read on|off: specifies whether or not a data read is

rformed before a data write is performed. If off, bits that are not explicitly being set by the put value are set to 0.

fault, this option is on. This option is mainly used for boundary ring puts to protect the integrity of the data alrea

t on the path.-e[END_STATE]:allows the user to leave the JTAG controller statemachine in a specific state. The

fault is the RUN-TEST-IDLE state. Other options might be PAUSE_IR or PAUSE_DR. If the -e option specifies

AG_RESET then the controller is reset after the command is executed. -errors on|off:specifies whether errors ar

ported to the screen. By default, this option is on.-fieldpath [0-2]:specifies how much of the target string to print o

e screen:

0: print all terms and value (default)

1: print field name and value only

2: print return value only

get ir_get -errors on|off -htarget_stringtarget _string= complex:node:path:device

nodenode name defined in complex.cfg.



rors on|off:specifies whether errors are reported to the screen. By default, this option is on.

put ir_put [-errors on|off -h]target_stringvaluetarget_string= complex:node:path:device

Running SCAN


8/10/2019 Superdome

37/42

complex complex name defined in complex.cfg.

nodenode name defined in complex.cfg

pathscan path number that is defined in node_x.cfg


valuehex value of data to put in the field (e.g. 0xf1b).

rors on|off:specifies whether errors are reported to the screen. By default, this option is on.

ock block [-data_read on|off -errors on|off -h]target_stringtarget_string= complex:node:path:device:ring

complex complex name defined in complex.cfg.nodenode name defined in complex.cfg.


devicedevice name that is defined in node_x.cfg

ringring name that is defined in field.map orjtag.def.

ata_read on|off:specifies whether or not a data read is performed before a data write is performed. If off, bits tha

t explicitly being set by the put value are set to 0. By default, this option is on. This option is mainly used for boun

g puts to protect the integrity of the data already out on the path.

ly one ring can be specified. Since a block reads in one ring from each device on the scan path, wildcards are not supporing token. If more than one ring on a path needs to be specified, this should be accomplished through the use of setior

r example: if there are 6 devices on path 36 (p00 - p05) and p01 needs to be in boundary mode and p02 needs to be in an

ernal mode (e.g. SCAN10), the steps are as follows:

rors on|off: specifies whether errors are reported to the screen. By default, this option is on.

t>> setr 36:p01:BOUNDARYjust>> block 36:p02:SCAN10This locks the boundary ring of p01 and the scan10 ring2 and the bypass ring of all others.

et bget [-errors on|off -h]target_stringtarget_string= complex:node:path:device:ring

complexcomplex name defined in complex.cfg




ringring name that is defined in field.map orjtag.def.


rors on|off: specifies whether errors are reported to the screen. The default is on.

ut bput [-errors on|off -h]target_stringvaluetarget_string= complex:node:path:device:ring




devicedevice name that is defined in node_x.cfg.ringring name that is defined in field.maporjtag.def.

fieldfield name that is defined in field.map file.

valuehex value of data to put in the field (e.g. 0xf1b).

rors on|off: specifies whether errors are reported to the screen. By default, this option is on.

bputwill not write the data out to the scan path until a bscanor bunlockis performed.

nlock bunlock [-errors on|off -h]target_stringtarget_string = complex:node:path

rors on|off:-errors on|off: specifies whether errors are reported to the screen. By default, this option is on.

Running SCAN


8/10/2019 Superdome

38/42




nlockwrites the data out to the scan path and unlocks the scan path.

ractical Testing Tips

ST (a.k.a Scan and JTAG testing) are low level tests that must not be peformed on a running system unless you know exat you are doing. It is very easy to crash running partitions or, even damage the hardware if the tests are not performed

operly. The following sections present scenarios and situations where scan test would be an appropriate form ofubleshooting and which test would probably be most beneficial.

ystem Installstem install time is the most obvious time for scan. The system has just been received from shipment and is in an unknondition. Even though it was thoroughly tested at HP Manufacturing, it has been boxed and shipped in airplanes and truck

ter assembling the system as per the Superdome Installation Manual, test the system. First, complete the tasks in the Ins

anand Configuring Scannuggets, then invoke JUST and run the tests. Use the building block approach. Selecting a few

hout going to a low level test, can be confident that everything is seated and connecting properly. It is rare that compon

l actually be damaged during shipment, it is usually a poor connection that cause errors.

Typically, the first command to run is ms(MakeSafe). This puts the machine into a known state. Remember, the com

should be at BIB (Boot is Blocked) for scan tests.

1.

Second should probably be idv(ID Verify). This checks the JTAG ID of all parts in the complex by rings.2.

Next, choose d. This is the DC Connectivity test. It checks the connection state of all scannable parts in the complexconfiguration that was built with the cmdcommand when you were configuring the complex.

3.

The next choice should probably be drv. This command will test the drivers of a wire. This will electrically test the

in a different way than d. Dlooks for opens, shorts and stuck-ats. DRVwill give a better electrical test by runningpatterns on each wire in a different manner. Both tests are important, and drvbuilds upon d.

4.

Follow the drvcommand with cable. By allowing the default modes to run on these tests, all components in theconfiguration are be tested. Cable will test the flex cables and U-Turn cables within the cabinet or complex.

5.

you well know, the items tested are contained in the complex.cfgand node_x.cfgfiles. These are built with themmand. Be absolutely certain, when changing the configuration of the complex by adding or removing components, to

reun cmd.

all of the above tests pass successfully, there is good confidence the system connections are good and you can safely proh the system installation.

re to be added soon.

Configuring SCAN Overview of AC Scan Link Tests

Running SCAN


8/10/2019 Superdome

39/42


Overview of AC Scan Link Tests

What Are They?

here are two ac scan link tests (aclts) for Superdome servers: one to test the ring input/output (RIO EO) links between a cell and its I/O subsystem, called reo_link_ac_test; one to test the crossbar (orBC) links between a logical XBC and the attached cells, called xbc_link_ac_test.

The aclts verify the ability of a link to pass data at speed, whereas, dc link testing verifies th

existence and continuity of the link's conductors.

oth of the acltsare Perl scripts, that require a Joint Usability Action Group Scan Test (JUST) daem

nning on HP-UX on the support management station (SMS), in order to verify the functionality of

dividual link (high speed data path between two or more application specific integrated circuitsASICs)). ASICs may reside on the same backplane, or on separate backplanes within another cabine

complex.

All acltsare verifiers, not diagnostics or exercisers.

nlike the dc scan testing, that uses boundary scans to test targetASIC devices, all acltsuse scan on

y (SOTF) operations, that control the functionality of the targetlink (between two or more ASICs)

odifying the internal control and status register (CSR) values of both sources, and capturerst-in-first-outs (FIFOs). All aclttesting employs multiple SOTF operations to initialize, send, and

pture data patterns, across individual ports on the targetASIC devices, at full speed across the link

Those acltsthat test links to a coherency controller (CC) chip also use internal scan and musperiodically clock halt the CC chip.

Where Are They?ll scan utilities, including the aclts, reside in the/users/hduser//binsubdirec

n the SMS. Scan software consists of the JUST utility program, Perl scripts, and many files consisti

configuration and rule files.

When To Use Them?

se them whenever cable links are established during installations, or when adding more cells, partit

O card cages, or nodes. Most repairs that require powering down a partition to replace link cables, o


ttp://superdome-test.fc.hp.com/sd_epss_cdrom/content/00/02/BD/idd_1/114.html (1 of 4) [2/14/2001 2:46:46 PM]

8/10/2019 Superdome

40/42

eir corresponding ASICs, are also candidates for ac scan link testing.

henever CSR values are modified, ASIC functionality may change in a manner that is harmful tortition operation. For XBC to XBC links, all partitions within the cabinet or cabinets where the AS

nder test reside mustbe offline, or be brought offline, before starting any scan tests.

or CC to XBC links, only the cell containing the link(s) under test must be offline.

Running acltson an active cell will likely crash the operating system (OS), or any running

program or application, and is to be avoided. Also, XBC to XBC link testing within an activ

node will crash the node.

How To Select Them?

nowledge of which acltscript to select requires some knowledge of cabinet topology because diffe

pes of links connect the different parts of a Superdome complex. Figure 1 identifies all the testable

nks (marked with the letters a - f) within an Superdome 32 Way cabinet and an adjacent I/O expans

binet:igure 1 Data Paths of Testable Links



8/10/2019 Superdome

41/42

C Scan Test for REO Links

Figure 1, the Ring I/O Adapter (REO) links between a cell and its I/O subsystem are marked as "(a

ll eight REO links for a Superdome SPU cabinet are shown: four I/O subsystems are within the samuperdome SPU cabinet, with the cells using unshielded cable pair, and four I/O subsystems are with

adjacent I/O expansion cabinet, using shielded cable pairs.

C Scan Test for XBC Links

he links for each cell to XBC (Crossbar Chip) are marked as "(b)." All eight XBC links are on the

ckplane, within the Superdome SPU cabinet.

he intra-cabinet links between logical XBC chips are marked as "(c)." These logical XBC-to-logicaBC links are on the backplane, within the Superdome SPU cabinet.



8/10/2019 Superdome

42/42

he inter-cabinet links between logical XBC chips are marked as "(d)." These logical XBC-to-logica

BC links are across ribbon cables, that connect a left backplane within one Superdome SPU cabine

right backplane within another Superdome SPU cabinet (not shown).

Running SCAN Utilit

http://superdome-test.fc.hp.com/sd_epss_cdrom/content/hrdwr/util/129.htmlhttp://superdome-test.fc.hp.com/sd_epss_cdrom/content/hrdwr/util/129.html

Superdome 扩容

Documents

Transcript of Superdome 扩容