Op er a t or ’s Gu id e
HP 9000 V2500/V2600 SCA Ser ver
Fir st Ed ition
A5845-96001
Cu st om er Or d er Nu m ber : A5845-90001
J u ly 1999
Printed in: USA
Download from Www.Somanuals.com. All Manuals Search And Download.
Con ten t s
P r efa ce . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Notational conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Safety and regulatory information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Safety in material handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
USA radio frequency interference FCC Notice . . . . . . . . . . . . . . . . . . xvi
Japanese radio frequency interference VCCI . . . . . . . . . . . . . . . . . . xvii
EMI statement (European Union only). . . . . . . . . . . . . . . . . . . . . . . xvii
Digital apparatus statement (Canada) . . . . . . . . . . . . . . . . . . . . . . . xvii
BCIQ (Taiwan) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Acoustics (Germany). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
IT power system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
High leakage current . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
Installation conditions (U.S.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Fuse cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Associated documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xx
Technical assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Reader feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii
1
Over view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
V-Class System Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
The Service Support Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Server Console and Diagnostic Connections . . . . . . . . . . . . . . . . . . . .4
V-Class Server Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
V2500/V2600 Crossbar Interconnection . . . . . . . . . . . . . . . . . . . . . . . . .6
V2500/V2600 Cabinet Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Core Utilities Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Input/Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Multiple-Cabinet Server Connections . . . . . . . . . . . . . . . . . . . . . . . . . .15
V2500/V2600 Cabinet Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . .18
2
In d ica t or s, sw it ch es, a n d d isp la ys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Operator panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Key switch panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Key switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
DC ON LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
TOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Table of Contents
iii
Download from Www.Somanuals.com. All Manuals Search And Download.
DVD-ROM drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Disk loading slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Busy indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Eject button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Optional DAT drive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Eject button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
System Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
LCD (Liquid Crystal Display) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Node status line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Processor status line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Message display line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Attention light bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Environmental errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3
SSP op er a t ion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
SSP and the V-Class system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
SSP log-on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
SSP sppuser windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Message window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Console window (sppconsole - complex console). . . . . . . . . . . . . . . . 40
Console window (sppconsole - Node X console) . . . . . . . . . . . . . . . . 40
Console bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
ksh shell windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Using the CDE (Common Desktop Environment) Workspace menu . . 41
CDE Workspace menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Using the console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Creating new console windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Starting the console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Starting the console from the Workspace menu . . . . . . . . . . . . . . . 46
Starting the console using the sppconsole command. . . . . . . . . . . . 46
Starting the console using ts_config . . . . . . . . . . . . . . . . . . . . . . . . . 47
Starting the console using the consolebar . . . . . . . . . . . . . . . . . . . . 48
Starting the console by logging back on . . . . . . . . . . . . . . . . . . . . . . 49
Console commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Watching the console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Assuming control of the console . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Changing a console connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Accessing system logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
The set_complex command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Targeting commands to nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
SSP file system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
/spp/etc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
iv
Table of Contents
Download from Www.Somanuals.com. All Manuals Search And Download.
/spp/bin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
/spp/scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
/spp/data/complex_name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
/spp/firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
/spp/est . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
/spp/man . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
Device files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
System log pathnames. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58
4
F ir m w a r e (OBP a n d P DC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Boot sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Boot process output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62
HP mode boot menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
Enabling Autoboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
HElp command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
5
Con figu r a tion u t ilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
ts_config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Starting ts_config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
ts_config operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Configuration procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
Upgrade J TAG firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
Configure a Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77
Configure the scub_ip address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Reset the Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
Deconfigure a Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84
Add/Configure the Terminal Mux . . . . . . . . . . . . . . . . . . . . . . . . . . .84
Remove terminal mux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
Console sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
V2500/V2600 SCA (multinode) configuration . . . . . . . . . . . . . . . . . . . .87
V2500/V2600 split SCA configuration . . . . . . . . . . . . . . . . . . . . . . . . . .92
ts_config files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
SSP-to-system communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
LAN communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98
SSP host name and IP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98
Serial communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
ccmd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100
xconfig . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102
Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
Table of Contents
v
Download from Www.Somanuals.com. All Manuals Search And Download.
Node configuration map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Node control panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Configuration utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
autoreset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
est_config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
report_cfg. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Effects of hardware and software deconfiguration . . . . . . . . . . . . 112
report_cfg summary report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
report_cfg ASIC report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
report_cfg I/O report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
report_cfg memory report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
report_cfg processor report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
xsecure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
6
HP -UX Op er a tin g System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
HP-UX on the V2500/V2600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Displaying System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Listing the Server Hardware Configuration . . . . . . . . . . . . . . . . . 118
Configuring HP-UX for V-Class Servers . . . . . . . . . . . . . . . . . . . . . . 120
HP-UX parameter sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Multiple-cabinet kernel configurations . . . . . . . . . . . . . . . . . . . . . 121
Process and Thread “Gang Scheduling”. . . . . . . . . . . . . . . . . . . . . . . 122
HP-UX 11.10 SCA Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
HP-UX SCA Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Starting HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Power-On Sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Boot variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Reviewing the state of the file system . . . . . . . . . . . . . . . . . . . . . . . . 128
Stopping HP-UX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Shutdown considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Rebooting the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Shutting down the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Resetting the V2500/V2600 server hardware . . . . . . . . . . . . . . . . . . 134
7
Recover in g fr om fa ilu r es . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Collecting information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Performance problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
System hangs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
System panics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Peripheral problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Interface card and system problem . . . . . . . . . . . . . . . . . . . . . . . . . . 143
File system problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
LAN communication problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
vi
Table of Contents
Download from Www.Somanuals.com. All Manuals Search And Download.
Logical Volume Manager (LVM) related problem . . . . . . . . . . . . . . . .145
Recovery from other situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145
Rebooting the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146
Monitoring the system after a system panic. . . . . . . . . . . . . . . . . . . .146
Abnormal system shutdowns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147
Fast dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147
Overview of the dump and save cycle . . . . . . . . . . . . . . . . . . . . . . . . .148
Crash dump destination and contents . . . . . . . . . . . . . . . . . . . . . . . .148
New SCA-Extended Crash Dump Format . . . . . . . . . . . . . . . . . . . .149
Memory Dumped on V2500/V2600 SCA Servers. . . . . . . . . . . . . . .149
Configuration criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150
System recovery time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150
Crash information integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152
Disk space needs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154
Defining dump devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155
Kernel dump device definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . .156
Runtime dump device definitions. . . . . . . . . . . . . . . . . . . . . . . . . . .158
Dump order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160
What happens when the system crashes?. . . . . . . . . . . . . . . . . . . . . .160
Operator override options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161
The dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161
The reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162
What to do after the system has rebooted?. . . . . . . . . . . . . . . . . . . . .162
Using crashutil to complete the saving of a dump . . . . . . . . . . . . .163
Crash dump format conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . .163
Analyzing crash dumps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164
Ap p en d ix A: LED cod es . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Power on detected errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166
CUB detected memory power fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171
CUB detected processor error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172
CUB detected I/O error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173
CUB detected fan error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174
CUB detected ambient air errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175
CUB detected hard error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176
CUB detected intake ambient air error . . . . . . . . . . . . . . . . . . . . . . . . .177
CUB detected dc error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178
Table of Contents
vii
Download from Www.Somanuals.com. All Manuals Search And Download.
viii
Table of Contents
Download from Www.Somanuals.com. All Manuals Search And Download.
F igu r es
Figure 1
Figure 2
Figure 3
Figure 4
Figure 5
Figure 6
Figure 7
Figure 8
J apanese radio frequency notice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
BCIQ (Taiwan). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
V-Class Server Components: Cabinet and Service Support Processor . . . . . . . .2
Four-Cabinet V2500/V2600 Server Components . . . . . . . . . . . . . . . . . . . . . . . . .3
Console and Diagnostic Connections for a Four-Cabinet V2500/V2600 Server .5
Functional Diagram of a Single-Cabinet V2500/V2600 Server . . . . . . . . . . . . .7
V2500/V2600 HyperPlane Crossbar Connections . . . . . . . . . . . . . . . . . . . . . . . .8
Conceptual Overview of V2500/V2600 Memory Board . . . . . . . . . . . . . . . . . . .10
Numbering and Locations of Single-Cabinet V2500/V2600 PCI I/O . . . . . . . .13
Numbering and Locations of Multiple-Cabinet V2500/V2600 PCI I/O . . . . . .14
Four-Cabinet V2500/V2600 Server CTI Cable Connections . . . . . . . . . . . . . . .16
Sample V2500/V2600 Cabinet Configurations . . . . . . . . . . . . . . . . . . . . . . . . .19
Operator panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Key switch panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
DVD-ROM drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
DDS-3 DAT drive front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
System displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Front panel LCD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
SSP user windows for V2500/V2600 servers with one node . . . . . . . . . . . . . . .38
SSP user windows for V2500/V2600 servers with more than two nodes . . . . .39
SSP Workspace submenus for V2500/V2600 . . . . . . . . . . . . . . . . . . . . . . . . . . .42
SSP Workspace submenus for V2500/V2600 . . . . . . . . . . . . . . . . . . . . . . . . . . .42
SSP file system for V2500/V2600 servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Boot process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
ts_configsample display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
ts_configshowing node 0 highlighted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76
ts_config“Upgrade J TAG firmware” selection.. . . . . . . . . . . . . . . . . . . . . . .76
Upgrade J TAG firmware confirmation panel . . . . . . . . . . . . . . . . . . . . . . . . . .77
ts_configpower-cycle panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77
ts_configindicating Node 0 as not configured. . . . . . . . . . . . . . . . . . . . . . . .78
ts_config“Configure Node” selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
ts_confignode configuration panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
ts_configrestart workspace manager panel.. . . . . . . . . . . . . . . . . . . . . . . . .80
ts_configindicating Node 0 is configured . . . . . . . . . . . . . . . . . . . . . . . . . . .80
ts_config“Configure ‘scub_ip’ address” selection . . . . . . . . . . . . . . . . . . . . .81
ts_config“SCUB OK” panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
ts_configscub_ip address configuration confirmation . . . . . . . . . . . . . . . . .82
ts_configscub_ip address set confirmation panel . . . . . . . . . . . . . . . . . . . . .82
ts_config“Reset Node” selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
ts_confignode reset panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
Figure 9
Figure 10
Figure 11
Figure 12
Figure 13
Figure 14
Figure 15
Figure 16
Figure 17
Figure 18
Figure 19
Figure 20
Figure 21
Figure 22
Figure 23
Figure 24
Figure 25
Figure 26
Figure 27
Figure 28
Figure 29
Figure 30
Figure 31
Figure 32
Figure 33
Figure 34
Figure 35
Figure 36
Figure 37
Figure 38
Figure 39
Figure 40
List of Figures
ix
Download from Www.Somanuals.com. All Manuals Search And Download.
Figure 41
Figure 42
Figure 43
Figure 44
Figure 45
Figure 46
Figure 47
Figure 48
Figure 49
Figure 50
Figure 51
Figure 52
Figure 53
Figure 54
Figure 55
Figure 56
Figure 57
Figure 58
Figure 59
Figure 60
Figure 61
ts_config“Add/Configure Terminal Mux” selection . . . . . . . . . . . . . . . . . . . 84
Terminal mux IP address panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
“Start Console Session” selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Started console sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
SSP supporting two single-node complexes . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
ts_configConfigure Multinode complex selection . . . . . . . . . . . . . . . . . . . . 88
Configure Multinode Complex dialog window . . . . . . . . . . . . . . . . . . . . . . . . . 88
Configure Multinode Complex dialog window with appropriate values . . . . . 90
Configuration started information box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
ts_configshowing newly configured complexes . . . . . . . . . . . . . . . . . . . . . . 92
ts_configSplit Multinode complex operation . . . . . . . . . . . . . . . . . . . . . . . . 93
ts_configSplit Multinode complex panel . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
ts_configSplit Multinode complex panel filled in . . . . . . . . . . . . . . . . . . . . 94
Split Multinode confirmation panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
ts_configSplit Multinode operation complete . . . . . . . . . . . . . . . . . . . . . . . 94
SSP-to-system communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
xconfigwindow—physical location names . . . . . . . . . . . . . . . . . . . . . . . . . 103
xconfigwindow—logical names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
xconfigwindow menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
xconfigwindow node configuration map . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
xconfigwindow node control panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
x
List of Figures
Download from Www.Somanuals.com. All Manuals Search And Download.
Ta bles
Table 1
Table 2
Table 3
Table 4
Table 5
Table 6
Table 7
Table 8
Table 9
Table 10
Table 11
Table 12
Table 13
Table 14
Table 15
Table 16
Table 17
Table 18
Table 19
Table 20
Table 21
Table 22
Table 23
Valid CTI cache sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Indicator LED operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Processor initialization steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Processor run-time status codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Message display line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Commands for creating console windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
sppconsole commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
Device file differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
System log pathnames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58
Boot menu commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
ts_configstatus values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
report_cfgoptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111
Hardware Path Numbering for V2500/V2600 Cabinets . . . . . . . . . . . . . . . .119
Boot variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
CUB detects power on error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166
CUB detects memory power fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171
CUB detects processor power fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172
CUB detects I/O (IOB) power fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173
CUB detects fan power fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174
CUB detects ambient air error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175
Hard error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176
Ambient air (intake) error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177
dc error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178
List of Tables
xi
Download from Www.Somanuals.com. All Manuals Search And Download.
xii
List of Tables
Download from Www.Somanuals.com. All Manuals Search And Download.
P r efa ce
The Operator’s Guide HP 9000 V2500/ V2600 Server documents the
information necessary to operate and monitor HP V-Class servers. This
book is intended to be a reference for system administrators, system
operators, and system managers.
Preface
xiii
Download from Www.Somanuals.com. All Manuals Search And Download.
Preface
Nota tion a l con ven tion s
This section describes notational conventions used in this book.
bold monospace
In command examples, bold monospace
identifies input that must be typed exactly as
shown.
monospace
In paragraph text, monospaceidentifies
command names, system calls, and data
structures and types.
In command examples, monospaceidentifies
command output, including error messages.
italic
In paragraph text, italic identifies titles of
documents.
In command syntax diagrams, italic identifies
variables that you must provide.
The following command example uses
brackets to indicate that the variable
output_file is optional:
commandinput_file [output_file]
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 aor b:
command {a | b}
xiv
Preface
Download from Www.Somanuals.com. All Manuals Search And Download.
Preface
Horizontal ellipses
(...)
In command examples, horizontal ellipses
show repetition of the preceding items.
Vertical ellipses
Vertical ellipses show that lines of code have
been left out of an example.
Keycap
Keycap indicates the keyboard keys you must
press to execute the command example.
NOTE
A note highlights important supplemental information.
CAUTION
Cautions highlight procedures or information necessary to avoid injury
to personnel. The caution should tell the reader exactly what will result
from what actions and how to avoid them.
WARNING
A warning highlights procedures or information necessary to avoid
damage to equipment, damage to software, loss of data, or invalid test
results.
Preface
xv
Download from Www.Somanuals.com. All Manuals Search And Download.
Preface
Sa fety a n d r egu la tor y in for m a tion
For your protection, this product has been tested to various national and
international regulations and standards. The scope of this regulatory
testing includes electrical/mechanical safety, radio frequency
interference, ergonomics, acoustics, and hazardous materials. Where
required, approvals obtained from third-party test agencies are shown on
the product label.
Sa fety in m a ter ia l h a n d lin g
CAUTION
Do not lift the node manually. To avoid physical injury you must use a
mechanical lifting device.
USA r a d io fr eq u en cy in ter fer en ce F CC Not ice
The Federal Communications Commission (in CFR Part 15) has specified
that the following notice be brought to the attention of the users of this
product.
NOTE
This equipment has been tested and found to comply with the limits for a
Class A digital device, pursuant to Part 15 of the FCC Rules. These limits
are designed to provide reasonable protection against harmful interference
when the equipment is operated in a commercial environment. This
equipment generates, uses, and can radiate radio frequency energy and, if
not installed and used in accordance with the instruction manual, may cause
harmful interference to radio communications. Operation of this equipment
in a residential area is likely to cause harmful interference in which case the
user will be required to correct the interference at his own expense.
The user is cautioned that changes or modifications not expressly
approved by Hewlett-Packard could result in the equipment being
noncompliant with FCC Class A requirements and void the user’s
authority to operate the equipment.
xvi
Preface
Download from Www.Somanuals.com. All Manuals Search And Download.
Preface
J a p a n ese r a d io fr eq u en cy in t er fer en ce VCCI
Figu r e 1
J a p a n ese r a d io fr eq u en cy n otice
This equipment is a Class A category (Information Technology
Equipment to be used in commercial and /or industrial areas) and
conforms to the standards set by the Voluntary Control Council for
Interference by Information Technology Equipment aimed at preventing
radio interference in commercial and/or industrial areas.
Consequently, when used in a residential area or in an adjacent area
thereto, radio interference may be caused to radios and TV receivers, etc.
Read the instructions for correct handling.
E MI st a t em en t (E u r op ea n Un ion on ly)
This is a Class A product. In a domestic environment this product may
cause radio interference in which case the user may be required to take
adequate measures.
Digit a l a p p a r a t u s st a t em en t (Ca n a d a )
This Class A digital apparatus meets all requirements of the Canadian
Interference-Causing Equipment Regulations.
Cet appareil numérique de la classe A respecte toutes les exigences du
Règlement sur le matériel brouilleur du Canada.
BCIQ (Ta iw a n )
This product has been reviewed, evaluated by GesTek Taiwan and is
fully compliant to CNS 13438 (CISPR 22: 1993) Class A.
Preface
xvii
Download from Www.Somanuals.com. All Manuals Search And Download.
Preface
Figu r e 2
BCIQ (Ta iw a n )
3862H354
Acou stics (Ger m a n y)
Laermangabe (Schalldruckpregel LpA) gemessen am fiktiver
Arbeitsplatz bei normalem Betrieb nach DIN 45635, Teil 19: LpA =65.3
dB.
Acoustic Noise (A-weighted Sound Pressure Level LpA) measured at the
bystander position, normal operation, to ISO 7779: LpA = 65.3 dB.
IT p ow er system
This product has not been evaluated for connection to an IT power
system (an AC distribution system having no direct connection to earth
according to IEC 950).
High lea k a ge cu r r en t
CAUTION
Attention
Achtung
High leakage current. Ground (earth) connection essential before
connecting the supply.
Forts courants de peretes. Connection a une borne de terre est
essentielle avant tout raccord electrique.
Hoher ableitstrom. Vor inbetreiebnahme schutzleiterverbindung
herstellen.
xviii
Preface
Download from Www.Somanuals.com. All Manuals Search And Download.
Preface
In sta lla tion con d ition s (U.S.)
See installation instructions before connecting to the supply.
Voir la notice d’installation avant de raccorder au réseau.
Please note the following conditions of installation:
CAUTION
An insulated earthing conductor that is identical in size, insulation
material, and thickness to the earthed and unearthed branch-circuit
supply conductors except that it is green with or without one or more
yellow stripes is to be installed as part of the branch circuit that
supplies the unit or system. The earthing conductor described is to be
connected to earth that the service equipment or, if supplied by a
separately derived system, at the supply transformer or motor-
generator set.
The attachment-plug receptacles in the vicinity of the unit or system
are all to be of an earthing type, and the earthing conductors serving
these receptacles are to be connected to earth at the service
equipment.
CAUTION
CAUTION
For supply connections, use wires suitable for at least 60 °C.
Utillser des fils convenant à une température de 60 °C pour les
connexions d’allmenation.
F u se ca u tion s
Disconnect power before changing fuse.
Attention
CAUTION
Coupier le courant avant de remplacer le fusible.
For continued protection against risk of fire, replace fuses only with
same type and rating.
Attention
Pour ne pas compromettre la protection contre les risques d’incendle,
remplacer par un fusible de même type et de mêmes caractéristiques
nominales.
Preface
xix
Download from Www.Somanuals.com. All Manuals Search And Download.
Preface
Associa ted d ocu m en ts
Associated documents include:
•
•
HP Diagnostic Guide: V2500/ V2600 Servers, (A5824-96002)
HP-UX SCA Programming and Process Management White Paper
–
Available in /usr/share/doc for HP-UX 11.10
HP-UX 11.0 Configurable Kernel Parameters
Available online at: http://docs.hp.com/hpux/os
•
–
•
•
HP-UX 11.10 Installation and Configuration Notes HP V2500
Servers, (A5532-90005)
HP V-Class Server HP-UX Configuration Notes (for 11.0), (A4801-
90001)
•
•
•
Managing Systems and Workgroups, (B2355-90157)
PA-RISC 2.0 Architecture Reference Manual, (ISBN 0-13-182734-0)
V2500 SCA HP-UX System Guide, (A5532-90003)
xx
Preface
Download from Www.Somanuals.com. All Manuals Search And Download.
Preface
Tech n ica l a ssist a n ce
If you have questions that are not answered in this book, contact the
Hewlett-Packard Response Center at the following locations:
•
•
Within the continental U.S., call 1 (800) 633-3600.
All others, contact your local Hewlett-Packard Response Center or
sales office for assistance.
Preface
xxi
Download from Www.Somanuals.com. All Manuals Search And Download.
Preface
Rea d er feed ba ck
This document was produced by the System Supportability Lab Field
Engineering Support organization (SSL/FES). If you have editorial
suggestions or recommended improvements for this document, please
write to us.
Please report any technical inaccuracies immediately.
You can reach us through email at:
Please include the following information with your email:
•
•
Title and part number of the document
Edition number
xxii
Preface
Download from Www.Somanuals.com. All Manuals Search And Download.
1
Over view
This chapter introduces Hewlett-Packard V-Class system components
and includes a brief overview of V2500/V2600 server hardware resources.
Some basic details about HP-UX use also are provided. For details on the
external cabinet controls and displays, see Chapter 2.
The V2500/V2600 model of V-Class server can have up to 128 processors,
128 Gbytes of memory, and 112 PCI I/O cards.
One new feature of the HP V2500/V2600 server is its Scalable
Computing Architecture (SCA) design, which allows multiple V2500/
V2600 cabinets to be connected to form a single HP-UX system. These
SCA features are made available through HP’s Coherent Toroidal
Interconnect (CTI) technology.
A V2500/V2600 server can include from one to four cabinets that contain
the server resources, with each V2500/V2600 cabinet containing from
two to 32 processors, from 512 Mbytes to 32 Gbytes of memory, and up to
28 PCI I/O cards.
Each V-Class system also includes a dedicated workstation connected to
the server: the Service Support Processor (SSP workstation). The Service
Support Processor is used for server booting, monitoring, and other
operations. Details on using the Service Support Processor are provided
in Chapter 3.
This book covers both single-cabinet and multiple-cabinet server
configurations, support, and operations.
Chapter 1
1
Download from Www.Somanuals.com. All Manuals Search And Download.
Overview
V-Class System Components
V-Cla ss Syst em Com p on en t s
Each V-Class system includes two main components: a V-Class server
and a Service Support Processor (SSP workstation) dedicated to
supporting the server, as shown below in Figure 3.
Figu r e 3
V-Cla ss Ser ver Com p on en t s: Ca b in et
a n d Ser vice Su p p or t P r ocessor
CO
DC
ENNSOL
AB
OF
E
F
LE
CO
S
E
N
S
L
O
C
U
L
E
DC
RE
ON
TO
C
V25U075
10/13/98
The V-Class cabinet contains all V-Class server resources, such as
processors, memory, disks, power, and so forth. The Service Support
Processor has software that allows you to monitor the resources in a V-
Class cabinet. The V-Class server and the Service Support Processor run
separate instances of the HP-UX operating system.
Multiple-cabinet servers may contain up to four V2500/V2600 cabinets,
which are booted as a single HP-UX system. Each cabinet has its own
cabinet ID (0, 2, 4, or 6) and contains processors, memory, and I/O
resources that are available to HP-UX and the applications that run on
the server. Cabinets are numbered based on their location in the server.
Cabinet ID 0 is the “monarch” or “root” cabinet, which contains the I/O
device used for booting and volume group 0. The other cabinets (IDs 2, 4,
and 6) are “serf” cabinets, located as shown in Figure 5 on page 5.
2
Chapter1
Download from Www.Somanuals.com. All Manuals Search And Download.
Overview
Support Processor that is used for console, diagnostic, and other support
work. The V2500/V2600 cabinets are tightly interconnected by Coherent
Toroidal Interconnect (CTI) cables, as described in “Multiple-Cabinet
Server Connections” on page 15. Connections among the Service Support
Processor and V2500/V2600 cabinets are covered in “Server Console and
Diagnostic Connections” on page 4.
Figu r e 4
Fou r -Ca b in et V2500/V2600 Ser ver Com p on en ts
CO
DC
O
E
NSO
FF
NABLELE
CO
SE
N
C
SLOLE
UR
DC
ON
E
TOC
CO
DC
E
N
N
S
O
OF
F
LE
AB LE
CO
SE
N
C
S
LO
RELE
U
D
C
O
N
TO
C
V25U074
10/6/98
Th e Ser vice Su p p or t P r ocessor
The Service Support Processor (SSP workstation) is an HP 712 or B180
workstation connected to the V-Class server. Key operations supported
by the Service Support Processor include booting, configuring, and
Chapter 1
3
Download from Www.Somanuals.com. All Manuals Search And Download.
Overview
V-Class System Components
monitoring the server hardware, as well as diagnostics operations. You
also must use the Service Support Processor when installing or
upgrading V-Class firmware.
The Service Support Processor runs HP-UX V10.20. In addition to HP-
UX software, the Service Support Processor includes files and utility
software for managing and monitoring the V2500/V2600 server. These
items and all other V2500/V2600-related files, including log files, that
are stored on the Service Support Processor can be found in the directory
/spp.
The default user account for Service Support Processor operations is
sppuser, with a home directory of /users/sppuser.
NOTE
The abbreviation “spp” stands for “scalable parallel processor” and is not
to be confused with “SSP”.
See Chapter 3 for more detailed information on the Service Support
Processor.
Ser ver Con sole a n d Dia gn ostic Con n ection s
The V2500/V2600 server’s utilities board provides connections from the
Service Support Processor to a V2500/V2600 server’s cabinet or cabinets.
Both the console port and diagnostic LAN on each cabinet are connected
to the Service Support Processor for system monitoring, booting, and
other operations.
The Service Support Processor connections to a V2500/V2600 server
provide only console, diagnostics, and preliminary booting support. For
V2600 HP-UX system. Cross-cabinet connections are covered in the
section “Multiple-Cabinet Server Connections” on page 15.
A single-cabinet V2500/V2600 server is connected directly to the Service
As shown in Figure 5, multiple-cabinet V2500/V2600 servers have
connections from each cabinet’s utilities board to either the Service
Support Processor or a terminal server.
While a four-cabinet V2500/V2600 server configuration is shown in
Figure 5, a two-cabinet or three-cabinet configuration involves the same
type of set up among the Service Support Processor, V2500/V2600
cabinets, and the terminal server.
4
Chapter1
Download from Www.Somanuals.com. All Manuals Search And Download.
Overview
V-Class System Components
Figu r e 5
Con sole a n d Dia gn ost ic Con n ection s
for a Fou r -Ca b in et V2500/V2600 Ser ver
2
6
Util.
Util.
4
0
Util.
Util.
(diagnostic LAN)
2
1
0
Term. Server
SSP Workstation
(console)
The console port on cabinet ID 0’s utilities board connects to the Service
Support Processor, and console ports on cabinet IDs 2, 4, and 6 connect to
the terminal server (port numbers 2, 3, and 4, respectively).
The diagnostic LAN connects between, and is terminated at, the Service
Support Processor and the terminal server. Between these two points,
the diagnostic LAN runs in sequence to cabinet IDs 0, 2, 4, and 6.
Chapter 1
5
Download from Www.Somanuals.com. All Manuals Search And Download.
Overview
V-Class Server Architecture
V-Cla ss Ser ver Ar ch itectu r e
The V2500/V2600 server has a powerful set of interconnecting hardware
components that allow the server’s processors, memory, and I/O
components to operate with minimal interruptions or contentions for
resources.
The processor agents serve as a bus connection for a subset of the
system’s processors. Memory controllers provide cache-coherent access to
cards.
CTI controllers are an SCA feature used only in multiple-cabinet servers.
The CTI controllers are connected to memory controllers and provide
high-bandwidth connections to other cabinets that comprise the server.
See Figure 11 on page 16 for an overview of cross-cabinet CTI
connections.
V2500/V2600 Cr ossb a r In ter con n ect ion
The primary interconnecting component of each V2500/V2600 server
cabinet is the HyperPlane Crossbar, which provides connections from
processors and I/O to memory.
simultaneously. This crossbar provides a central connection among the
V2500/V2600 cabinet. On multiple-cabinet V2500/V2600 servers high-
speed CTI interconnections provide access to “remote” memory or other
resources on remote cabinets. See “Multiple-Cabinet Server Connections”
on page 15 for multiple-cabinet information.
As Figure 7 on page 8 shows, the crossbar has four Exemplar Routing
Access Controllers (ERACs), each of which connects to 4 processor agents
and four memory controllers. All memory controllers and processor
agents connect to two separate ERACs, thus making the entire system’s
memory addressable by all processors and I/O devices in the system.
6
Chapter1
Download from Www.Somanuals.com. All Manuals Search And Download.
Overview
V-Class Server Architecture
Figu r e 6
F u n ct ion a l Dia gr a m of a Sin gle-Ca bin et V2500/V2600 Ser ver
CPU CPU
PCI
Controller
Processor
Agent
Memory
Controller
Memory
Memory
Memory
Memory
Memory
Memory
Memory
Memory
CPU CPU
CPU CPU
CTI
PCI
Controller
Processor
Agent
Memory
Controller
CPU CPU
CPU CPU
CTI
PCI
Controller
Processor
Agent
Memory
Controller
CPU CPU
CPU CPU
CTI
PCI
Controller
Processor
Agent
Memory
Controller
CPU CPU
CPU CPU
CTI
PCI
Controller
Processor
Agent
Memory
Controller
CPU CPU
CPU CPU
CTI
PCI
Controller
Processor
Agent
Memory
Controller
CPU CPU
CPU CPU
CTI
PCI
Controller
Processor
Agent
Memory
Controller
CPU CPU
CPU CPU
CTI
PCI
Controller
Processor
Agent
Memory
Controller
CPU CPU
CTI
Core Utilities
Board
SSP Workstation
Chapter 1
7
Download from Www.Somanuals.com. All Manuals Search And Download.
Overview
V-Class Server Architecture
Figu r e 7
V2500/V2600 Hyp er P la n e Cr ossba r Con n ect ion s
Each ERAC has 16 ports, 4 send and 4 receive on each side, which may
•
•
•
•
“Core Utilities Board” on page 9
“Processors” on page 9
“Memory” on page 9
“Input/Output” on page 12
In Chapter 2, you can find details on the V2500/V2600 cabinet external
controls, such as the on/off key switch panel, and cabinet displays,
including the LCD and attention light.
8
Chapter1
Download from Www.Somanuals.com. All Manuals Search And Download.
Overview
V-Class Server Architecture
Cor e Utilities Boa r d
The utilities board provides boot, diagnostics, and console connections
from the V-Class cabinet to the Service Support Processor, as well as
system clock, system LCD, and other functionality. It also stores the boot
On multiple-cabinet servers, the Service Support Processor and a
terminal server are connected to the console port and diagnostic LAN of
each cabinet’s utilities board. Details of these connections are shown in
Figure 5 and in the section “Server Console and Diagnostic Connections”
on page 4.
P r ocessor s
A V2500/V2600 server can include up to 128 processors. Each V2500/
V2600 cabinet may contain from two to 32 64-bit processors. The V2500
uses the 440 MHz HP PA-8500 processor. The V2600 uses the 552 MHz
PA-8600 processor. Each processor board contains one or two processors,
with up to two processor boards connecting to each of the eight processor
agents per cabinet.
The PA-8500 and PA-8600 processors are based on version 2.0 of
Hewlett-Packard’s Reduced Instruction Set Computer (RISC) processor
architecture.
NOTE
The PA-RISC architecture is presented in the PA-RISC 2.0 Architecture
reference manual. Please refer to that document for detailed information
about processor features. This Operator’s Guide does not duplicate
information in that manual.
Other models of V-Class servers, including V2200 and V2250 servers, use
Hewlett-Packard’s PA-8200 processor. Upgrading these other models of
servers to a V2500/V2600 involves upgrading the processor, among other
components.
Mem or y
A four-cabinet V2500/V2600 server can contain up to 128 Gbytes of
memory when all slots on all memory boards are populated with 256
MByte DIMMs. A maximum of 32 Gbytes of memory may be installed
per V2500/V2600 cabinet. For both single-cabinet and multiple-cabinet
servers, all memory boards within a cabinet must be configured
identically.
Chapter 1
9
Download from Www.Somanuals.com. All Manuals Search And Download.
Overview
V-Class Server Architecture
Three DIMM sizes are supported for use in V2500/V2600 servers:
32 MByte, 128 MByte, and 256 MByte. Only specified mixed DIMM size
configurations are supported.
bit DIMMs and configure your V2500/V2600 server to be one-fourth, one-
half, or fully populated with DIMMs.
Single-cabinet servers can instead use 80-bit DIMMs and may also be
As Figure 8 shows, each memory board includes a memory access
controller, memory DIMMs, and a CTI controller. The CTI controller is
not used in single-cabinet servers, but is present for connecting cabinets
in multiple-cabinet servers. Details on multiple-cabinet CTI connections
are available in “Multiple-Cabinet Server Connections” on page 15.
Figu r e 8
Con cep t u a l Over view of V2500/V2600 Mem or y Boa r d
Memory
Memory
Controller
(to crossbar)
CTI
(X-dimension
cabinet connection)
(Y-dimension
cabinet connection)
The V-Class cabinet has a Symmetric Multi-Processing (SMP) design,
which gives all processors equal access to all memory and a uniform
latency for memory accesses.
This provides SMP-like access to memory that resides on the same
cabinet as the requesting processor and gives the whole system a cache-
coherent non-uniform memory (ccNUMA) architecture. By dedicating
some memory as “CTI cache” memory, you can enhance performance by
allowing frequently used data that resides in memory on remote cabinets
to be encached on the local cabinet. See “CTI Cache Memory” on page 11.
10
Chapter1
Download from Www.Somanuals.com. All Manuals Search And Download.
Overview
V-Class Server Architecture
Mem or y In t er lea vin g
separate read and write access to the memory DIMMs. Up to 16 DIMMs
may be installed per board, providing up to 256-way memory
interleaving per cabinet when all memory boards are fully populated.
Slots for DIMMs on each memory board are conceptually grouped in four
quadrants. Each quadrant, as Figure 8 on page 10 shows, has a separate
interleaving memory within a memory board.
Memory also is interleaved across memory controllers, allowing separate
controllers and separate parts of the V2500/V2600 crossbar to
simultaneously access memory on different controllers. See Figure 7 on
page 8 for details.
CTI Ca ch e Mem or y
A portion of the memory on each cabinet of a V2500/V2600 SCA system
is used to implement the CTI cache memory. The CTI cache (also called
“network cache”) is memory that is used to minimize the latency of
remote memory accesses.
The CTI cache is directly mapped and physically indexed, unlike the
processor data caches. The size of the CTI cache is tunable and may
range from 8MB to 16GB, depending on the configuration of the memory
boards.
To set the CTI cache size, use the xconfigutility. The xconfigprogram
has a graphical interface and resides on (and is run from) the Service
Support Processor. The xconfigutility’s Memory menu allows the CTI
cache to be set through the Configure Network Cache menu item.
You also can configure CTI cache using the ts_configutility, which is
on the Service Support Processor. For details, see Chapter 5,
“Configuration utilities” or the ts_config man page.
The amount of memory dedicated as CTI cache must be set to be the
same for each cabinet in the V2500/V2600 server. So, for example, a
128 MByte per-cabinet CTI cache setting would consume a total of
256 Mbytes of memory for a two-cabinet V2500/V2600 server. Single-
cabinet servers should not have any memory dedicated as CTI cache, as
it is unnecessary.
Chapter 1
11
Download from Www.Somanuals.com. All Manuals Search And Download.
Overview
V-Class Server Architecture
With small CTI cache sizes, additional aliasing between memory
locations may occur, reducing the cache hit rate and increasing the
latency for remote accesses. The bold entries in Table 1 show the
minimal CTI cache sizes needed to avoid excessive aliasing.
Ta b le 1
Va lid CTI ca ch e sizes
Nod e Mem or y
size
Nod e CTI Ca ch e
size in MB
4 GB
32, 64, 128, 256, 512, 1024, 2048
8 GB
32, 64, 128, 256, 512, 1024, 2048, 4096
32, 64, 128, 256, 512, 1024, 2048, 4096, 8192
64, 128, 256, 512, 1024, 2048, 4096, 8192
64, 128, 256, 512, 1024, 2048, 4096, 8192, 16384
16 GB
24 GB
32 GB
CTI cache memory is configured at system boot time. The CTI cache
memory is dedicated only to be used for encaching remote accesses, and
is not available for any other use, such as use by HP-UX or applications.
In p u t/Ou tp u t
A multiple-cabinet V2500/V2600 server can contain up to 112 PCI I/O
cards, with each cabinet containing up to 28 PCI I/O cards. Each V2500/
V2600 cabinet includes 64-bit PCI chassis, eight PCI buses, and
connections for either three or four PCI cards per PCI bus.
The following I/O cards are supported on HP V2500/V2600 servers:
•
•
•
•
•
•
Tachyon Fibre Channel
HVD FWD SCSI
LVD Ultra2 SCSI
10/100 Base T Ethernet
1000 Base SX Gigabit Ethernet
FDDI
12
Chapter1
Download from Www.Somanuals.com. All Manuals Search And Download.
Overview
V-Class Server Architecture
Each V2500/V2600 I/O port is capable of direct memory access (DMA),
which eliminates processor involvement during data transfers and
streamlines data transfer for large disk blocks and high-speed network
The PCI bus controllers are numbered based on the V2500/V2600 cabinet
in which they reside. The first component of the hardware path (such as
reported by the HP-UX ioscanutility) indicates which cabinet a
hardware component resides upon.
Figure 9 on page 13 shows the PCI bus numbers and card cage locations
for a single-cabinet server. The I/O card cages are accessible from either
the top-left or the bottom-right sides of the V2500/V2600 cabinet.
Figu r e 9
Nu m b er in g a n d Loca tion s of Sin gle-Ca b in et V2500/V2600 P CI I/O
1
5
0
4
0
0
1
2
3
0
1
2
0
1
2
3
0
1
2
1
2
3
4
5
6
7
Top left PCI card cage, as viewed from the left side
of the V2500/V2600 cabinet. The PCI bus numbers (1, 5,
0, 4) are shown at the top, and card slots (0–3) are num-
bered in the card cage above.
7
3
6
2
2
1
0
3
2
1
0
2
1
0
3
2
1
0
Bottom right PCI card cage, as viewed from the right side
of the V2500/V2600 cabinet. The PCI bus numbers (7, 3,
6, 2)
are shown at the top, and card slots (0–3) are numbered
The PCI busses in a single-cabinet server are numbered from 0 to 7, as
shown above. This numbering also is used for the PCI busses in cabinet 0
of a multiple-cabinet server.
Chapter 1
13
Download from Www.Somanuals.com. All Manuals Search And Download.
Overview
V-Class Server Architecture
For multiple-cabinet servers, the PCI bus numbering is as shown in
Figure 10. The PCI bus number also serves as the first field of the
associated devices’ hardware path, so I/O devices on cabinet ID 0 are
For cabinet ID 2, the PCI bus numbers are from 64 to 71. PCI busses on
cabinet ID 4 are from 128 to 135, and cabinet ID 6 devices are numbered
from 192 to 199.
The PCI bus and card slot numbering for multiple-cabinet servers is
illustrated in Figure 10 on page 14.
Figu r e 10
Nu m b er in g a n d Loca tion s of Mu ltip le-Ca b in et V2500/V2600 P CI
I/O
65
69
64
68
193
197
192
196
0 1 2 3
0 1 2
0 1 2 3
0 1 2
0 1 2 3
0 1 2
0 1 2 3
0 1 2
Top left PCI card cage, cabinet ID 2.
Top left PCI card cage, cabinet ID 6.
71
67
70
66
199
195
198
194
2 1 0
3 2 1 0
2 1 0
3 2 1 0
2 1 0
3 2 1 0
2 1 0
3 2 1 0
Bottom right PCI card cage, cabinet ID 2.
Bottom right PCI card cage, cabinet ID 6.
1
5
0
4
129
133
128
132
0 1 2 3
0 1 2
0 1 2 3
0 1 2
0 1 2 3
0 1 2
0 1 2 3
0 1 2
Top left PCI card cage, cabinet ID 0.
Top left PCI card cage, cabinet ID 4.
7
3
6
2
135
131
134
130
2 1 0
3 2 1 0
2 1 0
3 2 1 0
2 1 0
3 2 1 0
2 1 0
3 2 1 0
Bottom right PCI card cage, cabinet ID 0.
Bottom right PCI card cage, cabinet ID 4.
14
Chapter1
Download from Www.Somanuals.com. All Manuals Search And Download.
Overview
V-Class Server Architecture
For an example of listing I/O devices on various cabinets and details of
listing other V-Class server hardware configuration details, see “Listing
the Server Hardware Configuration” on page 118.
Mu lt ip le-Ca b in et Ser ver Con n ect ion s
All cabinets in a multiple-cabinet V2500/V2600 server are tightly
CTI is an extension of the Scalable Coherent Interface standard defined
by the IEEE.
CTI cables connect among the CTI controllers on the various cabinets.
An overview of the CTI connections for a four-cabinet V2500/V2600
server is shown in Figure 11.
Chapter 1
15
Download from Www.Somanuals.com. All Manuals Search And Download.
Overview
V-Class Server Architecture
Each CTI controller connects to a corresponding CTI controller on a
remote cabinet by cables that provide both send (local-to-remote) and
receive (remote-to-local) connections among the cabinets.
Figu r e 11
Fou r -Ca b in et V2500/V2600 Ser ver CTI Ca b le Con n ection s
2
6
0
4
Two dimensions of CTI connections are possible. Y-dimension cables
connect between cabinets 0 and 2, and between cabinets 6 and 4. X-
dimension cables connect cabinets 0 and 4, and cabinets 6 and 2.
Send and receive connections are provided in two dimensions on each
controller, for a total of four connections per controller possible. In a two-
cabinet server, cabinets 0 and 2 are connected via Y-dimension
CTI cables only. For a three-cabinet server, cabinet 0 has Y-dimension
CTI connections to cabinet 2 and X-dimension CTI connections to
cabinet 4.
For Y-dimension connections, CTI cables connect to their counterparts on
the remote cabinet. For example, the CTI cable connects from “Y-send” on
memory board 0 to the remote cabinet’s “Y-receive” on memory board 0.
16
Chapter1
Download from Www.Somanuals.com. All Manuals Search And Download.
Overview
V-Class Server Architecture
For X-dimension connections, CTI cables connect to the opposite
controller on the remote cabinet. This means—for X-dimension CTI
connections—memory boards connect in the following pairs: 0 and 2,
1 and 3, 4 and 6, and 5 and 7.
For details on CTI cable connections refer to qualified HP service
personnel.
Chapter 1
17
Download from Www.Somanuals.com. All Manuals Search And Download.
Overview
V2500/V2600 Cabinet Configurations
V2500/V2600 Ca b in et Con figu r a t ion s
This section shows two sample V2500/V2600 server configurations: a
single-cabinet system and a three-cabinet system, filled to one-half
processor capacity and to one-half and full memory capacity, respectively.
Each V2500/V2600 cabinet can contain up to 32 processors, 32 Gbytes of
memory, and 28 PCI cards, with up to four cabinets (up to 128 processors,
128 Gbytes of memory, and 112 I/O cards) comprising a V2500/V2600
server.
Additional server configuration and ordering information is available
from the following Web site.
http://eproducts.hp.com/
18
Chapter1
Download from Www.Somanuals.com. All Manuals Search And Download.
Overview
V2500/V2600 Cabinet Configurations
Figu r e 12
Sa m p le V2500/V2600 Ca b in et Con figu r a tion s
A single-cabinet V2500/V2600 server with 16 pro- A three-cabinet V2500/V2600 server with 48 pro-
cessors and 16 Gbytes memory, using 256 MByte
cessors and 96 Gbytes memory, using 256 MByte
Chapter 1
19
Download from Www.Somanuals.com. All Manuals Search And Download.
Overview
V2500/V2600 Cabinet Configurations
20
Chapter1
Download from Www.Somanuals.com. All Manuals Search And Download.
2
In d ica t or s, sw it ch es, a n d
d isp la ys
This section describes indicators, switches, and displays of the HP 9000
V2500 server.
Chapter 2
21
Download from Www.Somanuals.com. All Manuals Search And Download.
Indicators, switches, and displays
Operator panel
Op er a tor p a n el
The operator panel is located on the top left side of the server and
contains the key switch panel, DVD-ROM drive, optional DAT tape
drive, and the LCD display. Figure 13 shows the location of the operator
panel and its components.
Figu r e 13
Op er a tor p a n el
LCD display
Optional DAT drive
DVD-ROM drive
Key switch panel
CONSOLE
ENABLE
D
C
O
F
F
CONSLOLE
SECURE
D
C
O
N
TOC
V25U102
3/24/99
22
Chapter2
Download from Www.Somanuals.com. All Manuals Search And Download.
Indicators, switches, and displays
Operator panel
Key sw itch p a n el
The key switch panel is located on the left of the operator panel, as
shown in Figure 13 on page 22. The key switch panel contains a two
position key switch, a DC ON LED, and a TOC (Transfer Of Control)
button, as shown in Figure 14.
Figu r e 14
Key sw itch p a n el
DC ON
ON
DC OFF
TOC
IOEXS095
10/10/97
Key sw itch
The key switch has two positions:
•
DC OF F
DC power is not applied to the system. Placing the key switch in this
position is the normal method for turning off power to the system.
•
ON
DC power is applied to the system. POST (Power On Self Test) begins
executing and brings up the system from an indeterminate state and
then calls OBP.
DC ON LED
This LED indicates that DC power has been applied to the system.
Chapter 2
23
Download from Www.Somanuals.com. All Manuals Search And Download.
Indicators, switches, and displays
Operator panel
TOC
the system.
DVD-R OM d r ive
The DVD-ROM drive is located on the left of the operator panel, as
shown in Figure 13 on page 22. Figure 15 shows the DVD-ROM drive
front panel in detail.
Figu r e 15
DVD-ROM d r ive
Disk loading slot
Headphone jack
Busy indicator
Eject button
Volume control
V25U101
3/17/99
Disk loa d in g slot
Place the disk into the slot with the label side up. Gently push the front
edge of the disk to load it into the drive. When an 8-cm disk is used, it
must be set into an adapter prior to loading.
24
Chapter2
Download from Www.Somanuals.com. All Manuals Search And Download.
Indicators, switches, and displays
Operator panel
Bu sy in d ica tor
The busy indicator LED flashes to indicate that a read operation is
occurring.
CAUTION
Do not push the eject button while this LED is flashing. If you do, the
operation in progress is aborted, and the DVD-ROM is ejected, possibly
causing a loss of data.
Eject bu tton
Op t ion a l DAT d r ive
The DAT drive is located on the right of the operator panel, as shown in
Figure 13 on page 22. The DAT drive front panel contains two indicator
LEDs and an eject button, as shown in Figure 16.
Figu r e 16
DDS-3 DAT d r ive fr on t p a n el
Tape Clean
Eject button
Activity LED
Attention LED
LEDs
The two LEDs provide operating information for normal as well as error
conditions. Table 2 shows the meaning of the different LED patterns.
Chapter 2
25
Download from Www.Somanuals.com. All Manuals Search And Download.
Indicators, switches, and displays
Operator panel
Ta b le 2
Ta p e
In d ica t or LE D op er a tion
Clea n
(At ten t ion ) LED
(a m b er )
(Act ivit y)
LED (gr een )
Mea n in g
Flashing slowly Off
A load or unload of a cartridge is in progress.
Flashing
rapidly
Off
A cartridge is loaded and a read or write is in
progress.
On
Off
A cartridge is loaded.
Any
Flashing slowly
Media caution signal. Indicates that a cartridge is
near the end of its life or that the heads need
cleaning.
Any
On
Fault
Flashing slowly Off
Power-on (starts with two steady lights)
Eject bu tton
Push the eject button to remove cartridges from the tape drive. The drive
performs the following Unload sequence:
1. The tape is rewound to Beginning of Partition (BOP) for Partition 0.
2. If the tape is write-enabled, the copy of the Tape log is written back to
tape.
3. The tape is then rewound to Beginning of Media (BOM), unthreaded
from the mechanism, and ejected.
WARNING
Do n ot p u sh th e eject b u t ton w h ile t h e LE D is fla sh in g. If you d o,
th e op er a t ion in p r ogr ess is a b or ted a n d th e ca r t r id ge is eject ed ,
p ossib ly ca u sin g a loss of d a ta .
26
Chapter2
Download from Www.Somanuals.com. All Manuals Search And Download.
Indicators, switches, and displays
System Displays
System Disp la ys
The V-Class servers provide two means of displaying status and error
reporting: an LCD and an Attention light bar.
Figu r e 17
System d isp la ys
CONSOLE
DC OFF
ENABLE
CONSLOLE
SECURE
D
C
O
N
TOC
LCD display
Attention light bar
IOLM010
9/18/97
Chapter 2
27
Download from Www.Somanuals.com. All Manuals Search And Download.
Indicators, switches, and displays
LCD (Liq u id Cr ysta l Disp la y)
The LCD display is located on the right of the operator panel, as shown
in Figure 17 on page 27. The LCD is a 20-character by 4-line liquid
crystal display. Figure 18 shows the display and indicates what each line
on the display means.
Figu r e 18
Fr on t p a n el LCD
Node status line
0 (0,0)
Processor status line—lower 16
MIII IIII IIII IIII
IIII IIII IIII IIII
abcedfghijklr
Processor status line—upper 16
Message display line
is initially blank.
Power-On Self Test (POST) takes about 20 seconds to start displaying
output to the LCD. POST is described in the HP Diagnostics Guide:
V2500/ V2600 Servers. The following explains the output shown in
Figure 18:
Nod e sta t u s lin e
P r ocessor sta tu s lin e
The processor status line shows the current run state for each processor
in the node. Table 3 shows the initialization step code definitions and
Table 4 shows the run-time status codes. The M in the first processor
status line stands for the monarch processor.
28
Chapter2
Download from Www.Somanuals.com. All Manuals Search And Download.
Indicators, switches, and displays
System Displays
Ta b le 3
P r ocessor in it ia liza t ion step s
Descr ip tion
Step
0
1
2
3
4
5
6
7
8
9
a
Processor internal diagnostic register initialization
Processor early data cache initialization.
Processor stack SRAM test.(optional)
Processor stack SRAM initialization.
Processor BIST-based instruction cache initialization.
Processor BIST-based data cache initialization
Processor internal register final initialization.
Processor basic instruction set testing. (optional)
Processor basic instruction cache testing. (optional)
Processor basic data cache testing. (optional)
Processor basic TLB testing (optional)
b
Processor post-selftest internal register cleanup. (optional)
Ta b le 4
P r ocessor r u n -tim e sta tu s cod es
Descr ip tion
St a tu s
R
I
RUN: Performing system initialization operations.
IDLE: Processor is in an idle loop, awaiting a command.
MONARCH: The main POST initialization processor.
M
H
HPMC: processor has detected a high priority machine check
(HPMC).
T
S
TOC: processor has detected a transfer of control (TOC).
SOFT_RESET: processor has detected a soft RESET.
DEAD: processor has failed initialization or selftest.
D
Chapter 2
29
Download from Www.Somanuals.com. All Manuals Search And Download.
Indicators, switches, and displays
System Displays
St a tu s
Descr ip tion
d
-
DECONFIG: processor has been deconfigured by POST or the user.
EMPTY: Empty processor slot.
?
Messa ge d isp la y lin e
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 5 shows the code definitions.
Ta b le 5
Messa ge d isp la y lin e
Messa ge d isp la y cod e
Descr ip t ion
a
Utilities board (SCUB) hardware initialization.
Processor initialization/selftest rendezvous.
Utilities board (SCUB) SRAM test. (optional)
Utilities board (SCUB) SRAM initialization.
Reading Node ID and serial number.
Verifying non-volatile RAM (NVRAM) data structures.
Probing system hardware (ASICs).
b
c
d
e
f
g
h
i
Initializing system hardware (ASICs).
Probing processors.
j
Initialing, and optionally testing, remaining SCUB SRAM.
Probing main memory.
k
l
Initializing main memory.
m
n
o
Verifying multi-node hardware configuration
Multi-node initialization starting synchronization
Multi-node hardware initialization
30
Chapter2
Download from Www.Somanuals.com. All Manuals Search And Download.
Indicators, switches, and displays
System Displays
Messa ge d isp la y cod e
Descr ip t ion
Multi-node hardware verification
p
q
r
Multi-node initialization ending synchronization
At t en t ion ligh t b a r
The Attention light bar is located at the top left corner on the front of the
V2500/V2600 server as shown in Figure 17 on page 27. The light bar
displays system status in three ways:
•
•
•
OFF—dc power is turned off. Either the key switch or the side circuit
breaker is in the off position.
ON—Both the side circuit breaker and the keyswitch are in the on
position and no environmental warning, error, or hard error exists.
Flashing—There is an environmental error, warning, or hard error
condition. Also indicates scanning during diagnostic execution.
NOTE
NOTE
The light bar flashing during initial start up does not indicate a fault.
The types of environmental conditions that are monitored include:
•
•
•
ASIC installation error sensing
ASIC configuration or status
48V failure
48V failures are cleared only after a power cycle.
•
•
•
Power failure sensing
Fan sensing
Thermal sensing
Types of environmental control functions monitored include:
•
•
Power-on
Voltage margining (SSP interface)
Chapter 2
31
Download from Www.Somanuals.com. All Manuals Search And Download.
Indicators, switches, and displays
System Displays
En vir on m en ta l er r or s
Environmental errors are detected by two basic systems in the V2500/
V2600 server: Power-On and Environmental Monitor Utility Chip
(MUC).
Power-On detected errors such as ASIC install or ASIC not OK are
detected immediately and will not allow dc power to turn on until that
condition is resolved.
MUC detected errors such as Ambient Air Hot allows the dc power to
turn on for approximately 1.2 seconds before the dc power is turned off. If
two or more fans fail simultaneously, the MUC will shut off dc power.
Other MUC detected errors such as Ambient Air Warm will flash the
LED and not turn off dc power.
Error codes may be viewed by using the SSP utility command pceto
read the status of the CUB. However, this feature will only work after
database generation is complete, not before.
Using the SSP utility man leds to decode the CUB status nibbles.
The current environmental temperature set-points are:
•
•
Warm = 32 degrees Celsius (89.6 degrees Fahrenheit)
Hot = 37 degrees Celsius (98.6 degrees Fahrenheit)
Disp la yin g t h e CUB LE D va lu es u sin g p ce
Use the sppdshcommand pceto display the value of the LEDs on the
CUB.
St ep 1. Bring up the sppdshprompt at a sppuser window by entering:
$sppdsh
St ep 2. Use the pcecommand to display the LED values for all nodes, enter:
sppdsh:pce all
Node
IP address Clocks
LEDS @C U SHPT Supply1 Supply2 Supply3 Supply4
------------------- ------ --------- ---- ------ ------- ------- ------- -------
0 15.99.111.116 Normal 0x00
2 15.99.111.117 Normal 0x00
25 1 0000 Nominal Nominal Nominal Nominal
25 1 0000 Nominal Nominal Nominal Nominal
For more information about the pcecommand see the sppdsh man page.
St ep 3. Decode the LED values using Appendix A, “LED codes” .
32
Chapter2
Download from Www.Somanuals.com. All Manuals Search And Download.
Indicators, switches, and displays
System Displays
Id en t ifyin g a n od e w it h t h e b lin k com m a n d
The blink command is used to physically identify a node. This command
forces the node attention light bar to blink or turns off blinking, provided
an error does not exist on the node.
St ep 1. Bring up the sppdshprompt at a sppuser window by entering:
$sppdsh
St ep 2. Use the blinkcommand to cause the attention light bar to blink on a
specific node by entering the blinkcommand followed by the node
number. For example:
sppdsh:blink 0
For more information about the blinkcommand see the sppdsh man
page.
St ep 3. After you have physically identified the node cause the attention light
bar to return to a steady state by entering:
sppdsh:blink 0
Chapter 2
33
Download from Www.Somanuals.com. All Manuals Search And Download.
Indicators, switches, and displays
System Displays
34
Chapter2
Download from Www.Somanuals.com. All Manuals Search And Download.
3
SSP op er a t ion
•
•
•
•
•
SSP log-on
Using the CDE (Common Desktop Environment) Workspace menu
Using the console
SSP file system
System log pathnames
Chapter 3
35
Download from Www.Somanuals.com. All Manuals Search And Download.
SSP operation
SSP and the V-Class system
SSP a n d t h e V-Cla ss syst em
The Service Support Processor (SSP) is either a Hewlett-Packard B180L
or 712 workstation that performs the following functions for the V-Class
system:
•
•
•
•
•
•
Running diagnostics
Updating of CUB (Core Utility Board) firmware
Logging environmental and system level events
Configuring of hardware and boot parameters
Booting the operating system
Accessing V-class console
The SSP is closely interfaced with the Core Utility Board (CUB), located
on the Mid-plane Interconnect Board (MIB). It has the ability to access
each section of the CUB, allowing for control, verification, testing, and
normal management of the V-Class server.
A private ethernet bus called the “test bus” connects the SSP to the CUB
located within the V-Class server.
The SSP has HP-UX installed and operates independently from the main
server.
IMPORTANT
HP-UX 10.20 is required to allow the workstation to function as the SSP.
Additional software has been added to the basic HP-UX 10.20 to provide
all the necessary functions of the SSP.
36
Chapter3
Download from Www.Somanuals.com. All Manuals Search And Download.
SSP operation
SSP log-on
SSP log-on
Two UNIX user accounts are created on the SSP during the HP-UX 10.20
operating system installation process.
sppuser
This user is the normal log-on for the SSP during
system operation, verification, and troubleshooting.
Default password: spp user
Please note the space between spp and user.
root
This user has the ability to modify and configure every
parameter on the SSP.
Default password: serialbus
NOTE
If the passwords to these accounts are changed by the customer, the new
passwords must be supplied to the Hewlett-Packard Customer Engineer
(CE) upon request.
SSP sp p u ser w in d ow s
When the user is logged on to the SSP on a V2500/V2600 server that
consists of less than two nodes, the windows appear in the configuration
shown in Figure 19. The Workspace, however, does not appear until a
mouse button is clicked anywhere in the CDE backdrop.
If the V2500/V2600 server consists of more than two nodes, the console
windows are replaced by a consolebar as shown in Figure 20.
Chapter 3
37
Download from Www.Somanuals.com. All Manuals Search And Download.
SSP operation
SSP log-on
Messa ge w in d ow
The message window displays status from the ccmddaemon running on
the SSP approximately 60 seconds after power on. The hard error logger
also displays status in this window. This is a display window only and
does not accept input.
Con sole w in d ow (sp p con sole - com p lex con sole)
The complex console window is the main console window for the V-Class
server complex. It displays all POST (Power-On Self -Test) status for
node 0. The user can boot and configure the server from this window
using the boot menu (Command:prompt). The user can also enter a
special mode called “forth mode” (OBP) to perform special configuration
commands.
A second sppconsole window is spawned when two nodes exist.
Con sole w in d ow (sp p con sole - Nod e X con sole)
sppconsolewindows for each node in the complex are spawned using
the “consolebar” which is available from the desktop Workspace menu.
All POST (Power-On Self -Test) status for node X is displayed here. The
user can boot and configure the server from this window using the boot
menu. The user can also enter the special forth mode to perform special
configuration commands.
Con sole ba r
The console bar appears on the SSP workspace for systems that have
more than two nodes (or complexes in the case of SCA systems). To see
the complex console, click on the appropriate button in the console bar.
k sh sh ell w in d ow s
The kshwindows are local shell windows on the SSP. The user can enter
commands into these windows to invoke scripts or functions on the SSP.
Some commands like the do_resetcommand are scripts that begin
execution on the SSP and then control the V-Class server.
40
Chapter3
Download from Www.Somanuals.com. All Manuals Search And Download.
SSP operation
Using the CDE (Common Desktop Environment) Workspace menu
Usin g th e CDE (Com m on Desk top
En vir on m en t) Wor k sp a ce m en u
The SSP uses the CDE Workspace Manager to control the windows on
the screen. The Workspace menu is Workspace Manager main menu. The
Workspace menu selects create new windows, initiate diagnostic tools,
and perform other tasks.
CDE Wor k sp a ce m en u
The following section describes how to use the CDE Workspace menu on
V2500/V2600 servers:
St ep 1. Move the pointer over the CDE workspace backdrop.
appears.
St ep 3. Drag the mouse pointer to an option.
St ep 4. Release the mouse button to select the option.
Figure 21 shows the V2500/V2600 SSP Workspace menu and Figure 22
shows the submenus.
Chapter 3
41
Download from Www.Somanuals.com. All Manuals Search And Download.
SSP operation
Using the CDE (Common Desktop Environment) Workspace menu
V2500/V2600 Workspace menu options include:
•
V-Cla ss Com p lex: name—Opens this submenu for the node/complex.
If more than one node/complex has been configured, multiple V-Class
Complexes are available by name.
•
Con sole—Creates a new console window for a list of available
node/complexes.
•
•
Sh ells—Selects a shell: sppdsh, ksh, tcsh, csh, and shshells.
Dia gn ost ic Tools—Performs a do_resetor invokes cxtest,
est, or xconfig.
•
•
•
k sh —Creates a new kshwindow on the screen.
con soleb a r —Creates GUI console select bar on the screen.
ts_con fig—System monitoring, and diagnostic capabilities. Runs as
sppuser allowing the resetting of nodes/complexes and console session
generation.
•
ts_con fig (r oot )—Configures the SSP console, system monitoring,
and diagnostic capabilities. Runs as root, requires the password,
allows reconfiguration of nodes multinode complexes, and
configuration of the terminal mux.
•
teststa t ion con sole—Creates a new console window on the screen.
NOTE
Only one SSP console per node can be active at any time. If a new SSP
console is started, any existing SSP console sessions for that particular
node are disabled. The old console windows remain on the screen, but no
new console messages are sent to the old sessions. Only the most recent
SSP console will receive SSP console output.
•
•
xsecu r e—Use this tool to disable modem and LAN activity.
X tools—Lists several X tools including the load average display and
xlock(screen lock/saver).
Workspace actions include:
•
•
•
Sh u ffle u p —Moves the bottom window in a stack of windows to the
top.
Sh u ffle d ow n —Moves the top window in a stack of windows to the
bottom.
R efr esh a ll—Refreshes the entire X display.
Chapter 3
43
Download from Www.Somanuals.com. All Manuals Search And Download.
SSP operation
Using the CDE (Common Desktop Environment) Workspace menu
•
•
R est a r t Wor k sp a ce Ma n a ger —Stops and restarts the Workspace
Manager.
logou t—Closes all open windows and stops Workspace Manager.
44
Chapter3
Download from Www.Somanuals.com. All Manuals Search And Download.
SSP operation
Using the console
Usin g th e con sole
The console serves as the communication device for the V-Class server.
system software crash dump.
Cr ea t in g n ew con sole w in d ow s
Console windows can also be created using the sppconsoleand xterm
commands from the SSP; see Table 6 for details.
Ta b le 6
Com m a n d s for cr ea tin g con sole w in d ow s
SSP com m a n d
Descr ip t ion
/spp/scripts/sppconsole
The sppconsolescript provides an
HP-UX console interface in the
current SSP window.
/usr/bin/X11/xterm
Creates a SSP login window.
Creates a SSP console window.
/usr/bin/X11/xterm -C
Sta r t in g t h e con sole
The console server program automatically starts the console on the SSP
when you log on as sppuser. If the console stops running, restart it from
the SSP using one of the following methods: the Workspace menu, the
sppconsole command, ts_config, consolebar, or logging back on.
Methods for starting the console V2500/V2600 servers are:
•
Workspace menu
• sppconsolecommand
• ts_config
•
•
consolebar
logging back on
Chapter 3
45
Download from Www.Somanuals.com. All Manuals Search And Download.
SSP operation
Using the console
St a r tin g th e con sole fr om th e Wor k sp a ce m en u
To start the console using the Workspace menu, complete the following
steps:
St ep 1. Move the pointer over the CDE workspace backdrop.
St ep 2. Press and hold down any mouse button. The Workspace (root) menu
appears.
St ep 3. Drag the mouse pointer to the “V-Class Complex: complex_name” option.
St ep 4. Release the mouse button to select the option.
St ep 5. Drag the mouse pointer to the Console option.
St ep 6. Release the mouse button to select the option.
St ep 7. Select the desired V2500/V2600 complex.
NOTE
If the desired V2500/V2600 Complex name is not listed in the menu,
restart the Workspace manager. The desktop Workspace menus are
updated whenever a node is configured or deconfigured, but the new
menus are not activated until the Workspace Manager is restarted.
St ep 8. Select Console menu.
St ep 9. Select Node X/complex. The new console window appears.
St a r tin g th e con sole u sin g th e sp p con sole com m a n d
This method of starting the console works from the SSP or after logging
on ot the SSP from another system.
To start the console using the sppconsolecommand, complete the
following steps:
St ep 1. Select a shell window by placing the mouse pointer in the window.
St ep 2. If more than one V-Class complex is connected to the SSP, use the
set_complexcommand to select the desired complex by entering:
set_complex.
An output similar to the following will be displayed. Enter the desired
complex from the list provided.
46
Chapter3
Download from Www.Somanuals.com. All Manuals Search And Download.
SSP operation
Using the console
For example:
COMPLEX_NAME = [Select from colossus, guardian]colossus
St ep 3. Start the console. Enter:
sppconsole
NOTE
Running sppconsolewithout any additional parameters defaults to
Node 0 in the current complex. sppconsole 2would start a console on
Node 2.
The new sppconsole window appears.
In the example above, even if the user’s "default complex" is set to
colossus, the user could start a console on guardian Node 0 by entering
the Node Name in the following format:
Complex Name-nnnn
where nnnn is the Node ID extended to four digits and zero-filled on the
left. These names can be viewed using jf-ccmd-info or ts_config.
For example:
sppconsole guardian-0000
To start a console on Node 2 of the complex named guardian enter:
sppconsole guardian-0002
St a r tin g th e con sole u sin g ts_con fig
This method of starting the console works from the SSP or after logging
on from another system.
To start a console session from within ts_config, complete the
following steps:
St ep 1. Move the pointer over the CDE workspace backdrop.
St ep 2. Press and hold down any mouse button. The Workspace (root) menu
appears.
St ep 3. Drag the mouse pointer to the ts_config(root) option.
St ep 4. Release the mouse button to select the option.
Chapter 3
47
Download from Www.Somanuals.com. All Manuals Search And Download.
SSP operation
Using the console
St ep 5. Enter the root password.
Refer to “Starting ts_config” on page 92 for information on starting
ts_configfrom a local or remote shell.
St ep 6. Select the desired node(s) from the list in the display panel. For example,
clicking on node 0 in the list highlights that line in the window.
St ep 7. Start the console session by doing one of the following:
•
Select “Actions” to drop the pop-down menu and then click “Start
Console Session.”
•
Click the right-mouse button and select “Start Console Session.”
The console window(s) appears.
St a r tin g th e con sole u sin g th e con soleba r
This method of starting the console works from the SSP or after logging
on from another system.
The consolebarutility is an GUI that shows the configured nodes,
grouped by complex. Each node is a push-button that, when pushed,
activates a console session for that node.
If more than two nodes are configured on a V2500/V2600 SSP,
consolebarautomatically starts when the sppuser logs in at the SSP
display.
To start a console session using consolebarcomplete the following
steps:
St ep 1. Move the pointer over the CDE workspace backdrop.
St ep 2. Press and hold down any mouse button. The Workspace (root) menu
appears.
St ep 3. Drag the mouse pointer to the consolebar option.
St ep 4. Release the mouse button to select the option.
St ep 5. Enter the root password. The console bar appears.
St ep 6. Click on the button of the node to start
48
Chapter3
Download from Www.Somanuals.com. All Manuals Search And Download.
SSP operation
Using the console
St a r tin g th e con sole by loggin g ba ck on
This method of starting the console works from the SSP or after logging
on from another system.
To start the console by logging out of the SSP and logging back on again,
complete the following steps:
St ep 1. Move the pointer over the CDE workspace backdrop.
St ep 2. Press and hold down any mouse button. The Workspace (root) menu
appears.
St ep 3. Drag the mouse pointer to the logout menu option.
St ep 4. Release the mouse button to select the option. The SSP closes all open
windows and returns a HP-UX login prompt.
St ep 5. Log into the SSP as sppuser. The new sppconsole window displays.
Con sole com m a n d s
Use the sppconsole commands to control the console. Using these
commands allows the user to watch or to assume control of the console
window.
Ta b le 7
sp p con sole com m a n d s
Com m a n d
Descr ip tion
Force control of the console interface.
^Ecf
^Ecs
Relinquish control of the interface and return to spy
mode.
Display a list of other users connected to the console.
List the console escape command sequences.
Exit the console program.
^Ecw
^Ec?
^Ec.
NOTE
^E is the Ctrl and e keys pressed simultaneously. The e does not have to
be an uppercase E.
Chapter 3
49
Download from Www.Somanuals.com. All Manuals Search And Download.
SSP operation
Using the console
Example: Performing a ^E command
To execute the ^Ecfcommand complete the following steps:
1. Press the Cntrl key and the e key simultaneously.
2. Release the Cntrl key and the e key.
3. Press the c key.
4. Press the f key.
Any user can display the console via a remote login to the SSP, so it is
possible to have many different processes watching the console at the
same time. This is sometimes referred to as “spy mode.” Only one
window can actually control the console; see “Assuming control of the
console” on page 51, for more information.
To monitor the console from a system other than the SSP, complete the
following steps:
St ep 1. Remotely log in to the SSP as sppuser (default password: spp user) with
the following command:
rlogin hostname
login:sppuser
Password:spp user
St ep 2. Access the system console with the following command:
sppconsole
At this point the console is in “spy mode,” meaning the user can only
monitor what is going on at the system console. If commands are entered
the following message is displayed:
[read-only -- use ‘^Ecf’ to attach, ‘^Ec?’ for help]
Disp la y a list of ot h er con sole u ser s
St ep 1. Display a list of other users connected to the console with the following
command:
CTRL-Ecw
St ep 2. Exit the session with the following command:
50
Chapter3
Download from Www.Somanuals.com. All Manuals Search And Download.
SSP operation
Using the console
CTRL-Ec.
The period is part of the command.
Assu m in g con tr ol of th e con sole
System maintenance or diagnostics can be performed remotely by
assuming control of the console from a remote terminal. Upon gaining
control of the console, the user has write access to that window.
Only one window can be active at a time.
To assume control of the console, complete the following steps:
St ep 1. Remotely log in to the SSP as sppuser (default password: spp user) with
the following command:
rlogin hostname
login:sppuser
Password:spp user
St ep 2. Access the system console with the following command:
sppconsole
At this point the console is in spy mode, meaning the user can only
monitor what is going on at the system console. If commands are entered
the following message is displayed:
[read-only -- use ‘^Ecf’ to attach, ‘^Ec?’ for help]
St ep 3. Assume control of the console by attaching to it with the following
command:
CTRL-Ecf
St ep 4. To relinquish control of the console and return to spy mode, enter the
following command:
CTRL-Ecs
St ep 5. Exit the session with the following command:
CTRL-Ec.
Chapter 3
51
Download from Www.Somanuals.com. All Manuals Search And Download.
SSP operation
Using the console
Ch a n gin g a con sole con n ection
Once the console is started as a watch or a control connection, the
connection type can be changed with escape characters.
To change a watch window to an active console window, enter:
CTRL-Ecf
To change an active console window to watch window, enter:
CTRL-Ecs
Accessin g syst em logs
Monitor system status via two logs, event_logand consolelogX
(where Xis the node_id), located in /spp/data/complex_name on the SSP.
The event_logfile periodically logs system status. Once the file reaches
1 Mbyte, the system compresses it to event_log.old.Zand creates a
new event_logfile.
The consolelogXfiles grow without bounds. These need to be
periodically checked by the system administrator.
Th e set _com p lex com m a n d
From an existing shell on the SSP, the user can set the “default complex”
for the shell by executing the set_complexcommand.
set_complexcomplex name
The set_complexcommand lists the configured complex names and
prompts the user for a selection. After a complex has been selected, the
user can issue diagnostic, scan, and console commands against a
particular node ID (e.g. 0). The SSP software accesses the correct node by
combining the user-specified node ID with the complex name selected by
the last set_complexcommand run from the shell. The default complex
name is always visible. It is enclosed in parenthesis as part of the shell
prompt and included in the Window title if the shell is on the SSP
desktop.
set_complexdefault
If there is only one complex configured on a SSP, there is no need to run
the set_complexcommand since there is only one complex (in fact,
set_complexautomatically assigns the default complex name without
52
Chapter3
Download from Www.Somanuals.com. All Manuals Search And Download.
SSP operation
Using the console
prompting the user if only one complex is configured). This utility
accesses the desired node based on node ID. However, the single node
must still be configured by ts_configand assigned a complex name
before it can be accessed.
Ta r get in g com m a n d s t o n od es
Use the jf-ccmd_infocommand to determine what names or IP
addresses the J TAG interfaces have been set to on an SPP. The command
provides a list with the following information:
•
•
•
•
•
•
•
•
Ethernet Address (MAC)
IP Address
Complex Serial Number
Node Number
Environmental LED’s
Power Status
SCUB Status
Diagnostic (J TAG) node names
The diagnostic node name or the J TAG IP address is required when
using the load_epromcommand. Since the SSP software allows
changing the default J TAG hostnames and IP addresses, the user may
need to run this command to view the unique names and active IP
addresses for J TAG.
Example:
load_eprom -n COMPLEX_NAME-0000 -l /spp/firmware/diaglifhdr.fw
Chapter 3
53
Download from Www.Somanuals.com. All Manuals Search And Download.
SSP operation
SSP file system
The /spp and /users/sppuser directories contain most of the SSP specific
files. Other files in various directories are also modified. This section
restricts, however, its discussion to the /spp directory.
Figure 23 shows the SSP file system structure for V2500/V2600 servers.
Figu r e 23
SSP file syst em for V2500/V2600 ser ver s
/ spp
bin
(compiled executables)
(spp specific daemons)
(support for scan testing)
(firmware directory)
etc
est
firmware
man
(Man pages for / spp commands)
(executable scripts)
scripts
data
(ccmd_log and config files)
(consolelogs, event_log, hard_hist)
(consolelog, event_log, hard_hist)
COMPLEX_NAME
COMPLEX2_NAME
/sp p /et c
The /spp/etc directory contains many of the unique daemons that run on
the SSP. These daemons manage of the V-Class node. Two daemons that
are always running on the SSP are:
ccmd
A daemon that maintains a database of information
about the V-Class hardware. It also monitors the
system and reports any significant changes in system
status. For more information, see the ccmdman page.
54
Chapter3
Download from Www.Somanuals.com. All Manuals Search And Download.
SSP operation
SSP file system
conserver
The console-server that directs RS-232 console traffic
from the Utility Board to the various sppconsole
sessions.
/sp p /b in
In the /spp/bin directory are specific commands and daemons that
manage a V-Class node. Some of these are:
est
The command (Exemplar Scan Test) to initiate scan
testing.
do_reset
sppdsh
The command executed on the SSP to reset the V-Class
node remotely.
An enhanced version of the Korn Shell (ksh) with all of
the functionality of ksh, as well as new commands that
are suited to a diagnostic environment.
event_logger A daemon that receives messages from diagnostic
utilities through rpc calls and writes them to the event
log for later review or processing.
dcm
Dump Configuration Map. dcm dumps the boot
configuration map information for the specified node.
/sp p /scr ip t s
The /spp/scripts directory contains scripts that perform a variety of
functions.
sppconsole
The console utility.
hard_logger
The hard error logger script run automatically by
ccmd.
/sp p /d a ta /com p lex_n a m e
The /spp/data/complex_name directory contains:
node_0.cfg
Configuration file with scan rings and configured
hardware. This file describes all the ASIC chips
populated in a V-Class node and also defines the scan
rings which are used by the est (Exemplar Scan Test)
utility. This file is a very useful troubleshooting tool for
tracking scan ring failures to devices.
Chapter 3
55
Download from Www.Somanuals.com. All Manuals Search And Download.
SSP operation
SSP file system
consolelogX A file containing all the console activity on the system,
where X is the node ID.
est.log
The scan testing log.
hard_hist
Log of all hard failure information. Logs the output of
all suspected ASIC (Application Specific Integrated
Circuits). This file may be useful in troubleshooting
intermittent ASIC failures.
event_log
Log of all event information. A read only file which
captures information generated by the ccmddaemon.
/sp p /fir m w a r e
The /spp/firmware directory is where firmware files are written when
SSP software is installed. The firmware files are loaded from this
directory into flash or SRAM.
/sp p /est
The est directory contains files used during scan testing.
/sp p /m a n
The /spp/man directory contains the man (manual) pages on many of the
SSP specific commands.
56
Chapter3
Download from Www.Somanuals.com. All Manuals Search And Download.
SSP operation
SSP file system
Device files
Table 8 shows the differences in the device files between the HP B180L
and HP 712 SSPs.
Ta b le 8
Device file d iffer en ces
712
B180L
Loca tion on
Device
Loca tion on
w or k st a tion
Device file
Device file
w or k st a tion
Private/diagnostic LAN
Global/customer LAN
Node 0 console port
RS-232
LAN-TP
RS-232
/dev/lan1
/dev/lan0
/dev/tty0p0
/dev/ty1p0
LAN-AUI
Slot 2
/dev/lan0
/dev/lan1
Serial 1
Serial 2
/dev/tty1p0
/dev/tty0p0
Terminal mux
9-PIN
configuration port
connector of
the Y-Cable
Remote modem
9-PIN
connector of
the Y-Cable
/dev/ttyd1p0 Serial 2
or
/dev/cua1p0
or
/dev/ttyd0p0
or
/dev/cua0p0
or
/dev/cul1p0
/dev/cul0p0
Chapter 3
57
Download from Www.Somanuals.com. All Manuals Search And Download.
SSP operation
System log pathnames
System log p a th n a m es
To separate the configuration and log files for each complex, several files
have been moved to complex-specific directories. In Table 9, complex
using ts_config.
The /spp/data/complex directories are created by ts_configduring the
“Configure Node” process. Configuration and log files are then created by
the various daemon and utility programs as necessary.
The old/new pathname mappings are shown in Table 9.
Ta ble 9
System log p a th n a m es
Log n a m e
CCMD log file
V2500/V2600 p a t h n a m e
/spp/data/ccmd_log
CCMD old log file
Node 0 consolelog
Node 2 consolelog
Node CFG file
Node PWR file
Event log
/spp/data/ccmd_log.old.Z
/spp/data/complex/consolelog0
/spp/data/complex/consolelog2
/spp/data/complex/node_0.cfg
/spp/data/complex/node_0.pwr
/spp/data/complex/event_log
/spp/data/complex/event_log.old.Z
/spp/data/complex/hard_hist
/spp/data/complex/hl
Event log archive
Hard Logger log
Hard Logger temp
autoreset config
EST log
/spp/data/complex/.ccmd_reboot
/spp/data/complex/est.log
EST prior log
/spp/data/complex/est.log.old
/spp/data/complex/cxtest.log
cxtest log (GUI)
58
Chapter3
Download from Www.Somanuals.com. All Manuals Search And Download.
4
Fir m w a r e (OBP a n d P DC)
This chapter discusses the boot sequence and the commands available
from the boot menu.
Chapter 4
59
Download from Www.Somanuals.com. All Manuals Search And Download.
Firmware (OBP and PDC)
Boot sequence
Boot seq u en ce
OpenBoot PROM (OBP) and SPP Processor Dependent Code (SPP_PDC)
boot HP-UX.
Once a machine powers on, the firmware controls the system until the
operating system (OS) executes. If the system encounters an error any
time during the boot process, it stops processing and goes to HP mode
boot menu. See “HP mode boot menu” on page 64 for more information.
When the operator powers on or resets the machine, the following
process occurs:
1. Power-On Self Test (POST) runs. POST is described in “LCD (Liquid
Crystal Display)” on page 28 and in the HP Diagnostics Guide:
V2500/ V2600 Servers.
2. OBP probes all the devices.
3. OBP loads SPP_PDC in RAM.
4. OBP starts the HP-UX loader, which in turns calls SPP_PDC to set
up CPU’s, memory, and I/O devices in a way that HP-UX
understands.
presses a key within 10 seconds.
2. If autoboot is disabled or if the user presses a key within 10
seconds, the boot menu is displayed. For further information see,
“Enabling Autoboot” on page 67.
Figure 24 on page 61 illustrates the initialization and start-up process.
60
Chapter4
Download from Www.Somanuals.com. All Manuals Search And Download.
Firmware (OBP and PDC)
Boot sequence
Figu r e 24
Boot p r ocess
NO
Au tob oot
E n a b led ?
Boot m en u
d isp la ys
YES
P r om p t d isp la ys:
Processor is starting the autoboot process.
To discontinue, press any key within 10 seconds.
NO
Con tin u e
Au t om a tica lly?
P r ess a n y k ey
to d isp la y boot m en u
YES
H P -UX b oots
Chapter 4
61
Download from Www.Somanuals.com. All Manuals Search And Download.
Firmware (OBP and PDC)
Boot process output
Boot p r ocess ou tp u t
The following output illustrates what typically displays on the console as
the system starts up:
POST Hard Boot on [0:PB4L_A]
HP9000/V2500 POST Revision 1.0.0.2, compiled 1999/04/12 11:51:10
Probing CPUs: PB4L_A
Completing core logic SRAM initialization.
Starting main memory initialization.
Probing memory: MB0L MB1L MB2R MB3R
Installed memory: 2048 MBs, available memory: 2048 MBs.
Initializing main memory.
r0
r1
r2
r3
PB4L_A MB0L [:::: ____][:::: ____][____ ____][____ ____]
PB4L_A MB1L [:::: ____][:::: ____][____ ____][____ ____]
PB4L_A MB2R [:::: ____][:::: ____][____ ____][____ ____]
PB4L_A MB3R [:::: ____][:::: ____][____ ____][____ ____]
Building main memory map.
Main memory initialization complete.
Starting multinode initialization.
Collecting memory configuration from nodes: 0,2
Initializing ERI rings for node 0,2
Synchronizing nodes: 0,2
Initializing CTI cache.
r0
r1
r2
r3
PB4L_A MB0L [LLLL ____][CCCC ____][____ ____][____ ____]
PB4L_A MB1L [LLLL ____][CCCC ____][____ ____][____ ____]
PB4L_A MB2R [LLLL ____][CCCC ____][____ ____][____ ____]
PB4L_A MB3R [LLLL ____][CCCC ____][____ ____][____ ____]
Synchronizing nodes: 0,2
Verifying remote memory access.
Enabling Time of Century synchronization routing.
Synchronizing nodes: 0,2
Multinode initialization complete.
Booting OBP
OBP Power-On Boot on [0:8]
Node 0 OBP attempting to synchronize with node 2.
Node(s) { 2 } now synchronized.
62
Chapter4
Download from Www.Somanuals.com. All Manuals Search And Download.
Firmware (OBP and PDC)
Boot process output
-------------------------------------------------------------------------------
PDC Firmware Version Information
PDC_ENTRY version 4.2.0.4
POST Revision: 1.0.0.2
OBP Release 4.2.0, compiled 99/01/06 14:00:18 (3)
SPP_PDC 2.0.0 (03/08/99 11:47:51)
-------------------------------------------------------------------------------
Multi-node Configuration Summary
===============================================================================
NODE 0
UART? No
CORE MAC address 0:a0:d9:0:bf:16 IP# 15.99.111.166 (0x0f636fa6)
JTAG MAC address 0:a0:d9:0:bf:3
MEMORY 2048 MB memory installed
CPUs 8
IP# 15.99.111.116 (0x0f636f74)
1024 MB CTI cache configured
PACs 0,1,2,3,4,5,6,7
TACs 0,1,2,3
MACs 0,1,2,3
PCIs 0,3,4,7
-------------------------------------------------------------------------------
NODE 2
UART? No
CORE MAC address 0:a0:d9:0:be:eb IP# 15.99.111.167 (0x0f636fa7)
JTAG MAC address 0:a0:d9:0:c3:a3 IP# 15.99.111.117 (0x0f636f75)
MEMORY 2048 MB memory installed
CPUs 15
PACs 0,1,2,3,4,5,6,7
TACs 0,1,2,3
1024 MB CTI cache configured
MACs 0,1,2,3
PCIs 2,6
-------------------------------------------------------------------------------
4096 MB memory installed
2048 MB CTI cache configured (total, all nodes)
Primary boot path = 1/0/0.6.0
Primary boot arguments =
Alternate boot path = 15/3 NFS 15.99.111.99:/spp/os/uxinstlf
Alternate boot arguments =
Console path
Keyboard path
= 15/1
= 15/1
[*** Manufacturing (or Debug) Permissions ON ***]
System is HP9000/800/V2500 series
Autoboot and Autosearch flags are both OFF or we are in HP core mode.
Processor is entering manual boot mode.
Chapter 4
63
Download from Www.Somanuals.com. All Manuals Search And Download.
Firmware (OBP and PDC)
HP mode boot menu
HP m od e boot m en u
In some instances, the boot menu displays; otherwise the operating
system boots and the system is ready for use. The boot menu displays
when one of the following occurs:
•
•
•
The system encounters a problem while booting
Autoboot is disabled
The operator interrupts the boot process
Command
-------
Description
-----------
AUto [BOot|SEArch|Force ON|OFF] Display or set the specified flag
BOot [PRI|ALT|<path> <args>]
BootTimer [time]
CLEARPIM
Boot from a specified path
Display or set boot delay time
Clear PIM storage
CPUconfig [<cpu>] [ON|OFF|SHOW] (De)Configure/Show Processor
DEfault
Set the system to defined values
Display this menu
DIsplay
ForthMode
Switch to the Forth OBP interface
List the I/O devices in the system
List the boot or flash volume
Set the Forth password
IO
LS [<path>|flash]
PASSword
PAth [PRI|ALT|CON] [<path>]
PDT [CLEAR|DEBUG]
Display or modify a path
Display/clear Non-Volatile PDT state
PIM_info [cpu#] [HPMC|TOC|LPMC] Display PIM of current or any CPU
RemoteCommand node# command
RESET [hard|debug]
Execute command on a remote node
Force a reset of the system
Display/Select restricted access to Forth
RESTrict [ON|OFF]
SCSI [INIT|RATE] [bus slot val] List/Set SCSI controller parms
SEArch [<path>]
SECure [ON|OFF]
Search for boot devices
Display or set secure boot mode
TIme [cn:yr:mo:dy:hr:mn[:ss]] Display or set the real-time clock
VErsion
[0] Command:
Display the firmware versions
At this point, the user can either enter any command on the menu or
continue the boot process. To continue booting, enter the following
command:
Command: boot
Commands and options are case-insensitive (auto = AUTO). Each
command has a shortcut, which is the minimum letters that can be
entered to execute the command. For example, to execute the search
command, enter SEA, SEAR, SEARC, or SEARCH. This shortcut is
indicated by capital letters in Table 10 and in the rest of this chapter.
64
Chapter4
Download from Www.Somanuals.com. All Manuals Search And Download.
Firmware (OBP and PDC)
HP mode boot menu
Table 10 lists the commands available from the Command:prompt.
Ta b le 10
Boot m en u com m a n d s
Com m a n d
Descr ip t ion
AUto [BOot|SEArch|Force
ON|OFF]
Displays or sets the Autoboot or Search flag. If
Autoboot is on, the system boots automatically
after reset. If AutoSearch is on, the system
searches for and displays all I/O devices that the
system can boot from. If Autoforce is on, OBP
allows HP-UX to boot even if one or more cabinets
does not complete power on self test.
BOot [PRI|ALT|path args]
Initiates the boot sequence. A default or specified
path to the boot device can be used.
BootTimer [time]
Displays or sets a delay time for the system to
wait for external mass storage devices to come
online.
CLEARPIM
Clears (zeros) Processor Internal Memory (PIM)
storage after a system crash. CAUTION: this
command can delete important troubleshooting
information; do not enter the CLEARPIM
command unless directed to.
CPUconfig [proc] [ON|OFF]
DEfault
Displays or sets the configuration of processors.
Sets the system environment variables to defined
values and changes certain HP variables so that
HP-UX can boot.
DIsplay
Displays this menu.
ForthMode
Switches to the Forth OBP interface. For use by
service personnel only.
IO
Displays all I/O devices in the system whose SCSI
controller cards are enabled.
LS [path|flash]
PASSword
Displays the LIF contents (boot or flash volume)
of a device.
Defines the password used to control access to
ForthMode. Same as UNIX passwordcommand.
Chapter 4
65
Download from Www.Somanuals.com. All Manuals Search And Download.
Firmware (OBP and PDC)
HP mode boot menu
Com m a n d
Descr ip t ion
PAth [PRI|ALT|CON] [path]
Displays or sets primary, alternate, console, and
keyboard hardware paths. Keyboard path cannot
be modified.
PDT [CLEAR|DEBUG]
Displays or clears Page Deallocation Table (PDT)
information. For use by service personnel only.
PIM_info [cpu#]
[HPMC|TOC|LPMC]
Displays Processor Internal Memory (PIM)
information for current or any CPU.
RemoteCommand node# command
Executes the specified command on the remote
node identified by node number.
RESET [hard|debug]
RESTrict [ON|OFF]
Resets the system state.
Displays or sets restricted access to Forth mode.
SCSI [INIT|RATE] [bus slot
val]
Displays or sets SCSI controller initiator ID or
transfer rate.
SEArch [path]
Displays pathnames for devices with bootable
media in the system.
SECure [ON|OFF]
Displays or sets secure boot mode. If secure mode
is set, the boot process cannot be interrupted.
Only useful if autoboot is on; the system will
autosearch and autoboot.
TIme [cn:yr:mo:dy:hr:mn[:ss]]
VErsion
Displays or sets the realtime clock.
Displays the internal firmware versions.
66
Chapter4
Download from Www.Somanuals.com. All Manuals Search And Download.
Firmware (OBP and PDC)
Enabling Autoboot
En a blin g Au toboot
AUtodisplays or sets the Autoboot or Search flag, which sets the way a
system will behave after powering on. If Autoboot is ON, the system
boots automatically after reset. If AutoSearch is ON and Autoboot is
OFF, the system searches for and displays all I/O devices from which the
system can boot. Changes to a flag take effect after a system reset or
power- on. The default value for both Autoboot and Autosearch is OFF.
Syn ta x
AUto[BOot| SEArch] [ON| OFF]
•
Used alone, this command displays the current status of the Autoboot
and Autosearch flags.
• BOot- If ON, the OS is automatically loaded from the primary boot
path after a power-up or reset. Otherwise, the system displays the
boot menu and waits for interactive boot commands. During an
autoboot, the process pauses for 10 seconds to allow the operator to
stop the boot process.
• SEArch- If ON, the system searches for all I/O devices that it can
boot from and displays a list. Usually disabled because the search can
be time-consuming.
• ON enables the indicated feature.
• OFF disables the indicated feature.
Chapter 4
67
Download from Www.Somanuals.com. All Manuals Search And Download.
Firmware (OBP and PDC)
Enabling Autoboot
E xa m p les
au
This command displays the status of the Autoboot and
Autosearch flags.
Autoboot:ON
Autosearch:ON
au bo
This command displays the current setting of the
Autoboot flag.
Autoboot:ON
au bo on
This command sets the Autoboot flag ON.
Autoboot:ON
68
Chapter4
Download from Www.Somanuals.com. All Manuals Search And Download.
Firmware (OBP and PDC)
HElpcommand
HElpcom m a n d
The helpcommand displays help information for the specified command
or redisplays the boot menu.
Syn ta x
HElp [command]
Used alone, HElp displays the boot menu. Specifying command displays
the syntax and description of the named command.
E xa m p les
The following example illustrate use of this command:
help au
This command displays information for the auto
command.
AUto[BOot|SEArch] [ON|OFF] Display or set the specified flag
AUto boot on
Enable auto boot on next boot.
Disable auto boot on next boot.
Enable auto search on next boot.
Disable auto search on next boot.
AUto boot off
AUto search on
AUto search off
Auto search enables the automatic search of a boot device.
Auto boot enables the autoboot sequence.
Chapter 4
69
Download from Www.Somanuals.com. All Manuals Search And Download.
Firmware (OBP and PDC)
HElpcommand
70
Chapter4
Download from Www.Somanuals.com. All Manuals Search And Download.
5
Con figu r a t ion u t ilit ies
• ts_config
• ccmd
• xconfig
•
Configuration utilities
Two utilities, sppdshand xconfig, allow reading or writing
configuration information. OBP can also be used to modify the
configuration.
The SSP allows the user to configure the node using the ts_config
utility. This is the preferred method for V2500/V2600 servers.
ts_configconfigures the SSP to communicate with the node. The SSP
daemon, ccmd, monitors the node and reports back configuration
information, error information and general status. ts_configmust be
run before using ccmd.
Chapter 5
71
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
ts_config
t s_con fig
ts_config [-display display name]
Any V2500/V2600 nodes added to the SSP must be configured by
ts_configto enable diagnostic and scan capabilities, environmental
and hard-error monitoring, and console access.
Once the configuration for each node is set, it is retained when new SSP
software is installed.
ts_configtasks include:
•
•
•
•
Configuring a node—Adding and removing a node to the SSP
configuration
Configuring the terminal mux—Configuring and removing the
terminal mux on the SSP
Installing a node—Upgrading J TAG firmware, configuring a node
scub_ip address, and resetting a node
Configuration of Multiple-node complex—Configuring V2500/V2600
nodes into a single complex and splitting V2500/V2600 nodes out of a
multiple-node complex.
•
Operational support—Resetting a V2500/V2600 node or multiple-
node complex and starting console sessions.
The user must have root privilege to configure a node or the terminal
mux, because several HP-UX system files are modified during the
configuration.
Sta r t in g t s_con fig
To start ts_configfrom the SSP 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_configfrom a shell (local or remote), ensure that the
DISPLAY environment variable is set appropriately before starting
ts_config.
72
Chapter5
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
ts_config
For example:
$ DISPLAY=myws:0; export DISPLAY
(sh/ksh/sppdsh)
% setenv DISPLAY myws:0
(csh/tcsh)
Also, the -displaystart-up option may be used as shown below:
For example:
# /spp/bin/ts_config -display myws:0
NOTE
For shells that are run from the SSP desktop, the DISPLAY variable is
set (at the shell start-up) to the local SSP display.
ts_con fig op er a tion
The ts_configutility displays an active list of nodes that are powered
up and connected to the SSP diagnostic LAN. The operator selects a node
and configures the selected node. A sample display is shown below.
Figu r e 25
ts_configsa m p le d isp la y
The window has three main parts: the drop-down menu bar, the display
panel, and the message 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 in the message panel at
the bottom of the ts_configwindow. If an action needs to be performed
to configure the node, specific instructions are included.
Chapter 5
73
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
ts_config
ts_configautomatically updates the display when it detects either a
change in the configuration status of any node or a newly detected node.
The node display is not updated while an Action is being processed or
while the user is entering information into an Action dialog.
The upper right corner of the ts_configwindow indicates whether a
The ts_configwindow title includes in parenthesis the name of the
effective user ID running ts_config, either root or sppuser along with
the host name of the SSP.
The ts_configdisplay shows the configuration status of the nodes.
Table 11 shows the possible status values.
Ta b le 11
ts_configst a t u s va lu es
Con figu r a tion
St a tu s
Descr ip tion
Action R eq u ir ed
Upgrade J TAG
firmware
The version of J TAG firmware
running on the SCUB does not
support the capabilities
required to complete the node
configuration process.
Select the node and follow the
instructions given at the bottom of
the ts_config window. ts_config
guides the operator through the
J TAG firmware upgrade procedure.
Not Configured ts_confighas detected the
Select the node and follow the
node on the Diagnostic LAN and
instructions given at the bottom of
the J TAG firmware is capable of the ts_configwindow.
supporting the node
configuration activity and the
node needs to be configured.
ts_configguide the operator
through the node configuration
procedure described later in this
document.
74
Chapter5
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
ts_config
Con figu r a tion
St a tu s
Descr ip tion
Action R eq u ir ed
Active
The node is configured and
answering requests on the
Diagnostic LAN.
None required. This is the desired
status.
Inactive
The SSP node configuration file
contains information about the
specified node, but the node is
not responding to requests on
the Diagnostic LAN.This status
is also shown if a node was
configured and then removed
from the SSP LAN without
being deconfigured.
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,”
“Deconfigure Node,” and click “Yes.”
Node Id
changed
The node is configured and
answering requests on the
diagnostic LAN, but the node ID
currently reported by the node
does not match the SSP
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,”
“Configure Node,” then click
“Configure.” The SSP configuration
information is updated using the
new node ID.
configuration information.
Con figu r a t ion p r oced u r es
The following procedures provide additional details about each
configuration action and are intended as a reference. ts_config
automatically guides the user through the appropriate procedure when a
node is selected.
Up gr a d e J TAG fir m w a r e
NOTE
If the node shows “Not Configured,” do not perform this procedure.
Perform the following procedure only when the status shows “Upgrade
J TAG firmware.”
St ep 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 26.
Chapter 5
75
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
ts_config
Figu r e 26
ts_configsh ow in g n od e 0 h igh ligh ted
information concerning the node. In this step, it tells the user what
action to take next, “This node’s J TAG firmware must be upgraded.
Select “Actions,” “Upgrade J TAG firmware” and “Yes” to upgrade.”
St ep 2. Select “Actions” to drop the pop-down menu and then click “Upgrade
J TAG firmware,” as shown in Figure 27.
Figu r e 27
ts_config“Up gr a d e J TAG fir m w a r e” select ion .
St ep 3. A message panel appears as the one shown in Figure 28. Read the
message. If this is the desired action, click “Yes” to begin the upgrade.
76
Chapter5
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
ts_config
Figu r e 28
Up gr a d e J TAG fir m w a r e con fir m a t ion p a n el
St ep 4. After the firmware is loaded a panel appears as the one shown in Figure
29. Click “OK” and then power-cycle the node to activate the new
firmware.
Figu r e 29
ts_configp ow er -cycle p a n el
to “Not Configured.”
Con figu r e a Nod e
St ep 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 30.
Notice the bottom of the display indicates the Node 0 is not configured
and provides the steps necessary to configure the node.
Chapter 5
77
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
ts_config
Figu r e 30
ts_configin d ica tin g Nod e 0 a s n ot con figu r ed
St ep 2. Select “Actions” and then click “Configure Node,” as shown in Figure 31.
ts_config“Con figu r e Nod e” selection .
Figu r e 31
After invoking ts_configto configure the node, a node configuration
panel appears as the one in Figure 32.
78
Chapter5
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
ts_config
Figu r e 32
ts_confign od e con figu r a t ion p a n el
St ep 3. Enter a name for the V2500/V2600 System. The SSP uses this name as
the “Complex Name” and to generate the IP host names of the Diagnostic
and OBP LAN interfaces. Select a short name that SSP users can easily
relate to the associated system (for example: hw2a, swtest, etc.).
St ep 4. Select an appropriate serial connection for the V2500/V2600 console from
the pop-down option menu in the node configuration panel.
ts_configautomatically assigns the first unused serial port. If the
terminal mux has been configured, 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_configutility automatically changes the IP address of the
diagnostic LAN interface to prevent a duplicate when other nodes are
added to this SSP configuration.
ts_configautomatically updates the local /etc/hosts file with the
names and addresses of the Diagnostic and OBP LAN interfaces.
St ep 5. Click “Configure.”
This updates several SSP files. The node configuration confirmation
panel appears as the one in Figure 33.
Chapter 5
79
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
ts_config
Figu r e 33
ts_configr est a r t w or k sp a ce m a n a ger p a n el.
St ep 6. Read the panel and click “OK.” When the configuration process is
complete, the “Configuration Status” of the node changes to “Active,” as
shown in Figure 34.
Figu r e 34
ts_configin d ica tin g Nod e 0 is con figu r ed
St ep 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 SSP, wait until the final node is added
before restarting the Workspace Manager.
80
Chapter5
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
ts_config
Con figu r e th e scu b_ip a d d r ess
St ep 1. Select the desired node from the list of available nodes.
St ep 2. In the ts_configdisplay panel, select “Actions” and then “Configure
‘scub_ip’ address,” as shown in Figure 35.
Figu r e 35
ts_config“Con figu r e ‘scu b_ip ’ a d d r ess” selection
ts_configchecks the scub_ip address stored in NVRAM on the SCUB
in the node. This would initially be the default address set at the factory.
If the scub_ip address is correct, the panel shown in Figure 36 is
displayed and no action is required. If the node is not detected and
scanned by ccmd, ts_configmay ask you to try again later. The ccmd
detection scan process should take less than a minute.
Figu r e 36
ts_config“SCUB OK” p a n el
St ep 3. If prompted by ts_config(as indicated by the panel in Figure 37), click
“Yes” to correctly set the scub_ip address.
Chapter 5
81
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
ts_config
Figu r e 37
ts_configscu b _ip a d d r ess con figu r a t ion con fir m a t ion
St ep 4. A panel as the shown in Figure 38 appears confirming that the scub_ip
address is set. Click OK.
Figu r e 38
ts_configscu b _ip a d d r ess set con fir m a t ion p a n el
Initiate a node reset to activate the new scub_ip address.
Reset t h e Nod e
St ep 1. Select the desired node from the list of available nodes.
St ep 2. Select “Actions,” then “Reset Node.” This is indicated in Figure 39.
82
Chapter5
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
ts_config
Figu r e 39
ts_config“Reset Nod e” selection
A panel as the one shown in Figure 40 appears.
Figu r e 40
ts_confign od e r eset p a n el
St ep 3. In the Node Reset panel, select the desired “Reset Level” and “Boot
Options,” then click Reset.”
Chapter 5
83
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
ts_config
Decon figu r e a Nod e
Deconfiguring a node removes the selected node from the SSP
configuration. The SSP will no longer monitor the environmental and
hard-error status of this node. Console access to the node is also be
disabled.
St ep 1. Select the desired node from the list of available nodes.
St ep 2. Select “Actions,” then “Deconfigure Node,” then click “Yes.”
Ad d /Con figu r e th e Ter m in a l Mu x
To add or reconfigure the terminal mux, perform the following procedure.
St ep 1. In the ts_configdisplay, select “Actions,” then “Configure Terminal
Mux.”
Select “Add/Configure Terminal Mux.” This is indicated in Figure 41.
Figu r e 41
ts_config“Ad d /Con figu r e Ter m in a l Mu x” select ion
St ep 2. Connect a serial cable from serial port 2 on the SSP to port 1 on the
terminal mux.
St ep 3. A panel shown in Figure 42 display the IP address.
84
Chapter5
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
ts_config
Figu r e 42
Ter m in a l m u x IP a d d r ess p a n el
Rem ove ter m in a l m u x
ts_configdoes not remove the terminal mux if any node consoles are
assigned to terminal mux ports.
St ep 1. Select “Actions,” then “Configure Terminal Mux.”
Con sole session s
ts_configmay also start console sessions by selecting the desired
node(s) and then selecting the “Start Console Session” action as shown in
Figure 43. Figure 44 shows the started console sessions.
Chapter 5
85
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
ts_config
V2500/V2600 SCA (m u lt in od e) con figu r a t ion
single-node complexes. After the system has rebooted to OBP, node 0
becomes the console for the SCA complex.
To configure the two-node system in the example, start ts_configas
described in “Starting ts_config” on page 72. Once ts_confighas
started, a window like that shown in Figure 45 is displayed.
Figu r e 45
SSP su p p or tin g t w o sin gle-n od e com p lexes
example.
St ep 1. Select the nodes by clicking anywhere in the information display for each
node. As the nodes are selected, they become highlighted.
St ep 2. Select “Action” and then “Configure Multinode complex” as shown in
Figure 46.
Chapter 5
87
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
ts_config
Figu r e 46
ts_configCon figu r e Mu lt in od e com p lex selection
St ep 3. When “Configure Multinode complex” is selected, a configuration dialog
appears as shown in Figure 57.
Figu r e 47
Con figu r e Mu ltin od e Com p lex d ia log w in d ow
88
Chapter5
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
ts_config
St ep 4. Enter the required fields into the Configure Multinode Complex dialog
window.
•
•
•
V-Class Complex Name—Current complex name of either node or a
new complex name.
Complex Serial Number—Unique serial number of the complex. This
is not required if the nodes have the same serial numbers.
Complex Key—Number required to enter the Complex Serial
Number.
NOTE
If all of the SCA system complex serial numbers are the same, no
complex key is required.
St ep 5. Select the desired node IDs from the “New Node ID” drop-down lists.
St ep 6. If the console connection must be changed, select appropriate connection
from the “Console Connection” drop-down list.
St ep 7. In the “Hypernode bitmask” section select “POST will determine
bitmask.”
St ep 8. If necessary, select the desired CTI cache size from the “CTI cache size”
drop-down list.
St ep 9. If necessary, select the node-local memory size from the “Node local size”
pull-down list.
NOTE
The default settings for CTI cache and node-local memory are
recommended.
Chapter 5
89
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
ts_config
Figu r e 48
Con figu r e Mu ltin od e Com p lex d ia log w in d ow w it h a p p r op r ia t e
va lu es
St ep 10. Click the “Configure” button to start the configuration. A message box
appears indicating that the configuration has started.
Figu r e 49
Con figu r a tion sta r t ed in for m a t ion box
The following activities occur during the configuration process:
•
•
SSP files are updated based on the new complex and node names.
Essential console server processes are started, and the now-obsolete
server processes are halted.
•
New node information is written to the COP chip in each node.
90
Chapter5
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
ts_config
This information includes:
•
•
•
Node ID
Complex serial number (if it has been modified)
Requested or auto-generated software identifier
•
Configuration Manager Daemon, ccmd, is notified of the new
configuration.
•
•
The shared-memory database of node information is updated.
Multinode configuration parameters are written to NVRAM in each
node. These include:
•
•
•
•
•
Hypernode bitmask
X- and Y-ring information
Node count
CTI cache size
Node-local memory size
•
The boot vector of each node is set to OBP and each node is reset.
When the configuration process is complete, ts_configshows the new
multinode complex, as in Figure 50. The restart process activates the
new SSP root menu which includes customized menus for each complex.
The Workspace Manager must be restarted or else the root menu will be
outdated (the rest of the configuration process is complete).
Chapter 5
91
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
ts_config
Figu r e 50
ts_configsh ow in g n ew ly con figu r ed com p lexes
When remotely running ts_config, the Restart Workspace Manager
step cannot be performed, because it is the SSP Workspace Manager that
needs to be restarted. The Workspace Manager can be restarted at any
time by clicking on the desktop background and selecting Restart
Workspace Manager, then OK.
Any of the configurable parameters on the Multinode Configuration
dialog may be changed by selecting each node and choosing the
“Configure Multinode complex” action. Set the desired options and click
Configure. During a reconfiguration, several of the required fields in the
Multinode Configuration dialog are filled in by ts_config.
V2500/V2600 sp lit SCA con figu r a t ion
ts_configalso provides a “Split Multinode complex” action that takes
an SCA complex and logically splits it into single node systems. Each
The following procedure allows the user to split the SCA system:
St ep 1. In the ts_config window, select the desired nodes.
St ep 2. Select every node in the desired complex, then “Actions,” and then “Split
Multinode complex.” Figure 52 shows the ts_configSplit Multinode
complex panel.
92
Chapter5
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
ts_config
Figu r e 51
ts_configSp lit Mu lt in od e com p lex op er a tion
Figu r e 52
ts_configSp lit Mu lt in od e com p lex p a n el
St ep 3. Enter the complex names for each node. New complex serial numbers
may be assigned. Each node becomes node 0 in a new complex. Figure 53
shows the Split Multinode panel filled in. Click the Split Complex button
to initiate the configuration process.
Chapter 5
93
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
ts_config
Figu r e 53
ts_configSp lit Mu lt in od e com p lex p a n el filled in
The message shown in Figure 54 appears indicating the configuration is
taking place.
Figu r e 54
Figure 55 shows the main ts_configdisplay after the split multinode
operation has completed. It shows the resulting configuration: two single
node complexes (two node 0s) with names assigned in the prior step.
Figu r e 55
ts_configSp lit Mu lt in od e op er a t ion com p let e
94
Chapter5
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
ts_config
ts_con fig files
ts_configeither reads or maintains the following SSP configuration
files:
/etc/hosts
The standard system hosts file, includes entries for the
cabinet related IP addresses.
/etc/services
Service definitions for the console interface.
/etc/
inetd.conf
Contains entries for starting console related processes
/spp/data/
nodes.conf
Contains entries which define the complexes (either
single cabinet or multi-cabinet) managed by the SSP.
This file is maintained by the Configure Node Action of
ts_config, but other commands can also update this
file: delete_node, configure_node, and
split_multinode.
/spp/data/
conserver.cf
Connection definitions for the console interface.
/spp/data/
consoles.conf
Console name to ttylink number resolution. This file is
maintained by the Configure Mux Action of
ts_config.
/spp/data/
<complex_name>
For each newly configured complex, there is a complex-
specific directory that contains complex-specific files,
such as event and console logs. ts_configgenerates
each <complex_name> during configuration.
The nodes.conf file contains most of the configuration management
information. It defines the relationship between complex names,
cabinets (nodes) within that complex and the associated host names and
console port connections.
Each node has an entry in the nodes.conf file as follows:
Chapter 5
95
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
ts_config
NODE Complex Node ID JTAG-hostname OBP-hostname SSP-hostname Console-port
The variables of the entry are defined as follows:
NODE—Keyword designating a cabinet (node) entry.
Complex—Name to which the node (cabinet) is associated.
In a multi-cabinet complex all the cabinets comprise a single system
(complex) and are managed by a single console (the console on cabinet 0).
Each cabinet, however, has its own console that can report diagnostic
information, and there is still a console configuration entry for each
cabinet. These consoles, however, are not normally accessed.
Node ID—The identification of the V-Class node. This number can be 0,
2, 4, or 6.
J tag-hostname—Host name used by the SSP to communicate with the
J TAG firmware on the associated node. J TAG IP addresses are
15.99.111.116 through 15.99.111.131.
Obp-hostname—Host name used for OBP communication (not normally
referenced while administering the complex). OBP IP addresses are
15.99.111.166 through 15.99.111.181.
SSP-hostname—Local host name of the private/diagnostic LAN. The
default host name for this interface is tsdart-d.
Console-port—Name of the physical connection to the node RS-232
console port. The port name is linked to a ttylink service entry via the file
/spp/data/consoles.conf.
The get_node_infoprogram extracts information from the nodes.conf
file.
IMPORTANT
Most SSP configuration is carried out by ts_config. Sometimes
problems are caused by manually editing the files maintained by
ts_config, resulting in it not be able to properly parse the files on its
own.
The ts.installscript is designed not to run after initial installation to
prevent inadvertent removal of changes made to the configuration files
by ts_config. It can be forced to run, however, in order to put all the
configuration files back to factory defaults. To rerun ts.install,
execute the following command:
/spp/scripts/inst/ts.install
96
Chapter5
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
SSP-to-system communications
SSP -to-system com m u n ica tion s
Figure 56 depicts the V-Class server to SSP communications using
HP-UX.
Figu r e 56
SSP -to-syst em com m u n ica t ion s
JTAG
Test AUI
ccmd
ethernet
event_logger
hard_logger
Scan
JTAGFW
memlog
syslog
Private LAN
NFS-FWCP
pciromldr
private ethernet
ethernet
Core AUI
HPUX
spp_pdc
OBP
ccmd
fwcp/nfs
PCI
Global LAN
global ethernet
ethernet
console
messages
RS-232
RS-232
LCD
RS-232A
console messages
console messages/LCD
console
DUART
POST
/test controller
sppconsole
ttylink
Cabinet
consolelogx
remote diagnostic
modem
SSP
A layer of firmware between HP-UX and OBP (Open Boot PROM) called
spp_pdcallows the HP-UX kernel to communicate with OBP. spp_pdc
is platform-dependent code and runs on top of OBP providing access to
the devices and OBP configuration properties.
Chapter 5
97
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
SSP-to-system communications
LAN com m u n ica tion s
There are two ethernet ports located on the SCUB as shown in the
diagram in the upper-left side of the node (dotted line) in Figure 56 on
page 97. These comprise the “private” or diagnostic LAN. The J TAG port
is used for scanning, and the NFS-FWCP port is used for downloading
system firmware via nfsusing the fwcputility, via tftpusing the
pdcflutility, downloading disk firmware using the dfdutilutility
(dfdutiluses tftpfor reading peripheral firmware), and loading
Symbios FORTH code using the pciromldrutility. For more
information on dfdutil, tftp, and pciromldr, see the appropriate
man pages.
The configuration daemon, ccmd, which is located on the SSP obtains
system configuration information over the private LAN from the J TAG
port. It builds a configuration information database on the SSP. 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.
IMPORTANT
Both the B180L and the 712 workstations must have two ethernet
connections: one for the private LAN and one for the global LAN. These
ports are different on each model of workstation. It is important that the
installer connect the LAN cables to the correct connector on the SSP.
The SSP can be placed on the customers Local Area Network using the
SSP’s global ethernet.
SSP h ost n a m e a n d IP a d d r esses
The SSP software installation process assigns the correct IP address to
the appropriate LAN device.
The SCUB IP address 15.99.111.116 is the first SCUB IP address
available on the SSP. If more nodes are added, they are assigned
15.99.111.117, 15.99.111.118, and so on. ts_configkeeps track of
which addresses are assigned.
The SCUB IP host name is “complexname-000n,” where n is the node ID.
The SSP supports multiple complexes (that is, multiple node 0s).
98
Chapter5
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
SSP-to-system communications
Ser ia l com m u n ica tion s
The DUART port on the SCUB provides an RS232 serial link to the SSP.
Through this port HP-UX, OBP, POST (Power-On Self Test) and the Test
Controller send console messages. The SSP processes these messages
using the sppconsoleand ttylinkutilities and the consolelogxlog
file. POST and OBP also send system status to the LCD connected to the
DUART. For more information on sppconsole, ttylink, and
consolelogx, see the appropriate man pages.
NOTE
The second RS-232 port on the workstations are unused and not enabled
at this time.
Chapter 5
99
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
ccmd
ccm d
ccmd(Complex Configuration Management Daemon) is a daemon that
maintains a database of information about the V2500/V2600 hardware.
ccmdalso monitors the system and reports any significant changes in
system status. It supports multiple nodes, multiple complexes and nodes
that have the same node number.
There are two types of related information in the database: node
information (node numbers, IP addresses and scan data) and
configuration data which is initialized by POST. The node information is
scanned from the hardware and processed with the aid of data files at
/spp/data. The POST configuration data is required so that certain
scan based utilities can emulate various hardware functions.
ccmdperiodically sends out a broadcast to determine what nodes are
available. If ccmdcan not talk to a node that it previously reached, it
sends a response to the console and the log. If it establishes or re-
establishes contact, or if a node powers up, ccmdreads hardware
information from the node and interrogates it through scan to determine
the node configuration. From this data, a complete database is built on
the SSP that will be used for all scan based diagnostics.
Once running, ccmdchecks for power-up, power-down, reset, error, and
environmental conditions on regular intervals. If at any time ccmd
detects a change in the configuration, it changes the database, updates
the /spp/data/complex.cfgfile, sets up a directory in /spp/datafor
each complex and initializes a node_#.pwrfile for each node in the
complex specific subdirectory.
If ccmddetects an error condition, it invokes an error analysis tool
(hard_logger) that logs and diagnoses error conditions. After an error
is investigated, ccmdreboots the node or complex associated with the
error. The reboot operation can be avoided with the use of the
autoreset [complex] on|off|chk utility in /spp/scripts.
ccmdis listed in /etc/inittab as a process that should run continuously. It
may be started manually, but since it kills any previous copies at start-
up, diagnostic processes that may be running will be orphaned. Only one
copy of ccmdmay run on a SSP.
100
Chapter5
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
ccmd
If started with no options, ccmddisassociates itself from the terminal or
window where it was started. It instead reports to the console window
and the file /spp/data/ccmd_log.
If ccmdis sent a SIGHUP, it regenerates the database.
All scan-based operations require ccmd. If POST is unable to run, then
ccmdis not able to read configuration data and some system information
is not accessible.
ccmdworks in co-operation with most utilities to share a common
ethernet port and Diagnostic (DART) bus. In general, the scan data is
sent via UDP. The DART bus should be separate from any general
purpose ethernet bus. If the DART bus is improperly set-up, ccmdcannot
run properly.
Since ccmdcan become corrupted by bad data, it may be necessary to kill
the ccmdprocess to refresh the SSPs configuration image. Killing the
ccmdprocess is not always enough. If the “heart beat” LED from the
SCUB is not functioning then ccmdis unable to communicate with the
system. A pingcommand to the SCUB will not be successful either. In
this case, the system or node must be powered down to reset the SCUB
and re-establish communication with the SSP.
Chapter 5
101
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
xconfig
xcon fig
xconfigis the graphical tool that can also modify the parameters
initialized by POST to reconfigure a node.
The graphical interface allows the user to see the configuration state.
configuration parameters are hidden to the user. The drawback of
xconfigis that it can not be used as a part of script-based tests, nor can
it be used for remote debug.
xconfigis started from a shell. Information on node 0 is read and
interpreted to form the starting X-windows display shown in Figure 57.
The xconfig window appears on the system indicated by the
using the following command:
% xconfig -display system_name:0.0
The xconfig window has two display views: one shows each component as
a physical location in the server, the other shows them as logical names.
Figure 57 and Figure 58 show the window in each view, respectively. To
switch between views, click on the Help button in menu bar and then
click the Change names option. See “Menu bar” on page 105.
102
Chapter5
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
xconfig
Figu r e 58
xconfigw in d ow —logica l n a m es
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 SSP’s image of the node.
When the user is satisfied with the new configuration, it should be copied
back into the node, and the node should be reset to enable the changes.
104
Chapter5
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
xconfig
The main xconfigwindow has three sections:
•
•
•
Menu bar—Provides additional capability and functions.
Node configuration map—Provides the status of the node.
Node control panel—Provides the capability to select a node and
control the way data flows to it.
Men u b a r
The menu bar appears at the top of the xconfigmain window. It has
four menus that provide additional features:
•
•
File menu—Displays the file 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 configuration.
Help menu—Displays the help and about options.
The menu bar is shown in Figure 59.
Figu r e 59
xconfigw in d ow m en u ba r
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 5
105
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
xconfig
Nod e con figu r a tion m a p
The node configuration map is a representation of the left and right side
views of a node as shown in Figure 60.
Figu r e 60
xconfigw in d ow n od e con figu r a tion m a p
106
Chapter5
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
xconfig
The button boxes are positioned to represent the actual boards as viewed
from the left and right sides. Each of the configurable 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 deconfigure
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
Nod e con t r ol p a n el
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 flow between the node and the xconfigutility. It is shown in
Figure 61.
Chapter 5
107
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
xconfig
Figu r e 61
xconfigw in d ow n od e con t r ol p a n el
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 pull-
down 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.
108
Chapter5
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
xconfig
When a new node is selected and available, its data is automatically read
and the node configuration map updated. The data image is kept on the
SSP 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 reconfigures 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 SSP 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 5
109
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
Configuration utilities
Con figu r a tion u tilities
V2500/V2600 diagnostics provides utilities that assist the user with
configuration management.
a u t or eset
autoresetallows 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. autoresetoccurs if a
ccmd_reset file does not exist in the complex-specific directories
Arguments to autoresetarguments include <complex_name> onand
<complex_name> off or chk.
The output of the chkoption for a complex name of hw2a looks like:
Autoreset for hw2a is enabled.
or
Autoreset for hw2a is disabled.
NOTE
autoresetdetermines the behavior of ccmdwhen it encounters an error
condition. ccmdmakes its decision whether to reset a complex
immediately after running hard_logger. Enabling autoresetafter
hard_loggerhas run does not reset the complex.
est _con fig
est_configis a utility that builds the node and complex descriptions
used by est. est_configreads 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 configuration directory can be specified using the -p
argument. est_configworks across all nodes unless a specific node or
complex is requested with the -noption.
110
Chapter5
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
Configuration utilities
NOTE
If there is a node_#.pwr file that is older than the node_#.cfg file, existing
node configuration files do not need to be updated.
r ep or t_cfg
This utility generates a report summarizing the configuration of all
nodes/complexes specified on the command line. The format of
report_cfgis as follows:
report_cfg [<node id|complex> [<node id|complex> ...]]
node idmay be a node number, IP name, or “all.” If no node ID is
specified, the utility defaults to all nodes in the current complex.
One or more of the options in Table 12 must be specified:
Ta b le 12
report_cfgop tion s
-d
-s
-a
-A
-i
-m
-p
Show all details
Show summary only
Show summary and details (same as -d and -s)
Show ASIC detail
Show I/O detail
Show memory detail
Show processor detail
If the report_cfgtool detects any nodes of complexes that contain SCA
DIMMS and some memory boards that are not populated with STACS, it
generates a report.
Example configuration report:
The system inventory has determined that you’ll need to order 8 SCA Upgrade Kits
in order to connect this cabinet with other SCA cabinets. These upgrade kits are
available by additionally ordering opt. 010 of the required SCA HyperLink product
(A5518A or A5519A). You may also have to order additional memory DIMMs, memory
boards and or processor boards to meet the minimum requirements for a SCA
configuration. Refer to the HP 9000 V-Class Ordering Guide for details.
Chapter 5
111
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
Configuration utilities
Effects of h a r d w a r e a n d softw a r e d econ figu r a tion
report_cfgcounts all processors, STACs, SMACs, SAGAs and ERACs
if POST has not marked them as empty. This results in ASICs and
processors being included in the summary count even though they may
have failed or have been deconfigured by software. This is necessary
because POST deconfigures STACs in a single node configuration. To
allow the tool to count these ASICs, it must report all ASICs that are
installed, not just those enabled by POST.
report_cfgincludes all DIMMs that POST has not marked as empty. If
the user deconfigures a SMAC with software or the SMAC fails the
POST selftest, POST marks the DIMMs on that SMAC as empty. If
POST has written valid size information into the BCM for a DIMM,
report_cfgreports the physical size reported by POST.
For example, if a node has both 80- and 88-bit DIMMs, POST
reconfigures the 88-bit DIMMs to behave as 80-bit DIMMs, and the
system logically behaves as if it has all 80-bit DIMMs. report_cfg,
however, distinguishes (using the physical attribute in the BCM)
between the 80- and 88-bit DIMMs in its reports.
Another example would be a system that contains 16 GBytes of memory
but half of the DIMMs are deconfigured by software. report_cfgstill
reports that the system contains 16 Gbytes of memory.
r ep or t_cfg su m m a r y r ep or t
To obtain a system summary report, use the -soption for the command.
The following is a sample summary report by report_cfg:
report_cfg -s
Complex name
Complex serial number Node ID
------------------ --------------------- -------
hw4a
hw4a
USR1234567
USR1234567
0
2
Cabinets:
Processors:
Processor boards:
Memory boards:
TAC chips:
2
30
30 (30 singles, 0 duals)
16
16
Enabled Memory (Mb): 8192
88-bit 128Mbyte: 112
112
Chapter5
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
Configuration utilities
r ep or t_cfg ASIC r ep or t
To obtain a report on the ASICs in a complex, use the -Aoption. The
following is a sample ASIC report by report_cfg:
report_cfg -A
Complex
|Node#|
MIB COP
|
SCUB COP
====================+=====+=======================+=======================
hw2a
hw2a
0 A5074-60002 00 a 3845 A5074-60003 00 b 3830
2 A5074-60002 00 a 3840 A5074-60003 00 b 00XA
+----- ASIC revisions ------+
Complex
|Node| Slot | PAC | MAC | TAC | RAC |
====================+====+=======+======+======+======+======+
hw2a
hw2a
hw2a
hw2a
hw2a
hw2a
hw2a
hw2a
hw2a
hw2a
hw2a
hw2a
hw2a
hw2a
hw2a
hw2a
0
0
0
0
0
0
0
0
2
2
2
2
2
2
2
2
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
2
2
2
2
2
2
2
r ep or t_cfg I/O r ep or t
To obtain an I/O report, use the -ioption. The following is a sample I/O
report by report_cfg:
report_cfg -i
Complex
|Node#|
MIB COP
|
SCUB COP
====================+=====+=======================+=======================
hw2a
hw2a
0 A5074-60002 00 a 3845 A5074-60003 00 b 3830
2 A5074-60002 00 a 3840 A5074-60003 00 b 00XA
Complex
|Node#|I/O board | COP
====================+=====+==========+=======================
hw2a
hw2a
hw2a
hw2a
0
0
2
2
IORF_B
IORF_A
IOLF_B
IOLF_A
A5080-60001 00 a 3821
A5080-60001 00 a 3821
A5080-60001 00 a 3821
A5080-60001 00 a 3821
Chapter 5
113
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
Configuration utilities
r ep or t_cfg m em or y r ep or t
To obtain a report on the memory in a complex, use the -moption. The
following is a sample memory report by report_cfg:
report_cfg -m
Complex
|Node#|
MIB COP
|
SCUB COP
====================+=====+=======================+=======================
hw2a
hw2a
0 A5074-60002 00 a 3845 A5074-60003 00 b 3830
2 A5074-60002 00 a 3840 A5074-60003 00 b 00XA
| 80-bit | 88-bit
|
|
| | 1 | 2 | | 1 | 2
| 3 | 2 | 5 | 3 | 2 | 5
| 2 | 8 | 6 | 2 | 8 | 6
|Mem. |
|Node|Board|
Complex
COP
============+====+=====+=======================+===+===+===+===+===+====
hw4a
hw4a
hw4a
hw4a
hw4a
hw4a
hw4a
hw4a
hw4a
hw4a
hw4a
hw4a
hw4a
hw4a
hw4a
hw4a
0 MB0L A5078-60003 01 a 00XB
0 MB1L A5078-60003 01 a 00XB
0 MB2R A5078-60003 01 a 00X2
0 MB3R A5078-60003 01 a 00X2
0 MB4L A5078-60003 01 a 00XA
0 MB5L A5078-60003 01 a 00X2
0 MB6R A5078-60003 01 a 00XA
0 MB7R A5078-60003 01 a 00X2
2 MB0L A5078-60003 01 a 00XA
2 MB1L A5078-60003 01 a 3842
2 MB2R A5078-60003 01 a 00XA
2 MB3R A5078-60003 01 a 00XB
2 MB4L A5078-60003 01 a 3843
2 MB5L A5078-60003 01 a 00XD
2 MB6R A5078-60003 01 a 00XB
2 MB7R A5078-60003 01 a 00XD
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
114
Chapter5
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
Configuration utilities
r ep or t_cfg p r ocessor r ep or t
To obtain a report on the processor in a complex, use the -poption. The
following is a sample processor report by report_cfg:
report_cfg -p
Complex
|Node#|
MIB COP
|
SCUB COP
====================+=====+=======================+=======================
hw2a
hw2a
0 A5074-60002 00 a 3845 A5074-60003 00 b 3830
2 A5074-60002 00 a 3840 A5074-60003 00 b 00XA
Complex
|Node#|Processor | COP
| CPU rev
====================+=====+==========+=======================+========
hw2a
hw2a
hw2a
hw2a
hw2a
hw2a
hw2a
hw2a
hw2a
0
0
0
0
0
0
0
0
0
PB0L_A
PB1R_A
PB1L_A
PB4L_A
PB5L_A
PB0L_B
PB1L_B
PB4L_B
PB5L_B
A5077-60005 00 a 00XA
A5492-60001 00 b 00XC
A5491-60001 00 a 00XA
A5492-60001 00 b 00XB
A5492-60001 00 a 00XB
A5077-60005 00 a 00XA
A5491-60001 00 a 00XA
A5492-60001 00 b 00XB
A5492-60001 00 a 00XB
2.0
2.3
2.0
3.0
2.0
2.0
2.0
2.0
2.0
Complex
|Node#|Processor | COP
| CPU rev
====================+=====+==========+=======================+========
hw2a
hw2a
hw2a
hw2a
hw2a
hw2a
2
2
2
2
2
2
PB2L_A
PB2R_A
PB3R_A
PB4L_A
PB5L_A
PB4L_B
A5491-60001 00 a 00XA
A5492-60001 00 a 00XA
A5491-60001 00 a 00XA
A5492-60001 00 b 00XC
A5491-60001 00 a 00XA
A5492-60001 00 b 00XC
2.0
2.0
2.0
2.0
2.0
2.3
xsecu r e
xsecureis an application that helps make a V2500/V2600 class SSP
secure from external sources. This tool disables modem and LAN activity
to provide an extra layer of security for the V2500/V2600 system.
xsecuremay 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.
Chapter 5
115
Download from Www.Somanuals.com. All Manuals Search And Download.
Configuration utilities
Configuration utilities
If the command line [-on | -off | -check]options are used,
xsecuredoes 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 SSP is secure. A green indicator and the
appropriate label shows that the network is available and the SSP may
be accessed through the ethernet port.
In order for xsecureto work properly the SSP, console cables, terminal
mux and modems must be configured in specific ways. The SSP J TAG
connections, OBP connections and an optional terminal mux must all be
connected to the Diagnostic LAN and identified in the /etc/hostsfile
as tsdart-d. The sppconsole serial cable must be connected to serial
port 1 and to node 0. An optional modem may be connected to serial port
2.
116
Chapter5
Download from Www.Somanuals.com. All Manuals Search And Download.
6
H P -UX Op er a t in g Syst em
related to using HP-UX V11.0 and HP-UX V11.10 on V-Class servers.
that HP-UX V11.10 be installed. Topics covered in this section include:
•
•
•
HP-UX on the V2500/V2600
Starting HP-UX
Stopping HP-UX
Chapter 6
117
Download from Www.Somanuals.com. All Manuals Search And Download.
HP-UX Operating System
HP-UX on the V2500/V2600
HP -UX on th e V2500/V2600
In general HP-UX administration tasks are performed on V-Class
servers as they are on other HP servers. One difference is that V-Class
servers run the HP-UX kernel only in 64-bit mode. This facilitates
addressing the larger memory capacity available on the V2500/V2600.
However, both 32-bit and 64-bit applications may be run simultaneously
on the server.
Disp la yin g System In for m a t ion
This section gives brief information on the model, top, and ioscanHP-
UX commands. More HP-UX information is available from the following
Web site.
http://docs.hp.com/
The modelcommand prints the hardware series and model for the
machine it is issued on. On V2500/V2600 servers it displays information
as shown in the command example below.
# model
9000/800/V2500
For details, see the model(1) man pages.
The topcommand displays information on the top processes (based on
CPU use) on the system, and lists CPU utilization data for the system’s
processors. Because V-Class servers can have many processors, you may
want to issue top -hwhen using this command. The -hoption
suppresses printing individual lines of processor information, instead
printing only a one-line system average. This makes room on the screen
for showing the active processes running on the system. For more
information, see the top(1) man pages.
Listin g th e Ser ver Ha r d w a r e Con figu r a tion
The ioscanutility scans the system’s hardware and lists all hardware
found, including processors, memory, I/O devices, and interface cards. On
V-Class servers, ioscanalso reports PCI controllers and the core utility
controller and its connections to the Service Support Processor. For more
details, see the ioscan (1M) man pages.
118
Chapter6
Download from Www.Somanuals.com. All Manuals Search And Download.
HP-UX Operating System
HP-UX on the V2500/V2600
On multiple-cabinet V2500/V2600 servers, the first component of the
hardware path indicates which cabinet a hardware component resides
upon.
Hardware on cabinet ID 0 is listed with a first hardware path field
starting at 0, hardware on cabinet ID 2 is listed starting at 64, cabinet
ID 4 starts at 128, and cabinet ID 6 starts at 192.
For example, a disk on cabinet ID 0 could have a hardware path of:
1/2/0.9.0
The above disk is on cabinet ID 0, is connected to PCI bus 1, slot 2, and
cabinet ID 2 has a hardware path of:
65/2/0.9.0
The above disk is on cabinet ID 2, and is connected to PCI bus 65, slot 2,
and has a target (SCSI ID) of 9. This corresponds to the top left PCI card
cage of cabinet ID 2, as shown in Table 13.
The following table lists the hardware path numbering for key V2500/
V2600 system components as they are numbered on the various cabinets
in a multiple-cabinet V2500/V2600 server.
Ta b le 13
Ha r d w a r e Pa t h Nu m b er in g for V2500/V2600 Ca b in ets
V2500/V2600
Ca b in et ID
F ir st F ield of
Ha r d w a r e P a th
Descr ip t ion of
Ha r d w a r e Com p on en t
Cabinet ID 0
0–7
8
PCI I/O bus bridges (card cages)
Memory
15
Core utilities board
16–47
64–71
72
Processors (PA-RISC CPUs)
PCI I/O bus bridges (card cages)
Memory
Cabinet ID 2
79
Core utilities board
80–111
Processors (PA-RISC CPUs)
Chapter 6
119
Download from Www.Somanuals.com. All Manuals Search And Download.
HP-UX Operating System
HP-UX on the V2500/V2600
V2500/V2600
Ca b in et ID
F ir st F ield of
Ha r d w a r e P a th
Descr ip t ion of
Ha r d w a r e Com p on en t
Cabinet ID 4
128–135
136
PCI I/O bus bridges (card cages)
Memory
143
Core utilities board
144–175
192–199
200
Processors (PA-RISC CPUs)
PCI I/O bus bridges (card cages)
Memory
Cabinet ID 6
207
Core utilities board
208–239
Processors (PA-RISC CPUs)
Con figu r in g HP -UX for V-Cla ss Ser ver s
HP-UX V11.0 provides several tuned parameter sets that are useful on
HP V-Class servers. Configuring HP-UX with these parameter sets can
improve your V-Class server’s performance when using it for different
purposes, such as scientific, data processing, or mixed interactive use.
Using the SAM utility (/usr/sbin/sam), you can configure an HP-UX
kernel for HP V-Class servers. To do so, select Kernel Configuration, then
the Configurable Parameters subarea, and apply the tuned parameter
set for your type of server use via the Actions menu.
HP -UX p a r a m et er set s
HP-UX kernel configurations are provided for the following types of V-
Class server use:
•
Scientific and technical use—Servers running applications that have
very large data sets and may have long processing times. Examples
include NASTRAN, Abaqus, mechanical and electrical design
applications, and fluid dynamics applications.
The “V-Class Technical Server” tuned parameter set provides HP-UX
kernel parameter settings for running such workloads on HP V-Class
servers.
120
Chapter6
Download from Www.Somanuals.com. All Manuals Search And Download.
HP-UX Operating System
HP-UX on the V2500/V2600
•
•
Dedicated commercial data processing use—Servers whose use is
restricted for online transaction processing (OLTP), running Oracle,
and running other data processing workloads. These systems provide
limited, if any, interactive user access.
The “OLTP/Database Server System” tuned parameter set provides a
good HP-UX configuration for using HP V-Class servers for dedicated
commercial data processing.
Mixed interactive and data processing use—Servers used for
interactive user log-ins, and for running OLTP/data processing
workloads and miscellaneous other applications.
The “OLTP/Database Monolithic System” tuned parameter set is
appropriate for mixed-use V-Class servers.
Mu ltip le-ca bin et k er n el con figu r a tion s
The following are notable initial kernel parameter settings for multiple-
cabinet V2500/V2600 servers. There settings are provided when
installing HP-UX 11.10 on multiple-cabinet servers.
•
•
•
maxuprc—Maximum number of user processes.
Initial SCA value: 256
maxusers—The MAXUSERS value, used in various kernel formulae.
Initial SCA value: 256
max_thread_proc—Maximum number of threads allows in each
process.
Initial SCA value: 500
•
maxswapchunks—Maximum number of swap chunks. The size of
each swap chunk is defined by the swchunk kernel parameter, which
specifies the number of 1 KByte blocks.
Initial SCA value: 5000
NOTE
Note that the maxswapchunks parameter setting (and the swchunk
setting) may need to be adjusted based on your system’s swap space and
crash dump needs.
These tuned parameter sets are available from the SAM utility’s
Configurable Parameters subarea, as described above, and are stored as
files in the following directory.
Chapter 6
121
Download from Www.Somanuals.com. All Manuals Search And Download.
HP-UX Operating System
HP-UX on the V2500/V2600
/usr/sam/lib/kc/tuned
Refer to the SAM online help for examples and details on using kernel
parameters.
P r ocess a n d Th r ea d “Ga n g Sch ed u lin g”
HP-UX V11.0 includes support for kernel threads and provides a “gang
scheduling” feature for managing how threads belonging to the same
process or application are executed.
The HP-UX gang scheduler permits a set of MPI processes, or multiple
threads from a single process, to be scheduled concurrently as a group.
Gang scheduling is enabled and disabled by setting the MP_GANG
environment variable to ONor OFF.
The gang scheduling feature can significantly improve parallel
application performance in loaded timeshare environments that are
oversubscribed. Oversubscription occurs when the total number of
runnable parallel threads, runnable MPI processes, and other runnable
processes exceeds the number of processors in the system.
Gang scheduling also permits low-latency interactions among threads in
shared-memory parallel applications.
Only applications using the HP-UX V11.0 MPI or pthread libraries can
be gang scheduled. Because HP compiler parallelism is primarily built
on the pthread library, programs compiled with HP compilers can benefit
from gang scheduling.
For more details, refer to the gang_sched(7) man page.
H P -UX 11.10 SCA E n h a n cem en ts
Hewlett-Packard’s Scalable Computing Architecture (SCA) design allows
for multiple resource localities (or “locality domains”) to be combined to
form a single system running a single instance of the HP-UX operating
system. One example of an SCA system is a multiple-cabinet HP V2500/
V2600 server where each cabinet comprises a locality domain.
HP-UX V11.10 provides SCA enhancements. These include a utility
(mpsched) as well as system calls and library routine extensions for
controlling how processes and threads are launched, where they are
placed for execution, whether they may migrate (move) during execution,
and how they use memory. These SCA interfaces and programming
122
Chapter6
Download from Www.Somanuals.com. All Manuals Search And Download.
HP-UX Operating System
HP-UX on the V2500/V2600
extensions also provide system inquiry features for retrieving
information about the current hardware topology, as well as thread and
process inquiry features. Both traditional system architectures as well as
SCA systems are supported by the HP-UX 11.10 enhancements.
HP -UX SCA Fea t u r es
HP-UX V11.10 SCA programming and launch features provide the
following capabilities.
•
Inquiry Features—Provide system hardware topology information,
thread and process binding information, and thread and process
launch policy information.
You can print or retrieve information about the system hardware
configuration using the mpschedutility, the mpctlsystem call, and
pthread library features. These interfaces also allow for retrieving
information about thread and process bindings and launch policies.
•
Targeting and Binding—Provide locality domain, processor, and
memory targeting and binding.
You can specify the locality domain or processor on which a process
runs by using the mpschedcommand, the mpctlsystem call, and the
pthread interfaces pthread_processor_bind_npand
pthread_ldom_bind_np.
You also can specify the locality from which a process’ memory is
allocated via the mmapand shmgetsystem calls.
•
Launch and Scheduling—Provide launch policies for threads and
processes and support for “gang scheduling” of threads and processes.
You can set the launch policy for a process with the mpschedutility,
the mpctlsystem call, and the pthread interface
pthread_launch_policy_np. The launch policies supported in HP-
UX 11.10 include the following.
•
None—The system tries to launch threads and processes in a
manner that provides the best performance, though applications
should not rely on this providing any specific launch behavior.
(This is the default policy for launching threads and processes.)
•
Round Robin—Alternate among all localities until all localities
have been selected once, then start over as needed.
Chapter 6
123
Download from Www.Somanuals.com. All Manuals Search And Download.
HP-UX Operating System
HP-UX on the V2500/V2600
•
•
•
Fill First—Fill a locality first, then spill over to another locality, as
needed. Once all localities are filled, start over as needed.
Packed—Place all threads or processes in the same locality; do not
spill over.
least-loaded at the time of its creation.
Gang scheduling of threads and processes is supported through the
mpsched -goption and the MP_GANGHP-UX environment variable.
Details are provided in the gang_sched(7) man page and in the
section “Process and Thread “Gang Scheduling”” on page 122.
More details about HP-UX programming, scheduling, and launch
enhancements are available in the HP-UX V11.10 online man pages and
in the HP-UX SCA Programming and Process Management White Paper.
124
Chapter6
Download from Www.Somanuals.com. All Manuals Search And Download.
HP-UX Operating System
Starting HP-UX
Sta r t in g HP -UX
Bringing the V-Class server to a usable state involves two systems and
their hardware and software. This section provides a brief overview of
the process; for complete instructions, see Managing Systems and
Workgroups. Additional information is contained in the V2500/ V2600
SCA HP-UX System Guide. This section describes:
A V-Class server consists of two systems:
•
System Support Processor (SSP)
•
•
•
•
Boots the V-Class server
Monitors the V-Class server for hardware errors
Debugs a hung system
Runs HP-UX
•
V-Class cabinet
•
•
Hosts OpenBoot PROM (OBP) software
Runs HP-UX
The main firmware interface, the OBP boot menu, provides a
straightforward interface for managing a system before HP-UX boots.
The OBP menu is available through the V-Class console interface.
In multiple-cabinet V2500/V2600 SCA systems, each V2500/V2600
cabinet runs its own copy of the firmware. Normally during booting you
only need to interact with the OBP menu on cabinet ID 0, which serves
as the “monarch” or master cabinet. The other cabinets (IDs 2, 4, and 6, if
present) run the same set and version of firmware, but are considered to
be “serf” cabinets under control of the monarch cabinet once OBP starts.
IMPORTANT
Only I/O devices on cabinet ID 0 may be used as the boot device for a V-
Class server. Likewise, only logical volumes that reside entirely on
cabinet ID 0 may be used as the boot device.
Chapter 6
125
Download from Www.Somanuals.com. All Manuals Search And Download.
HP-UX Operating System
Starting HP-UX
Start up, or boot, HP-UX after the operating system has been completely
shut down or partially shut down to perform system administration
tasks. The boot procedure differs according to the value of the Autoboot
flag. See “Enabling Autoboot” on page 67 for information on how to set
Autoboot. After you power-up your V-Class server, if Autoboot is set to:
• ON, OBP automatically starts HP-UX. (Press the ESC key within 10
seconds to interrupt the boot process and enter bootmenu commands.)
• OFF, the user must:
•
Start OBP at the SSP’s HP-UX prompt by entering the following
command:
do_reset
•
Start the V-Class server using default values at OBP’s default
prompt by entering the following command:
boot
P ow er -On Seq u en ce
Turn on the SSP power and allow it to boot before powering on the V-
Class server’s cabinets. This allows the SSP to be used to monitor and
control the V-Class server as it boots is used.
The following is the sequence for powering on an HP V-Class server and
its SSP:
St ep 1. Power on the SSP and allow it to boot HP-UX.
St ep 2. Power on the V-Class server cabinets.
On multiple-cabinet V2500/V2600 SCA systems, the serf cabinets
(cabinet IDs 2, 4, and 6, if present) should be powered on before the
monarch cabinet (cabinet ID 0). This helps ensure that all cabinets
synchronize following power on self test.
St ep 3. Select a device on V-Class cabinet ID 0 from which to boot HP-UX, as
needed.
The OBP menu’s SEARCH command searches for bootable devices
connected on the cabinet. Only devices on cabinet ID 0 may be booted.
You can designate an I/O device to be the primary (PRI) or alternate
(ALT) boot device by using the OBP menu’s PATHcommand.
126
Chapter6
Download from Www.Somanuals.com. All Manuals Search And Download.
HP-UX Operating System
Starting HP-UX
St ep 4. Issue the OBP menu’s BOOTcommand to boot HP-UX on the V-Class
server.
You can set the server to automatically boot HP-UX if you have also set a
primary boot device (PRI). The OBP menu provides the AUTO BOOT
option, which causes the server to automatically boot HP-UX from the
primary boot device when AUTO BOOT is set to ON.
If a cabinet is already powered on before the SSP booted, the cabinet can
be reset from the SSP after it boots, using the do_resetcommand.
Boot va r ia bles
Several variables affecting the boot process can be set using the HP boot
(OBP) menu. For example, you can set the server to automatically
proceed to boot HP-UX by setting the AUTO BOOToption to ONand
setting the PRIboot path variable.
Boot variable settings are stored in non-volatile memory (NVRAM)
residing on the utility board of each V-Class server cabinet. These
variables are stored permanently until they are modified using the HP
boot menu interface. Refer to Chapter 4, “Firmware (OBP and PDC)” for
more information.
On multiple-cabinet V-Class servers the boot variable settings for the
monarch cabinet (cabinet ID 0) determine the server’s boot-time
behavior.
You should ordinarily need to interact with only the monarch cabinet’s
OBP menu, although the RC(RemoteCommand) option is available for
interacting with the OBP menus on other cabinets. See also “Assuming
control of the console” on page 51.
Chapter 6
127
Download from Www.Somanuals.com. All Manuals Search And Download.
HP-UX Operating System
Starting HP-UX
Ta b le 14
Boot va r ia b les
Va r ia b le
Descr ip t ion
AUto BOot [ON|OFF]
If set to ON, the server automatically boots HP-
UX from the primary (PRI) device during system
startup or reset. When set to OFFthe server boots
to the OBP menu interface.
AUto SEArch[ON| OFF]
AUto Force [ON| OFF]
If set to ON, the server searches for and lists all
bootable I/O devices.
If set to ON, then OBP allows HP-UX to boot even
if one or more cabinets does not complete power
on self test. When set to OFF, all cabinets must
successfully pass power on self test for OBP to
permit the server to boot HP-UX.
BootTimer [seconds]
PAth [PRI|ALT|CON][path]
SECure [ON|OFF]
Sets the number of seconds for the system to wait
before booting. This is used to allow external
mass storage devices to come online.
Displays and sets primary, alternate, and console
hardware paths. Keyboard path is displayed but
cannot be modified.
If set to ON, enables secure boot mode. If set, the
boot process cannot be interrupted. Only useful if
autoboot is ON; the system will autosearch and
autoboot.
R eview in g t h e sta te of t h e file system
During the start-up process, the /sbin/bcheckrcscript executes
/usr/sbin/fsclean. This command determines the shut down status
of the system and returns three possibilities:
1. Proper file system shut down
The startup process continues, and the following message is
displayed:
/usr/sbin/fsclean:/dev/dsk/0s0(root device) ok file system is OK, not running
fsck
2. Improper file system shut down
128
Chapter6
Download from Www.Somanuals.com. All Manuals Search And Download.
HP-UX Operating System
Starting HP-UX
The start-up process is interrupted:
/usr/sbin/fsclean:/dev/dsk/0s0 not ok run fsck FILE SYSTEM(S) NOT PROPERLY
SHUTDOWN, BEGINNING FILE SYSTEM REPAIR.
At this point, the system runs /usr/sbin/fsckin a mode that
corrects certain inconsistencies in the file systems without your
intervention and without removing data. The fsckcommand does
one of the following:
•
•
Repairs and reboots the system, incorporating the changes
Prompts the user to run the fsckcommand manually. If fsck
needs to be run manually, see the fsck(1m) manpage
3. Other errors detected
An error message displays (for example, unable to open a specified
device file), the start-up process ends, and the problem will have to be
solved before proceeding.
Chapter 6
129
Download from Www.Somanuals.com. All Manuals Search And Download.
HP-UX Operating System
Stopping HP-UX
Stop p in g HP -UX
This section provides a brief overview of the process; for complete
instructions, see Managing Systems and Workgroups. Additional
information is contained in the V2500/ V2600 SCA HP-UX System
Guide.
Typically, the system is shut down to:
•
Put it in single-user state so that the system can be updated or to
check file systems.
•
Turn it off in order to perform a task such as installing a new disk
drive.
CAUTION
Never stop the system by turning off the power. Stopping the system
improperly can corrupt the file system. Use the shutdownor reboot
commands.
Sh u t d ow n con sid er a t ion s
Only the system administrator or a designated superuser can shut down
the system.
The /sbin/shutdowncommand:
•
Warns all users to log out of the system within a grace period you
specify
•
•
•
•
•
Halts daemons
Kills unauthorized processes
Unmounts file systems
Puts the system in single-user mode
Writes the contents of the I/O buffers to a disk
CAUTION
Do not run shutdownfrom a remote system via rloginif a network
service is used. The shutdown process logs the user out prematurely and
returns control to the console. Run shutdownfrom the sppconsole
window on the SSP.
130
Chapter6
Download from Www.Somanuals.com. All Manuals Search And Download.
HP-UX Operating System
Stopping HP-UX
See the shutdown man page for a complete description of the shutdown
process and available options.
Chapter 6
131
Download from Www.Somanuals.com. All Manuals Search And Download.
HP-UX Operating System
Stopping HP-UX
R ebootin g t h e syst em
To shutdown HP-UX and reboot the V-Class server, perform the
following steps:
St ep 1. If the server is running HP-UX, log in to the server as root.
St ep 2. Check activity on the server and warn users of the impending server
reboot.
If HP-UX is hung, to reboot HP-UX you may need to reset the server. See
“Resetting the V2500/V2600 server hardware” on page 134.
St ep 3. Change to the root directory. Enter:
cd /
St ep 4. Shut down the system using the shutdownor rebootcommand. Enter:
shutdown -r
or
reboot
Progress messages detailing system shutdown activities print to the
terminal. Upon reaching run-level 0, the system:
•
•
Restarts in single-user mode
Displays the root prompt
See the shutdown and reboot man pages for complete descriptions of the
commands and available options.
132
Chapter6
Download from Www.Somanuals.com. All Manuals Search And Download.
HP-UX Operating System
Stopping HP-UX
Sh u t t in g d ow n t h e syst em
To shut down the V-Class server, perform the following steps:
St ep 1. Login to the server as root.
St ep 2. Check activity on the server and warn users of the impending server
shutdown.
St ep 3. Change to the root directory. Enter:
cd /
St ep 4. Shut down the system using the shutdownor rebootcommand. Enter:
shutdown
Progress messages detailing system shutdown activities print to the
terminal. Upon reaching run-level 0, the system:
•
•
Restarts in single-user mode
Displays the root prompt
St ep 5. Shut down and halt HP-UX using the shutdownor rebootcommand.
Enter:
shutdown -h
or
reboot -h
Progress messages detailing system shutdown activities print to the
terminal.
CAUTION
Turn power off to the cabinet only after the words CPU haltedhave
been displayed in the sppconsole window.
See the shutdown and reboot man pages for complete descriptions of the
commands and available options.
Chapter 6
133
Download from Www.Somanuals.com. All Manuals Search And Download.
HP-UX Operating System
Stopping HP-UX
R eset tin g t h e V2500/V2600 ser ver h a r d w a r e
The /spp/bin/do_resetcommand resets the V-Class hardware. The
do_resetcommand is run from the Service Support Processor, causes
OBP to reboot, and halts all activity on the V-Class server cabinets
involved. For details see the do_reset man page on the Service Support
Processor.
NOTE
Before running do_resetfrom the Service Support Processor you
should shut down HP-UX running on the V-Class server, if possible, to
avoid losing data.
Four levels of system reset are provided by do_reset, from level 1 (the
default) to level 4 (Transfer of Control).
On multiple-cabinet V-Class server configurations, you can reset all
cabinets or just selected cabinets with do_reset. Larger systems such
as those with additional cabinets take more time to reset.
The do_resetcommand’s syntax is as follows:
do_reset [node_id | all] [level] [boot_option]
If do_resetis specified with no arguments then the default level 1 reset
of all cabinets is performed, rebooting the server to OBP.
Either a cabinet ID (node_id) or the keyword allcan be specified to
indicate which cabinets are to be reset. If a cabinet ID is specified, the
reset level also must be specified.
Reset levels (level) of 1 through 4 are supported and are specified as
numbers. Level 1, the default, provides a hard reset and reboots to OBP.
A level 4 reset provides a Transfer of Control (TOC), equivalent to
pressing the TOC button on a V-Class cabinets.
NOTE
Only one request for a level 4 reset (TOC) should be issued at a time.
This ensures that the server properly completes the reset process.
Various boot_options are supported for level 1 resets. Normally only
trained HP service personnel use these.
Examples
• do_reset
This performs a level 1 reset of all cabinets, resetting the server and
rebooting to OBP.
• do_reset all 4
134
Chapter6
Download from Www.Somanuals.com. All Manuals Search And Download.
HP-UX Operating System
Stopping HP-UX
Performs a level 4 reset of all cabinets. This causes a Transfer of
Control (TOC) that initiates a crash dump of the operating system, if
crash dump is configured.
See the savecrash(1M) man page for crash dump details.
To reset the V-Class server hardware, perform the following steps:
St ep 1. Shut down HP-UX on the V2500/V2600 server.
This involves logging in to the server and issuing the shutdown -hor
reboot -hcommand. For details see the procedure “Shutting down the
system” on page 133.
If the V-Class server is hung and you can not log in and shut down HP-
UX, you can proceed with Step Two and may want to perform a level 4
reset at Step Three.
St ep 2. Access a Service Support Processor login shell.
You can do this directly at the Service Support Processor workstation, or
by remotely logging in with a telnetor rloginsession.
St ep 3. Issue the do_resetcommand from a Service Support Processor login
shell.
By default, do_resetperforms a level 1 reset of all cabinets. See the
do_reset(1) man page on the Service Support Processor for details.
A level 4 reset (do_reset all 4) performs a Transfer of Control (TOC)
that resets the server and initiates the HP-UX crash dump process for it,
if configured.
Pressing the TOC button on a V-Class server cabinet has the same effect
as a level 4 do_reset.
Issue only one level 4 reset to ensure a proper TOC.
Chapter 6
135
Download from Www.Somanuals.com. All Manuals Search And Download.
HP-UX Operating System
Stopping HP-UX
136
Chapter6
Download from Www.Somanuals.com. All Manuals Search And Download.
7
R ecover in g fr om fa ilu r es
This chapter provides detailed information on recovering from HP-UX
system interruptions.
Usually, the first indication of a problem is that the system does not
respond to user input. This lack of response indicates either a
performance problem or system interruption.
Performance problems are generally characterized by:
•
The system responds to one or more programs/users but not all, or
sluggishly to others.
•
The system seems to be very slow
System interruptions usually result in a total loss of CPU resources for
all users/programs due to a:
•
•
•
System hang
System panic
HPMC
Chapter 7
137
Download from Www.Somanuals.com. All Manuals Search And Download.
Recovering from failures
Collecting information
Collectin g in for m a tion
Providing the Response Center with a complete and accurate symptom
description is important in solving any problem. The V-Class server’s
SSP automatically records information on environmental and system
level events in several log files. See “SSP file system” on page 54 for more
information about these files.
Use the following procedure to collect troubleshooting information:
St ep 1. If an error message is displayed on the system console, record it.
St ep 2. Record the information displayed on the system LCD. See “LCD (Liquid
Crystal Display)” on page 28 for more information.
St ep 3. Record any relevant information contained in the log files in
the /spp/data/complex directory on the SSP:
• event_log
Main log file
• hard_hist
Filtered output from the hard_logger, appended after each error
St ep 4. Record any relevant information contained in the syslog.log file in
the /var/adm/syslog directory on the system disk. Access to this log file
may require rebooting the system if it has hung or crashed.
138
Chapter7
Download from Www.Somanuals.com. All Manuals Search And Download.
Recovering from failures
Performance problems
P er for m a n ce p r oblem s
Performance problems are generally perceived as:
•
•
•
Sluggish response at the operating system prompt
Slow program execution
Some users/programs unable to get a response
Use the following procedure to troubleshoot a performance problem:
St ep 1. At the console window of the SSP, use one or both of the following
commands to check for active processes making heavy use of system
resources:
• ps
• top
See Managing Systems and Workgroups and the psand topman pages
for more information about options and usage.
St ep 2. Enter a Ctrl-C from the terminal exhibiting the problem to abort an
executing command.
St ep 3. Check another terminal to verify that the problem is not just a console
hang.
St ep 4. Contact the Hewlett-Packard Customer Response Center.
HP-UX kernel configuration can affect performance. Refer to
“Configuring HP-UX for V-Class Servers” on page 120. For more detailed
information refer to HP-UX 11.0 Configurable Kernel Parameters and HP
V-Class Server HP-UX Configuration Notes available at the following
web site:
http://docs.hp.com/hpux/os
Chapter 7
139
Download from Www.Somanuals.com. All Manuals Search And Download.
Recovering from failures
System hangs
System h a n gs
System hangs are characterized by users unable to access the system,
although the LCD display and attention light may not indicate a problem
exists. The system console may or may not be hung.
Use the following procedure to troubleshoot a system hang:
St ep 1. Press Enter at a terminal several times and wait for a response.
St ep 2. Press Ctrl-C at a terminal to abort an executing command.
St ep 3. Check another terminal to verify that the problem is not just a console
hang.
St ep 4. At the console window of the SSP, use one or both of the following
utilities to communicate with the server:
• ping
• telnet
• rlogin
See the ping, telnet, and rloginman pages for more information
about options and usage.
St ep 5. If possible, wait about 15 minutes to see if the computer is really hung or
if it has a performance problem. With some performance problems, a
computer may not respond to user input for 15 minutes or longer.
V2600 server hardware” on page 134.
St ep 7. Save the core dump file and contact the HP Response Center to have the
core dump file analyzed. Refer to the service contract for the phone
number of the Hewlett-Packard Response Center. See “Fast dump” on
page 147 for more information.
140
Chapter7
Download from Www.Somanuals.com. All Manuals Search And Download.
Recovering from failures
System panics
System p a n ics
A system panic is the result of HP-UX encountering a condition that it is
unable to respond to and halting execution.
System panics are rare and are not always the result of a catastrophe.
They may occur on bootup, if the system was previously shut down
improperly. Sometimes they occur as a result of hardware failure.
Recovering from a system panic can be as simple as rebooting the
system. At worst, it may involve reinstalling HP-UX and restoring any
files that were lost or corrupted. If the system panic was caused by a
hardware failure such as a disk head crash, repairs have to be made
before reinstalling HP-UX or restoring lost files.
NOTE
It is important to maintain an up-to-date backup of the files on the
system so that data can be recovered in the event of a disk head crash or
similar situation. How frequently the backups are updated depends on
how much data one can afford to be lose. For information on how to back
up data, refer to Managing Systems and Workgroups.
After HP-UX experiences a system panic, the system:
•
May display an HPMC tombstone on the console if panic was caused
by an HPMC. A tombstone is a list of register values used for
troubleshooting.
•
May attempt to save a core file (an image of physical memory) to the
dump device (by default this is the primary swap device).
•
•
Attempts to reboot.
Usually displays a panic message on the console. A panic message
consists of several lines of text starting with the heading System
Panic.
•
May attempt to copy the core file to the file system (by default, to the
directory /tmp/syscore) if HP-UX can reboot.
Use the following procedure to troubleshoot a system panic:
St ep 1. If an HPMC tombstone appears on the console, copy or print out the
“Machine Check Parameters” field, and all information that follows
them.
Chapter 7
141
Download from Www.Somanuals.com. All Manuals Search And Download.
Recovering from failures
System panics
St ep 2. Record the panic message displayed on the system console. Look for text
on the console that contains terms like:
•
•
•
•
•
System Panic
HPMC
Privilege Violation
Data Segmentation Fault
Instruction Segmentation Fault
St ep 3. Categorize the panic message. The panic message describes why HP-UX
panicked. Sometimes panic messages refer to internal structures of HP-
UX (or its file systems) and the cause might not be obvious.
The wording of the panic message should allow the problem to be
classified into one of the following areas:
•
•
•
•
•
•
Peripheral problem
Server or I/O card problem
File system problem
LAN communication problem
Logical Volume Manager (LVM) related problem
Other
P er ip h er a l p r oblem
Use the following procedure to troubleshoot an apparent peripheral
hardware failure:
St ep 1. Check to ensure the device is powered on and online.
WARNING
Do n ot con n ect or d iscon n ect ca bles or p ow er off or on SCSI
d evices w h ile t h e V-Cla ss ser ver is p ow er ed on . Doin g so cou ld
lea d t o cor r u p tion of d isk d a t a .
St ep 2. Check the device’s error display. If an error is displayed:
1. Record the error message or display.
142
Chapter7
Download from Www.Somanuals.com. All Manuals Search And Download.
Recovering from failures
System panics
2. Take the device offline.
3. Power down the device.
4. If it is a disk drive, wait for the disk to stop spinning.
5. Power up the device.
6. Place the device back online.
St ep 4. Check cable and terminator connections.
St ep 5. If the system does not reboot by itself, reboot the computer by issuing the
resetcommand in the console window or do_resetcommand at the
ksh-shell window. For more information about rebooting the system see
“Rebooting the system” on page 146.
St ep 6. If the problem reappears on the device there may be an interface card or
system problem.
If the problem reappears, it might be necessary to have the problem fixed
by Hewlett-Packard service personnel.
In t er fa ce ca r d a n d syst em p r ob lem
Use the following procedure if a hardware failure appears to be
associated with an interface card or with the an internal component of
the system:
St ep 1. If an HPMC tombstone is displayed, record it.
St ep 2. Record the information displayed on the LCD. See “LCD (Liquid Crystal
Display)” on page 28 for more information.
St ep 3. Record any relevant information contained in the following log files in
the /spp/data/COMPLEX directory on the SSP:
• event_log
Main log file
• hard_hist
Filtered output from the hard_logger, appended after each error
• consolelog
Complete log of all input/output from the sppconsole window
Chapter 7
143
Download from Www.Somanuals.com. All Manuals Search And Download.
Recovering from failures
St ep 4. If the system does not reboot by itself, reboot the computer by issuing the
resetcommand in the console window or do_resetcommand at the
ksh-shell window. For more information about rebooting the system see
“Rebooting the system” on page 146.
If the problem reappears, it might be necessary to have the problem fixed
by Hewlett-Packard service personnel.
F ile system p r ob lem
reboot the system and run the file system checker fsckto check and
correct the problem. Follow all directions that fsckdisplays. Especially
when the root file system (the one with the / directory) has problems, it is
important to use the -noption to the rebootcommand, right after fsck
completes. fsckis normally run automatically at boot time. See
“Rebooting the system” on page 146.
LAN com m u n ica tion p r oblem
Use the following procedure if the panic messages indicate a problem
with LAN communication:
St ep 1. Check LAN cable and media access unit (MAU) connections.
St ep 2. Ensure that all vampire taps are tightly connected to their respective
cables.
St ep 3. Ensure that the LAN is properly terminated. Each end of the LAN cable
must have a 50-ohm terminator attached. Do not connect the system
directly to the end of a LAN cable.
If the problem reappears or if the hardware failure appears to be
associated with a LAN card or an internal component of the V-Class
server, it might be necessary to have the problem fixed by Hewlett-
Packard service personnel.
144
Chapter7
Download from Www.Somanuals.com. All Manuals Search And Download.
Recovering from failures
System panics
Logica l Volu m e Ma n a ger (LVM) r ela ted
p r ob lem
If the size of a logical volume that contains a file system is reduced such
that the logical volume is smaller than the file system within it, the file
system will be corrupted. When an attempt is made to access a part of
the truncated file system that is beyond the new boundary of the logical
volume a system panic will often result.
The problem might not show up immediately. It will occur when the
truncated part of the file system is overwritten by something else (such
as a new logical volume or the extension of a logical volume in the same
volume group as the truncated file system).
When a problem appears with something other than that has previously
been discussed or the problem can not be classified, proceed to
“Rebooting the system” on page 146. Ensure that the exact text of the
panic message is recorded for future troubleshooting purposes. See
“Collecting information” on page 138 for further information.
Chapter 7
145
Download from Www.Somanuals.com. All Manuals Search And Download.
Recovering from failures
Rebooting the system
Rebootin g th e system
Once a problem has been corrected, reset and reboot the system.
St ep 1. Reset the V-Class server. See “Resetting the V2500/V2600 server
hardware” on page 134.
St ep 2. If the system panicked due to a corrupted file system, fsckwill report
the errors and any corrections it makes. If fsckterminates and requests
to be run manually, refer to Managing Systems and Workgroups for
further instructions. If the problems were associated with the root file
system, fsckwill ask the operator to reboot the system when it finishes.
Use the command:
reboot -n
The -noption tells reboot not to sync the file system before rebooting.
Since fsck has made all the corrections on disk, this will not undo the
changes by writing over them with the still corrupt memory buffers.
Mon it or in g th e syst em a ft er a system p a n ic
If the system successfully reboots, there is a good chance that it can
resume normal operations. Many system panics are isolated events,
unlikely to reoccur.
Check applications to be sure that they are running properly and
monitor the system closely for the next 24 hours. For a short while,
backups may be done more frequently than normal until confidence in
the system has been restored.
146
Chapter7
Download from Www.Somanuals.com. All Manuals Search And Download.
Recovering from failures
Abnormal system shutdowns
Abn or m a l syst em sh u td ow n s
Abnormal systems shutdowns (often referred to as system crashes) can
occur for many reasons. In some cases, the cause of the crash can be
easily determined. In some extreme cases, however, it may be necessary
to analyze a snapshot (called a core dump or simply dump) of the
computer’s memory in order to determine the cause of the crash. This
may require the services of the Hewlett-Packard Response Center.
V-Class servers using HP-UX Release 11.0 or greater employ a more
efficient dump mechanism than other HP servers using previous releases
of HP-UX. This mechanism is called fast dump.
Fa st d u m p
When a system crashes, the operator can now choose whether or not to
dump, and if so, whether the dump should contain the relevant subset of
memory or all memory (without operator interaction).
By default fast dump selectively dumps only the parts of memory that
are expected to be useful in debugging. It improves system availability in
terms of both the time and space needed to dump and analyze a large
memory system.
The following commands allow the operator to configure, save, and
manipulate the fast core dump:
• crashconf—Configures the destination and contents of a crash
dump without rebooting. See the crashconf(1M) man page for more
information.
• savecrash—Runs at boot time and saves any information that may
be overwritten by normal system activity. See the savecrash(1M) man
page for more information.
• crashutil—Saves or manipulates the crash dump (if desired). It can
format the dump snapshot so that it can be read by the older
commands. See the crashutil(1M) man page for more information.
Installations that used to call savecorein any way other than by the
HP-supplied, unmodified /sbin/init.d/savecorescript need to be
updated to use savecrashand/or crashutil.
Chapter 7
147
Download from Www.Somanuals.com. All Manuals Search And Download.
Recovering from failures
Abnormal system shutdowns
The on-disk and file system formats of a crash dump have changed with
HP-UX 11.0.
libcrash(3) is a new library provided to allow programmatic access to a
crash dump. supports all past and current crash dump formats. By using
libcrash(3) under certain configurations, crash dumps no longer need
to be copied into the file system before they can be debugged. See the
libcrash(3) man page for more information.
Over view of t h e d u m p a n d sa ve cycle
When the system crashes, HP-UX saves the image of physical memory or
certain portions of it to predefined locations called dump devices. When
the operator next reboots the system, a special utility copies the memory
image from the dump devices to the HP-UX file system area. Once
copied, the memory image can be analyzed with a debugger or saved to
tape for later analysis.
Prior to HP-UX 11.0, dump devices had to be defined in the kernel
configuration, and they still can be using Release 11.0. Beginning with
Release 11.0, however, a new more-flexible method for defining dump
devices is available using crashconf.
Beginning with HP-UX Release 11.0, there are three places where dump
devices are configured:
1. In the kernel (same as releases prior to Release 11.0)
2. During system initialization when the initialization script for
crashconfruns (and reads entries from the /etc/fstabfile)
3. During runtime, by the operator or administrator manually running
the /sbin/crashconfcommand.
Cr a sh d u m p d est in a t ion a n d con ten t s
Defining the contents and destination of the crash dump are two
important factors to consider when preparing for the dump. The
destination and contents are configurable without rebooting, using the
crashconfinterface. See the crashconf(1M) man page for more
information.
In order to capture the memory image of the system when a crash occurs,
the image storage location(s) must be defined in advance.
148
Chapter7
Download from Www.Somanuals.com. All Manuals Search And Download.
Recovering from failures
Abnormal system shutdowns
IMPORTANT
Crashdump must be configured to dump on cabinet zero disks only.
It is important to have sufficient space to capture the part of memory
that contains the instruction or data that caused the crash. More than
one dump device can be defined so that if the first one fills up, the next
one continues dumping until the dump is complete or no more defined
space is available. To ensure enough dump space, define a dump area
that is at least as big as the computer’s physical memory plus 1 Mbyte.
Setting the amount of memory dumped and the classes of the memory
pages determines the size of the dump. The content can be configured
while the system is running and changed without rebooting the system.
The larger the size of the system’s physical memory, the longer it takes to
dump it to disk (and the more disk space it consumes).
New SCA-Ext en d ed Cr a sh Du m p For m a t
A new crash dump format is provided to support dumping selected
memory on multiple-cabinet V2500/V2600 servers. This new SCA-
extended crash dump format is used only on V2500/V2600 SCA systems
and requires the crash dump utilities provided in the HP-UX 11.10
release.
Non-SCA systems, including single-cabinet V2500/V2600 servers and all
other HP systems, use the non-SCA crash dump format. Unlike the SCA-
extended crash dump format, the non-SCA crash dump format is
backward compatible and does not require HP-UX 11.10 crash dump
utilities.
For more information see the Release Notes fpr HP-UX 11.10 SCA.
Mem or y Du m p ed on V2500/V2600 SCA Ser ver s
Crash dump on multiple-cabinet V2500/V2600 servers dumps memory
from all cabinets, including the following:
All cabinet ID 0 memory, except memory dedicated as CTI cache.
All cabinet-private memory on serf cabinets (cabinet IDs 2, 4, and 6).
Crash dump does not dump memory used as CTI cache. The CTI cache is
physical memory dedicated as a cache for internode communication, and
is not made available to HP-UX or applications.
For V2500/V2600 SCA servers, the crash dump volume must reside
entirely on cabinet ID 0.
Chapter 7
149
Download from Www.Somanuals.com. All Manuals Search And Download.
Recovering from failures
Abnormal system shutdowns
To calculate an appropriate size for a V2500/V2600 SCA crash dump
volume, estimate that you will need at most the following amount of
space: the total amount of physical memory in the system, plus space to
allow for dump headers and tables, minus the amount of memory
dedicated as CTI cache, and minus the amount of memory that is kernel
text replicated across cabinets.
The total amount of space required depends on whether a full dump or a
selective dump is performed, and whether the crash dump is compressed
regarding how to configure system dumps. The criteria are:
•
•
•
System recovery time—Get the system back up as soon as possible
Crash information integrity—Capture the correct information
following factors:
•
•
•
•
Dump level
Compressed save vs. noncompressed save
Using a device for both paging and dumping
Partial save
These factors are discussed in the following sections.
Du m p level
With HP-UX 11.0 the operator can select three levels of core dumps: no
dump, selective dump, or full dump.
Selective dump causes only the selected memory pages to get dumped,
see the crashconf(1M) man page for more information.
NOTE
In some specific cases, HP-UX will override the selective dump and
request a full dump. The operator is given ten seconds to override HP-UX
and continue with a selective dump.
150
Chapter7
Download from Www.Somanuals.com. All Manuals Search And Download.
Recovering from failures
Abnormal system shutdowns
The fewer pages dumped to disk (and on reboot, copied to the HP-UX file
system area), the faster the system can be back up and running.
Therefore, avoid using the full dump option.
When defining dump devices, whether in a kernel build or at run time,
the operator can list which classes of memory must always get dumped,
and which classes of memory should not be dumped. If both of these
“lists” are left empty, HP-UX decides which parts of memory should be
dumped based on what type of error occurred. In nearly all cases, leaving
the lists empty is preferred.
NOTE
Even if a full dump has not been defined (in the kernel or at run time),
the definitions can be overridden (within a ten second window) and a
request for a full dump after a system crash can be performed. Likewise,
if the cause of the crash is known, a request to not dump can be
performed as well.
Com p r essed sa ve vs. n on com p r essed sa ve
System dumps can be so large that they tax the HP-UX file system area.
The boot time utility, savecrash, can be configured (by editing the file
/etc/rc.config.d/savecrash) to compress or not compress the data
as it copies the memory image from the dump devices to the HP-UX file
system area during the reboot process. This effects system recovery time
in that data compression takes longer. Therefore, if there is enough disk
space and the fastest system recovery is required, configure savecrash
to not compress the data. See the savecrash(1M) man pages for more
information.
Usin g a d evice for b ot h p a gin g a n d d u m p in g
It is possible to use a specific device for both paging (swapping) and as a
dump device. If system recovery time is critical, do not configure the
primary paging device as a dump device.
When the primary paging device is not used as one of the dump devices
or after the crash image on the primary paging device has been saved, by
default, savecrashruns in the background. This reduces system boot
time by running the system with only the primary paging device.
Another advantage to keeping paging and dump devices separate is that
paging does not overwrite the information stored on a dump device, no
matter how long the system has been up or how much activity has taken
place. Disabling savecrashprocessing at boot time (by editing the file
Chapter 7
151
Download from Www.Somanuals.com. All Manuals Search And Download.
Recovering from failures
Abnormal system shutdowns
/etc/rc.config.d/savecrash) reduces system recovery time. After
the system recovery, run savecrashmanually to copy the memory
image from the dump area to the HP-UX file system area.
Pa r t ia l sa ve
If a memory dump resides partially on dedicated dump devices and
partially on devices that are also used for paging, only those pages that
are endangered by paging activity can be saved.
Pages residing on the dedicated dump devices can remain there. It is
possible to analyze memory dumps directly from the dedicated dump
devices using a debugger that supports this feature. If, however, there is
a need to send the memory dump to someone else for analysis, move the
pages on the dedicated dump devices to the HP-UX file system area.
Then use a utility such as tarto bundle them for shipment. To do that,
use the command /usr/sbin/crashutilinstead of savecrashto
complete the copy.
Cr a sh in for m a tion in tegr ity
This section discusses how to make sure the part of memory that
captured. The factors that must be considered are:
•
•
•
Full dump vs. selective dump
Dump definitions built into the kernel vs. defined at runtime
Using a device for both paging and as a dump device
F u ll d u m p vs. select ive d u m p
The only way to guarantee capturing the specific instruction or data that
caused the crash is to capture everything. This means selecting a full
dump of memory.
Be aware, however, that this can be costly in terms of time and disk
space. A large amount of time and disk space is needed to dump the
entire contents of memory in a system with a large memory
configuration or to copy a large memory image to the HP-UX file system
area during the reboot process.
The amount of dump area should at least be equal to the amount of
memory in the system; depending on a number of factors, additional disk
space greater than the amount of physical memory in the system may be
needed
152
Chapter7
Download from Www.Somanuals.com. All Manuals Search And Download.
Recovering from failures
Abnormal system shutdowns
Du m p d efin it ion s b u ilt in t o t h e k er n el vs. d efin ed a t
r u n t im e
There are three places to define which devices are to be used as dump
devices:
1. During kernel configuration
2. At boot time (entries defined in the /etc/fstabfile)
3. At run time (using the /sbin/crashconfcommand)
Definitions at each of these places add to or replace any previous
definitions from other sources. However, consider the following situation:
Example
A system called appserver has 1-Gbyte of physical memory. If the dump
devices for this system are defined with a total of 256-Mbytes of space in
the kernel file and an additional 768-Mbytes of disk space in the /etc/
fstabfile, there would be enough dump space to hold the entire memory
image (a full dump).
If the crash occurs, however, before /etc/fstabis processed, only the
amount of dump space already configured is available at the time of the
crash; in this example, it is 256-Mbytes of space.
Define enough dump space in the kernel configuration if it is critical to
capture every byte of memory in all instances, including the early stages
of the boot process.
NOTE
This example is presented for completeness. The actual amount of time
between the point where kernel dump devices are activated and the
point where runtime dump devices are activated is very small (a few
seconds), so the window of vulnerability for this situation is practically
nonexistent.
Usin g a d evice for b ot h p a gin g a n d a s a d u m p d evice
It is possible to use a specific device for both paging purposes and as a
dump device. If, however, crash dump integrity is critical, this is not
recommended.
If savecrashdetermines that a dump device is already enabled for
paging and that paging activity has already taken place on that device, a
warning message indicates that the dump may be invalid. If a dump
device has not already been enabled for paging, savecrashprevents
Chapter 7
153
Download from Www.Somanuals.com. All Manuals Search And Download.
Recovering from failures
Abnormal system shutdowns
paging from being enabled to the device by creating the file /etc/
savecore.LCK. swapondoes not enable the device for paging if the
device is locked in /etc/savecore.LCK.
Systems configured with small amounts of memory and using only the
primary swap device as a dump device might not be able to preserve the
dump (copy it to the HP-UX file system area) before paging activity
destroys the data in the dump area. Larger memory systems are less
likely to need paging (swap) space during start-up and are therefore less
likely to destroy a memory dump on the primary paging device before it
can be copied.
Disk sp a ce n eed s
This section discusses how to manage limited disk resources on the
memory image. The factors to consider are:
•
•
•
Dump level
Compressed save vs. noncompressed save
Partial save (savecrash -p)
Du m p level
There are three levels of core dumps: full dump. selective dump, and no
dump. The fewer pages required to dump, the less space is required to
hold them. Therefore, a full dump is not recommended. If disk space is
really at a premium, one option is no dump at all.
A third option is called a selective dump. HP-UX 11.0 can determine
which pages of memory are the most critical for a given type of crash,
and save only those pages. Choosing this option can save a lot of disk
space on the dump devices and again later on the HP-UX file system
area. For instructions on how to do this see “Defining dump devices” on
page 155.
Com p r essed sa ve vs. n on com p r essed sa ve
Regardless of whether a full or selective dump is chosen, whatever is
saved on the dump devices needs to be copied to the HP-UX file system
area before it can be used.
154
Chapter7
Download from Www.Somanuals.com. All Manuals Search And Download.
Recovering from failures
Abnormal system shutdowns
NOTE
With HP-UX 11.0, it is possible to analyze a crash dump directly from
dump devices using a debugger that supports this feature. If, however,
there is a need to save it to tape or send it to someone, copy the memory
image to the HP-UX file system area first.
If there is a disk space shortage in the HP-UX file system area (as
opposed to dump devices), the operator can elect to have savecrash(the
boot time utility that does the copy) compress the data as it makes the
copy.
Pa r t ia l sa ve (sa vecr a sh -p )
If the system has plenty of dump device space but is limited in HP-UX
file system space, consider using the -poption for the savecrash
command. This option copies only those pages on dump devices that are
endangered by paging activity (i.e. pages on the devices used for both
paging and as dump devices). Pages that are on dedicated dump devices
remain there.
To configure this option into the boot process, edit the file
/etc/rc.config/savecrashand comment out the line that sets the
environment variable SAVE_PART=1.
Defin in g d u m p d evices
When defining dump devices, it is important to accurately determine the
amount of space needed to hold the dump without wasting disk space. To
save a full dump, the amount of dump space needed is equal to the size of
the system’s physical memory.
For selective dumps, the size of dump space varies, depending on the
classes of memory be saved. To determine amount of space needed,
perform the following procedure:
St ep 1. When the system is running with a typical workload, enter the following
command:
/sbin/crashconf -v
The following typical output appears:
Chapter 7
155
Download from Www.Somanuals.com. All Manuals Search And Download.
Recovering from failures
Abnormal system shutdowns
CLASS
PAGES INCLUDED IN DUMP DESCRIPTION
-------- ---------- ---------------- -------------------------------------
UNUSED
USERPG
BCACHE
KCODE
USTACK
FSDATA
KDDATA
KSDATA
2036 no, by default unused pages
6984 no, by default user process pages
15884 no, by default buffer cache pages
1656 no, by default kernel code pages
153 yes, by default user process stacks
133 yes, by default file system metadata
2860 yes, by default kernel dynamic data
3062 yes, by default kernel static data
Total pages on system:
Total pages included in dump:
32768
6208
DEVICE
------------ ---------- ---------- ------------ -------------------------
31:0x00d000 52064 262144 64:0x000002 /dev/vg00/lvol2
----------
262144
OFFSET(kB) SIZE (kB) LOGICAL VOL. NAME
St ep 2. Multiply the number of pages listed in “Total pages included in
dump” by the page size (4-Kbytes) and add 25% for a margin of safety. In
the above example, the calculation would be:
(6208 x 4 Kbytes) x 1.25 = approx. 30 Mbytes
Ker n el d u m p d evice d efin it ion s
Capturing dumps for crashes that occur during early stages of the boot
process requires sufficient dump space in the kernel configuration.
Usin g SAM t o con figu r e d u m p d evices in t o t h e k er n el
The easiest way to configure dump devices is to use SAM. A screen for
dump device definition is located in the Kernel Configuration area. After
changing the dump device definitions, a new kernel must be built and
the system rebooted using the new kernel file to make the changes take
effect. To configure dump devices into the kernel, perform the following
procedure:
St ep 1. Run SAM and select the Kernel Configuration Area
St ep 2. From the Kernel Configuration Area, select the Dump Devices area
A list of dump devices configured into the next kernel built by SAM is
displayed. This is the list of pending dump devices.
156
Chapter7
Download from Www.Somanuals.com. All Manuals Search And Download.
Recovering from failures
Abnormal system shutdowns
St ep 3. Use the SAM action menu to add, remove, or modify devices or logical
volumes.
NOTE
The order of the devices in the list is important. Devices are used in
reverse order from the way they appear in the list. The last device in the
list is as the first dump device.
St ep 4. Follow the SAM procedure for building a new kernel.
St ep 5. Boot the system from the new kernel file to activate the new dump device
definitions.
Usin g HP -UX com m a n d s t o con figu r e d u m p d evices in t o
t h e k er n el
The systemfile can be edited and the configprogram used to build the
new kernel. For details see Managing Systems and Workgroups. Perform
the following procedure to configure dump devices into the kernel using
HP-UX commands:
St ep 1. Edit the systemfile (the file that configuses to build the new kernel).
This is usually the file /stand/systembut it can be another file if that
is preferred.
Dump to Hardware Device—For each hardware dump device to be
configured into the kernel, add a dump statement in the area of the file
designated “* Kernel Device info” immediately prior to any tunable
parameter definitions. For example:
dump 2/0/1.5.0
dump 56/52.3.0
Dump to Logical Volume—For logical volumes, it is not necessary to
define each volume used as a dump device. For dumping to logical
volumes, the logical volumes must meet all of the following
requirements:
•
Each logical volume to be used as a dump device must be part of the
root volume group (vg00). For details on configuring logical volumes
as kernel dump devices, see the lvlnboot (1M) manpage.
•
The logical volumes must be contiguous (no disk striping or bad-block
reallocation is permitted for dump logical volumes).
Chapter 7
157
Download from Www.Somanuals.com. All Manuals Search And Download.
Recovering from failures
Abnormal system shutdowns
•
The logical volume cannot be used for file system storage, because the
whole logical volume is used.
To use logical volumes for dump devices (no matter how many logical
volumes are required), include the following dump statement in the
system file:
dump lvol
Configuring No Dump Devices—To configure a kernel with no dump
device, use the following dump statement in the system file:
dump none
To configured the kernel for no dump device, the above statement (dump
none) must be used.
NOTE
Omitting dump statements altogether from the systemfile results in a
kernel that uses the primary paging device (swap device) as the dump
device.
St ep 2. Once the systemfile has been edited, build a new kernel file using the
configcommand.
St ep 3. Save the existing kernel file (probably /stand/vmunix) to a safe place
(such as /stand/vmunix.safe) in case the new kernel file can not be
booted.
St ep 4. Boot the system from the new kernel file to activate the new dump device
definitions.
Ru n t im e d u m p d evice d efin ition s
If there is not a concern about capturing a dump that occurs during the
earliest stages of the boot process, replace or supplement any kernel
dump device definitions while the system is booting or running. There
are two ways to do this:
1. Using crashconfto read dump entries in the /etc/fstabfile
(using crashconf’s -aoption)
2. Using arguments to the crashconf command, directly specifying
the devices to be configured
158
Chapter7
Download from Www.Somanuals.com. All Manuals Search And Download.
Recovering from failures
Abnormal system shutdowns
Th e /et c/fst a b file
Define entries in the fstabfile to activate dump devices during the HP-
UX initialization (boot) process or when crashconfreads the file. The
format of a dump entry for /etc/fstablooks like the following:
devicefile_name / dump defaults 0 0
Examples:
/dev/dsk/c0t3d0 / dump defaults 0 0
/dev/vg00/lvol2 / dump defaults 0 0
/dev/vg01/lvol1 / dump defaults 0 0
Define one entry for each device or logical volume to be used as a dump
device.
NOTE
Unlike dump device definitions built into the kernel, with run time dump
definitions the logical volumes from volume groups other than the root
volume group can be used.
Th e cr a sh con f com m a n d
Use the /sbin/crashconf command to add to, remove, or redefine
dump devices. The following are two ways to do this:
•
•
Reread the /etc/fstabfile using the crashconf-aoption
Use device arguments with crashconfto configure the devices
With either method, use the crashconf-roption to specify that new
definitions replace, rather than add to, any previous dump device
definitions.
Examples:
To have crashconfread the /etc/fstabfile (thereby adding any listed
dump devices to the currently active list of dump devices), enter the
following command:
/sbin/crashconf -a
To have crashconfread the /etc/fstabfile (thereby replacing the
currently active list of dump devices with those defined in fstab),
enter the following:
/sbin/crashconf -ar
Chapter 7
159
Download from Www.Somanuals.com. All Manuals Search And Download.
Recovering from failures
Abnormal system shutdowns
To have crashconfadd the devices represented by the block device files
/dev/dsk/c0t1d0and /dev/dsk/c1t4d0to the dump device list,
enter the following:
/sbin/crashconf /dev/dsk/c0t1d0/dev/dsk/c1t4d0
To have crashconfreplace any existing dump device definitions with
the logical volume /dev/vg00/lvol3and the device represented by
block device file /dev/dsk/c0t1d0, enter the following:
/sbin/crashconf -r /dev/vg00/lvol3 /dev/dsk/c0t1d0
Du m p or d er
The order that devices dump after a system crash is important when
using the primary paging device along with other devices as a dump
device.
Regardless of how the list of currently active dump devices was built
(from a kernel build, from the /etc/fstabfile, from use of the
crashconfcommand, or any combination of the these) dump devices are
used (dumped to) in the reverse order from which they were defined. The
last dump device in the list is the first one used, and the first device in
the list is the last one used.
Place devices that are used for both paging and dumping early in the list
of dump devices so that other dump devices are used first and
overwriting of dump information due to paging activity is minimized.
Wh a t h a p p en s w h en th e syst em cr a sh es?
This section discusses the unlikely event of a V-Class system crash. A
system panic means that HP-UX encountered a condition that it could
not to handle. Sometimes the cause of the crash is apparent, but many
times an in-depth analysis is required. HP-UX is equipped with a dump
procedure to capture the contents of memory at the time of the crash.
160
Chapter7
Download from Www.Somanuals.com. All Manuals Search And Download.
Recovering from failures
Abnormal system shutdowns
Op er a tor over r id e op tion s
When the system crashes, the system console displays a panic message
similar to the following:
*** A system crash has occurred. (See the above messages for details.)
*** The system is now preparing to dump physical memory to disk, for use
*** in debugging the crash.
*** The dump will be a SELECTIVE dump: 21 of 128 megabytes.
*** To change this dump type, press any key within 10 seconds.
*** Select one of the following dump types, by pressing the corresponding key:
N) There will be NO DUMP performed.
S) The dump will be a SELECTIVE dump: 21 of 128 megabytes.
F) The dump will be a FULL dump of 128 megabytes.
O) The dump will be an OLD-FORMAT dump of 128 megabytes.
*** Enter your selection now.
The operator can override any dump device definitions by entering N (for
no dump) at the system console within the 10-second override period.
If disk space is limited, but the operator feels that a dump is important,
the operator can enter S (for selective dump) regardless of the currently
defined dump level.
Th e d u m p
After the operator overrides the current dump level, or the 10-second
override period expires, HP-UX writes the physical memory contents to
the dump devices until one of the following conditions is true:
•
•
•
The entire contents of memory are dumped (if a full dump was
configured or requested by the operator).
The entire contents of selected memory pages are dumped (if a
selective dump was configured or requested by the operator).
Configured dump device space is exhausted
Depending on the amount of memory being dumped, this process can
take from a few seconds to hours.
NOTE
During the dump, status messages on the system console indicate the
progress. Interrupt the dump at any time by pressing the ESC key.
However, if a dump is interrupted, all information is lost.
Chapter 7
161
Download from Www.Somanuals.com. All Manuals Search And Download.
Recovering from failures
Abnormal system shutdowns
Following the dump, the system attempts to reboot.
Th e r eboot
When dumping of physical memory pages is complete, the system
attempts to reboot (if the Autoboot is set). For information on the
Autoboot flag, see “Enabling Autoboot” on page 67.
sa vecr a sh p r ocessin g
During the boot process, a process called savecrashcan be used that
copies (and optionally compresses) the memory image stored on the
dump devices to the HP-UX file system area.
Du a l-m od e d evices (d u m p / sw a p )
By default, savecrashperforms its copy during the boot process.
Disable this operation by editing the file: /etc/rc.config.d/
savecrashand setting the SAVECRASHenvironment variable to a value
of zero. This is generally safe to do if the dump devices are not also being
used as paging devices.
WARNING
If u sin g d evices for b ot h p a gin g a n d d u m p in g, d o n ot d isa b le
sa vecr a sh b oot p r ocessin g. Loss of th e d u m p ed m em or y im a ge to
su b seq u en t syst em p a gin g a ctivity ca n occu r.
Wh a t t o d o a ft er th e syst em h a s r eb oot ed ?
After the system reboots, make sure that the physical memory image
dumped to the dump devices is copied to the HP-UX file system area
then either package and send it in for analysis or analyze it using a
debugger.
NOTE
With HP-UX 11.0, it is possible to analyze a crash dump directly from
dump devices. If, however, it needs to be saved to a tape or sent to
someone, first copy the memory image to the HP-UX file system area.
Unless specifically disabled during reboot, the savecrashutility copies
the memory image during the reboot process. The default HP-UX
directory for the memory image in is /var/adm/crash. Specify a
different location by editing the file /etc/rc.config.d/savecrash
and setting the environment variable called SAVECRASH_DIRto the
name of the directory the dumps are to be located.
162
Chapter7
Download from Www.Somanuals.com. All Manuals Search And Download.
Recovering from failures
Abnormal system shutdowns
Usin g cr a sh u til to com p lete th e sa vin g of a d u m p
If devices are being used for both paging (swapping) and dumping, it is
very important to not disable savecrashprocessing at boot time. If this
is done, there is a chance that the memory image in the dump area will
be overwritten by normal paging activity. If, however, there are separate
dump and paging devices (no single device used for both purposes),
copying the memory image to the HP-UX file system area can be delayed
in order to speed up the boot process. To do this, edit the file /etc/
rc.config.d/savecrashand set the environment variable called
SAVECRASH=0.
If copying the physical memory image from the dump devices to the HP-
UX file system area has been delayed, run savecrashmanually to do
the copy when the system is running. Confirm that enough space to hold
the copy in the HP-UX file system area has been configured before doing
so.
If a partial save is being done, the only pages copied to the HP-UX file
system area during the boot process are those that were on paging
devices. Pages residing on dedicated dump devices are still there. A
partial save can be selected by leaving the SAVECRASHenvironment set
to 1 and setting the environment variable SAVE_PART=1in /etc/
rc.config.d/savecrash. To copy the remaining pages to the HP-UX
file system area when the system is running again, use the command
crashutil. See the crashutil(1M) manpage for details.
Example
/usr/sbin/crashutil -v CRASHDIR /var/adm/crash/
crash.0
Cr a sh d u m p for m a t con ver sion
Use crashutilto convert the file format when analyzing a crash dump
on a computer running a different version of HP-UX than the V-Class
server, or if the debugging tool does not recognize the specific format of
the saved file.
The basic format of the crashutilcommand to do a conversion is:
/usr/sbin/crashutil -vversion source [destination]
version
source
Designates the version of the destination format.
Designates the pathname of the crash dump to be
converted.
Chapter 7
163
Download from Www.Somanuals.com. All Manuals Search And Download.
Recovering from failures
Abnormal system shutdowns
destination
Designates the pathname where the converted file will
be written. If no destination is specified the source will
be overwritten.
See the crashutil(1M) manpage for more information.
An a lyzin g cr a sh d u m p s
Analyzing crash dumps is not a trivial task. It requires intimate
knowledge of HP-UX internals and the use of debuggers. It is beyond the
scope of this document to cover the actual analysis process. Contact the
Hewlett-Packard representative for help in analyzing a crash dump.
164
Chapter7
Download from Www.Somanuals.com. All Manuals Search And Download.
A
LE D cod es
This appendix describes core utilities board (CUB) LED errors The
Attention LED on the core utilities board (CUB) turns on, and the
Attention light bar on the front of the node flashes to indicate the
presence of an error code listed Table 15. Additionally, only the highest
priority error is displayed. Once remedied, an error that is cleared may
expose a lesser priority error.
Appendix A
165
Download from Www.Somanuals.com. All Manuals Search And Download.
LED codes
Power on detected errors
This section describes core utilities board (CUB) LED errors from
highest to lowest priority detected at power on. The Attention LED on
the core utilities board (CUB) turns on, and the Attention light bar on
the front of the node flashes to indicate the presence of an error code
listed in Table 15. Additionally, only the highest priority error is
displayed. Once remedied, an error that is cleared may expose a lesser
priority error.
Errors are listed in sequence from the highest to lowest priority.
NOTE
Errors from LED hex code 00 through hex code 67 shut the system down,
and errors from hex-code 68 through 73 leave the system up.
Ta b le 15
CUB d et ects p ow er on er r or
LED
Fa u lt
Sym p tom s
Cor r ective a ction
00
3.3V error
(highest
priority)
1. 5V is up 3.3V is not.
2. SSP interface will not
function.
Call the Response Center.
01
02
ASIC Install 0
(MIB)
1. Incorrect rotation or part in
one of the processor agent
chip (PAC) sockets.
2. Incorrect rotation or part in
one of the routing (XBAR)
attachment chip (RAC)
sockets.
Call the Response Center.
ASIC Install 1
(EMB)
1. Incorrect rotation or part in
one of the memory access chip
(MAC) sockets.
Call the Response Center.
2. Incorrect rotation or part in
one of the toroidal access chip
(TAC) on memory board (MB).
166
AppendixA
Download from Www.Somanuals.com. All Manuals Search And Download.
LED codes
Power on detected errors
LED
03
Fa u lt
Sym p tom s
Cor r ective a ction
FPGA not OK
1. Core Utilities Board (CUB)
monitoring utilities chip
(MUC) problem.
2. MUC cannot get correct
program transfer from
EEPROM on power up.
•
•
Cycle the node power
using the Key switch.
Call the Response
Center.
04
05
06
07
dc OK error
(Upper Left)
1. Power supply is reporting
failure (dc OK) after
Call the Response Center.
Call the Response Center.
Call the Response Center.
Call the Response Center.
keyswitch is turned on, but
prior to CUB power on
sequence.
2. This is the first of two or more
supplies reporting failure.
dc OK error
(Upper Right)
1. Power supply is reporting
failure (dc OK) after
keyswitch is turned on, but
prior to CUB power on
sequence.
2. This is the first of two or more
supplies reporting failure.
dc OK error
(Lower Left)
1. Power supply is reporting
failure (dc OK) after
keyswitch is turned on, but
prior to CUB power on
sequence.
2. This is the first of two or more
supplies reporting failure.
dc OK error
(Lower Right)
1. Power supply is reporting
failure (dc OK) after
keyswitch is turned on, but
prior to CUB power on
sequence.
2. This is the first of two or more
supplies reporting failure.
Appendix A
167
Download from Www.Somanuals.com. All Manuals Search And Download.
LED codes
Power on detected errors
LED
Fa u lt
Sym p tom s
Cor r ective a ction
08-11
48V error
NPSUL failure
PWRUP=0-9
1. Error occurs when 48 volt
distribution falls below 42
volts during powerup state
displayed. Powerup state
indicates which loads are
being turned on.
Call the Response Center.
2. Excessive load on 48 volts due
to an inadequate number of
functioning 48 volt supplies
or overload condition on 48V
bus.
3. Possible node power supply
(NPS) upper left failure.
12-1B 48V error
NPSUR
1. Error occurs when 48 volt
distribution falls below 42
volts during powerup state
displayed. Powerup state
indicates which loads are
being turned on.
Call the Response Center.
failure
PWRUP=0-9
2. Excessive load on 48 volts due
to an inadequate number of
functioning 48 volt supplies
or overload condition on 48V
bus.
3. Possible node power supply
(NPS) upper right failure.
168
AppendixA
Download from Www.Somanuals.com. All Manuals Search And Download.
LED codes
Power on detected errors
LED
Fa u lt
Sym p tom s
Cor r ective a ction
1C-25 48V error
NPSLL failure
1. Error occurs when 48 volt
distribution falls below 42
volts during powerup state
displayed. Powerup state
indicates which loads are
being turned on.
Call the Response Center.
PWRUP=0-9
2. Excessive load on 48 volts due
to an inadequate number of
functioning 48 volt supplies
or overload condition on 48V
bus.
3. Possible node power supply
(NPS) lower left failure.
26-2F
48V error
NPSLR failure
PWRUP=0-9
1. Error occurs when 48 volt
distribution falls below 42
volts during powerup state
displayed. Powerup state
indicates which loads are
being turned on.
Call the Response Center.
2. Excessive load on 48 volts due
to an inadequate number of
functioning 48 volt supplies
or overload condition on 48V
bus.
3. Possible node power supply
(NPS) lower right failure.
Appendix A
169
Download from Www.Somanuals.com. All Manuals Search And Download.
LED codes
Power on detected errors
LED
Fa u lt
Sym p tom s
Cor r ective a ction
30-39
48V error
(maintenance)
no supply
failure
reported
PWRUP=0-9
1. Error occurs when 48 volt
distribution falls below 42
volts during powerup state
displayed. Powerup state
indicates which loads are
being turned on.
Call the Response Center.
2. Excessive load on 48 volts due
to an inadequate number of
functioning 48 volt supplies
or overload condition on 48V
bus.
3. Possible node power supply
(NPS) failure.
3A
48V Yo Yo
error
1. Core utilities board (CUB)
lost and then regained 48V
power without the machine
being turned off or ac power
failure.
2. Core utilities board (CUB)
will display this error and not
power on the system.
•
•
Cycle dc power to the
node using the keyswitch
to attempt to clear the
Yo Yo bit.
Call the Response
Center.
3B
3C
MIB power fail 1. VDD (3.3V) error on
•
•
Cycle dc power to the
node using the keyswitch
to attempt to clear the
error.
Call the Response
Center.
(MIBPB)
MidPlane power board
(MIBPB).
2. Midplane power fails and
entire node will power down.
3. Core utilities board (CUB)
still active.
Clock fail
•
Core utilities board (CUB)
monitors clock on MidPlane
(MIB).
Call the Response Center.
170
AppendixA
Download from Www.Somanuals.com. All Manuals Search And Download.
LED codes
CUB detected memory power fail
CUB d etected m em or y p ow er fa il
This describes covers memory errors detected by the monitoring utilities
chip (MUC) on the core utilities board after power-on.
Ta b le 16
LE D
CUB d et ects m em or y p ow er fa il
Fa u lt
Sym p tom s
Cor r ective a ction
40
41
42
43
44
45
46
47
MB0L Power Fail
MB1L Power Fail
MB2R Power Fail
MB3R Power Fail
MB4L Power Fail
MB5L Power Fail
MB6R Power Fail
MB7R Power Fail
1. 3.3V dropped below
acceptable level.
2. Core utilities board (CUB)
detected a power loss on
reported memory board
(MB).
Call the Response Center.
3. Core utilities board (CUB)
powers down the system
Appendix A
171
Download from Www.Somanuals.com. All Manuals Search And Download.
LED codes
CUB detected processor error
CUB d etected p r ocessor er r or
This section describes processor errors detected by the monitoring
utilities chip (MUC) on the core utilities board after power-on.
Ta b le 17
LED
CUB d et ects p r ocessor p ow er fa il
Fa u lt
Sym p tom s
Cor r ective a ct ion
48
49
4A
4B
4C
4D
4E
4F
50
51
52
53
54
55
56
57
PB0L Power Fail
PB1R Power Fail
PB2R Power Fail
PB3R Power Fail
PB4L Power Fail
PB5R Power Fail
PB6L Power Fail
PB7R Power Fail
PB0R Power Fail
PB1L Power Fail
PB2R Power Fail
PB3L Power Fail
PB4R Power Fail
PB5L Power Fail
PB6R Power Fail
PB7L Power Fail
1. 3.3V dropped below
acceptable level.
2. Core utilities board (CUB)
detected a power loss on the
reported processor board
(PB).
Call the Response Center.
3. Core utilities board (CUB)
powers down the system.
172
AppendixA
Download from Www.Somanuals.com. All Manuals Search And Download.
LED codes
CUB detected I/O error
CUB d etected I/O er r or
This section describes I/O errors detected by the monitoring utilities chip
(MUC) on the core utilities board after power-on.
Ta b le 18
CUB d et ects I/O (IOB) p ow er fa il
LE D
Fa u lt
Left Front
Sym p t om s
Cor r ective a ct ion
58
1. 3.3V or 5V dropped below
acceptable level (+12V and
-12V not monitored).
2. Core utilities board (CUB)
detected a power loss on
reported I/O board (IOB).
3. Core utilities board (CUB)
powers down the system.
Call the Response
Center.
I/O Board failure
59
Left Rear
I/O Board failure
5A
5B
Right Front I/O
Board failure
Right Rear
I/O Board failure
Appendix A
173
Download from Www.Somanuals.com. All Manuals Search And Download.
LED codes
CUB detected fan error
CUB d etected fa n er r or
This section describes fan errors detected by the monitoring utilities chip
(MUC) on the core utilities board after power-on.
NOTE
Fan positions are referred to as viewed from the rear of the server.
Ta b le 19
LED
CUB d et ects fa n p ow er fa il
Fa u lt
Sym p tom s
Cor r ect ive a ction
5C
5D
5E
5F
60
61
Fan failure Upper Right
Fan failure Upper Middle
Fan failure Upper Left
Fan failure Lower Right
Fan failure Lower Middle
Fan failure Lower Left
Sensor in the reported fan
(as viewed from rear of
system) determines fan
failure.
Call the Response
Center.
174
AppendixA
Download from Www.Somanuals.com. All Manuals Search And Download.
LED codes
CUB detected ambient air errors
CUB d etected a m b ien t a ir er r or s
This section describes air errors detected by the monitoring utilities chip
(MUC) on the core utilities board after power-on.
Ta b le 20
CUB d et ects a m b ien t a ir er r or
LE D
Fa u lt
Sym p t om s
Cor r ective a ction
62
Ambient hot 1. Ambient air too hot.
2. Core utilities board (CUB) powers
•
•
Check site temperature.
Call the Response
Center.
down system.
3. Should have received “ambient
air too warm” error 69 prior to
this error.
63
OVERTEM
PMIB
1. MidPlane (MIB) too hot.
2. Core utilities board (CUB) sensed
overtemp on MidPlane power
board (MIBPB) and powers down
the system.
•
Check that airflow is not
blocked.
Check fans.
Call the Response
Center.
•
•
64
65
66
67
QUADRL 0
QUADRU 1
QUADLL 2
QUADLU 3
1. Board overheated in Quadrant 0.
2. Core utilities board (CUB) sensed
overtemp in Quadrant 0 and
Call the Response Center.
Call the Response Center.
Call the Response Center.
Call the Response Center.
powers down the system.
1. Board overheated in Quadrant 1.
2. Core utilities board (CUB) sensed
overtemp in Quadrant 1 and
powers down the system.
1. Board overheated in Quadrant 2.
2. Core utilities board (CUB) sensed
overtemp in Quadrant 2 and
powers down the system.
1. Board overheated in Quadrant 3.
2. Core utilities board (CUB) sensed
overtemp in Quadrant 3 and
powers down the system.
Appendix A
175
Download from Www.Somanuals.com. All Manuals Search And Download.
LED codes
CUB detected hard error
CUB d etected h a r d er r or
This section describes hard errors detected by the monitoring utilities
chip (MUC) on the core utilities board after power-on.
Ta ble 21
Ha r d er r or
LE D
Fa u lt
Sym p t om s
Cor r ective a ction
68
Hard error
(RAC) (PAC)
(MAC) (TAC)
(SAGA)
1. Hard error lines to core utilities
board (CUB) reported ASIC
problem.
2. Bit and hard error bus
determine which ASIC to check
•
•
Read /spp/data/
hard_list.
Call the Response Center.
176
AppendixA
Download from Www.Somanuals.com. All Manuals Search And Download.
LED codes
CUB detected intake ambient air error
CUB d etected in ta k e a m bien t a ir er r or
This section describes air intake errors detected by the monitoring
utilities chip (MUC) on the core utilities board after power-on.
Ta b le 22
Am b ien t a ir (in t a k e) er r or
LED
Fa u lt
Sym p t om s
Cor r ect ive a ct ion
69
Ambient air too warm
is an environmental
warning
Intake air through CUB
too warm.
•
•
Check site temperature
and correct.
If the fault reoccurs
when room temperature
is within spec. call the
Response Center
Appendix A
177
Download from Www.Somanuals.com. All Manuals Search And Download.
LED codes
CUB detected dc error
CUB d et ect ed d c er r or
This section describes dc errors detected by the monitoring utilities chip
(MUC) on the core utilities board after power-on.
Ta b le 23
d c er r or
LE D
Fa u lt
Sym p t om s
Cor r ective a ct ion
70
NPSUL
failure
(warning)
1. Node power supply (Viewed from
Node front) failure reported.
2. Low-priority error for redundant
power configurations.
Call the Response Center
71
72
73
NPSUR
failure
(warning)
NPSLL
failure
(warning)
NPSLR
failure
(warning)
178
AppendixA
Download from Www.Somanuals.com. All Manuals Search And Download.
In d ex
Sym bols
bcheckrc script
savecrash, 147
and file system, 128
and shutdown status, 128
BCIQ, xvii
set_complex, 46, 52, 53
shutdown, 132
/spp directory, 4
/spp/bin, 55
sppconsole, 46
/spp/data, 55
binding
targeting nodes, 53
top, 118
/spp/est, 56
threads and processes, 123
/spp/etc, 54
blink, 33
complex, 98
/spp/firmware, 56
/spp/man, 56
boot menu
name, 46
list of commands, 65
boot process output, 62
boot sequence, 60
boot variables, 127, 128
booting
set_complex, 46, 52, 53
components of V-Class server, 2
configuration
/spp/scripts, 55
^E key sequence, 49
node, 77–80
Nu m er ics
of HP-UX, 120, 121
utilities, 71–116
10/100 Base T Ethernet, 12
1000 Base SX Gigabit
Ethernet, 12
I/O device on cabinet 0, 2
conserver, 54
console
C
32-bit applications, 118
64-bit applications, 118
712 workstation, 36, 98
see also SSP
cabinet, 2
assuming control, 51
changing connection, 52
commands, 49, 50
controlling remotely, 51
creating windows, 41
HP-UX, runs on, 125
starting, 45–49
cabinet ID, 2
configurations, 18
numbering, 2, 119
cache, 11
A
Abaqus, 120
CTI, 11, 12
abnormal system shutdown, 147
cards
accessing
I/O supported, 12
physical access, 14
caution, defined, xv
ccmd, 71, 98, 100, 101
ccNUMA, 10
commands, 45
I/O, 13
starting from ts_config, 85
switch modes, 52
using, 45
accounts, 37
acoustics, xviii
add terminal mux, 84, 85
applications
watching, 50, 51
console port, 4
cmd, 54
32-bit, 118
command prompt. see boot menu
commands
multiple-cabinet connections, 5
consolelog, 52, 55, 99
core dump, 147
64-bit, 118
associated documents, xx
attention light bar, 31
auto command, OBP, 67
autoboot, 67, 126, 128
enable, 67
see also utilities
autoboot, 67
Core Utility Board (CUB), 9
detected ambient air
errors, 175
blink, 33
crashconf, 147, 159
crashutil, 147
do_reset, 134
ioscan, 118
detected dc error, 178
detected fan error, 174
detected hard error, 176
detected I/O error, 173
detected intake ambient air
error, 177
autoforce, 128
automatic core dump, 147
autosearch, 67, 128
jf-ccmd_info, 53
model, 118
B
mpsched, 123
reboot, 132
B180L workstation, 36, 98
Index
179
Download from Www.Somanuals.com. All Manuals Search And Download.
detected memory power
fail, 171
Dual Universal Asynchronous
Receiver-Transmitter
(DUART), 99
front panel
DAT drive, 25
detected processor error, 172
core utility board (CUB), 36
CPU. see processor, 9
crash dump, 147
SCA, 149
fuse cautions, xix
dump, 147
configuring, 150–152
defining devices, 155–158
destination, contents, 148–149
order, 160
G
gang scheduler, 122
GUI
crashconf, 159
xconfig window, 103, 104, 105
menu bar, 105
crashutil, 147
overview, 148
creating new windows, 41
crossbar, 6
DVD-ROM drive, 24
busy indicator, 25
disk loading, 24
node configuration map, 106
node control panel, 108
CTI (Coherent Toroidal
Interconnect), 15
cables, 15
eject button, 25
H
illustrated, 24
hard_hist, 56
cache memory, 11, 12
controllers, 6, 15
CTI cache, 105
hard_logger, 55
E
hardware
eject button, 25
listing, 118
EMI, xvii
topology inquiry support, 123
help, 67
D
enable Autoboot, 67
environmental errors, 32
error codes. see LED errors
error indicator, 31
error information, 138
est, 55
DAT drive
Hewlett-Packard Response
Center, xxi
eject button, 26
indicators, 25
high leakage current, xviii
HP mode boot menu, 64
HP-UX, 36, 97, 99, 117
commands, 118
data processing, 121
dc off, 23
dc on, 23
event_log, 52, 56
dcm, 55
event_logger, 55
configuring, 120, 121
documentation Web site, 118
gang scheduler, 122
ioscan command, 118
model command, 118
rebooting after a system
panic, 146
DDS-3 DAT drive, 25
deconfigure node, 84
default passwords, 37
device files, 57
Exemplar Routing Access
Controllers (ERACs), 6
F
dfdutil, 98
failure information. see also logs
and LED errors
failures, recovery, 137
fast dump, 147
diagnostic LAN, 4, 57, 98
multiple-cabinet connections, 5
digital apparatus statement, xvii
DIMM, 105
shut down procedure, 132, 133
starting, 125
FCC, xvi
stopping, 130
DIMMs, 11
FDDI, 12
system calls, 123
direct memory access, 13
displays, 21
file system
top command, 118
tuned parameter sets, 120, 121
HP-UX system
and bcheckrc script, 128
firmware, 60, 97
Forbin Project, The, 47
force, 128
DMA, 13
do_reset, 55
interruptions, 137
HP-UX, runs on test station, 125
HVD FWD SCSI, 12
FORTH, 98
180
Index
Download from Www.Somanuals.com. All Manuals Search And Download.
HyperPlane Crossbar, 6
LCD (Liquid Crystal Display),
28
core utility 53, 172
core utility 54, 172
core utility 55, 172
core utility 56, 172
core utility 57, 172
core utility 58, 173
core utility 59, 173
core utility 5A, 173
core utility 5B, 173
core utility 5C, 174
core utility 5D, 174
core utility 5E, 174
core utility 5F, 174
core utility 60, 174
core utility 61, 174
core utility 62, 175
core utility 63, 175
core utility 64, 175
core utility 65, 175
core utility 66, 175
core utility 67, 175
core utility 68, 176
core utility 69, 177
core utility 70, 178
core utility 71, 178
core utility 72, 178
core utility 73, 178
codes, tables, 29–30
message display line, 30
node status line, 28
processor status line, 28
LED errors
I
I/O
controllers, 13
listing, 118
multiple-cabinet
numbering, 14
core utility 01, 166
core utility 02, 166
core utility 03, 167
core utility 04, 167
core utility 05, 167
core utility 06, 167
core utility 07, 167
core utility 08, 168
core utility 09, 168
core utility 10, 168
core utility 11, 168
core utility 12-1B, 168
core utility 1C-25, 169
core utility 26-2F, 169
core utility 30-39, 170
core utility 3A, 170
core utility 3B, 170
core utility 40, 171
core utility 41, 171
core utility 42, 171
core utility 43, 171
core utility 44, 171
core utility 45, 171
core utility 46, 171
core utility 47, 171
core utility 48, 172
core utility 49, 172
core utility 4A, 172
core utility 4B, 172
core utility 4C, 172
core utility 4D, 172
core utility 4E, 172
core utility 4F, 172
core utility 50, 172
core utility 51, 172
core utility 52, 172
numbering, 119
physical access, 13
supported cards, 12
indicator LEDs
DAT, 25
DVD-ROM, 24
indicators, 21
DAT drive LEDs, 25
dc on LED, 23
light bar, 31
installation conditions, xix
interconnecting hardware, 6
interleaving of memory, 11
ioscan command, 118
IP address, 53, 98
IT power system, xviii
J
jf-ccmd_info, 53
J TAG, 53, 98
LEDs
attention light bar, 27
CUB error, 32
DC ON, 23
K
libcrash, 147
kernel
library routines
SCA extensions, 122
light bar, 31
configuration, 120
threads, 122
key switch panel, 23
locality domain, 122
binding, 123
L
launch policies, 123
log files
LAN
712/B180L, 57
launch policies, 123
LCD, 99
event_log, 52
logging in, 37
logons, 37
LVD Ultra2 SCSI, 12
Index
181
Download from Www.Somanuals.com. All Manuals Search And Download.
LVM (Logical Volume Manager),
numbering, 119
help, 69
problems, 145
Scalable Computing
Architecture, 1
io, 65
ls, 65
server configurations, 117
password, 65
path, 66, 128
pdt, 66
M
material handling
safety, xvi
N
pim_info, 66
RemoteCommand, 66
reset, 66
media
NASTRAN, 120
network cache. see CTI cache
memory
DAT, 25
tape, 25
restrict, 66
memory
node
scsi, 66
80-bit DIMMs, 10
88-bit DIMMs, 10
board, 11
see also complex
configure, 77–80
deconfigure, 84
search, 66
secure, 66, 128
shortcuts, 64
time, 66
controllers, 6
reset, 82, 83
CTI cache memory, 11, 12
interleaving, 11
latency, 10
node routing board
MUC detected errors, 171
poweron detected errors, 166
node status line, 28
node. see cabinet
node_0.cfg, 55
version, 66
defined, 60
enabling Autoboot, 67
OLTP, 121
numbering, 119
population, 10
supported DIMM sizes, 10
memory power fail, 171
MIB, 36
on/off switch, 23
Open Boot PROM (OBP), 97, 99,
109
notational conventions, xiv
note, defined, xv
NRB, 36
operating system, 117
operator panel, 22
Oracle, 121
midplane, 36
migration of threads and
processes, 122
model command, 118
modem, 57
numbering
I/O devices, 14
ordering
of hardware components, 119
NVRAM, 127
V-Class servers, 18
overview, 1
MPI
scheduling, 122
mpsched command, 123
mu-000X, 98
O
P
OBP, 60, 71, 127, 128
PA-RISC, 9
commands
MUC
pce_util, 55
auto, 65, 67
detected errors, 171
multiple-cabinet
cabinet IDs, 2
PCI
autoboot, 128
autoforce, 128
autosearch, 128
boot, 65
controller numbering, 13
controllers, 6
configurations, 18
console and diagnostic
connections, 4
numbering, 14
physical location, 13
supported cards, 12
pcirom, 98
boottimer, 65, 128
clearpim, 65
cpuconfig, 65
default, 65
CTI cable connections, 16
CTI controller, 6
I/O numbering, 14
memory configuration, 10
PDC, 60
performance problems, 139
POST, 97–102, 107, 109, 112
display, 65
forthmode, 65
182
Index
Download from Www.Somanuals.com. All Manuals Search And Download.
power, 23
S
shutdown, 132
powering down the system, 130
Power-On Self Test (POST), 28
private ethernet, 36
private LAN, 57
private LAN see diagnostic LAN
processor
shutdown command
and remote systems, 130
authorized users, 130
considerations, 130
shutdown status and bcheckrc
script, 128
safety and regulatory, xvi
acoustics (Germany), xviii
BCIQ (Taiwan), xvii
digital apparatus
statement, xvii
EMI (European), xvii
FCC notice, xvi
binding, 123
SMP, 10
numbering, 119
PA-8200, 9
specify complex, 52
split SCA, 92–94
spp_pdc, 97
fuse cautions, xix
high leakage current, xviii
installation conditions, xix
IT power system, xviii
material handling, xvi
radio frequency
PA-8500, 9
PA-8600, 9
SPP_PDC (SPP Processor
Dependent Code), 60
sppconsole, 55, 99
commands, 49
processor agents, 6
Processor Dependent Code
(PDC), 60
interference, xvi
processor status line, 28
programming extensions
SCA features, 122
prompt
complex console, 39
spy mode, 49
VCCI, xvii
SAM utility, 120
starting, restarting, 45
the command, 46
sppdsh, 71
savecore, 147
savecrash, 147
command, 64
SCA, 1
pthread
sppuser, 37
see also multiple-cabinet
configuration
split, 92–94
SCA features, 123
account, 4
scheduling, 122
passwords, 37
windows, 37
HP-UX support, 122
kernel configuration, 121
Scalable Coherent Interface, 15
Scalable Computing
Architecture.see SCA
SCSI, 12
spy mode, 49
R
SSP, 41, 100
radio frequency interference, xvi
Reader feedback, xxii
reboot, 132
ccmd running on, 100
configuration utilities, 71
console window, 40
see also console
rebooting, 146
scub_ip address, 81, 82
configure, 81, 82
recovering from failures, 137
remote console, 51
remove
file system, 54
logons, 37
server configurations, 18
Service Support Processor, 2, 3
connections to V2500/V2600
server, 4
message output, 39
message window, 40
operation, 35–58
root, 37
terminal mux, 85
report_cfg, 111
reset, 24, 134
operations, 3
reset node, 82, 83
Response Center, xxi
RISC processor architecture, 9
root, 37
sppuser, 37
ts_config utility, 11
utilities board connection, 9
xconfig utility, 11
set_complex, 46, 52, 53
shared-memory
tcsh shell windows, 40
test station console, 39
windows, illustrated, 39
SSP-to-system, illustrated, 97
Stingray Core Utilities Board
(SCUB), 98
RS-232, 99
latency, 122
shortcuts, 64
Index
183
Download from Www.Somanuals.com. All Manuals Search And Download.
Stop-on-hard button, 109
supported I/O cards, 12
switches, 21
scheduling, 122
TOC, 23, 24, 134
top command, 118
ts_config, 11, 71–96, 98
configuration procedures, 75–
94
V-Class
components, 2
hardware configuration, 18
HP-UX configuration, 120
ordering, 18
Symbios, 98
Symmetric Multi-Processing
(SMP), 10
Service Support Processor
connection, 9
system
files, 95–96
displays, 27
operation, 73–75
starting, 72, 73
ttylink, 99
technical assistance, xxi
V2200 server, 9
hangs, 140
logs, 52
V2250 server, 9
panics, 141
V2500/V2600 server, 1
volume group zero (vg00), 2
file system problem, 144
interface card problem, 143
lan problem, 144
logical volume manager
problem, 145
U
UNIX. see HP-UX
upgrade J TAG firmware
J TAG, upgrade firmware, 75–
77
USA radio frequency notice, xvi
using the console, 45
utilities
W
warning, defined, xv
Web site, 18, 118
white paper
monitoring the system, 146
peripheral problem, 142
reboot procedure, 132, 146
reset, 24
HP-UX SCA Programming and
Process Management White
Paper, 124
autoreset, 110
reset procedure, 134
shutdown procedure, 133
shutdown, abnormal, 147
shutting down, 130
startup, 60
ccmd, 71, 98, 100, 101
consolelog, 99
windows, 39
workspace menu
V2500, 41–44
dfdutil, 98
est_config, 110
workstation
pcirom, 98
712, 36, 98
status, 99
spp_pdc, 97
B180L, 36, 98
sppconsole, 99
differences, 98
T
sppdsh, 71
Tachyon Fibre Channel, 12
tape, 25
ts_config, 71–96, 98
xconfig, 71, 102–109
xsecure, 115
X
xconfig, 11, 71, 102–109
description, 102
tcsh, 39
technical assistance
V-Class servers, xxi
terminal mux, 9
add/configure, 84, 85
remove, 85
utilities board, 4, 9
multiple-cabinet connections, 5
numbering, 119
menu bar, 105
node configuration, 106
node control panel, 108
window, 103, 104, 105
X-dimension CTI cables, 16
xsecure, 115
V
test bus, 36
V2500/V2600
teststation see SSP
tftp, 98
differences, 9
V2500/V2600 server
overview, 1
Y
threads
Y-dimension CTI cables, 16
inquiry features, 123
variables, boot, 127, 128
VCCI, xvii
launch policies, 123
184
Index
Download from Www.Somanuals.com. All Manuals Search And Download.
|