HP SMS PDF

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

a newer version of this PDF at http://superdome.hp.com
Overview: Support Management Station
System Hardware > Support Management Station Hardware
Functions
Two "big pipe" applications: SCAN and FWUU'
Repository for files and functions needed for SuperDome
Installation
Rack: IOX or other rack
Table
Up to 8 SuperDomes per Support Management Station (approx.) need one TS for SCAN/FWUU,
if more than one: need to reset IPs
Challenge in site prep: get IP for each TS on customer's LAN
LAN
Private LAN: the "big pipe"
Customer LAN: access to the rest of the net
Platform Comparison
A180 A500
Staccato Crescendo
18 Gig HD 18 Gig HD
256 M mem 256 M mem
two LANs two LANs
180 MHz 360 MHz
single proc single/dual proc
early release all other shipments (different SCSI cables needed)
Software
Big two (loaded from CD along with diagnostics)
http://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]

Several others including tsinstall and a chassis code capture program
Support Management Station Hardware Finding More System Management Station Information

Finding More System Management Station Information
Finding More System Management Station Information

For installation, racking, and other general information about the A-class servers upon which the System
Management Station is based, visit the A-Class servers website at
http://info.fc.hp.com/hpux/systems/#aclass.
For SMS installation, console configuration, and LAN setup, read the SuperDome Installation Guide,
especially Chapter 3.
For the minimum SMS configuration, read the SuperDome Configuration Guide.
Overview: Support Management Station Installing Firmware Update Utility (FWUU)
http://superdome-test.fc.hp.com/sd_epss_cdrom/content/00/00/MK/idd/107.html [2/14/2001 2:46:06 PM]

Installing Firmware Update Utility (FWUU)
Installing FWUU from CD-ROM

The Firmware Update Utility (fwuu) is a tool to aid in updating firmware files on the superdome family
of computers. It resides on the Support Management Station (SMS) in the /opt/fwuu directory. For more
information on using fwuu, see Using the Firmware Update Utility.
To install fwuu from the Support + Media CD-ROM: (assuming already logged in to SMS)
1. Insert the Support + media in the SMS DVD drive.
2. Mount the drive. <mount /dirname / device> The dirname can be anything you like, but typically it
is something easy like /CD, /SDROM, /CD-ROM. Names like that. The /device is the HPUX name
for the CD or DVD drive. It will typically have a name like /dev/dsk/c0t1d2 or something similar.
To find the proper name, use the HPUX command ioscan -fnC disk. You must be root to
use the ioscan command.
3. Type swinstall -s /CD (for example) In the window that appears for the software you should see
FWUU and Scan-Released. There may be other files, too, but these two should be there. Select
FWUU by highlighting it, then marking it for selection. Then start the install.
4. 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.
5. If you are finished with the CD, unmount the drive (umount /CD) and remove the media.
Installing FWUU from Depot

There are different ways to obtain needed software from the various depots at HP. How we retrieve it
depends upon the host we are using to retrieve the software and where it is located. If we are outside of
the HP firewall, there are various depots around the world for customers to download patches and
firmware files. If we are inside the HP firewall, we can use swinstall or swcopy to retrieve the needed
files, archive them to tape and carry the tape to the customer site. This section will not attempt to list the
names of the various depots. It is a procedural listing for retrieving the needed files, getting them to the
appropriate system and loading them into the proper directory.
Example 1 Obtaining FWUU from external depot directly to customer's SMS
http://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]

1. The swinstall command is probably easiest. As root, type swinstall -s <depot> <cr>.
2. 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.
3. Start the install process from the Action heading, selecting Install.
4. When download is complete, exit the program.
5. Verify the fwuu executable file is in the proper directory. The absolute path is /opt/fwuu/fwuu.
6. Loading and / or updating the firmware files used by fwuu is covered in Updating Superdome
Firmware.
Example 2 Obtaining FWUU from internal HP depot to an alternate host
1. This section is still under test. It will be completed soon.
Finding More System Management Station Information Updating Superdome Firmware
http://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]

Updating Superdome Firmware
Updating SuperDome Firmware Files
About Firmware Update Utility (FWUU)
Updating FWUU from CD-ROM
Updating FWUU via network

This document is incomplete at this time. It will be updated soon. Some of the information is just not
available at this time.
Installing Firmware Update Utility (FWUU) Using the Firmware Update Utility
http://superdome-test.fc.hp.com/sd_epss_cdrom/content/00/00/M4/idd/109.html [2/14/2001 2:46:15 PM]

Using the Firmware Update Utility
General Description
The Firmware Update Utility (FWUU) is a tool developed by the System Supportability Lab / Diagnostic and Support
Tools team for verifying the revisions of firmware on the various entities in the superdome system and updating those
firmware files, if needed. At superdome first release, it will be available only in HPUX and will reside in the
/opt/fwuu directory on the Support Management Station. Later FWUU will be ported to the Microsoft Windows
environment for inclusion on the CE Toolkit.
Two Versions of FWUU

In the early stages of superdome release, there are two versions of the Firmware Update Utility. One is fwuu_30 and
the other is fwuu_44. There are many different versions of the superdome firmware during the pre-release stages of
the product. The version of fwuu needed is dependent upon the revision of firmware installed.
At this time, fwuu_30 can always be used to update the superdome firmware. It has a drawback, though. Fwuu_30
will update the files one at a time. Even if you input multiple flash handles on the command line, fwuu will update the
entities singly. If you were to try to update all the PDC files in a 32way machine with one command you would enter
fwuu> update 1152-1159 hd.bin.6.0.frm. With fwuu_30, all eight cells would have the PDC files
updated, but one at a time. This will take about 30 minutes or more.
With fwuu_44, the command executes the download in parallel. The same command as the one above would execute
and load all of the cell boards at the same time reducing the download time to about 5 minutes. There is a warning
with fwuu_44, however. GSP firmware version 6.4, dated 8/15/00 or later is required to run fwuu_44. If you have an
earlier version of GSP firmware, update the GSP file first, then you can use fwuu_44 to update the rest of the
machine.
GSP firmware 6.4, dated 8/15/00, is required to run fwuu_44. Serious problems could occur if
fwuu_44 is used with any firmware earlier than 8/15/00
FWUU Commands
The Firmware Update Utility has five commands to aid the user in successfully performing a firmware update task.
They 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 <flash handles>
<firmware file>
HELP--Displays help information
EXIT--Disconnects from remote system and exits program
Invoking (Starting) FWUU

To start the Firmware Update Utility, perform the following steps:
http://superdome-test.fc.hp.com/sd_epss_cdrom/content/00/01/8M/idd/110.html (1 of 6) [2/14/2001 2:46:20 PM]

Step 1. Log in to the Support Management Station as hduser.
Step 2. Change the working directory to /opt/fwuu (cd /opt/fwuu).
Start FWUU with the command ./fwuu. FWUU then asks for the IP address of the GSP on the system to
Step 3.
be updated.
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

Step 4.
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......

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>
Identifying the Entities to Update

The example above shows the different columns and the values associated with them. These values uniquely identify
an 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

Flash Handle--A unique number based on a mapping algorithm whereby no two entities within a complex can
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.
Updating Firmware
To update the firmware on an entity or entities, use the UPDATE command. The format of the command is as
follows:
UPDATE <flash handle number(s)> <firmware file>
If multiple entities are being updated with the same command line, they must all be the same type. For example, if
there is more than one cell board to be updated, the PDC on every cell board in a cabinet could be updated with one
command line as shown below:
UPDATE 1152 1153 1154 1155 1156 1157 1158 1159 pdc.4.11.frm
Instead of entering all of the Flash Handles separately, they can be entered as a range (provided that they all are
included). The following is an example:
UPDATE 1152-1159 pdc.4.11.frm
All entities of a type within a partition must have the same firmware revision. As an example, suppose one cabinet
with eight cells divided equally into two partitions, and the four cells in the first partition have PDC firmware rev 4.10
while the four cells in second partition are running PDC 4.22. This is an acceptable configuration. To replace a cell in
one of the partitions, you would have to check the revision of the firmware (PDC and PDHC) on the new cell board
before 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 firmware
file.
There will be a table of compatible hardware and firmware revisions published. Always check for the latest
version of the compatibility document before updating firmware to a new revision.
Certain rules about the state of the hardware apply to Firmware Update Utility. These are listed below by the type of
firmware 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).

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 operating
partitions.
Because the GSP must be reset upon completion, the connection from the Support Management Station to the
GSP will be lost and all consoles, VFPs, and other connections to the GSP will be disconnected. Once the GSP
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 mistake
and selected the wrong revision of the firmware file. The firmware file will be incomplete, corrupted,
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, the
corrupted firmware file will load from Flash to RAM and the board will be inoperable. The only to do
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%

The above example appears to have had problems because of the Warning: statement. In this case, it is a successful
update. As mentioned previously, when the GSP is updated, it will reset, dropping all connections to it. As a user,
give 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>
As stated in the last line of the above example, the update of CLU firmware was not successful. However, the Update
Utility was successful in that it determined the cabinet was in a powered up state. The utility requires the +48 V to be
off before it will update the CLU or PM firmware. The rules for machine state before updating firmware are enforced
by FWUU but not explained beforehand.
Exiting FWUU
When the update task has been completed, exit FWUU and log off of the Support Management Station. Type exit
<cr> to get back to the Support Management Station HPUX prompt. Type exit <cr> again to disconnect from the
Support Management Station.
Updating Superdome Firmware Installing SCAN

Installing SCAN
Installing SCAN Tools
Before Installation
Before you install the scan tools, there is a check that should be made. There are two tunables in the kernel that need
to checked and modified, if necessary. Using SAM, go to Kernel Configuration, then select Configurable
Parameters, then set maxdsiz to at least 128 MB (0x08000000) and maxuprc to 200. Select kernel rebuild and
reboot the SMS to put the changes into effect. When the SMS has finished rebooting you may install the Scan
software by either Support + media (CD), from a self-built tape, or directly from the depot (internal only). There are
sections below detailing how to install Scan by each of the methods mentioned.
Installing SCAN Tools from Support + Media (CD-ROM)

The files needed to run scan on a superdome system are contained on the Support + media and on various depots
within the HP firewall.
To install Scan tools from the Support + media CD-ROM (assuming already logged in as root to SMS):
Step 1. Insert the Support + media in the SMS DVD drive.
Mount the drive. <mount /dirname /device> The dirname can be anything, but typically it is something
easy to remember as /CD, /SDROM, /CD-ROM. The /device is the HPUX name for the CD or DVD drive.
Step 2.
It will typically have a name such as /dev/dsk/c0t1d2 or something similar. To find the proper
name, use the HPUX command ioscan -fnC disk. You must be root to use the ioscan command.
Enter swinstall -s /CD (for example). FWUU and Scan-Released should appear the software
Step 3.
window. There may be other files, too, but these two should be there.
Step 4. Select Scan-Released by highlighting it and then marking it for selection.
Step 5. Start the install by selecting Action / Install.
After the file install is complete, check the SMS directory, /opt/scansw. There should be three
Step 6. directories: bin, data, and scripts. The swinstall process also creates the hduser username and password
setup.
Step 7. When finished with the CD, unmount the drive (umount /CD) and remove the media.
Test the process. Log out as root and log back in as hduser (password: hd<space>user). You should be
Step 8.
able to run the /opt/scansw/bin/cmd command, which builds the configuration files for the Superdome.
Installing SCAN Tools From a Self Built Tape

The Scan executable and its associated files will not be placed on an external depot server. Because Scan is
considered a diagnostic tool, it must remain confidential. Therefore, files needed for scan will only be obtainable
from the Support + media or from an internal software depot. Since customer sites are outside of the HP firewall,
download the files to a local server via swcopy and transfer the files to tape. You can then carry the tape to the
customer site and install the files on the Support Management Station with the swinstall command.
The Scan software can be retrieved from an internal depot,
http://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]

Installing SCAN
hpdst123.cup.hp.com/scan/depots/released/IPR0103. The basic name should stay the same, but

"IPR0103" changes periodically (usually quarterly). The following procedure retrieves the scan software to a local
HPUX machine, transfers the bundle to tape, and installs the files from tape to the Superdome Support Management
Station.
The 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
Step 1. Insert the blank or scratch tape into the DDS drive.
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 swcopy
Step 2. process.
Whatever directory is specified, it will become registered with SD. In the future, whenever you use a SD
command (swinstall, swcopy, swpackage, swremove, etc.), the directories you have used will appear in
the list of depots.
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
Step 3. WWSIT or WTEC for the latest depot site. Be sure to substitute the latest depot site (IPR0112, IPR0203,
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/scan for scan software would keep it separate from all of the patch bundles that are
copied by this same process.
When the files are copied to the specified directory, close the swcopy window.
Step 4. The files will now be moved to tape in a way that swinstall understands. This will facilitate the
installation at the customer's site.
Enter the sw command.

There are a lot of arguments available to this command, being part of the SD command family. Use the
HPUX man pages for the specific command, or, enter man 5 sd. This gives a generic listing of the SD
commands, their arguments and options. The command for this example is:
Step 5. /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 your
particular system is set up. The above swpackage command example uses the /tmp/scan depot to find
the files we wish to package, the target is a tape, and the specific device is /dev/rmt/0m. The output from
the above command is shown in Example 1 below.
Take the tape (can be done with a CD, also) to the customer's site and load into the Superdome SMS DDS
Step 6.
drive.

Installing SCAN
Install the Scan software package by entering the following command:

/usr/sbin/swinstall -s /dev/rmt/0m
Step 7. The DDS drive on the SMS should be this name. The tape built in the earlier steps contains an SD image
of the files on the depot. The swinstall screens operate normally. The install takes a little longer, since the
files are on tape and not coming over the network.
When the installation is complete, check the files under /opt/scansw for error. Log out as root and log
Step 8. in as hduser (password: hd<space>user), run the ./bin/scan_setup script., and then run the cmd command
and you are ready to go. For more information on scan_setup and 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 "root@gromit1.rsn.hp.com".
* 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 been
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).

Installing SCAN
* Writing the fileset "Fwuu-SW.FWUU" (1 of 5)

* Writing the fileset "Scan-SW.BIN" (2 of 5)
* Writing the fileset "Scan-SW.DATA" (3 of 5)
* Writing the fileset "Scan-SW.DOC" (4 of 5)
* Writing the fileset "Scan-SW.SCRIPTS" (5 of 5)
* Tape #1: CRC-32 checksum & size: 2749493802 16650240
* Removing the temporary depot.
* Tapemaker Phase succeeded.
======= 10/30/00 10:18:08 CST END swpackage SESSION
#
Installing Scan Tools Directly From the Depot

If the SMS is within the HP firewall, retrieve the Scan files directly from the depot by entering the following:
/usr/sbin/swinstall -s hpdst123.cup.hp.com:/scan/depots/released/<filename>
Instead of filename, substitute the bundle name such as IPR1299, HPUX1110, or something similar. This will
install the files directly to the SMS in their proper location, and if swagent is running, register the depot for future
upgrades. For more information on swinstall, swpackage, swcopy, and so forth, type man 5 sd or view the man
page for each individual command.
Using the Firmware Update Utility Configuring SCAN

Configuring SCAN
Configuring Scan Software (JUST)
The Importance of cmd

When testing the Superdome machine the Scan software, JUST and its libraries, use configuration files to determine what items
are present and are to be tested. The cmd command builds the configuration files. Every time a board configuration change is
made to a Superdome cabinet, cmd must be re-run to update the configuration files. If cmd is not run after a change, any portion
no longer present may still be in the configuration file. This will produce errors during test. If cmd is not run after a new part is
installed, the new part will not be tested, since it is not in the configuration file.
Each part that can be scanned, either a board or an ASIC, has a data or definition file associated with it that tells JUST how to
deal with that part. These definition files are automatically included in the Scan software bundle and placed in the proper
directories for JUST. (See Installing Scan )
For scan, each cabinet is considered a node. In a Superdome complex, there can be up to four nodes. When cmd is run against
such a complex, it creates a directory under the /opt/scansw/data directory called cplx-name. Where name is the name
of the Private GSP LAN name. This directory contains configuration files for each node called node_x.cfg, where x equals
the cabinet number set on the UGUY board for each cabinet. cmd also creates and/or modifies the complex.cfg file. This
file contains the information about each complex served by this Support Management Station (SMS).
Example 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
http://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]

Configuring SCAN
End_Of_Complex
End_Of_File
In Example 1 above, the /opt/scansw/data/complex.cfg file shows the SMS has two systems configured, The first,
priv-04, is a Superdome 16 Way machine. We can tell by the architecture number 48. 48 is designated for 16 way cabinets and
32 is designated for 32 way cabinets. Even though a left and right cabinet together equals a 64 way machine, each cabinet or
node is a 32 way. Scan treats each node as a separate entity. Priv-05 is a Superdome 64 Way. We can tell by remembering our
configuration rules. All compute cabinets will be numbered from 0 to 7 with even numbers on left cabinets and odd numbers on
right cabinets. All I/O Expansion cabinets are numbered from 8 through 15. Therefore, priv-05 is a 64 way box with one I/O
Expansion cabinet attached.
Using CMD to configure JUST

At this time, there is a script available to help configure the Scan software. It is /opt/scan/bin/scan_setup. This script
guides you through the process of configuring some parameters for JUST and cmd. You must run cmd to get the configuration
files built; scan_setup helps with some of the parameters. A couple of the questions in the scan_setup script ask for the
complex name and the IP address in dot notation. These questions are referring to the Private LAN interface on the GSP. You
can retrieve this information by logging into the GSP and executing the LS command.
After running the scan_setup script, run /opt/scansw/bin/cmd by entering ./cmd. This creates and/or modifies the
configuration files needed: /opt/scansw/data/complex.cfg, /opt/scansw/data/cplx.ini, and
/opt/scansw/data/cplx_priv-xx/node_y.cfg, where xx is the number from the Private GSP LAN (priv-01,
priv-02, etc.) and y is the cabinet number or node.
Example 2 Example of node_x.cfg file
% cat node_0.cfg
#-----------------------------------------------------------------
# This is a CMD generated JUST Node Configuration file.
#
# The node config file provides JUST with the following data:
# 1. What boards are installed in the system.
# 2. What paths exist in the system and the devices that
# compose those paths.
#-----------------------------------------------------------------
#-----------------------------------------------------------------
# A board entry has the following format.
#
# Board <board id> <board name> <board_part_number)_<scan rev>
#
# Board is a keyword for JUST.
#
# <board id> is a unsigned long value which encodes the board
# family, board type, board number and node number to which the
# board belongs.
#
# <board name> This field is used as a handy name for referencing
# the board.
#

Configuring SCAN
# <board part number> This is the part number of the board as

# specified in the boards serial eprom.
#
# <scan rev> 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
#
# Path <path number>
# Device <board id> <mech name> <ref des> <jtag id> <part #>_<part rev>
# .
# .
# Device <board id> <mech name> <ref des> <jtag id> <part #>_<part rev>
# End
#
# Path, Device, and End are all keywords used to parse this file.
#
# <path number> is a unique number identifying this path.
#
# Within each path is a list of devices present on that path.
#
# <board id> This field identifies which board the device is on.
#
# <mech name> This field gives the device a unique name and comes from
# a user generated file.
#
# <ref dex> This field is the reference designator of the device.
#
# <jtag id> This field is the jtag id of the device.
#
# <part #> This is the part number of the device.
#
# <part rev> 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
##########################################################################
##########################################################################
Device 03100000 cc U44 0x14076049 dna
##########################################################################
##########################################################################
Device 03100000 dillon U7 0x11250005 dillon
End
Path 4
##########################################################################
##########################################################################
Device 03100000 cpu0 U35 1QM1-000A pcxw
##########################################################################
##########################################################################
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
##########################################################################
##########################################################################
Device 03100000 m1y U51 0x14091049 m2
##########################################################################
##########################################################################
Device 03100000 m0y U50 0x14091049 m2
##########################################################################
##########################################################################
End
Path 12
##########################################################################
##########################################################################
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
##########################################################################
##########################################################################
Device 03130000 m2x U37 0x14091049 m2
End
Path 14
##########################################################################
##########################################################################
Device 03130000 m0x U71 0x14091049 m2
##########################################################################
##########################################################################
Device 03130000 m1x U72 0x14091049 m2
##########################################################################
##########################################################################
Device 03130000 m1y U51 0x14091049 m2
##########################################################################
##########################################################################
Device 03130000 m0y U50 0x14091049 m2
##########################################################################
##########################################################################
End
Path 30
##########################################################################
##########################################################################
Device 02310000 p00 U5001 0x582360a9 elroy
##########################################################################
##########################################################################
##########################################################################
##########################################################################
##########################################################################

Configuring SCAN

##########################################################################
##########################################################################
##########################################################################
##########################################################################
##########################################################################
End
Path 31
##########################################################################
##########################################################################
##########################################################################
##########################################################################
##########################################################################
##########################################################################
##########################################################################
##########################################################################
##########################################################################
##########################################################################
##########################################################################
##########################################################################
End
Path 32
##########################################################################

Configuring SCAN

##########################################################################
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
##########################################################################
##########################################################################
##########################################################################
##########################################################################
##########################################################################
##########################################################################
##########################################################################
##########################################################################
##########################################################################
##########################################################################
##########################################################################
##########################################################################
End
Path 43
##########################################################################

Configuring SCAN
##########################################################################
##########################################################################
##########################################################################
##########################################################################
##########################################################################
##########################################################################
##########################################################################
##########################################################################
##########################################################################
##########################################################################
##########################################################################
End
Path 44
##########################################################################
##########################################################################
Device 05150000 diva U18 1821-3440 diva
##########################################################################
##########################################################################
Device 05150000 cio_lan U8 1821-3749 cio_lan
##########################################################################
##########################################################################
Device 02350000 reo U5000 0x14081049 reo
End
cmd Errors
As with any program, sometimes there are errors. This section is not an attempt to document every error that could ever occur,

Configuring SCAN
but show examples and explain the most common error(s) encountered with cmd.
Scenario: You've just installed a Superdome complex and its Support Management Station. You've installed the Scan-Released
bundle on the SMS and are now ready to configure the Scan software to Scan test the Superdome complex before releasing it to
the customer. You run the command /opt/scansw/bin/cmd and then /opt/scansw/bin/just -s priv-yy where yy equals the
complex (priv-01, priv-02, etc). Just fails. Can't find complex information.
What happened?: The cmd command failed without informing you. To be more precise, the cmd command never really got to
run, as shown in the example below.
Example 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 justerrorfile
feshd5-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
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%
Above, the warning, "Initializing resend of com." points to the fact that cmd couldn't communicate with the complex. We can
see this is the content of the complex.cfg file. Also, the cplx_priv-yy directory that gets created by the cmd command
is empty.
Problem: Network Diagnostics was disabled on the GSP of the complex being polled. This is a very typical problem
Solution: Access the GSP of the complex, enter Command Mode (cm), execute the GSP command nd, and enable Network
Diagnostics. Exit the Command Mode, then exit the GSP. Now try the cmd command again. It should execute properly. You
will see valid contents in the complex.cfg file and there will be node_xx.cfg entries in the cplx_priv_yy directory.
This is shown in the example below.
Example 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

Node_Reference 8 1.0@ 1 96768
End_Of_Nodes
End_Of_Complex
End_Of_File
feshd5-t% cd cplx_priv-05
feshd5-t% ll
total 140
-rw-rw-rw- 1 hduser users 3540 Jan 10 08:46 flex.mte
-rw-rw-rw- 1 hduser users 30652 Jan 10 08:46 node_0.cfg
feshd5-t%
If all of the nodes of the complex are shown in the complex.cfg file, you are now ready to run JUST to test the system. See
Running Scan.
Installing SCAN Running SCAN

Running SCAN
Running Scan Tool (JUST)
About JUST
The 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
The JUST programs, libraries, configuration files, data files, and scripts reside on the Superdome Support Management Station
(SMS) in the /opt/scansw directory.
Configuring JUST
After installing the Scan software (See Installing Scan), the Private network between the SMS and the Superdome GSP must be
tested and the Scan software configured to support the complex.
To configure JUST for use on the Superdome complex, see Configuring Scan (JUST).
Testing the Private Network

Before running JUST, test the Private network connection (SMS to GSP). If the SMS has been properly installed and
configured, /usr/sbin/ping priv-01 should respond without error.
If the Private network has not been installed and/or configured, refer to Chapter 3 of the Superdome Installation Manual. If
JUST has not been run on the complex, scannable hardware has been added to the complex, or a new system is being installed,
see Configuring Scan to make sure the files needed for scan have been set up.
Remember that the hostname, priv-01, applies to the first GSP attached to the Private network, priv-02 for the second, priv-03
for the third, and so forth.
Methods of Running JUST

There are two methods of running JUST: as a command-line program that kills all of its related processes and removes the
command line when exited and as a daemon argument that keeps JUST running to watch for other processes that may need to
use the JUST interface.
Command Line Style
The actual JUST executable resides in /opt/scansw/bin. To invoke JUST in command-line style, change directories to
/opt/scansw and enter the following:
./bin/just -s <priv-xx>.
Where xx equals the private LAN name such as priv-01, priv-02, and so forth.
JUST needs to be invoked in this manner because it is dependent upon finding its library, configuration, and data files within the
sub-directory structure. It can be invoked with an argument to alter its behavior from the default. The arguments are:
-node node_x.cfg--Used to test just one node of a multi-node complex. Substitute the number of the node to be tested
for the x.
-daemon -jp 2222 --Invokes JUST to run as a daemon. This is needed when running SOTF (Scan on the Fly) or AC
scripts. The -jp 2222 argument tells JUST to listen on port 2222 for commands.

Running SCAN
-f script file--Runs the script file.

-l logfile--Creates a logfile of the actions and reports that are taking place. It is similar to a console log. By using -L
logfile, you can append to an existing logfile. The default file is just.log.
-e errorfile--Creates a file to dump errors encountered. Using -E errorfile, you can append to an existing
errorfile. The default is justerrorfile.
-d debug level--Sets the debug level to a value of 0, 1, 2, or 3. The higher the number, the more verbose the
reporting. The default is 0.
Level 3 is very verbose. Do not set to 3 unless you are asked to do so.
-s server name--Establishes a JUST connection over the private LAN to a complex other than the default, priv-01.
Use this only when there are multiple complexes connected to the same Support Management Station.
-v--Displays the version stamp and then exit.
Example 1 Example of JUST connection
feshd4-t% ./bin/just -s priv-04

JUST Version 2.3.2, Nov. 22, 2000
General JUST Commands:

ms ... makesafe - put the node in a safe state
id_verify ... verify JTAG IDs
idmode ... Place parts in JTAG ID mode
siso ... scan data in and out of a scan path
d ... DC connectivity (checks wires for shorts and opens)
drv ... drive test (checks all drivers)
g ... gate array test
tbc ... single mode test the Test Bus Controller
mtbc ... multiple mode test the Test Bus Controller
info ... retrieve information on JUST configuration
get ... get a value associated with a data field
put ... put a hex value into a data field
ir_get ... get the instruction ring value of a device
ir_put ... put a hex value into the instruction ring of a device
block ... lock a path data buffer for bit manipulation
bget ... get data associated with a field from the locked buffer
bput ... put a hex value associated with a field into the locked buffer
bunlock ... unlock and write out the locked data buffer
h ... help
q ... quit
Enter '[command] -h' for help on individual commands
Connected to priv-04 Node number 0

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

Running SCAN
........................................................
just>> idv
Performing MakeSafe-> ..........................................
ID verify successful on Complex priv-04 Node 0 Path 0
JUST: Test Passed
just>>
In Example 1, JUST prints out the version number of the JUST executable, displays the general JUST commands with a brief
description of each, connects to the host/node specified, and stops at the JUST prompt. The example executes the id_verify
command.
JUST is now waiting for a command/argument string to begin test execution. Commands, arguments and a brief description of
what is being tested is listed below. The commands invoked without arguments will take the default action, which is usually test
everything.
JUST commands
JUST and JUST commands affect components within a cabinet. NEVER run JUST or JUST commands on cabinet that
has a partition running. All partitions contained wholly or in part within the cabinet being tested should be at BIB.
The following section contains a description of each JUST command. Entering the command followed by a -h at the JUST
prompt displays the usage information for that command.
ms: Make Safe ms [-complex complex] [-node node] [-path path]
complex refers to the name of a given complex; the default is all complexes currently in memory.
node refers to the number of a given node; the default is all nodes currently in memory.
path refers to the given scan path; the default is all scan paths.
id_verify (idv): JTAG ID Verify Ring Test id_verify (idv) [-node node] [-path path]
node refers to the number of a given node; the default is all nodes currently in memory.
path refers to the number of a given scan path; the default is all paths.
The id_verify test verifies the configuration stored in memory against the real hardware configuration JTAG IDs under
scan.
cable: Cable Test cable [-cable <cable name>] [-pattern <number>] [-wireinfo] [-untested] [-step]

Running SCAN
-cable specifies the cable to be tested.

cable name refers to which cable to use. Cables are listed in the flex.mte file. The default is all cables.
-pattern runs only specific patterns.
<number> refers to the pattern number(s) to use - default is all patterns (first pattern is 0).
-wireinfo displays some wire information.
-untested displays untested wire information. Not needed if -w is set. Displays wires not fully tested. A fully tested
wire has been set to 0 and 1. Displays all wires if -p option is used.
-step is the step mode for debug pruposes.
d: DC Connectivity Test d [-pattern number] [-wireinfo] [-untested]
-pattern runs only a specific pattern.number refers to which specific pattern number to use. The default is all
generated patterns. First pattern is 0.
-wireinfo displays some wire information
-untested displays untested wire information.This is not needed if -w is set. Displays wires not fully tested. A fully
tested wire has been set to a 0 AND 1. It displays all wires if -p option is used.
drv: Driver Test drv [-wireinfo] [-step]
-wireinfo displays some wire information
-step is the step mode for debug purposes
h: Help Help function for JUST commands.
info: Information Command info type [-p path] [-D deviceIndex]
type refers to the type of information requested as follows: node displays node information
path displays path information.
device displays device information.
env displays ist environment information
wire displays wire information.
path refers to the number of a given scan path.
deviceIndex refers to which device in path (relative to 0)
Use info node to get:
deviceIndexwire also accepts [-ts targetstring] [-pin name] [-dctest] [-spn] [-smi]
targetstring is complex:node:path:part
name is pin name or pin number.
-dctest shows only dc testable wires. The default is to show both dc and non dc testable wires.
-spn shows wires with pin names. The default is to show wires with pin numbers.
-smi shows more info on wires.
q; Quit Exit JUST and return to the HP-UX prompt.
The following commands, while valid JUST commands, are considered Expert level commands. The Expert
level commands are potentially destructive to the hadware if not executed properly.
tbc: Test Bus Controller Test tbc [-complex complex] [-node node] [-path path] [-mode mode] [-submode sub-mode]
[-data data]
complex refers to the name of the complex. The default is all complexes in memory.
node refers to the number of a given node. The default is all nodes in memory.

Running SCAN
path refers to the number of a given scan path. The default is all paths
mode refers to a JTAG mode to set all parts to. The default is all available modes. Potential modes are: bypass,
sample, id, internal
sub-mode refers to an integer index into the mode
data refers to a 16-bit hes format to scan in/out. The default is the following set of patterns: 0x0000, 0xffff, 0xaaaa,
0x5555, 0x3333, 0xcafe
g: Gate Array Test g [options]
By default, all arrays that can be tested, will be tested.
The options are:
-refdes test arrays with a matching reference designator value.
-board test arrays on a given board. board is a name or slot number.
-jtag_id test arrays matching a JTAG id (e.g. 0x12345678)
-type test arrays mathcing a type (e.g. dna)
-start number indicates the start with a given pattern number
-end number indicates the end on a certain pattern number
-max number runs a maximum of number patterns per file
-opt maps a device to an index number number is the index number to map device to. board is name or slot number
of board. refdes is the reference designator of device. Only tests device number 0 unless pattern specifies a change
to a different device.
-vectorfile filename specifies the vector file to use.
-patternfile filename specifies the pattern file to use.
-nomakesafe indicates not to perform makesafe steps. This could be VERY dangerous. Do not do this unless
specifically told by support personnel.
siso: Scan In Scan Out siso [-path path] [-mode mode [:sub-mode]] [-submode sub-mode] [-data data][-errorcount
number]
path refers to the number of a specific scan path to test. The default is to test all paths.
mode refers to a specific JTAG mode to test. The default is to test all testable modes. Valid modes are:sample
internal. sub-mode refers to an integer index into the mode.
data refers to a specific 16-bit hex number (i.e. 0xffff) to scan. The default is to use all of a set of patterns:0x0000
0xffff 0xaaaa 0x5555 0x3333 0xcafe
number refers to the number of errors to display. The default is 3.
mtbc: Multiple Mode tbc Test mtbc [-mode mode1[:sub-mode1] -mode mode2[:sub-mode2] [-complex complex] [-node
node] [-path path] [-data data] [-node number]
mode1 and mode2 refer to a JTAG mode to put all parts into.mode1 is applied to a single part per scan test
operation. mode2 is applied to the rest of the parts. Potential modes are: bypass, sample id, and internal.
sub-mode1 and sub-mode2 refer to an integer index into the respective mode.
complex refers to the name of a given complex. The default is all complexes in memory.
node refers to the number of a given node.The default is all nodes in memory.
path refers to the number of a given scan path. The default is all paths.
data refers to a 16-bit hex format to scan in/out. The default is the following set of patterns: 0x0000 0xffff 0xaaaa
0x5555 0x3333 0xcafe
-node number refers to the number of errors to display.

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

This puts one device at a time in sample and all the other devices into bypass. It will use 0xcafe for the data and displays
only one error (even though there may be more). It does this for all devices of all paths.
get get [-i on|off -errors on|off -fieldpath [0-2] -h] target_string target_string = complex:node:path:device:ring:field
complex names that is defined in complex.cfg.
node node name that is defined in complex.cfg.
path scan path number that is defined in node_x.cfg.
device device name that is defined in node_x.cfg.
ring ring name that is defined in field.map or jtag.def.
field field name that is defined in field.map file.
-i on|off: specifies whether or not an instruction write is done before a data read. This is useful if multiple scans are
needed 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.
put put [-i on|off -data_read on|off -e [END_STATE] -errors on|off-h] target_string value target_string =
complex:node:path:device:ring:field :
complex complex name defined in complex.cfg.
node node name defined in complex.cfg
value hex value of data to put in the field(e.g. 0xf1b).
-i on|off: specifies whether or not an instruction write is done before a data read. This is useful if multiple scans are
needed on the same part. By default, this option is on. -data_read on|off: specifies whether or not a data read is
performed before a data write is performed. If off, bits that are not explicitly being set by the put value are set to 0. By
default, this option is on. This option is mainly used for boundary ring puts to protect the integrity of the data already
out on the path.-e[END_STATE]:allows the user to leave the JTAG controller statemachine in a specific state. The
default is the RUN-TEST-IDLE state. Other options might be PAUSE_IR or PAUSE_DR. If the -e option specifies a
JTAG_RESET then the controller is reset after the command is executed. -errors on|off:specifies whether errors are
reported to the screen. 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 value (default)
1: print field name and value only
2: print return value only
ir_get ir_get -errors on|off -h target_string target _string = complex:node:path:device
node node name defined in complex.cfg.
-errors on|off:specifies whether errors are reported to the screen. By default, this option is on.
ir_put ir_put [-errors on|off -h] target_string value target_string = complex:node:path:device

Running SCAN

node node name defined in complex.cfg
path scan path number that is defined in node_x.cfg
value hex value of data to put in the field (e.g. 0xf1b).
-errors on|off:specifies whether errors are reported to the screen. By default, this option is on.
block block [-data_read on|off -errors on|off -h] target_stringtarget_string = complex:node:path:device:ring
device device name that is defined in node_x.cfg
-data_read on|off:specifies whether or not a data read is performed before a data write is performed. If off, bits that are
not explicitly being set by the put value are set to 0. By default, this option is on. This option is mainly used for boundary
ring puts to protect the integrity of the data already out on the path.
Only one ring can be specified. Since a block reads in one ring from each device on the scan path, wildcards are not supported in
the ring token. If more than one ring on a path needs to be specified, this should be accomplished through the use of seti or setr.
For 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
internal mode (e.g. SCAN10), the steps are as follows:
just>> setr 36:p01:BOUNDARYjust>> block 36:p02:SCAN10 This locks the boundary ring of p01 and the scan10 ring of
p02 and the bypass ring of all others.
bget bget [-errors on|off -h] target_string target_string = complex:node:path:device:ring
complex complex name defined in complex.cfg
-errors on|off: specifies whether errors are reported to the screen. The default is on.
bput bput [-errors on|off -h] target_string value target_string = complex:node:path:device:ring
value hex value of data to put in the field (e.g. 0xf1b).
A bput will not write the data out to the scan path until a bscan or bunlock is performed.
bunlock bunlock [-errors on|off -h] target_string target_string = complex:node:path
-errors on|off:-errors on|off: specifies whether errors are reported to the screen. By default, this option is on.

Running SCAN

bunlock writes the data out to the scan path and unlocks the scan path.
Practical Testing Tips

JUST (a.k.a Scan and JTAG testing) are low level tests that must not be peformed on a running system unless you know exactly
what you are doing. It is very easy to crash running partitions or, even damage the hardware if the tests are not performed
properly. The following sections present scenarios and situations where scan test would be an appropriate form of
troubleshooting and which test would probably be most beneficial.
System Install
System install time is the most obvious time for scan. The system has just been received from shipment and is in an unknown
condition. Even though it was thoroughly tested at HP Manufacturing, it has been boxed and shipped in airplanes and trucks.
After assembling the system as per the Superdome Installation Manual, test the system. First, complete the tasks in the Installing
Scan and Configuring Scan nuggets, then invoke JUST and run the tests. Use the building block approach. Selecting a few tests,
without going to a low level test, can be confident that everything is seated and connecting properly. It is rare that components
will actually be damaged during shipment, it is usually a poor connection that cause errors.
1. Typically, the first command to run is ms (MakeSafe). This puts the machine into a known state. Remember, the complex
should be at BIB (Boot is Blocked) for scan tests.
2. Second should probably be idv (ID Verify). This checks the JTAG ID of all parts in the complex by rings.
3. Next, choose d. This is the DC Connectivity test. It checks the connection state of all scannable parts in the complex
configuration that was built with the cmd command when you were configuring the complex.
4. The next choice should probably be drv. This command will test the drivers of a wire. This will electrically test the wire
in a different way than d. D looks for opens, shorts and stuck-ats. DRV will give a better electrical test by running
patterns on each wire in a different manner. Both tests are important, and drv builds upon d.
5. Follow the drv command with cable. By allowing the default modes to run on these tests, all components in the
configuration are be tested. Cable will test the flex cables and U-Turn cables within the cabinet or complex.
As you well know, the items tested are contained in the complex.cfg and node_x.cfg files. These are built with the cmd
command. Be absolutely certain, when changing the configuration of the complex by adding or removing components, to
re-reun cmd.
If all of the above tests pass successfully, there is good confidence the system connections are good and you can safely procced
with the system installation.
More to be added soon.
Configuring SCAN Overview of AC Scan Link Tests

Overview of AC Scan Link Tests
What Are They?

There are two ac scan link tests (aclts) for Superdome servers: one to test the ring input/output (RIO or
REO) links between a cell and its I/O subsystem, called reo_link_ac_test; one to test the crossbar (or
XBC) 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 the
existence and continuity of the link's conductors.
Both of the aclts are Perl scripts, that require a Joint Usability Action Group Scan Test (JUST) daemon
running on HP-UX on the support management station (SMS), in order to verify the functionality of an
individual link (high speed data path between two or more application specific integrated circuits
(ASICs)). ASICs may reside on the same backplane, or on separate backplanes within another cabinet of
a complex.
All aclts are verifiers, not diagnostics or exercisers.
Unlike the dc scan testing, that uses boundary scans to test target ASIC devices, all aclts use scan on the
fly (SOTF) operations, that control the functionality of the target link (between two or more ASICs) by
modifying the internal control and status register (CSR) values of both sources, and capture
first-in-first-outs (FIFOs). All aclt testing employs multiple SOTF operations to initialize, send, and
capture data patterns, across individual ports on the target ASIC devices, at full speed across the link.
Those aclts that test links to a coherency controller (CC) chip also use internal scan and must
periodically clock halt the CC chip.
Where Are They?

All scan utilities, including the aclts, reside in the /users/hduser/<complex>/bin subdirectory
on the SMS. Scan software consists of the JUST utility program, Perl scripts, and many files consisting
of configuration and rule files.
When To Use Them?

Use them whenever cable links are established during installations, or when adding more cells, partitions,
I/O card cages, or nodes. Most repairs that require powering down a partition to replace link cables, or
http://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]

their corresponding ASICs, are also candidates for ac scan link testing.
Whenever CSR values are modified, ASIC functionality may change in a manner that is harmful to
partition operation. For XBC to XBC links, all partitions within the cabinet or cabinets where the ASICs
under test reside must be offline, or be brought offline, before starting any scan tests.
For CC to XBC links, only the cell containing the link(s) under test must be offline.
Running aclts on 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 active
node will crash the node.
How To Select Them?

Knowledge of which aclt script to select requires some knowledge of cabinet topology because different
types of links connect the different parts of a Superdome complex. Figure 1 identifies all the testable
links (marked with the letters a - f) within an Superdome 32 Way cabinet and an adjacent I/O expansion
cabinet:
Figure 1 Data Paths of Testable Links

AC Scan Test for REO Links

In Figure 1, the Ring I/O Adapter (REO) links between a cell and its I/O subsystem are marked as "(a)."
All eight REO links for a Superdome SPU cabinet are shown: four I/O subsystems are within the same
Superdome SPU cabinet, with the cells using unshielded cable pair, and four I/O subsystems are within
an adjacent I/O expansion cabinet, using shielded cable pairs.
AC Scan Test for XBC Links
The links for each cell to XBC (Crossbar Chip) are marked as "(b)." All eight XBC links are on the
backplane, within the Superdome SPU cabinet.
The intra-cabinet links between logical XBC chips are marked as "(c)." These logical XBC-to-logical
XBC links are on the backplane, within the Superdome SPU cabinet.

The inter-cabinet links between logical XBC chips are marked as "(d)." These logical XBC-to-logical
XBC links are across ribbon cables, that connect a left backplane within one Superdome SPU cabinet, to
a right backplane within another Superdome SPU cabinet (not shown).
Running SCAN Utilities

HP SMS PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HP SMS PDF

Uploaded by

Copyright:

Available Formats

DISCLAIMER:

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

Overview: Support Management Station

http://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]

Several others including tsinstall and a chassis code capture program

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

Finding More System Management Station Information

Overview: Support Management Station Installing Firmware Update Utility (FWUU)

http://superdome-test.fc.hp.com/sd_epss_cdrom/content/00/00/MK/idd/107.html [2/14/2001 2:46:06 PM]

Installing Firmware Update Utility (FWUU)

Installing FWUU from CD-ROM

Installing FWUU from Depot

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

http://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]

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

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

Finding More System Management Station Information Updating Superdome Firmware

http://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]

Updating SuperDome Firmware Files

About Firmware Update Utility (FWUU)

Updating FWUU from CD-ROM

Updating FWUU via network

http://superdome-test.fc.hp.com/sd_epss_cdrom/content/00/00/M4/idd/109.html [2/14/2001 2:46:15 PM]

Using the Firmware Update Utility

Two Versions of FWUU

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

Invoking (Starting) FWUU

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

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

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

An partial output of the Group A Complex Profile

Example 1 Successful Connection - FWUU_30

Please enter address of Halfdome system: 15.99.111.101

Maximum USB transfer size is 4100

Retrieving Complex Profile Information......

http://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]

Firmware files found in "." directory:

Listing flash handle map of remote system "15.99.49.131":

Type HELP for command information.

Identifying the Entities to Update

Entity Type--The category or name of the entity

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

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

Example 2 Example of Successful Update

FWUU>update 576 sub.4.16.frm

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

Successful reset of all entity(s).

Warning: FWUU must abort execution, communication with

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

Example 3 Example of a Refused Update

FWUU>update 704 clu.4.6.frm

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

UPDATE was NOT successful

Updating Superdome Firmware Installing SCAN

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

Installing SCAN Tools

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

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

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

Installing SCAN Tools From a Self Built Tape

http://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]

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

At the # prompt enter the following: