Home » HP Manuals » Servers » HP Integrity Superdome SX2000 » Manual Viewer

HP Integrity Superdome SX2000 User Guide, Sixth Edition - HP Integrity Superdo - Page 300

Architecture Files, Example G-8, Typical, Board Name Mapping File, Format, Complex Architecture File

View all HP Integrity Superdome SX2000 manuals

Add to My Manuals
Save this manual to your list of manuals

Page 300 highlights

JUST Exploration Tool Data Files Example G-8 Typical cplx.ini File COMPLEX zurg-s 0x20 SH MP 0 1.0 TCP 15.99.83.130 5151 COMPLEX feynman-s 0x30 MH host_1 MP 0 1.0 UDP 19.99.83.101 5151 COMPLEX feynman-s 0x30 MH host_2 MP 0 1.0 TCP 15.99.83.102 5151 Board Name Mapping File The board_name.map file has two basic purposes. The first is to map board names to board part numbers. This mapping is required, because the part numbers in the EPROMs are changed to indicate repair history of the board. JET must be able to provide the JUST tool with part number matching its data files. The second is to support the JET interactive mode. This file contains scan handle values that map a board name with the type of board that name represents. When a user is adding a board of a specific type, JET looks though this file to find the name of all boards matching the specified type. It then displays a list of these board names for the user to select. This file is located by the default path search with the subdirectory arch_/cmd appended to the base path, unless it exists in the ./config directory. Format Comments Comments in the board_name.map file are specified by placing a # character at the beginning of the line containing the comment. End of line comments are not currently supported. Version The first non-comment field in the board_name.map file must start with the keyword FILE_VERSION followed by the version number entered as a double. FILE_VERSION Board Entries Each board in the system has an entry in this file, which consists of the following information: Board name-String representing the board name Board part number-String representing the board part number to place in the node configuration file for this board Scan Revision-Scan revision of the board Board family-Board family scan handle value Board type-Board type scan handle value Example G-9 Board Entries With Comments board family>

Section	Page
Preface	9
Scope	10
Book Layout	11
Revision History	12
1 Overview	13
Basic System Building Blocks	15
Configuration Rules	20
Utilities Subsystem	21
UGUY	21
SBCH	21
SBC	21
HUCB	21
Cell Board	22
Cell Controller	23
Processors and Front-Side Bus Interfaces	23
Crossbar Link	23
Remote I/O Link	24
Memory Interface—Memory Multiplexer	24
Processor Dependent Hardware	24
Cell Power Board	25
PCI-X I/O	26
PCI-X Backplane	26
PCI-X Power Board	27
PCI-X Transfer Board	28
Core I/O	28
System Backplane	29
Front Panel Display Cell OL* LED	30
Firmware	31
User Interface	31
Event IDs for Errors and Events	31
2 Installing the System	33
Introduction	34
Communications Interference	34
Electrostatic Discharge	34
Unpacking and Inspecting	35
Verifying Site Preparation	35
Checking the Inventory	35
Inspecting the Shipping Containers for Damage	36
Unpacking and Inspecting Hardware Components	38
Unpacking the PDCA	46
Returning Equipment	47
Setting Up the hp Integrity Superdome or hp 9000 Superdome	49
Moving the System and Related Equipment to the Installation Site	49
Unpacking and Installing the Blower Housings and Blowers	49
Attaching Side Skins and Blower Side Bezels	52
Attaching the Leveling Feet and Leveling the cabinet	55
Installing the Front Door Bezels and the Front and Back Blower Bezels	55
Installing and Verifying the PDCA	59
Removing the EMI Panels	64
Connecting the Cables	65
Routing I/O Cables	66
Connecting the MP to the Customer LAN	69
Connecting the MP to the Network	69
Setting Customer IP Address	70
Turning On Housekeeping Power	72
Booting and Verifying the System	75
Connecting to the Management Processor	75
Powering on the System 48 Volts	78
Booting hp Integrity Superdome to EFI Shell	79
Booting hp 9000 to BCH Shell	81
Verifying the System	82
Running JET Software	85
Power Cycling After Using JET	85
Attaching Rear Kick Plates	86
Performing a Visual Inspection and Completing the Installation	87
Post-System-Installation Check	91
3 Removing and Replacing Components	93
Powering Down and Powering Up the System	94
Removing and Replacing the Cabinet Side Skins	95
Removing the Cabinet Side Skins	96
Replacing the Cabinet Side Skins	96
Removing and Replacing the Front Electromagnetic Interference (EMI) Cover	97
Removing the Front EMI Cover	97
Replacing the Front EMI Cover	97
Removing and Replacing the Rear Electromagnetic Interference (EMI) Cover	98
Removing the Rear EMI Cover	98
Replacing the Rear EMI Cover	99
Removing and Replacing the Side EMI Covers (for a two cabinet system)	101
Removing the Side EMI Covers	101
Replacing the Side EMI Covers	101
Removing and Replacing the Bulk Power Supply (BPS)	102
Removing the Bulk Power Supply	102
Replacing the Bulk Power Supply	103
Installing An Additional Power Distribution Control Assembly	104
Adding the Option 6 or Option 7 PDCAs	104
Removing and Replacing the Front-End Power Supply	106
Removing Power From the Cabinet	106
Removing the FEPS from the Cabinet	106
Replacing the FEPS	112
Removing and Replacing the I/O Fan Module	115
Removing the I/O Fan Module	116
Replacing the I/O Fan Module	116
Removing and Replacing the I/O Fan Mounting Frame	117
Removing the I/O Fan Mounting Frame	117
Replacing the I/O Fan Mounting Frame	117
Removing and Replacing the Air Filter	118
Removing the Air Filters	119
Replacing the Air Filters	119
Removing and Replacing the Blower Side Bezels	120
Removing the Blower Side Bezels	120
Replacing the Blower Side Bezel	121
Removing and Replacing the Rear Blower Bezel	122
Removing the Rear Blower Bezel	123
Replacing the Rear Blower Bezel	123
Removing and Replacing the Blower Module	124
Removing the Blower Module	125
Replacing the Blower Module	125
4 System Specifications	127
Dimensions and Weights	128
Component Dimensions	128
Component Weights	129
Shipping Dimensions and Weights	130
Electrical Specifications	131
Grounding	131
Circuit Breaker	131
Power Options	131
System Power Requirements	133
Component Power Requirements	134
I/O Expansion Cabinet Power Requirements	134
I/O Expansion Cabinet Power Cords	135
Environmental Requirements	136
Temperature and Humidity Specifications	136
Power Dissipation	136
Acoustic Noise Specification	141
Air Flow	142
5 Site Preparation	143
Electrical and Environmental Guidelines	144
Electrical Factors	144
Environmental Elements	149
Facility Guidelines	160
Facility Characteristics	160
Space Requirements	163
Power Options	165
Power Cords	166
Pre-Installation Survey	176
Pre-Installation Survey Content	176
Typical Installation Schedule	176
Site Inspection	177
Delivery Survey	180
A Operating System Boot and Shutdown	183
System Boot Configuration Options	185
Booting HP-UX	188
HP-UX Booting	189
Single-User Mode HP-UX Booting	194
LVM-Maintenance Mode HP-UX Booting	197
Booting the Microsoft Windows Operating System	199
Booting the Red Hat Linux Operating System	201
Booting the SuSE Linux Enterprise Server Operating System	203
Shutting Down HP-UX	205
Shutting Down Microsoft Windows	207
Shutting Down Linux	209
B Powering On and Off the System	211
Shutting Down the System	212
Checking System Configuration	212
Shutting Down the Operating System	215
Preparing the Partitions for Shutdown	216
Powering Off the System Using the	218
Turning On Housekeeping Power	220
Powering on the System Using the	223
C EFI Boot Maintenance Manager for hp Integrity Superdome	225
Boot From a File	227
Add a Boot Option	228
Delete a Boot Option	229
Change Boot Order	230
Manage BootNext Setting	231
Set Auto Boot Timeout	232
Select Active Console Output/Input Devices	233
Select Active Standard Error Devices	234
Cold Reset	235
D Configuration	237
Configuration Guidelines	239
Memory Population	239
Cell Population	239
Partition Size	239
I/O Chassis Allocation	243
System Planner	244
E Replaceable Parts	245
F Management Processor Commands	255
MP Command: AR	256
MP Command: BO	257
MP Command: CA	258
MP Command: CC	259
MP Command: CP	260
MP Command: DATE	261
MP Command: DC	262
MP Command: DF	263
MP Command: DI	264
MP Command: HE	265
MP Command: ID	267
MP Command: IT	268
MP Command: LC	269
MP Command: LS	270
MP Command: MA	271
MP Command: MFG	272
MP Command: MR	273
MP Command: MS	274
MP Command: PD	275
MP Command: PS	276
MP Command: RL	278
MP Command: RR	279
MP Command: RS	280
MP Command: SO	281
MP Command: TC	282
MP Command: TE	283
MP Command: VM	284
MP Command: WHO	285
MP Command: XD	286
G JUST Exploration Tool	287
Jet Set-Up Utility (for PC SMS Only)	288
Command Line Arguments	289
JET Interactive Mode	290
JET Run Menu	290
JET Current Configuration Display Menu	291
JET Update Configuration Menu	293
JET Help Menu	297
Data Files	298
Input Data Files	298
Input Data File Locations	298
Configuration Files	298
Architecture Files	300
Output Data Files	306
Error Conditions	310
H Templates	311
Equipment Footprint Templates	315
Computer Room Layout Plan	316

Match case Limit results 1 per page

Appendix G

JUST Exploration Tool

Data Files

288

Example G-8

Typical

cplx.ini

File

COMPLEX zurg-s

0x20

1.0

TCP

15.99.83.130

5151

COMPLEX feynman-s

0x30

host_1

1.0

UDP

19.99.83.101

5151

COMPLEX feynman-s

0x30

host_2

1.0

TCP

15.99.83.102

5151

Board Name Mapping File

The

board_name.map

file has two basic purposes. The first is to map board names to board part numbers.

This mapping is required, because the part numbers in the EPROMs are changed to indicate repair history of

the board. JET must be able to provide the JUST tool with part number matching its data files. The second is

to support the JET interactive mode. This file contains scan handle values that map a board name with the

type of board that name represents. When a user is adding a board of a specific type, JET looks though this

file to find the name of all boards matching the specified type. It then displays a list of these board names for

the user to select.

This file is located by the default path search with the subdirectory

arch_<arch_code>/cmd

appended to the

base path, unless it exists in the

./config

directory.

Format

Comments

Comments in the

board_name.map

file are specified by placing a # character at the beginning of the line

containing the comment. End of line comments are not currently supported.

Version

The first non-comment field in the

board_name.map

file must start with the keyword

FILE_VERSION

followed by

the version number entered as a double.

FILE_VERSION <version number>

Board Entries

Each board in the system has an entry in this file, which consists of the following information:

Board name—String representing the board name

Board part number—String representing the board part number to place in the node configuration file for this board

Scan Revision—Scan revision of the board

Board family—Board family scan handle value

Board type—Board type scan handle value

Example G-9

Board Entries With Comments

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

#<board family> <board part num> <scan revision> <board family> <board type>

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

HIOB

A4856-60001

Architecture Files

Architecture files describe the system architecture, providing complex, node, board, and device information

needed to properly interrogate the complex.

Complex Architecture File

This file describes the complex and contains information on the types of entities in the complex. Currently

valid entity types are MPs and nodes. This file must have the name

complex.arc