HP V2500 User Manual

Download

Page 1

HP Diagnostics Guide

V2500 Server

First Edition

A5075-96006

HP Diagnostics Guide: V2500 Server

Customer Order Number: A5075-90006

December 1998

Printed in: USA

Page 2

Revision History

Edition: First

Document Number: A5075-90006 Remarks: Initial release. December, 1998.

Notice

The information contained in this document is subject to change without notice.

Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and ﬁtness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance or use of this material.

Page 3

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvii

Notational conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Utilities board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

Core logic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Flash memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Nonvolatile static RAM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

DUART. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

RAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Console ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Attention lightbar and LCD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

COP interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

SPUC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

SMUC and Power-on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

SMUC environmental monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Environmental condition detected by power-on function . . . . . . . . . .9

Environmental conditions detected by SMUC. . . . . . . . . . . . . . . . . . .9

Environmental control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Power-on. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Voltage margining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Clock margining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

JTAG interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Teststation interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

DC test of a node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

AC test of a node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

JTAG fanout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

System displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Front panel LCD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Node status line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Processor status line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Message display line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

Power supply indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Attention light bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

SCUB 3.3-Volt error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

ASIC installation error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

DC OK error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

48-Volt error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

48-Volt yo-yo error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Clock failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Table of Contents iii

Page 4

FPGA conﬁguration and status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Board over-temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Fan sensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Power failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

MidPlane Interface Board (MIB) power failure. . . . . . . . . . . . . . . . 19

48-Volt maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Ambient air sensors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

AC circuit fail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2 Conﬁguration management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Teststation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

ts_conﬁg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Starting ts_conﬁg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

ts_conﬁg operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Conﬁguration Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Upgrade JTAG ﬁrmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Conﬁgure a Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Conﬁgure the “scub_ip” address . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Reset the Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Deconﬁgure a Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Add/Conﬁgure the Terminal Mux. . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Remove terminal mux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Teststation-to-system communications. . . . . . . . . . . . . . . . . . . . . . . . . . 38

LAN communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Serial communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

ccmd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

xconﬁg. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Node conﬁguration map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Node control panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Conﬁguration utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

autoreset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

est_conﬁg. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

xsecure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

3 Power-On Self Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

POST modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Interactive mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Interactive mode commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Conﬁguration parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

iv Table of Contents

Page 5

LCD messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Node status line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Processor status line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Message display line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Console messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

Type-of-boot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

Version and build . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

Processor probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

Utility board initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

Main memory initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

Memory probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

Installed memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

Main memory initialization started. . . . . . . . . . . . . . . . . . . . . . . . . .67

Parallel memory initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

Memory initialization progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

Main memory initialization complete . . . . . . . . . . . . . . . . . . . . . . . .68

System control to boot client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

Interactive boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

Interactive prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

Chassis codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

Error messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

Teststation parameters failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

Conﬁguration map failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70

ASIC probe failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70

Memory board deconﬁguration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71

Illegal memory board conﬁguration. . . . . . . . . . . . . . . . . . . . . . . . . .71

Memory remap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71

Processor initialization failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71

Monarch completing memory initialization. . . . . . . . . . . . . . . . . . . .72

PDT checksum failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

Memory hardware change detected . . . . . . . . . . . . . . . . . . . . . . . . . .72

Memory remapped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

Contiguous memory block not found . . . . . . . . . . . . . . . . . . . . . . . . .73

Processor not reported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

Processor initialization/selftest failure . . . . . . . . . . . . . . . . . . . . . . .73

Processor not responding to interrupt . . . . . . . . . . . . . . . . . . . . . . . .73

Shared Runway bus failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

New monarch processor selected . . . . . . . . . . . . . . . . . . . . . . . . . . . .74

New monarch processor not found. . . . . . . . . . . . . . . . . . . . . . . . . . .74

4 Test Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Test Controller modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

User interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77

Table of Contents v

Page 6

Main menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Test Conﬁguration menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Example of running diagnostics from Test Controller command line. . 93

Conﬁguration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Selecting classes and subtests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Starting tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Viewing the results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

5 cxtest. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Graphics interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

File menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Save Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Restore Selections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Clear Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Log to File/Close Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Test menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Class menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Subtest menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Global Test Parameters menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Command menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

System Conﬁguration menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Help menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Display area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Powering down the system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Command line interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Command line options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Command line test selections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Command line looping and pausing. . . . . . . . . . . . . . . . . . . . . . . . . . 112

Command line error counts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Command line class Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Command line subtest selections. . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Command line parameter speciﬁcations . . . . . . . . . . . . . . . . . . . . . . 114

Changing test controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Test output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Example of running diagnostics from cxtest window . . . . . . . . . . . . 115

6 Processor-dependent code

ﬁrmware loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

pdcﬂ loading, booting, and setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

NVRAM setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

vi Table of Contents

Page 7

Teststation setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120

pdcﬂ commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122

7 cpu3000. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

cpu3000 classes and subtests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126

cpu3000 classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126

cpu3000 subtests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126

cpu3000 errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131

8 io3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

io3000 classes and subtests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134

io3000 classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134

io3000 subtests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135

User parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147

Device speciﬁcation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150

io3000 error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154

io3000 general errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154

io3000 device speciﬁcation errors . . . . . . . . . . . . . . . . . . . . . . . . . . . .155

io3000 SAGA general errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155

io3000 SAGA CSR errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156

io3000 SAGA ErrorInfo CSR error . . . . . . . . . . . . . . . . . . . . . . . . . . .157

io3000 SAGA ErrorCause CSR errors. . . . . . . . . . . . . . . . . . . . . . . . .157

io3000 SAGA SRAM errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158

io3000 controller general errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159

io3000 PCI errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159

io3000 controller command errors. . . . . . . . . . . . . . . . . . . . . . . . . . . .160

io3000 DMA error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161

io3000 SCSI inquiry error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161

io3000 Symbios controller speciﬁc errors . . . . . . . . . . . . . . . . . . . . . .161

io3000 Tachyon controller speciﬁc errors . . . . . . . . . . . . . . . . . . . . . .162

io3000 DIODC driver errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163

Notes on io3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164

9 mem3000. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

mem3000 classes and subtests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166

mem3000 classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166

mem3000 subtests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167

V2500 memory conﬁgurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170

V2500 DIMM quadrant designations . . . . . . . . . . . . . . . . . . . . . . . . .171

V2500 DIMM conﬁguration rules . . . . . . . . . . . . . . . . . . . . . . . . . . . .172

V2500 memory board conﬁguration rules. . . . . . . . . . . . . . . . . . . . . .173

User parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174

mem3000 error codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176

Table of Contents vii

Page 8

Error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Type one error format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Type two errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Type three errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Notes on mem3000. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

10 Scan test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

est utility test environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Control of utility board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

est exit and reset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

est user interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Running the est GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

System Test button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

ring button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

dc button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

ac button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

ga’s button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Files button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Options button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Power button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Clocks button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Details button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Misc. button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Command line window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Connectivity test window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Gate array test window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Scan window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

SCI cable test window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Running est from command line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

AC Connectivity test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

Bypass test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

DC Connectivity test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

Gate Array test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

SCI test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

SCI_all test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

JTAG Identiﬁcation test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Margin commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

est miscellaneous commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

est run time option commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

est command ﬂags and options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Script ﬁles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

11 Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213

viii Table of Contents

Page 9

address decode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214

AutoRaid recovery map (arrm) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215

Starting arrm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215

Failure to open and recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216

consolebar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219

dcm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220

dfdutil. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224

dfdutil bootable device table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .226

dfdutil LIF ﬁle table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228

dfdutil commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228

DOWNLOAD command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .229

DISPMAP command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .229

DISPFILES command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231

LS command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231

RESET command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231

UTILINFO command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231

HELP command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231

Notes and cautions about dfdutil. . . . . . . . . . . . . . . . . . . . . . . . . . .232

Backup before downloads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .232

Halting the system during downloads . . . . . . . . . . . . . . . . . . . . . . .232

Power cycling after a download . . . . . . . . . . . . . . . . . . . . . . . . . . . .232

Shared SCSI Buses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233

Shared Nike Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233

dump_rdrs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .234

fwcp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .235

fw_init. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236

get_node_info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .238

hard_logger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240

lcd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242

load_eprom. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243

pim_dumper. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .246

set_complex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248

soft_decode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250

sppconsole . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251

tc_init . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255

tc_ioutil. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257

tc_show_struct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258

Version utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261

diag_version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261

ﬂash_info. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261

Table of Contents ix

Page 10

ver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Event processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

event_logger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

log_event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Miscellaneous tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

kill_by_name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

ﬁx_boot_vector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

12 Scan tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

sppdsh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Deﬁnitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

Miscellaneous commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Data transfer commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

Data conversion commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278

System information commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Conﬁguration commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

I/O buffering commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

Memory transfer commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

Map of alternate names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

do_reset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

jf-node_info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

jf-ccmd_info. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

jf-reserve_info. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

Appendix A: List of diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

x Table of Contents

Page 11

Figures

Figure 1 Location of the Utilities board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Figure 2 Utilities board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Figure 3 System displays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Figure 4 Front panel LCD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Figure 5 ts_config sample display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Figure 6 ts_config show node 0 highlighted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Figure 7 ts_config “Upgrade JTAG firmware” selection.. . . . . . . . . . . . . . . . . . . . . . .28

Figure 8 Upgrade JTAG firmware confirmation panel . . . . . . . . . . . . . . . . . . . . . . . . . .28

Figure 9 ts_config power-cycle panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Figure 10 ts_config indicating Node 0 as not configured. . . . . . . . . . . . . . . . . . . . . . . .29

Figure 11 ts_config “Configure Node” selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Figure 12 ts_config node configuration panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Figure 13 ts_config node configuration confirmation panel.. . . . . . . . . . . . . . . . . . . . .31

Figure 14 ts_config indicating Node 0 is configured . . . . . . . . . . . . . . . . . . . . . . . . . . .32

Figure 15 ts_config “Configure ‘scub_ip’ address” selection . . . . . . . . . . . . . . . . . . . . .33

Figure 16 ts_config scub_ip address configuration confirmation . . . . . . . . . . . . . . . . .33

Figure 17 ts_config scub_ip address set confirmation panel. . . . . . . . . . . . . . . . . . . . .34

Figure 18 ts_config “Reset Node” selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Figure 19 ts_config node reset panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Figure 20 ts_config “Add/Configure Terminal Mux” selection.. . . . . . . . . . . . . . . . . . .36

Figure 21 ts_config terminal mux IP address panel . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Figure 22 Terminal mux IP address entered into panel . . . . . . . . . . . . . . . . . . . . . . . . . .37

Figure 23 Teststation-to-system communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

Figure 24 xconfig window—physical location names . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Figure 25 xconfig window—logical names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Figure 26 xconfig window menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Figure 27 xconfig window node configuration map. . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Figure 28 xconfig window node control panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

Figure 29 Front panel LCD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Figure 30 cxtest menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104

Figure 31 Test Class Selection menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106

Figure 32 cxtest Global Test Parameters menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107

Figure 33 System configuration window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109

Figure 34 mem3000 Test Class Selection window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115

Figure 35 mem3000 Class 1 Subtest Selections window. . . . . . . . . . . . . . . . . . . . . . . . . .116

Figure 36 mem3000 Test Parameters window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116

Figure 37 io3000 test parameter device specification for directly attached SCSI targets

(words 8-19) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150

Figure 38 io3000 test parameter device specification for Fibre Channel attached SCSI

targets (words 20-37) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151

List of Figures xi

Page 12

Figure 39 V2500 DIMM locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Figure 40 Format of parameter 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Figure 41 Format of parameter7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Figure 42 Type one error message format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Figure 43 Type two error message format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Figure 44 Corresponding type two values to DIMM location. . . . . . . . . . . . . . . . . . . . . 181

Figure 45 Type 3 error message format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Figure 46 est main window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Figure 47 est command line window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Figure 48 est connectivity window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Figure 49 est gate array test window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Figure 50 est scan window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

Figure 51 est SCI cable test window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Figure 52 est Help window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Figure 53 est Help browser window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Figure 54 tc_init NVRAM entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

xii List of Figures

Page 13

Tables

Table 1 Environmental conditions monitored by the SMUC and power-on circuit . . .8

Table 2 Processor initialization steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Table 3 Processor run-time status codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

Table 4 Message display line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Table 5 Environmental attention light bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Table 6 ts_config status values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Table 7 Name of teststation IP address for listed utilities . . . . . . . . . . . . . . . . . . . . . .59

Table 8 Name of scub IP address for listed utilities . . . . . . . . . . . . . . . . . . . . . . . . . . .59

Table 9 Name of CTI cache size IP address for listed utilities . . . . . . . . . . . . . . . . . . .60

Table 10 Name of boot module for listed utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

Table 11 Name of selftest enable for listed utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

Table 12 Name of scuba test enable for listed utilities . . . . . . . . . . . . . . . . . . . . . . . . . .61

Table 13 Name of master error enable for listed utilities . . . . . . . . . . . . . . . . . . . . . . .61

Table 14 Name of use error overides for listed utilities . . . . . . . . . . . . . . . . . . . . . . . . .61

Table 15 Name of sforce monarch for listed utilities . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Table 16 Name of monarch number for listed utilities . . . . . . . . . . . . . . . . . . . . . . . . . .62

Table 17 Processor initialization steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64

Table 18 Processor run-time status codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64

Table 19 Message display line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Table 20 Processor States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82

Table 21 Parameter Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89

Table 22 Test patterns for subtests 230-238 and 330-338 . . . . . . . . . . . . . . . . . . . . . . .98

Table 23 Command line loading options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111

Table 24 Looping, pause, and control options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112

Table 25 Classes of cpu3000 tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126

Table 26 cpu3000 Class 1 subtests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127

Table 27 cpu3000 Class 2 subtests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128

Table 28 cpu3000 Class 3 subtests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128

Table 29 cpu3000 Class 4 subtests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128

Table 30 cpu3000 Class 5 subtests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129

Table 31 Classes of io3000 tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134

Table 32 io3000 Class 1 subtests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135

Table 33 io3000 Class 2 subtests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136

Table 34 io3000 Class 5 subtests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138

Table 35 io3000 Class 6 subtests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139

Table 36 io3000 Class 7 subtests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140

Table 37 io3000 Class 8 subtests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142

Table 38 io3000 Class 11 subtests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143

Table 39 io3000 Class 12 subtests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144

Table 40 io3000 Class 15 subtests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146

List of Tables xiii

Page 14

Table 41 io3000 Class 16 subtests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Table 42 io3000 test parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Table 43 io3000 user test parameter word 0 bit definition . . . . . . . . . . . . . . . . . . . . 149

Table 44 io3000 bit definition for direct SCSI device specification (words 8-19) . . . 151 Table 45 io3000 bit definition for Fibre Channel attached SCSI device specification (words 29-37) 152

Table 46 io3000 SAGA name to number correlation . . . . . . . . . . . . . . . . . . . . . . . . . 153

Table 47 io3000 general error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Table 48 io3000 device specification error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Table 49 io3000 SAGA general errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Table 50 io3000 SAGA CSR errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Table 51 io3000 SAGA ErrorInfo CSR error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Table 52 io3000 SAGA ErrorCause CSR errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Table 53 io3000 SAGA SRAM errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Table 54 io3000 Controller general errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Table 55 io3000 PCI errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Table 56 io3000 controller command errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Table 57 io3000 DMA error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Table 58 io3000 SCSI inquiry error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Table 59 io3000 Symbios controller specific errors . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Table 60 io3000 Symbios controller specific errors . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Table 61 io3000 DIODC controller specific errors . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Table 62 Symbios controller status codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Table 63 mem3000 test classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Table 64 mem3000 class 1 subtests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Table 65 mem3000 class 2 subtests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Table 66 mem3000 class 3 subtests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Table 67 mem3000 class 4 subtests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Table 68 mem3000 class 5 subtests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Table 69 mem3000 class 6 subtests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Table 70 DIMM row/bus table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Table 71 Quadrant assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Table 72 Memory board configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Table 73 User parameter definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Table 74 mem3000 error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Table 75 Extended range for error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Table 76 Patterns used in specified subtests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Table 77 est command line options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Table 78 AC Connectivity test options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

Table 79 Dc Connectivity test options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

Table 80 Gate Array test options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Table 81 Valid values for clock and power supplies . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Table 82 est runtime option commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Table 83 load_eprom options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Table 84 pim_dumper options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

xiv List of T ables

Page 15

Table 85 kill_by_name options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266

Table 86 sppdsh parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .270

Table 87 Valid COP IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .272

Table 88 System rings to alternates names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282

Table 89 List of diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .289

List of Tables xv

Page 16

xvi List of T ables

Page 17

Preface

This document describes the ofﬂine diagnostics for V2500 servers. It is not intended to be a tutorial or troubleshooting guide but a reference guide that contains information on all utilties and scripts used to troubleshoot these systems.

Notational conventions

This section describes notational conventions used in this book.

bold monospace In command examples, bold monospace

identiﬁes input that must be typed exactly as shown.

monospace In paragraph text, monospace identiﬁes

command names, system calls, and data structures and types. In command examples, monospace identiﬁes command output, including error messages.

italic In paragraph text, italic identiﬁes titles of

documents. In command syntax diagrams, italic identiﬁes variables that you must provide. The following command example uses brackets to indicate that the variable output_ﬁle is optional: command input_ﬁle [output_ﬁle]

Preface xvii

Page 18

Preface

Notational conventions

Brackets ( [ ] ) In command examples, square brackets

designate optional entries.

Curly brackets ({}), Pipe (|)

In command syntax diagrams, text surrounded by curly brackets indicates a choice. The choices available are shown inside the curly brackets and separated by the pipe sign (|). The following command example indicates that you can enter either a or b:

command {a | b}

Keycap Keycap indicates the keyboard keys you must

press to execute the command example.

NOTE A note highlights important supplemental information.

CAUTION A caution highlights procedures or information necessary to avoid

damage to equipment, damage to software, loss of data, or invalid test results.

xviii Preface

Page 19

1 Introduction

This chapter presents an overview of the diagnostic mechanism for V2500 servers.

Chapter 1 1

Page 20

Introduction

Utilities board

The diagnostic mechanism in the V2500 servers is centered around the Stingray Core Utilities board (SCUB). The SCUB is mounted under the MidPlane Interconnect board (MIB) toward the front of the system. See Figure 1.

2 Chapter 1

Page 21

Figure 1 Location of the Utilities board

Power board

MidPlane

Utilities board

Introduction

Utilities board

IOEXS120

12/7/98

Chapter 1 3

Page 22

Introduction

Utilities board

The following devices connect to the Utilities board:

• Core logic bus

• Environmental sensors

• Test points

• Liquid crystal display (LCD)

• Attention lightbar

• Teststation

The teststation connects to the system via the ethernet and RS232 connections. It is used to conﬁgure and run diagnostics on the system. A system will boot and operate without a teststation, and failure of

the teststation will not cause interruption of the system. Figure 2 shows the Utilities board functional layout. The following hardware components comprise the Utilities board:

• Core logic—Contains initialization, booting ﬁrmware, controller for

ethernet and RS-232 interface, and various memories.

• Stingray Monitor Utilities controller (SMUC)—Collects

environmental interrupts.

• Power-On circuit—Controls powering up the entire system.

Environmental sensors are located throughout the system and

connect to the SMUC. The SMUC latches interrupts from these

sensors as well as other interrupts. The SMUC and the power-on

circuit together control system power-up. The power-on circuit drives

the attention lightbar diagnostic display through which the operator

can determine power-on status.

• Stingray Processor Utilities controller (SPUC)—Interfaces to the core

logic bus.

The SPUC connects to the two core logic buses. Each bus connects up

to four Stingray Processor Agent Controllers (SPACs).

• JTAG (Joint Test Action Group) interface—Supports a teststation for

running diagnostics. The V2500 servers use a test method called

scanning to test boards and other hardware units.

4 Chapter 1

Page 23

The microprocessor-controlled JTAG interface captures incoming command packets and sends out scan information packets across the ethernet connection to the teststation. Through the teststation connection, one can read and write every CSR in the system.

Figure 2 Utilities board

Introduction

Utilities board

SPACSPACSPAC SPAC SPAC SPAC SPACSPAC

Core logic bus Core logic bus

Node

scanning

power

controller

and interface

Ethernet

Teststation

JTAG

Clock

logic

Ethernet

Hard errors and

environmental

sensors

SPUC SMUC

Utility bus

Core logic

RS232

Liquid crystal

display

MIB

Utilities board

power

Power-on

Led display

IOEXS118

11/16/98

Chapter 1 5

Page 24

Introduction

Utilities board

Core logic

The core logic contains initialization and booting ﬁrmware and is described in the following sections.

Flash memory

The core logic contains a four-MByte electrically erasable programmable read only memory (EEPROM) storage for Processor-Dependent Code (PDC). PDC consists of Power-On Self Test (POST) and Open Boot PROM (OBP). The V2500 server uses these two components plus additional ﬁrmware called spp_pdc that is laid over OBP and interfaces OBP to HP-UX. Flash memory also contains all diagnostic test, utilities , and scripts.

Flash memory is conﬁgured as 512-KByte addresses by 32 data bits with only 32-bit read and write accesses allowed. EEPROM devices are used for ﬂash memory so that it may be rewritten for ﬁeld upgrades. It can also be written when the SPUC is scanned.

Nonvolatile static RAM

The core logic section contains a nonvolatile battery-backed 128-Kbyte RAM (NVRAM) for storing system log and conﬁguration information. This RAM is byte addressable and can be accessed even after power failures.

DUART

A Dual Universal Asynchronous Receiver-Transmitter (DUART) provides to RS232 serial ports and a single parallel port. One serial port provides an interface to a terminal used as a local console to analyze problems, reconﬁgure the system, and provide other user access.The parallel port of the DUART drives the LCD. The second RS232 port can be used for a modem for ﬁeld service.

RAM

Random access memory (RAM) provides support for the core system functions. When the system powers up, the processors operate out of this RAM to run self test and conﬁgure the rest of the node. Once the system is fully conﬁgured, the processors execute out of main memory. The RAM is byte addressable and is 512 KBytes, conﬁgured as 128-KByte addresses by 32 data bits.

6 Chapter 1

Page 25

Introduction

Utilities board

Console ethernet

The ethernet I/O port provides a connection to the teststation over LAN1.

Attention lightbar and LCD

The attention light bar displays environmental information, such as the source of an environmental error that caused the Utilities board to power down the node.

The liquid crystal display provides basic system information. The core logic drives the LCD through the parallel port on the DUART. The attention lightbar and LCD are detailed in “System displays” on page 12.

COP interface

A serial EEPROM (referred to as COP chip) is located on major boards with information such as serial number , assembly revision, wire revision, truncated board part number, and so on. The SMUC connects to the COP bus selector (CBS) chip on the MIB allowing each COP chip in a node to be read.

SPUC

The SPUC provides interrupts and error messages to and receives control messages from the processors through two 18-bit, bidirectional buses. Each bus connects up to four SP ACs . The SPUC also provides core logic bus arbitration for the processors.

SMUC and Power-on

The SMUC registers system environmental parameters. It connects to the utilities bus so that processors can monitor the node by accessing the appropriate CSRs. The SMUC works in conjunction with the power-on circuit to power up the entire system, and it can operate when the rest of the node is powered off or in some indeterminate state. The SMUC drives the environment LCD display. The teststation can also read the environmental LCD display using the sppdsh utility. See “sppdsh” on page 268.

Chapter 1 7

Page 26

Introduction

Utilities board

SMUC environmental monitoring

The following environmental conditions are monitored:

• ASIC installation error sensing

• FPGA conﬁguration and status

• Thermal sensing

• Fan Sensing

• Power failure sensing

• 48-V failure

• 48-V maintenance

• Ambient air temperature sensing.

• Power-on

Table 1 Environmental conditions monitored by the SMUC and power-

on circuit

Condition Type Action

ASIC Not InstalledOKEnvironmental

error

FPGA not OK Environmental

error

48-V Fail Environmental

error

MIB power fail Environmental

error

Board over temp Environmental

error

Fan not turning Environmental

error

Ambient air hot Environmental

error

Other power fail Environmental

error

8 Chapter 1

Power not turned on, LED indication

Power turned off, LED indication

Power off in one second, LED indication interrupt

Page 27

Condition Type Action

Introduction

Utilities board

Ambient air warm Environmental

warning

48-Volt maintenance Environmental

warning

Hard error Hard error LED indication, interrupt

LED indication, interrupt

Environmental condition detected by power-on function

The power-on function detects environmental errors (such as ASIC Not Installed OK or FPGA Not OK). It does not turn on power to the node until the conditions are corrected. It also detects environmental errors such as 48-V Fail while the system is powering up and MIB Power Fail after the system has powered up. If a failure is detected in these two cases, the power-on circuit turns off power to the system.

Environmental warnings such as 48-Volt maintenance are also detected by the power-on circuit.

In all cases, the power-on circuit sets an environmental attention light bar code. The code is prioritized so that it displays the highest priority error or warning. See “Attention light bar” on page 16 for a list of codes.

Environmental conditions detected by SMUC

The SMUC detects most of the environmental conditions. It samples error conditions during a time period derived from a local 10-Hz clock that drives the power-on circuit. It registers all the environmental error conditions twice and then logically ORs them together. If the conditions persist for 200 mS, the environmental error bit is set, and an environmental error interrupt is sent to the SPUC, which sends it on to the processors. The SMUC then waits 1.2 seconds and commands the power-on circuit to power down the system.

This same procedure exists for an environmental warning, except that an environmental warning interrupt is sent and the power-on circuit does not power down the system.

Chapter 1 9

Page 28

Introduction

Utilities board

The environmental error interrupt and the 1.2 second delay provide the system adequate time to read CSRs to determine the cause of the error, log the condition in NVRAM, and display the condition on the attention lightbar.

After the system is powered down, the Utilities board is still powered up, but all outputs are disconnected from the system.

Environmental control

The Utilities board performs the following functions to control the node environment.

Power-on

When the power switch is turned on, the outputs of the 48-Volt power supplies become active. Several hundred milliseconds after the Utilities board 5-V olt supply reaches its nominal level, the power-on circuit starts powering up the other DC-to-DC converters of the node in succession.

The power-on circuit does not power up the node if an ASIC is installed incorrectly (see “ ASIC installation error” on page 18) or if an FPGA is not conﬁgured (see “FPGA conﬁguration and status” on page 19). It keeps the system powered up unless an environmental condition occurs that warrants a power-down.

Voltage margining

Voltage margin is divided into four groups called quadrants. The user can margin quadrants separately. When setting the upper margin, for example, all boards in that quadrant are margined for upper.

Clock margining

Parallel ports on the core logic microprocessor select the nominal, upper, or external clock that drives the node.

JTAG interface

The JTAG interface supports a teststation and a mechanism to fanout JTAG to all the boards in a node. It is used only for testing.

JTAG functions are described in the following sections.

10 Chapter 1

Page 29

Introduction

Utilities board

Teststation interface

The teststation can be a PA-RISC based workstation. The interface to the teststation is an ethernet AUI port for ﬂexibility in connecting to many workstations. It is also easily expandable.

DC test of a node

To perform the DC test, the Test Bus Controller (TBC) ﬁrst scans data to all boards in a node. Then each JTAG device performs a capture step that completes the movement of the test data from the driver to the receiver. This step is described in the JTAG 1149.1 speciﬁcation.

AC test of a node

To perform theAC test, the Test Bus Controller (TBC) scans data to all boards in a node and then loads an AC test instruction into all ASICs on one board at a time. The scan ring on each board is paused.

Once all boards have been loaded with the AC test instruction, the TBC takes all boards out of pause mode simultaneously, causing them all to exit update together and execute the AC test.

The AC test enables clocks inside the ASICs so that they test internal and external paths at the system clock rate. They all execute on the same system clock.

JTAG fanout

The teststation interface is thin ethernet. In addition to the teststation, this port is also used for the console ethernet. There is one cable that connects to all the nodes and to the teststation (if it exists) and to whatever device or network that will display the console.

Chapter 1 11

Page 30

Introduction

System displays

The V2500 server provides two means of displaying status and error reporting: an LCD and an Attention light bar.

Figure 3 System displays

CONSOLE

DC OFF

ENABLE

CONSLOLE SECURE

DC ON

TOC

LCD display

Attention light bar

IOLM010

9/18/97

Front panel LCD

The front panel is a 20-character by 4-line liquid crystal display as shown in Figure 4.

12 Chapter 1

Page 31

Figure 4 Front panel LCD

0 (0,0) MIII IIII IIII IIII

IIII IIII IIII IIII abcedfghijklr

When the node key switch is turned on, the LCD powers up but is initially blank.

Power-On Self Test (POST) starts displaying output to the LCD. The following illustrates this output shown in Figure 4:

Node status line

The Node Status Line shows the node ID in both decimal and X, Y topology formats.

Introduction

System displays

Processor status line

The processor status line shows the current run state for each processor in the node. Table 2 shows the initialization step code deﬁnitions and Table 3 shows the run-time status codes. The M in the ﬁrst processor status line stands for the monarch processor.

Table 2 Processor initialization steps

Step Description

Chapter 1 13

Page 32

Introduction

System displays

Step Description

6 Processor internal register ﬁnal initialization. 7 Processor basic instruction set testing. (optional) 8 Processor basic instruction cache testing. (optional) 9 Processor basic data cache testing. (optional) a Processor basic TLB testing (optional) b Processor post-selftest internal register cleanup. (optional)

Table 3 Processor run-time status codes

Status Description

R RUN: Performing system initialization operations. I IDLE: Processor is in an idle loop, awaiting a command. M MONARCH: The main POST initialization processor. H HPMC: processor has detected a high priority machine

check (HPMC). T TOC: processor has detected a transfer of control (TOC). S SOFT_RESET: processor has detected a soft RESET. D DEAD: processor has failed initialization or selftest. d DECONFIG: processor has been deconﬁgured by POST or

the user.

- EMPTY: Empty processor slot. ? UNKNOWN: processor slot status in unknown.

Message display line

The message display line shows the POST initialization progress. This is updated by the monarch processor. The system console also shows detail for some of these steps. Table 4 shows the code deﬁnitions.

14 Chapter 1

Page 33

Table 4 Message display line

Introduction

System displays

Message

display code

a Utilities board (SCUB) hardware initialization. b Processor initialization/selftest rendezvous. c Utilities board (SCUB) SRAM test. (optional) d Utilities board (SCUB) SRAM initialization. e Reading Node ID and serial number. f Verifying non-volatile RAM (NVRAM) data

structures. g Probing system hardware (ASICs). h Initializing system hardware (ASICs). i Probing processors. j Initialing, and optionally testing, remaining SCUB

SRAM. k Probing main memory. l Initializing main memory.

Description

r Enabling system error hardware.

Power supply indicators

When the keyswitch on the operator panel is in the DC ON position both the AC power (amber) LED and the DC power (green) LED on each of the power supplies should be on.

Chapter 1 15

Page 34

Introduction

System displays

Attention light bar

The Attention light bar is located at the top left corner on the front of the HP 9000 V2500 server as shown in Figure 3 on page 12. This light bar displays system status in three ways:

• Off—system powered down

• Steady on—system powered up

• Flashing—error condition The SMUC prioritizes system environmental errors and warnings and

passes the information to the power-on circuit. This circuit prioritizes the 6-bit ﬁeld with its environmental conditions and produces a 7-bit ﬁeld plus an attention bit (ATTN) that drives the attention light bar. ATTN is on if there is an environmental warning. Second-level registers in the SMUC drive the attention light bar.

In general, the power-on-detected errors are a higher priority than SMUC-detected errors, the lower the error code number, the higher its priority. Environmental warnings are lower priority than the environmental errors. Table 5 shows the attention light bar error codes in hexadecimal. The top of the table is the highest priority, the bottom the lowest. If a higher condition occurs, that one is displayed.

Table 5 Environmental attention light bar

ATTN

bit

1 00 SCUB 3.3-V error (highest priority) 1 01 ASIC Install 0 (MIB) 1 02 ASIC Install 1 (MEM) 1 03 FPGA not OK 1 04-07 DC OK error (UL, UR, LL, LR) 1 08-11 48-V error, NPSUL fail, PWRUP=0-9 1 12-1B 48-V error, NPSUR failure, PWRUP=0-9 1 1C-25 48-V error, NPSLL failure, PWRUP=0-9

16 Chapter 1

attentio

n light

bar

Description

Page 35

Introduction

System displays

ATTN

bit

1 26-2F 48-V error, NPSLR failure, PWRUP=0-9 1 30-39 48-V error, no supply failure, PWRUP=0-9 1 3A 48-V yo-yo error 1 3B MIB power failure (PB) 1 3C Clock failure 1 3D-3F Not used (3) 1 40-47 MB0-MB7 power failure 1 48-4F PB0L, PB1R, PB2L, PB3R, PB4L, PB5R, PB6L,

1 50-57 PB0R, PB1L, PB2R, PB3L, PB4R, PB5L, PB6R,

1 58-5B IOB (LF,LR,RF,RR) power failure 1 5C-61 Fan failure (UR,UM,UL,LR,LM,LL) 1 62 Ambient hot or ambient shutdown

attentio

n light

bar

Description

PB7R power failure

PB7L power failure (possibly switch R and L)

1 63 Overtemp MIB 1 64-67 Overtemp quadrant (RL, RU, LL, LU) 1 68 Hard error 1 69 Ambient warm 1 6A-6F Not used (6) 1 70-73 DC supply maintenance (UL,UR,LL,LR) 1 74 AC circuit failure 1 75-7F Not used (11) 0 00-09 PWRUP state (00=System all powered up),

attention LED off

Chapter 1 17

Page 36

Introduction

System displays

SCUB 3.3-Volt error

This error indicates that the SCUB 3.3-Volt power supply has failed, but the 5-Volt supply has not.

ASIC installation error

Each ASIC in the node has ASIC Install lines to prevent power-up if an ASIC is installed incorrectly (such as a SPAC installed in an ERAC position). If an ASIC is improperly installed, the Utilities board does not power up the system. This condition is not monitored after power up.

DC OK error

When this error is displayed, the power-on circuit did not power up the system, because one or more 48-V olt power supplies reported an error. In systems with redundant 48-Volt power supplies, this error means that two or more 48-Volt supplies reported an error.

48-Volt error

If the 48-Volt supply has dropped below 42 volts for any reason other than normally turning off the system or an ac failure, then this error is displayed by the power-on circuit. Also, the 48-Volt supply that reported the error and the power-up state of the system at the time of the error is displayed.

48-Volt yo-yo error

This error indicates that a 48-V olt error occurred and the SCUB lost and then later regained power without the machine being turned off. The power-on circuit will display this error and not power on the system, because the 48-Volt supply is likely at fault.

Clock failure

If the system clock fails, the SMUC is unable to monitor environmental errors that could possibly damage the system. If the power-on circuit receives no response from the SMUC, it powers down the system and displays this error.

18 Chapter 1

Page 37

Introduction

System displays

FPGA conﬁguration and status

The SMUC is programmed by a serial data transfer from EEPROM upon utility board power-up. If the transfer does not complete properly, the SMUC cannot conﬁgure itself and many environmental conditions cannot be monitored. The power-on circuit monitors both the SMUC and SPUC and does not power up the system, if they are not conﬁgured correctly.

Board over-temperature

On each board in the node, there is one temperature sensor that detects board overheating. The sensors are bussed together into four-node quadrants, along with the MIB, and applied to the SMUC.

Fan sensing

The V2500 node has up to six fans, but only four may be conﬁgured. Sensors in the fans determine if the fans are running properly. The SMUC waits 12.8 seconds for the fans to spin up after power-up before monitoring them. It is assumed that the unconﬁgured fans do not report errors.

Power failure

Because a power failure on a board could cause damage to other boards, a mechanism on each board detects 3.3-Volt failures on each board. Power failures are considered environmental errors, and the system is powered down after they are detected.

MidPlane Interface Board (MIB) power failure

If the MIB power fails, the power-on circuit powers down the entire node . The Utilities board is still active, but the power-on circuit displays the power failure condition and disables all Utilities board outputs that drive the node. This condition persists until power is cycled on the Utilities board.

48-Volt maintenance

There are four 48-Volt power supplies; three are required, and one is a redundant source. Each sends a signal to the power-on circuit. If any supply fails at any time, the circuit asserts the 48-V maintenance line to

Chapter 1 19

Page 38

Introduction

System displays

the SMUC, which reports the environmental warning to the processors. The power-on circuit displays the “highest priority” 48-Volt supply that failed.

Ambient air sensors

The ambient air sensors detect a too warm or too hot condition in the input air stream to the Utilities board (and therefore the entire node). Ambient air too warm is an environmental warning; ambient air too hot is an environmental error that powers down the system.

The temperature set points are set using the sppdsh utility, described in “sppdsh” on page 268. The digital temperature sensor has nonvolatile storage for the temperature set points. Power-on reset starts the digital temperature sensor without the core logic microprocessor intervening.

AC circuit fail

An AC circuit failure denotes that the circuit that detects AC failures is broken. A power-on reset clears this warning.

20 Chapter 1

Page 39

2 Conﬁguration management

The teststation allows the user to conﬁgure the node using the ts_config utility. ts_config conﬁgures the teststation to communicate with the node. The teststation daemon, ccmd, monitors the node and reports back conﬁguration information, error information and general status. ts_config must be run before using ccmd.

Two additional utilities, sppdsh and xconfig, allow reading or writing conﬁguration information and changing it. OBP can also be used to modify the conﬁguration.

Chapter 2 21

Page 40

Conﬁguration management

Teststation

The teststation is used for conﬁguring, monitoring, testing, and error logging. It is not required for normal operation of a node.

The teststation communicates with the JTAG interface in the nodes. The JTAG port remains idle if no teststation is connected to it. It receives communications packets, interprets requests, and generates responses to them. The hardware on the node can read board information, system conﬁguration, device revisions, and environmental conditions. When a teststation is present, all of these parameters are read or written by the conﬁguration management tools.

The conﬁguration management daemon, ccmd, initiates communications between the teststation and the nodes.

22 Chapter 2

Page 41

Conﬁguration management

ts_conﬁg

ts_config [-display display name]

V2500 nodes added to the teststation must be conﬁgured by ts_config to enable diagnostic and scan capabilities, environmental and hard-error monitoring, and console access.

Once the conﬁguration for each node is set, it is retained when new teststation software is installed.

ts_config tasks include:

• Conﬁguring a node—Adding and removing a node to the teststation conﬁguration

• Conﬁguring the terminal mux—Conﬁguring and removing the terminal mux on the teststation

• Installing a node—Upgrading JTAG ﬁrmware, conﬁguring a node scub_ip address, and resetting a node

The user must have root privilege to conﬁgure a node of the terminal mux, because several HP-UX system ﬁles are modiﬁed during the conﬁguration.

Starting ts_conﬁg

To startts_config from the teststation desktop, click on an empty area of the background to obtain the Workspace menu and then select the ts_config (root) option. Enter the root password.

To start ts_config from a shell (local or remote), ensure that the DISPLAY environment variable is set appropriately before starting ts_config.

For example:

$ DISPLAY=myws:0; export DISPLAY (sh/ksh/sppdsh) % setenv DISPLAY myws:0 (csh/tcsh)

Also, the -display start-up option may be used as shown below:

For example:

# /spp/bin/ts_config -display myws:0

Chapter 2 23

Page 42

Conﬁguration management

ts_conﬁg

NOTE For shells that are run from the teststation desktop, the DISPLAY

variable is set (at the shell start-up) to the local teststation display.

ts_conﬁg operation

The ts_config utility displays an active list of nodes that are powered up and connected to the teststation diagnostic LAN. The operator selects a node and conﬁgures the selected node. A sample display is shown below.

Figure 5 ts_config sample display

The window has two main parts: the drop-down menu bar and the display panel. The display panel contains a list of nodes and their status. To select a node, click with the left-mouse button the line containing the desired node entry in the list. When a node is selected, information about that node is shown at the bottom of the ts_config window. If an action needs to be performed to conﬁgure the node, speciﬁc instructions are included.

ts_config automatically updates the display when it detects either a change in the conﬁguration status of any node or a new node. However, the automatic update is disabled while the user has a node selected.

After the node is selected, the display is not updated until the user selects an action or refreshes the node list. The upper right corner of the ts_config window indicates whether a node has been selected.

24 Chapter 2

Page 43

The ts_config window title includes in parenthesis the name of the effective user ID running ts_config, either root or sppuser.

The ts_config display shows the conﬁguration status of the nodes. Table 6 shows the possible status values.

Table 6 ts_config status values

Conﬁguration management

ts_conﬁg

Conﬁguration

Status

Upgrade JTAG ﬁrmware

Not Conﬁgured ts_config has detected the

The version of JTAG ﬁrmware running on the SCUB does not support the capabilities required to complete the node conﬁguration process.

node on the Diagnostic LAN and the JTAG ﬁrmware is capable of supporting the node conﬁguration activity and the node needs to be conﬁgured.

Description Action Required

Select the node and follow the instructions given at the bottom of the ts_conﬁg window. ts_config guides the operator through the JTAG ﬁrmware upgrade procedure.

Select the node and follow the instructions given at the bottom of the ts_config window. ts_config guide the operator through the node conﬁguration procedure described later in this document.

Chapter 2 25

Page 44

Conﬁguration management

ts_conﬁg

Conﬁguration

Status

Active The node is conﬁgured and

answering requests on the Diagnostic LAN.

Inactive The teststation node

conﬁguration ﬁle contains information about the speciﬁed node, but the node is not responding to requests on the Diagnostic LAN.This status is also shown if a node was conﬁgured and then removed from the teststation LAN without being deconﬁgured.

Node Id changed

The node is conﬁgured and answering requests on the diagnostic LAN, but the node ID currently reported by the node does not match the teststation conﬁguration information.

Description Action Required

None required. This is the desired status.

Power-up the node and/or check for a LAN connection problem. If the node information shown is for a node that has been removed, select the node then select “Actions,” “Deconﬁgure Node,” and click “Yes.”

Select the node to obtain additional information. If the node COP information was changed to a different node ID and the new node ID is correct, select “Actions,” “Conﬁgure Node,” then click “Conﬁgure.” The teststation conﬁguration information is updated using the new node ID.

Conﬁguration Procedures

NOTE This procedure does not need to be performed unless the status shows

“Upgrade JTAG ﬁrmware.” If the node shows “Not Conﬁgured,” skip this section.

The following procedures provide additional details about each conﬁguration action. ts_config automatically guides the user through the appropriate procedure when a node is selected.

26 Chapter 2

Page 45

Upgrade JTAG ﬁrmware

Step 1. Select the node from the list in the display panel. For example, clicking

on node 0 in the list highlights that line as shown in Figure 6.

Figure 6 ts_conﬁg show node 0 highlighted

Conﬁguration management

ts_conﬁg

Notice that after the node has been highlighted that ts_config displays information concerning the node. In this step, it tells the user what action to take next, “This node’s JTAG ﬁrmware must be upgraded. Select “Actions,” “Upgrade JTAG ﬁrmware” and “Yes” to upgrade.”

Step 2. Select “Actions” to drop the pop-down menu and then click “Upgrade

JTAG ﬁrmware,” as shown in Figure 7.

Chapter 2 27

Page 46

Conﬁguration management

ts_conﬁg

Figure 7 ts_config “Upgrade JTAG ﬁrmware” selection.

Step 3. A message panel appears as the one shown in Figure 8. Read the

message. If this is the desired action, click “Yes” to begin the upgrade.

Figure 8 Upgrade JTAG ﬁrmware conﬁrmation panel

Step 4. After the ﬁrmware is loaded a panel appears as the one shown in Figure

9. Click “OK” and then power-cycle the node to activate the new ﬁrmware.

28 Chapter 2

Page 47

Figure 9 ts_config power-cycle panel

When the node is powered up, the “Conﬁguration Status” should change to “Not Conﬁgured.”

Conﬁgure a Node

Step 1. Select the desired node from the list of available nodes. When the node is

selected, the appropriate line is highlighted as shown in Figure 10. Notice the bottom of the display indicates the Node 0 is not conﬁgured and provides the steps necessary to conﬁgure the node.

Figure 10 ts_config indicating Node 0 as not conﬁgured

Conﬁguration management

ts_conﬁg

Step 2. Select “Actions” and then click “Conﬁgure Node,” as shown in Figure 11.

Chapter 2 29

Page 48

Conﬁguration management

ts_conﬁg

Figure 11 ts_config “Conﬁgure Node” selection.

After invoking ts_config to conﬁgure the node, a node conﬁguration panel appears as the one in Figure 12.

Figure 12 ts_config node conﬁguration panel

Step 3. Enter a name for the V2500 System. The teststation uses this name as

the “Complex Name” and to generate the IP hostnames of the Diagnostic and OBP LAN interfaces. Select a short name that teststation users can easily relate to the associated system (for example: hw2a, swtest, etc.).

30 Chapter 2

Page 49

Conﬁguration management

Step 4. Select an appropriate serial connection for the V2500 console from the

pop-down option menu in the node conﬁguration panel. ts_config automatically assigns the ﬁrst unused serial port. If the

terminal mux has been conﬁgured, the terminal mux ports are included in the list of available serial connections.

The IP address information for the Diagnostic interface is provided. The ts_config utility automatically changes the IP address of the diagnostic LAN interface to prevent a duplicate when other nodes are added to this teststation conﬁguration.

ts_config automatically updates the local /etc/hosts ﬁle with the names and addresses of the Diagnostic and OBP LAN interfaces.

Step 5. Click “Conﬁgure.”

This updates several teststation ﬁles. The node conﬁguration conﬁrmation panel appears as the one in Figure 13.

Figure 13 ts_config node conﬁguration conﬁrmation panel.

ts_conﬁg

Step 6. Read the panel and click “OK.” When the conﬁguration process is

complete, the “Conﬁguration Status” of the node changes to “Active,” as shown in Figure 14.

Chapter 2 31

Page 50

Conﬁguration management

ts_conﬁg

Figure 14 ts_config indicating Node 0 is conﬁgured

Step 7. Restart the Workspace Manager: Click the right-mouse button on the

desktop background to activate the root menu. Select the “Restart” or “Restart Workspace Manager” option, then “OK” to activate the new desktop menu.

NOTE If adding multiple nodes to the teststation, wait until the ﬁnal node is

added before restarting the Workspace Manager.

Conﬁgure the “scub_ip” address

Step 1. Select the desired node from the list of available nodes. Step 2. In the ts_config display panel, select “Actions” and then “Conﬁgure

‘scub_ip’ address,” as shown in Figure 15.

32 Chapter 2

Page 51

Conﬁguration management

Figure 15 ts_config “Conﬁgure ‘scub_ip’ address” selection

ts_config checks the scub_ip address stored in NVRAM in the node.

ts_conﬁg

If the scub_ip address is correct, no action is required. If the node is not detected and scanned by ccmd, ts_config may ask you to try again later. The ccmd detection scan process should take less than a minute.

Step 3. If prompted by ts_config (as indicated by the panel in Figure 16), click

“Yes” to correctly set the scub_ip address.

Figure 16 ts_config scub_ip address conﬁguration conﬁrmation

Step 4. A panel as the shown in Figure 17 appears conﬁrming that the scub_ip

address is set. Click OK.

Chapter 2 33

Page 52

Conﬁguration management

ts_conﬁg

Figure 17 ts_config scub_ip address set conﬁrmation panel

Initiate a node reset to activate the new scub_ip address.

Reset the Node

Step 1. Select the desired node from the list of available nodes. Step 2. Select “Actions,” then “Reset Node.” This is indicated in Figure 18.

Figure 18 ts_config “Reset Node” selection

A panel as the one shown in Figure 19 appears.

34 Chapter 2

Page 53

Figure 19 ts_config node reset panel

Conﬁguration management

ts_conﬁg

Step 3. In the Node Reset panel, select the desired “Reset Level” and “Boot

Options,” then click Reset.”

Deconﬁgure a Node

Deconﬁguring a node removes the selected node from the teststation conﬁguration. The teststation will no longer monitor the environmental and hard-error status of this node. Console access to the node is also be disabled.

Step 1. Select the desired node from the list of available nodes. Step 2. Select “Actions,” then “Deconﬁgure Node,” then click “Yes.”

Add/Conﬁgure the Terminal Mux

To add or reconﬁgure the terminal mux, perform the following procedure.

Step 1. In the ts_config display, select “Actions,” then “Conﬁgure Terminal

Mux.”

Step 2. Select “Add/Conﬁgure Terminal Mux.” This is indicated in Figure 20.

Chapter 2 35

Page 54

Conﬁguration management

ts_conﬁg

Figure 20 ts_config “Add/Conﬁgure Terminal Mux” selection.

A panel appears as the on shown Figure 21. This panel requires the terminal mux IP address.

Figure 21 ts_config terminal mux IP address panel

Step 3. Connect a serial cable from serial port 2 on the teststation to port 1 on

the terminal mux.

Step 4. Enter the desired “Terminal Mux IP Address” and click “Conﬁgure,” as

indicated in Figure 22.

36 Chapter 2

Page 55

Figure 22 Terminal mux IP address entered into panel

Remove terminal mux

ts_config does not remove the terminal mux if any node consoles are assigned to terminal mux ports.

Step 1. Select “Actions,” then “Conﬁgure Terminal Mux.”

Conﬁguration management

ts_conﬁg

Step 2. Select “Remove Terminal Mux,” then click “Yes.”

Chapter 2 37

Page 56

Conﬁguration management

Teststation-to-system communications

This section describes how the teststation communicates with the system using the utilities presented in Chapter 11, “Utilities.”

Figure 23 depicts the V-Class server to teststation communications using HP-UX.

Figure 23 Teststation-to-system communications

ccmd

event_logger

hard_logger

private ethernet

global ethernet

RS232 (tty1)

RS232 (tty0)

sppconsole

ttylink

consolelogx

LAN 1

LAN 0

console

ethernet

(JTAG)

Scan

NFS-FWCP dfdutil pcirom

ethernet

Node ethernet

LCD

DUART

console messages

console messages/LCD

Node

memlog

events

syslog

POST

/test controller

fwcp/nfs

dfdutil

pcirom

JTAG FW

HPUX

spp_pdc

OBP

teststation

modem

for

system

38 Chapter 2

Page 57

Conﬁguration management

Teststation-to-system communications

The hardware components located on the SCUB are shown in the diagram on the left side of the node or system. They include three ethernet ports and one DUART.

A layer of ﬁrmware between HP-UX and OBP called spp_pdc allows the HP-UX kernel to communicate with OBP. spp_pdc is platformdependent code and runs on top of OBP providing access to the devices and OBP conﬁguration properties.

LAN communications

One system ethernet port connects to global LAN 0. The other ethernet port connects to the system private LAN 1. The JTAG port is used for scanning. The other port is used for downloading system ﬁrmware via nfs using fwcp, via tftp using pdcfl, downloading disk ﬁrmware using dfdutil (dfdutil uses tftp for read peripheral ﬁrmware), and loading Symbios FORTH code using pcirom.

The conﬁguration deamon, ccmd, which is located on the teststation obtains system conﬁguration information.

Serial communications

The DUART port on the SCUB provides an RS232 serial link (tty 0) to the teststation. Through this port HP-UX, OBP, POST and the Test Controller send console messages. The teststation processes these message using sppconsole, ttylink, and consolelogx. POST and OBP also send system status to the LCD connected to the DUART.

Chapter 2 39

Page 58

Conﬁguration management

ccmd

ccmd builds a conﬁguration information database on the teststation. The board names and revisions, the device names and revisions, and the start-up information generated by POST are all read and stored in memory for use by other diagnostic tools.

ccmd is typically run automatically from /etc/inittab on the teststation. Entering init on the teststation starts ccmd. init monitors ccmd and

respawns it if it ever stops. Once started, ccmd becomes a daemon and allocates a block of teststation memory used for a database for all nodes, boards, and devices.

ccmd broadcasts a command to all JTAG ports to report in. Each node responds with its IP address, error status, complex identiﬁcation, and the node identiﬁcation number. ccmd continues until no new responses are detected.

Once ccmd has all valid node numbers and IP addresses, it scans each ring of each node looking for JTAG device IDs. The JTAG IDs contain device and revision information stored in the teststation database. The JTAG ID is cross checked in the /spp/data/part_ids ﬁle to retrieve a complete device description of the part. The ﬁle for the part is also in /spp/data.

After ccmd loads all parts and their descriptions into the database, it reads all board information. Board and device information is cross checked in the ﬁle /spp/data/DB_RING_FILE. Complex and node conﬁguration ﬁles for est_config is written to the /spp/data/ directory.

Once all information is in place, ccmd monitors the node for changes in node conﬁguration or error status. After a 10 second pause, ccmd once again broadcasts to determine which nodes are powered up or have an error condition. If a node response is not received after six broadcasts, then the node is removed from the database of existing nodes.

If no nodes are responding, ccmd clears all node data and continues broadcasting, waiting for a node to respond. If a node powers up, the nodes database is rebuilt.

40 Chapter 2

Page 59

Conﬁguration management

If ccmd detects a hard error, it starts the hard_logger script to extract additional information from the node through the JTAG interface. After the hard_logger runs, ccmd resets the node or complex that failed. This behavior can be stopped with autoreset.

ccmd sends output to the console. If running under X-windows as sppuser, it sends its output to the teststation console message output window. The -d debug option generates a substantial amount of console output. Output is also sent to the ﬁle /spp/data/ccmd_log.

ccmd does respond to several signals. The SIGHUP signal tells ccmd to rebuild the teststation database. A sigint or sigabort signal terminates the ccmd process.

NOTE The time zone information is read when ccmd starts. If the time zone

information changes, ccmd should be restarted as well.

ccmd

Chapter 2 41

Page 60

Conﬁguration management

xconﬁg

xconfig is the graphical tool that can also modify the parameters initialized by POST to reconﬁgure a node.

The graphical interface allows the user to see the conﬁguration state. Also the names are consistent with the hardware names, since individual conﬁguration parameters are hidden to the user. The drawback of xconfig is that it can not be used as a part of script-based tests, nor can it be used for remote debug.

xconfig is started from a shell. Information on node 0 is read and interpreted to form the starting X-windows display shown in Figure 24.

The xconﬁg window appears on the system indicated by the environmental variable $DISPLA Y. This may be overridden, however, by using the following command:

% xconfig -display system_name:0.0

The xconﬁg window has two display views: one shows each component as a physical location in the server, the other shows them as logical names. Figure 24 and Figure 25 show the window in each view, respectively. To switch between view, click on the Help button in menu bar and then click the Change names option. See “Menu bar” on page 45.

42 Chapter 2

Page 61

Figure 24 xconfig window—physical location names

Conﬁguration management

xconﬁg

Chapter 2 43

Page 62

Conﬁguration management

xconﬁg

Figure 25 xconfig window—logical names

As buttons are clicked, the item selected changes state and color. There is a legend on the screen to explain the color and status. The change is recorded in the teststation’s image of the node.

When the user is satisﬁed with the new conﬁguration, it should be copied back into the node, and the node should be reset to enable the changes.

44 Chapter 2

Page 63

Conﬁguration management

xconﬁg

The main xconfig window has three sections:

• Menu bar—Provides additional capability and functions.

• Node conﬁguration map—Provides the status of the node.

• Node control panel—Provides the capability to select a node and control the way data ﬂows to it.

Menu bar

The menu bar appears at the top of the xconfig main window. It has four menus that provide additional features:

• File menu—Displays the ﬁle and exit options.

• Memory menu—Displays the main memory and CTI cache memory options.

• Error Enable menu—Displays the device menu options for error enabling and conﬁguration.

• Help menu—Displays the help and about options.

The menu bar is shown in Figure 26.

Figure 26 xconfig window menu bar

The File menu provides the capability to save and restore node images and to exit xconfig.

The Memory menu provides the capability to enable or disable memory at the memory DIMM level by the total memory size and to change the network cache size on a multinode complex.

The Error Enable menu provides the capability to change a device’s response to an error condition. This is normally only used for troubleshooting.

The Help menu provides a help box that acts as online documentation and also contains program revision information.

Chapter 2 45

Page 64

Conﬁguration management

xconﬁg

Node conﬁguration map

The node conﬁguration map is a representation of the left and right side views of a node as shown in Figure 27.

Figure 27 xconfig window node conﬁguration map

46 Chapter 2

Page 65

Conﬁguration management

xconﬁg

The button boxes are positioned to represent the actual boards as viewed from the left and right sides. Each of the conﬁgurable components of the node is in the display. The buttons are used as follows:

• Green button—Indicates that the component is present and enabled.

• Red button—Indicates that the component is software disabled in the system.

• White button—Indicates that it is not possible to determine what the status of the component would be if POST were to be started.

• Blue box—Indicates that the component is either not present or fails the power-on self tests.

• Brown button—Indicates that POST had to hardware deconﬁgure this component in order to properly execute.

• Grey button—Indicates a hardware component that did not properly initialize.

The colors are shown in the legend box of the node control panel. Components can change from enabled to disabled or disabled to

unknown by clicking on the appropriate button with the left mouse button.

A multinode system requires an additional component on a memory board to enable the scalable coherent memory interface. This component can be viewed by right clicking the on the memory board button. The right mouse button toggles the memory board display between the memory board and the SCI device

Node control panel

The node control panel allows the user to select a node, select the stop clocks on an error function, select the boot parameters for a node and direct data ﬂow between the node and the xconfig utility. It is shown in Figure 28.

Chapter 2 47

Page 66

Conﬁguration management

xconﬁg

Figure 28 xconfig window node control panel

The node number is shown in the node box. A new number can be selected by clicking on the node box and selecting the node from the pulldown menu. A new complex can be selected by clicking on the complex box and selecting it from the pull-down. A node IP address is displayed along with the node number and complex.

48 Chapter 2

Page 67

Conﬁguration management

xconﬁg

When a new node is selected and available, its data is automatically read and the node conﬁguration map updated. The data image is kept on the teststation until it is rebuilt on the node using the Replace button. This is similar to the replace command on sppdsh.

Even though data can be rebuilt on a node, it does not become active until POST runs again and reconﬁgures the system. The Reset or Reset All buttons can be used to restart POST on one or all nodes of a system. A multinode system requires a reset all to properly function.

A Retrieve button is available on the node control panel to get a fresh copy of the parameters settings in the system. Clicking this button overwrites the setting local to the teststation and xconfig.

The Stop-on-hard button is typically used to assist in fault isolation. It stops all system clocks shortly after an error occurs. Only scan-based operations are available once system clocks have stopped.

The last group of buttons controls what happens after POST completes. The node can become idle or boot OBP, the test controller, or spsdv. The test controller and spsdv are additional diagnostic modes.

Chapter 2 49

Page 68

Conﬁguration management

Conﬁguration utilities

V2500 diagnostics provides utilities that assist the user with conﬁguration management.

autoreset

autoreset allows the user to specify whether ccmd should automatically reset a complex after a hard error and after the hard logger error analysis software has run. autoreset occurs if a .ccmd_reset ﬁle does not exist in the complex-speciﬁc directories

Arguments to autoreset arguments include <complex_name> on and <complex_name> off or chk.

The output of the chk option for a complex name of hw2a looks like:

Autoreset for hw2a is enabled.

Autoreset for hw2a is disabled.

NOTE autoreset determines the behavior of ccmd when it encounters an error

condition. ccmd makes its decision whether to reset a complex immediately after running hard_logger. Enabling autoreset after hard_logger has run does not reset the complex.

est_conﬁg

est_config is a utility that builds the node and complex descriptions used by est. est_config reads support files at /spp/data/DB_RING_FILE, reads the electronic board identifier (COP chip) and scans to completely describe the node or complex. It also uses the hardware database created by ccmd. The data retrieved is organized and sorted into an appropriate node configuration file in the /spp/data/ <complex name> directory.

An optional conﬁguration directory can be speciﬁed using the -p argument. est_config works across all nodes unless a specific node or complex is requested with the -n option.

50 Chapter 2

Page 69

Conﬁguration management

Conﬁguration utilities

NOTE If there is a node_#.pwr ﬁle that is older than the node_#.cfg ﬁle, existing

node conﬁguration ﬁles do not need to be updated. est_config also generates a complex_uts.cfg ﬁle that can be compared against a complex.cfg ﬁle for accuracy and consistency.

xsecure

xsecure is an application that helps make a V2500 class teststation secure from external sources. This tool disables modem and LAN activity to provide an extra layer of security for the V2500 system. xsecure may be run as a command line tool or an windows-based application.

In secure mode, all network LANs other than the tsdart bus are disabled and the optional modem on the second serial port will be disabled. When in normal mode all networks and modems are re-enabled.

If the command line [-on | -off | -check] options are used, xsecure does not use the GUI interface. These options allow the user to turn the secure mode on, off or allow the user to check the secure mode status

A simple button with a red or green secure mode indicator provides the user with secure mode status information. The red indicator shows that the secure mode process has begun. The label near the red button will inform the user when the test station is secure. A green indicator and the appropriate label shows that the network is available and the teststation may be accessed through the ethernet port.

In order for xsecure to work properly the teststation, console cables, terminal mux and modems must be configured in specific ways. The teststation JTAG connections, OBP connections and an optional terminal mux must all be connected to the Diagnostic LAN and identified in the / etc/hosts file as tsdart-d. The sppconsole serial cable must be connected to serial port 0 and to node 0. An optional modem may be connected to serial port 1.

Chapter 2 51

Page 70

Conﬁguration management

Conﬁguration utilities

52 Chapter 2

Page 71

3 Power-On Self Test

POST is the Power On Self Test ﬁrmware for the V-Class platform. POST provides processor and system hardware initialization functionality, as well as providing basic processor selftest and utilities board SRAM pattern test capability. This chapter describes how POST initializes a node and handles power up errors.

Chapter 3 53

Page 72

Power-On Self Test

Overview

Upon power up, all processors and hardware must be initialized before the node proceeds with booting. POST begins executing and brings up the node from an indeterminate state and then calls OBP.

None of the POST modules can be directly controlled via a user interface. Program control is provided by a set of conﬁguration parameters (processing ﬂags and variable deﬁnitions) stored in NVRAM by OBP, do_rest, or xconfig.

The error reporting modules display error codes for all fatal errors that occur during the POST execution. Any errors that can be recovered from, are reported to OBP. POST status is reﬂected on the LCD display.

POST performs the following tasks:

• Initializes and conditionally performs cache tests on each processor in the node

• Validates all shared data structures within the NVRAM.

• Initializes the core logic required to start OBP execution

• Determines node conﬁguration

• Initializes all ASICs

• Initializes main memory

• Sets up CTI cache

• Invokes OBP or the Test Controller.

Any fatal errors are reported to the user by way of the system LCD and the system console. POST passes node conﬁguration and any options to OBP via shared data structures.

Reset

The following types of reset invoke POST:

• Power up reset— If a client had execution control before the power down condition, it invokes POST to initialize the hardware. POST initializes all hardware after a power up reset.

54 Chapter 3

Page 73

Power-On Self Test

Overview

• Hard reset—If a client had execution control before the hard reset, it invokes POST to initialize the hardware. POST restarts execution and reinitializes all hardware.

• Soft reset—If a soft reset condition has occurred while POST was executing, POST restarts execution but does not initialize main memory. It invokdes its interactive prompt.

Chapter 3 55

Page 74

Power-On Self Test

POST modules

POST executes modules listed below in chronological order:

• Processor Initialization and Selftest—Each processor initializes itself on power up or reset in parallel with the other processors. Initialization includes setting values into the internal diagnostic registers, initializing the instruction and data caches, clearing a scratch ram area for stack and data storage, and enabling highpriority machine checks (HPMC), low-priority machine checks (LPMC), and transfer of control (TOC). Selftest includes instruction set tests, instruction and data cache RAM tests and TLB RAM tests.

• SCUB Hardware Initialization—POST clears any error state in the SCUB, initializes the SCUB hardware registers and DUART, and initializes and optionally tests the SRAM on the SCUB (see scuba_test_enable).

• Non-volatile Conﬁguration Data Veriﬁcation—POST veriﬁes the checksum of all shared data regions in a battery-backed-up SRAM (NVRAM). POST veriﬁes only the regions it shares with other modules, such as OBP, and those private to POST. If a region fails, it is rebuilt using default values.

• Hardware Conﬁguration Determination—POST determines the ASIC installations status and veriﬁes that each installed ASIC responds to register accesses. If one does not, it is reported as failing. POST then conﬁgures the system to utilize the maximum amount of installed hardware based on the V2500 hardware conﬁguration rules.

• Node Hardware (ASIC) Initialization—POST sets up all available hardware with the proper operating mode(s) enabled. Routing is conﬁgured for the current hardware population.

• Node Main Memory Initialization—POST probes all installed memory boards for memory installation status. It then enables each memory board as a 2-, 4-, or 8-board conﬁguration based on V2500 conﬁguration rules. All remaining memory boards are conﬁgured to have the same logical memory population. It then initializes main memory in parallel, using up to eight processors using initialization hardware in the memory controllers.

56 Chapter 3

Page 75

Power-On Self Test

POST modules

• Page Deallocation Table Support—POST supports reading the page deallocation table (PDT) and remapping memory if it detects a bad page in the HPUX good-memory region. It updates all entries to reﬂect the new memory layout if remapping occurs. It also clears PDT if memory hardware change is detected.

• Client Boot—POST cleans up any residual state from POST execution and boots the client speciﬁed in boot_module. POST can boot clients with all processors or with just with the monarch processor leaving the other processors in an idle loop.

Chapter 3 57

Page 76

Power-On Self Test

Interactive mode

POST for the V2500 provides a command line interface for conﬁguration and debugging. The command line interface is invoked if boot_module is set to “interactive,” by a soft reset, or a TOC during POST execution.

Interactive mode commands

POST supports the following commands at the line prompt:

• help—Displays a list of supported commands and their usage.

• banner—Displays the POST version and build information.

• reset [loader|post|soft]—Causes POST to perform a reset of the node. If loader is speciﬁed, then the node is hard reset and executes the ﬁrmware loader PDCFL. If post is speciﬁed, the node is hard reset and executes POST. If soft is speciﬁed, the node is soft reset and executes POST.

• dcm—Dumps the configuration map from NVRAM and display the hardware status of the machine, showing what hardware is enabled, deconfigured, or failing.

• setenv <parm> <value>—Sets the configuration parameter specified by parm to the value.

• printenv [parm]—Prints the value of the configuration parameter specified by parm. If no parameter is specified, then all are printed.

• get_opt [asic_type [asic_number]]—Dumps the option mode bits for the ASIC type specified by asic_type. If an asic_number is also specified, then only the values of the ASIC are printed. If an asic_number is not specified, then all ASICs of that asic_type are dumped. If no asic_type is speciﬁed, then all ASICs are dumped.

• pdt—Dumps the current Page Deallocation Table (PDT) contents.

• clear_pdt—Clears out all entries in the PDT.

• memmap—Displays any rows that have been logically remapped due to PDT entries or failing software-deconﬁgured DIMMs.

58 Chapter 3

Page 77

Conﬁguration parameters

The following parameters control the runtime operation of POST:

• ts_ip—Speciﬁes the teststation IP address for LAN messaging. The value should be set to the IP address of the diagnostics LAN port on the teststation. [default: 15.99.111.99]

Table 7 Name of teststation IP address for listed utilities

Utility Parameter name

OBP ts-ip# POST ts_ip sppdsh ts_ip

• scub_ip—Speciﬁes the IP address used for LAN interface hardware on the utilities (SCUB) board. This is the IP address that POST, OBP, and the Test Controller use for LAN messaging with the teststation. [default: none]

Power-On Self Test

Interactive mode

Table 8 Name of scub IP address for listed utilities

Utility Parameter name

OBP obp-ip# POST scub-ip

sppdsh scub_ip ts_config scub_ip

• cti_cache_size—Speciﬁes the amount of memory, in megabytes, to reserve in the node for CTI cache. This is used only in multinode conﬁgurations. [default: 0 Mbytes]

Chapter 3 59

Page 78

Power-On Self Test

Interactive mode

Table 9 Name of CTI cache size IP address for listed utilities

Utility Parameter name

OBP cti-cache-size POST cti_cache_size sppdsh cti_cache_size

• boot_module—Speciﬁes which client to turn execution control over to at the completion of POST execution. [default: OBP]

Table 10 Name of boot module for listed utilities

Utility Parameter name

OBP boot-module POST boot_module sppdsh boot_module

• selftest_enable—Enables selftest control if the processor selftest is executed during POST start-up execution. [default: true]

Table 11 Name of selftest enable for listed utilities

Utility Parameter name

OBP selftest? POST selftest_enable sppdsh selftest_enable

• scuba_test_enable—Enables Scuba test control if the SCUB SRAM is tested before initialization. This affects the processor initialization, since processors test and initialize their own stack region. It also affects the SCUB initialization and core LAN SRAM initialization steps for the monarch. [default: true]

60 Chapter 3

Page 79

Table 12 Name of scuba test enable for listed utilities

Utility Parameter name

OBP scubatest? POST scuba_test_enable sppdsh scuba_test_enable

• master_error_enable—Determines whether POST will enable errors or not. This is used in conjunction with use_error_overrides to determine how errors are enabled. [default: true]

Table 13 Name of master error enable for listed utilities

Utility Parameter name

OBP master-error-enable? POST master_error_enable

Power-On Self Test

Interactive mode

sppdsh master_error_enable

• use_error_overrides—Determines if POST will use the built-in defaults for errors or the user error overrides. This is only checked if master_error_enable is enabled. [default: false]

Table 14 Name of use error overides for listed utilities

Utility Parameter name

OBP use-error-overrides? POST use_error_overrides sppdsh use_error_overrides

• force_monarch—Determines if POST will force the monarch selection to a specific processor. The processor is specified in monarch_number [default: false]

Chapter 3 61

Page 80

Power-On Self Test

Interactive mode

Table 15 Name of sforce monarch for listed utilities

Utility Parameter name

OBP force-monarch? POST force_monarch sppdsh force_monarch

• monarch_number—Specifies the monarch processor when force_monarch is enabled. [default: 0]

Table 16 Name of monarch number for listed utilities

Utility Parameter name

OBP monarch# POST monarch_number sppdsh monarch_number

62 Chapter 3

Page 81

Messages

POST has three types of messages: LCD, console, and error. This section discusses each type.

LCD messages

Each node has an LCD display. Figure 29 shows the display and indicates what each line on the display means.

Figure 29 Front panel LCD

Power-On Self Test

Messages

0 (0,0)

MIII IIII IIII IIII

IIII IIII IIII IIII abcedfghijklr

Node status line

The Node Status Line shows the physical node ID in both decimal and X, Y topology formats.

Processor status line

The processor status line shows the current run state for each processor in the node. Table 17 shows the initialization step code deﬁnitions and Table 18 shows the run-time status codes. The M in the ﬁrst processor status line stands for the monarch processor.

Node status line Processor status line—lower 16

Processor status line—upper 16

Message display line

Chapter 3 63

Page 82

Power-On Self Test

Messages

Table 17 Processor initialization steps

Step Description

0 Processor internal diagnostic register initialization 1 Processor early data cache initialization. 2 Processor stack SRAM test.(optional) 3 Processor stack SRAM initialization. 4 Processor BIST-based instruction cache initialization. 5 Processor BIST-based data cache initialization 6 Processor internal register ﬁnal initialization. 7 Processor basic instruction set testing. (optional) 8 Processor basic instruction cache testing. (optional) 9 Processor basic data cache testing. (optional) a Processor basic TLB testing (optional) b Processor post-selftest internal register cleanup. (optional)

Table 18 Processor run-time status codes

Status Description

R RUN: Performing system initialization operations.

I IDLE: Processor is in an idle loop, awaiting a command. M MONARCH: The main POST initialization processor. H HPMC: processor has detected a high priority machine check

(HPMC). T TOC: processor has detected a transfer of control (TOC). S SOFT_RESET: processor has detected a soft RESET. D DEAD: processor has failed initialization or selftest.

64 Chapter 3

Page 83

Status Description

d DECONFIG: processor has been deconﬁgured by POST or the user.

- EMPTY: Empty processor slot.

? UNKNOWN: processor slot status in unknown.

Message display line

The message display line shows the POST initialization progress. This is updated by the monarch processor. The system console also shows detail for some of these steps. Table 19 shows the code definitions.

Table 19 Message display line

Message display code Description

a Utilities board (SCUB) hardware initialization. b Processor initialization/selftest rendezvous.

Power-On Self Test

Messages

c Utilities board (SCUB) SRAM test. (optional) d Utilities board (SCUB) SRAM initialization. e Reading Node ID and serial number.

f Verifying non-volatile RAM (NVRAM) data structures. g Probing system hardware (ASICs). h Initializing system hardware (ASICs).

i Probing processors.

j Initialing, and optionally testing, remaining SCUB SRAM. k Probing main memory.

l Initializing main memory. r Enabling system error hardware.

Chapter 3 65

Page 84

Power-On Self Test

Messages

Console messages

POST provides several messages that are displayed on the teststation console. This section describes these console messages.

Type-of-boot

This message reports the type of boot for the current POST execution, and the node ID and monarch processor.

For example:

POST Hard Boot on [0:PB1R_A]

Version and build

This message reports the version and build information for POST.

For example:

HP9000/V2500 POST Release 1.0, compiled 1998/11/04 14:33:12

Processor probe

This message reports the processors as they are detected in the system. Only available processors are reported; any failing or deconfigured processors are not listed. Processors in this list may be deconfigured if they share a Runway bus with a processors that fails the probe or is deconfigured.

For example:

Probing CPUs: PB0L_A PB0R_A PB1R_A PB1L_A PB2L_A PB2R_A PB3R_A PB3L_A PB4L_A PB4R_A PB5R_A PB5L_A PB6L_A PB6R_A PB7R_A PB7L_A PB0L_B PB0R_B PB1R_B PB1L_B PB2L_B PB2R_B PB3R_B PB3L_B PB4L_B PB4R_B PB5R_B PB5L_B PB6L_B PB6R_B PB7R_B PB7L_B

Utility board initialization

This message reports that the Utilities board SRAM reserved for missing or unavailable CPUs is being initialized. The SRAM is tested prior to initialization if scuba_test_enable is true.

For example:

Completing core logic SRAM initialization.

66 Chapter 3

Page 85

Power-On Self Test

Messages

Main memory initialization

This message reports that main memory initialization has started.

For example:

Starting main memory initialization.

Memory probe

This message reports the status of the memory boards as they are detected and probed for DIMMs

For example:

Probing memory: MB0L MB1L MB2R MB3R MB4L MB5L MB6R MB7R

Installed memory

This message reports the total memory installed and available, in megabytes.

For example:

Installed memory: 2048 MBs, available memory: 2048 MBs

Main memory initialization started

This message marks the beginning of main memory initialization.

For example:

Initializing main memory.

Parallel memory initialization

This message reports that main memory initialization will be done with multiple processors in parallel. Only printed if more than one processor is available for memory initialization.

For example:

Parallel memory initialization in progress.

Memory initialization progress

This message reports the results of the initialization, the initializing processor, and the memory board for each board available in the node.

Chapter 3 67

Page 86

Power-On Self Test

Messages

Each character indicates the physical location of the DIMM and the logical size of the DIMM. The memory information is encoded as follows: Value Memory Type

. 32MB : 64MB | 128MB _ Empty # Hardware deconﬁgured $ Software (user) deconﬁgured

For example:

r0 r1 r2 r3

PB0L_A MB0L [.... ....][.... ....][____ ____][____ ____]

PB1R_A MB1L [.... ....][.... ....][____ ____][____ ____]

PB2L_A MB2R [.... ....][.... ....][____ ____][____ ____]

PB3R_A MB3R [.... ....][.... ....][____ ____][____ ____]

PB4L_A MB4L [.... ....][.... ....][____ ____][____ ____]

PB5R_A MB5L [.... ....][.... ....][____ ____][____ ____]

PB6L_A MB6R [.... ....][.... ....][____ ____][____ ____]

PB7R_A MB7R [.... ....][.... ....][____ ____][____ ____]

Main memory initialization complete

This message indicates that a main memory initialization is complete.

For example:

Main memory initialization complete.

System control to boot client

This message indicates that system control is being handed off to the specified boot client.

For example, one of the following:

Booting OBP Booting DIAG Booting SPSDV Booting RDR dumper

68 Chapter 3

Page 87

Power-On Self Test

Messages

Booting Boombox

Interactive boot

This message indicates that POST is entering it's interactive mode. POST provides a console interface for system configuration and debug.

For example:

Booting Interactive

Interactive prompt

The following is the POST interactive prompt and is only seen if boot_module is set to interactive.

For example:

[node id 0:monarch] POST>

Chassis codes

The processor initialization and selftest functions in POST report status and error information with chassis codes. These chassis codes are shared with cpu3000 and are documented in the man page with the exception of the following POST-specific codes:

0x6103C The processor is executing it's processor initialization

code

0x22025 The processor encountered a data error while loading

the processor Icache

0x22026 The processor encountered a tag error while loading

the processor Icache.

Error messages

POST provides error message that are printed to the console. This section describes these error message

Teststation parameters failure

This message reports the that test station parameters structure failed

Chapter 3 69

Page 88

Power-On Self Test

Messages

the checksum and was rebuilt to the default structure.

For example:

Test Station Parameters checksum FAILED, rebuilding...

This node may be forced with the sppdsh reboot <node> default command

Conﬁguration map failure

This message indicates that the conﬁguration map structure failed the checksum and was rebuilt to defaults. Any user deconﬁgured hardware state is lost.

For example:

Configuration Map checksum FAILED, rebuilding...

Conﬁguration map failure

This message indicates that the conﬁguration parameters structure failed the checksum and was rebuilt to the default structure. Any user overrides from the default value, for parameters that have a default, is lost. Some parameters have no default and retain the value in NVRAM. Since NVRAM could be corrupt, these values could be invalid.

For example:

Configuration Parameters checksum FAILED, rebuilding...

ASIC probe failure

This message indicates that the speciﬁed ASIC failed the probe. The status of any components that must be accessed through this component are unknown, and they are be available if installed.

For example:

Failed probe of P1R. Unable to determine status of PB1R_A PB1L_A PB1L_B PB1L_A IOLR_B.

70 Chapter 3

Page 89

Power-On Self Test

Messages

Memory board deconﬁguration

This message indicates that the speciﬁed memory board is deconﬁgured. This can be due to a memory board being found on one side of memory without a corresponding pair, since boards must be used in pairs of even/ odd boards. This can also occur when a memory board has no usable memory.

For example:

Deconﬁguring: MB5L

Illegal memory board conﬁguration

This message indicates that there is an unallowed memory board configuration. Memory boards can only be used in two-, four-, or eightboard conﬁgurations. In the following example, a six-board conﬁguration was detected, and two boards will be deconﬁgured.

For example:

Illegal 6 memory board configuration.

Memory remap

This message indicates that the speciﬁed physical row was mapped to the indicated logical row. This is done to accommodate either improperly installed DIMMs or when DIMMs in lower rows are not usable. This can occur when a DIMM is bad or when memory boards contain differing memory populations.

For example:

MB0L: Physical Row:2 mapped to Logical Row:0

Processor initialization failure

This message indicates that the speciﬁed processor failed to perform the step described during parallel main memory initialization. The monarch processor completes the initialization assigned the failing processor.

For example:

PB1R_A timed out during encache memory init code PB1R_A timed out during memory initialization PB1R_A timed out during idle request after memory init

Chapter 3 71

Page 90

Power-On Self Test

Messages

PB0L_B failed to go idle after memory init Unable to force CPU PB2L_A into idle loop

Monarch completing memory initialization

This message indicates that the monarch processor is completing the memory initialization assigned to the speciﬁed processor.

For example:

Using Monarch to initialize memory assigned to PB2L_A

PDT checksum failure

This message indicates that the page deallocation table structure failed the checksum and was rebuilt to defaults. All bad page information is lost.

For example:

Page Deallocation Table (PDT) checksum FAILED, rebuilding...

Memory hardware change detected

This message indicates that POST detected a change in memory hardware and cleared all entries in the PDT.

For example:

Detected a hardware change, clearing the Page Deallocation Table (PDT).

Memory remapped

This message indicates that POST remapped memory to achieve HP-UX good memory region. This occurs when a bad page is marked within the good memory region.

For example:

Memory was re-mapped to achieve HP/UX good memory region.

72 Chapter 3

Page 91

Power-On Self Test

Messages

Contiguous memory block not found

This message indicates that POST could not ﬁnd a block of contiguous memory to place at address zero to achieve good memory. POST will report no main memory to the OBP for this failure.

For example:

HP/UX good memory region could not be achieved.

Processor not reported

This message indicates that a processor failed to mark itself in the system report register. Reporting happens early in the sequence, and this failure usually indicates the processor has failed to execute any instructions.

For example:

Failed probe of PB1R_B, CPU failed to report in.

Processor initialization/selftest failure

This message indicates that a processor failed at some point during initialization or selftest. The chassis code for the module that failed is reported.

For example:

Failed probe of PB1R_B chassis code 0x6103C

Processor not responding to interrupt

This message indicates that a processor properly initialized itself but did not respond to an external interrupt

For example:

Failed probe of PB1R_B cpu PB1R_B did not respond to an interrupt

Shared Runway bus failure

This message indicates that an available processor has been deconﬁgured because it shares a Runway bus with a processor that failed to probe

Chapter 3 73

Page 92

Power-On Self Test

Messages

For example:

cpu PB1R_A deconfigured due to PB1R_B shutdown.

New monarch processor selected

This message indicates that the previous monarch processor was deconﬁgured and a new one was selected. The new monarch continues the initialization of the rest of the system

For example:

INFO: New monarch selected: PB0R_A

New monarch processor not found

This message indicates that the other processor on the Runway bus with the monarch processor was deconﬁgured or failed and another suitable processor could not be found to replace the monarch.

For example:

WARNING: The monarch shares a Runway bus with a failed cpu.

74 Chapter 3

Page 93

4 Test Controller

The Test Controller is an EEPROM-based utility that provides the environment for executing the ofﬂine diagnostic tests. It is controlled through parameters stored in the NVRAM on the Utilities board. The Test Controller reads these parameters to determine its execution mode , the number processors to test, which SMACs to include in the testing, which subtests to run, and other diagnostic test-speciﬁc information.

Chapter 4 75

Page 94

Test Controller

Test Controller modes

There are three basic operational modes for this utility:

• Stand-alone mode

• Interactive mode

• I/O Utility mode In stand-alone mode, cxtest invokes the Test Controller. The Test

Controller reads test parameters from NVRAM (these parameters are written into NVRAM by cxtest before it invokes the Test Controller), executes the test and subtests speciﬁed in NVRAM, and sets a completion bit in NVRAM when the test and subtests are ﬁnished. cxtest is described in Chapter 5.

In interactive mode, a user interface allows the user to select the processors to test, select the subtests to run, and examine error information. The user interface is a set of menus described in this chapter.

In the interactive mode, the Test Controller loops waiting for the start command. Prior to issuing the start command, any global and/or processor speciﬁc parameters can be modiﬁed. When all tests have completed, the Test Controller waits for the next start command. Any combination of parameter and tests may be modiﬁed and executed.

In I/O Utility mode, the Test Controller will load, and subsequenty exectue, a ﬁrmware utility module from the test station. There are currently two support utility modules: arrm and dfdutil. The teststation utility tc_ioutil identiﬁes the utility module to be loaded. tc_ioutil updates an NVRAM location with the ﬁle name of the utility module to be loaded. See tc_ioutil, arrm and dfdutil in Chapter 11, “Utilities,” or more details.

An example of tc_ioutil would be:

tc_ioutil <node> dfdutil.fw

76 Chapter 4

Page 95

Test Controller

User interface

The Test Controller provides for the control of ofﬂine diagnostic test execution. It utilizes a set of parameters to control its operation. The parameters consist of the following:

• Global set that controls the overall operation of the Test Controller

• Test set (one per test) that controls how the tests are executed by the Test Controller

• CPU parameters (one per processor) that contain status information about the tests executing on each processor

All these parameters are in NVRAM. The user interface allows the user to modify parameters that reside in

NVRAM, thereby controlling the operation of the Test Controller. It also allows the user to select which subtests are executed on each of the processors and modify the test parameters, as well as any other test information.

The Test Controller user interface consists of two basic menus. The ﬁrst is the main menu that gives the user the following capabilities:

• Modify the POST boot selection

• Control operation of the Test Controller

• Display the current global parameter selections

• Display processor summary

• Switch processors

• Go to the Test Conﬁguration menu

The second menu is the processor Test Control menu that provides the following capabilities:

• Select classes of subtests to execute

• Select subtests to execute

• Specify pause enables

• Specify whether or not to loop

• Specify the test and/or subtest error counts

Chapter 4 77

Page 96

Test Controller

User interface

• Read and write the 128 words of test speciﬁc information

• Select the hardware to test

• Display the current parameter selections

Main menu

Test Controller Main Menu

MAIN Menu commands

0=Quit Test Controller 1=Begin Test Controller Execution 2=Halt Test Controller Execution 3=Resume Test Controller Execution 4=Switch CPU 5=POST Boot Selection 6=Execution Mode Selection 7=Global Parameter Display 8=CPU Summary Display 9=Display CPU Errors A=Test Selection Menu B=Test Configuration Menu C=Debugging Menu D=Display revision

Enter Command:

Each main menu selection is deﬁned as follows:

• 0=Quit Test Controller—Terminates the Test Controller utility and either reboots the system (to POST and then to the selected program) or halts the system depending on the current value of the POST Boot Selection ﬂag.

• 1=Begin Test Controller Execution—Starts the Test Controller utility executing the speciﬁed subtests on the selected processors. The entire system is started from the beginning.

• 2=Halt Test Controller Execution—Suspends temporarily the operation of the Test Controller. This command may be entered at any time. Only the Test Controller is halted; subtests on other processors continue to execute.

78 Chapter 4

Page 97

Test Controller

User interface

• 3=Resume Test Controller Execution—Continues execution from the point of interruption.

• 4=Switch CPU—Allows the user to start the Test Controller on the speciﬁed processor. The previously used processor starts executing the command wait loop code. The user is prompted for the processor as follows:

Enter CPU (0-1f):

• 5=POST Boot Selection—Prompts the user for the new value with the following prompt:

Boot Option (1=OBP, 2=TC Interactive, 3=TC Standalone 4=Loader, 5=SPSDV, 6=RDR Dumper, 7=Boombox, 8=POST Interactive):

For all values, POST boots to ESPDV. The Test Controller performs a hard reset to POST when the Test Controller terminates.

• 6=Execution Mode Selection—Allows the user to select the mode for executing the subtests. The two options are serial and parallel. The following prompt queries for the selection:

Execution Mode Selection (0=serial, 1=parallel):

• 7=Global Parameter Display—Displays the available hardware components, the current “POST Boot Selection” value, and the current “Execution Mode Selection” value. The display is shown below:

Example Global Parameter display

Enter command: 7 MAIN Menu - Global Parameters Display

CPUs: 0* 1* 2* 3* 4* 5* 6* 7* 8* 9* A* B* C* D* E* F* 10*11*12*13*14*15 16*17*18*19*1A*1B*1C*1D 1E*1F

SPACs: 0* 1* 2* 3* 4* 5* 6* 7* SMACs: 0* 1* 2 3 4 5 6* 7* STACs: 0 1 2 3 4 5 6 7 SAGAs: 0 1* 2 3 4 5* 6 7 Execution Mode Selection: Serial Parallel* POST Boot Selection: TC Interactive

The asterisks denote the component has passed POST processing and is available for diagnostic testing (see processors 0-3 and SMACs 0, 2, 4, and 6 in the display).

Chapter 4 79

Page 98

Test Controller

User interface

• 8=CPU Summary display—Displays a summary of the current processor and testing information. An example of the display is shown below:

80 Chapter 4

Page 99

Example CPU summary display

MAIN Menu - CPU Summary Display Total Failures = 0 Configuration Map ================= CPUs : 0 1 2 3* 4 5 6 7 8 9 10 11 12 13 14 15 CPUs : 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 SPACs : 0* 1* 2* 3* 4* 5* 6* 7* SMACs : 0* 1* 2 3 4 5 6 7 STACs : 0 1 2 3 4 5 6 7 SAGAs : 0* 1 2 3 4* 5 6 7

FAIL CPU STATE COUNT SUBTEST TEST NAME === ===== ===== ======= ========= 0 Not Available n/a n/a n/a 1 Not Available n/a n/a n/a 2 Not Available n/a n/a n/a 3 Idle n/a n/a n/a 4 Not Available n/a n/a n/a 5 Not Available n/a n/a n/a 6 Not Available n/a n/a n/a 7 Not Available n/a n/a n/a 8 Not Available n/a n/a n/a 9 Not Available n/a n/a n/a 10 Not Available n/a n/a n/a 11 Not Available n/a n/a n/a 12 Not Available n/a n/a n/a 13 Not Available n/a n/a n/a 14 Not Available n/a n/a n/a 15 Not Available n/a n/a n/a 16 Not Available n/a n/a n/a 17 Not Available n/a n/a n/a 18 Not Available n/a n/a n/a 19 Not Available n/a n/a n/a 20 Not Available n/a n/a n/a 21 Not Available n/a n/a n/a 22 Not Available n/a n/a n/a 23 Idle n/a n/a n/a 24 Idle n/a n/a n/a 25 Not Available n/a n/a n/a 26 Not Available n/a n/a n/a 27 Not Available n/a n/a n/a 28 Not Available n/a n/a n/a 29 Not Available n/a n/a n/a 30 Not Available n/a n/a n/a 31 Not Available n/a n/a n/a Hit <ENTER> key to return to the MAIN Menu:

Test Controller

User interface

Each available hardware component is marked with an asterisk just to the right of its number (see processors 0-3 and SMACs 0, 2, 4, and 6 in the display).

Chapter 4 81

Page 100

Test Controller

User interface

The possible states in the CPU Summary Display are described in Table

20.

Table 20 Processor States

CPU State Description

Not Available Denotes processor is not available for testing. Running Denotes a test is currently running on this

Idle Denotes that no test is running on this processor. Ready Denotes last subtest completed and ready for

Test Completed Denotes test completed execution on this

Error Detected Denotes test halted due to an error condition on

processor.

next subtest.

processor.

this processor.

Test Timeout Denotes a timeout detected during test execution

on this processor; the test is halted.

HW Reqs Not Met Denotes the hardware selected does not meet the

minimum hardware required for executing the

test. User Halted Denotes user halted test. Unexpected

HPMC SW Deconﬁgured Denotes test automatically halted testing on this

• 9=Display CPU Errors—Displays the errors for the currently selected processor. When selected, the user is prompted for the processor as follows:

Enter CPU [0-1f]:

82 Chapter 4

Denotes running test caused an HPMC; the test is halted.

processor, because of a software restriction.