Page 1 Operator’s Guide HP 9000 V2500/V2600 SCA Server First Edition A5845-96001 Customer Order Number: A5845-90001 July 1999 Printed in: USA...
Page 2: Revision History
Revision History Edition: First Document Number: A5845-96001 Notice Copyright Hewlett-Packard Company 1999. All Rights Reserved. Reproduction, adaptation, or translation without prior written permission is prohibited, except as allowed under the copyright laws. The information contained in this document is subject to change without notice.
Page 3: Table Of Contents
Server Console and Diagnostic Connections ....4 V-Class Server Architecture ........6 V2500/V2600 Crossbar Interconnection .
Page 4 DVD-ROM drive ......... . 24 Disk loading slot .
Page 5 HP mode boot menu........
Page 6 HP-UX 11.10 SCA Enhancements ......122 HP-UX SCA Features ........123 Starting HP-UX .
Page 7 Logical Volume Manager (LVM) related problem....145 Recovery from other situations ......145 Rebooting the system .
Page 8 viii Table of Contents...
Page 9 V-Class Server Components: Cabinet and Service Support Processor..2 Figure 4 Four-Cabinet V2500/V2600 Server Components ......3 Figure 5 Console and Diagnostic Connections for a Four-Cabinet V2500/V2600 Server.5...
Page 10 Figure 41 ts_config “Add/Configure Terminal Mux” selection....84 Figure 42 Terminal mux IP address panel ........85 Figure 43 “Start Console Session”...
Page 11 Tables Table 1 Valid CTI cache sizes ..........12 Table 2 Indicator LED operation .
Page 12 List of Tables...
Page 13: Preface
Preface 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...
Page 14: Notational Conventions
Preface Notational conventions This section describes notational conventions used in this book. In command examples, bold monospace identifies input that must be typed exactly as shown. In paragraph text, monospace identifies monospace command names, system calls, and data structures and types. In command examples, monospace identifies command output, including error messages.
Page 15 Horizontal ellipses (...) Vertical ellipses Keycap 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...
Page 16: Safety And Regulatory Information
Preface Safety and regulatory information 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.
Page 17: Japanese Radio Frequency Interference Vcci
Preface Japanese radio frequency interference VCCI Figure 1 Japanese radio frequency notice 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.
Page 18: Acoustics (Germany)
Preface Figure 2 BCIQ (Taiwan) Acoustics (Germany) Laermangabe (Schalldruckpregel LpA) gemessen am fiktiver Arbeitsplatz bei normalem Betrieb nach DIN 45635, Teil 19: LpA =65.3 Acoustic Noise (A-weighted Sound Pressure Level LpA) measured at the bystander position, normal operation, to ISO 7779: LpA = 65.3 dB. IT power system This product has not been evaluated for connection to an IT power system (an AC distribution system having no direct connection to earth...
Page 19: Installation Conditions (U.s.)
Installation conditions (U.S.) See installation instructions before connecting to the supply. Voir la notice d’installation avant de raccorder au réseau. CAUTION Please note the following conditions of installation: 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.
Page 20: Associated Documents
– 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) •...
Page 21: Technical Assistance
Preface Technical assistance 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.
Page 22: Reader Feedback
Please report any technical inaccuracies immediately. You can reach us through email at: fes_feedback@rsn.hp.com Please include the following information with your email: • Title and part number of the document • Edition number...
Page 23: Overview
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.
Page 24: V-Class System Components
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.
Page 25: The Service Support Processor
Figure 4 Four-Cabinet V2500/V2600 Server Components The Service Support Processor 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...
Page 26: Server Console And Diagnostic Connections
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...
Page 27 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.
Page 28: V-Class Server Architecture
Overview V-Class Server Architecture V-Class Server Architecture 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.
Page 29: Figure 5 Console And Diagnostic Connections For A Four-Cabinet V2500/V2600 Server.5 Figure 6 Functional Diagram Of A Single-Cabinet V2500/V2600 Server
Figure 6 Functional Diagram of a Single-Cabinet V2500/V2600 Server Controller Controller Controller Controller Controller Controller Controller Controller SSP Workstation Chapter 1 Processor Agent Processor Agent Processor Agent Processor Agent Processor Agent Processor Agent Processor Agent Processor Agent Core Utilities Board...
Page 30: V2500/V2600 Cabinet Components
Each ERAC has 16 ports, 4 send and 4 receive on each side, which may operate simultaneously. V2500/V2600 Cabinet Components The key components within a V2500/V2600 server cabinet include: • “Core Utilities Board” on page 9 • “Processors” on page 9 •...
Page 31: Core Utilities Board
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.
Page 32: Figure 8 Conceptual Overview Of V2500/V2600 Memory Board
32 MByte, 128 MByte, and 256 MByte. Only specified mixed DIMM size configurations are supported. If planning for a multiple-cabinet server configuration, you must use 88- bit DIMMs and configure your V2500/V2600 server to be one-fourth, one- half, or fully populated with DIMMs.
Page 33 “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.
Page 34: Input/Output
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. Input/Output 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.
Page 35: Figure 9 Numbering And Locations Of Single-Cabinet V2500/V2600 Pci I/O
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 ioscan utility) 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.
Page 36: Figure 10 Numbering And Locations Of Multiple-Cabinet V2500/V2600 Pci I/O
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 numbered with the first field of the hardware path of 0 to 7.
Page 37: Multiple-Cabinet Server Connections
Server Hardware Configuration” on page 118. Multiple-Cabinet Server Connections All cabinets in a multiple-cabinet V2500/V2600 server are tightly connected using HP’s Coherent Toroidal Interconnect (CTI) technology. CTI is an extension of the Scalable Coherent Interface standard defined by the IEEE.
Page 38: Figure 11 Four-Cabinet V2500/V2600 Server Cti Cable Connections
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.
Page 39 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...
Page 40: V2500/V2600 Cabinet Configurations
Overview V2500/V2600 Cabinet Configurations V2500/V2600 Cabinet Configurations 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...
Page 41: Figure 12 Sample V2500/V2600 Cabinet Configurations
Figure 12 Sample V2500/V2600 Cabinet Configurations A single-cabinet V2500/V2600 server with 16 pro- cessors and 16 Gbytes memory, using 256 MByte Chapter 1 V2500/V2600 Cabinet Configurations A three-cabinet V2500/V2600 server with 48 pro- cessors and 96 Gbytes memory, using 256 MByte...
Page 42 Overview V2500/V2600 Cabinet Configurations Chapter 1...
Page 43: Indicators, Switches, And Displays
Indicators, switches, and displays This section describes indicators, switches, and displays of the HP 9000 V2500 server. Chapter 2...
Page 44: Operator Panel
Operator panel Operator panel 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.
Page 45: Key Switch Panel
Key switch panel 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.
Page 46: Toc
Indicators, switches, and displays Operator panel The TOC (Transfer Of Control) button is a recessed switch that resets the system. DVD-ROM drive 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.
Page 47: Busy Indicator
Busy indicator 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.
Page 48: Eject Button
Indicators, switches, and displays Operator panel Table 2 Indicator LED operation Tape Clean (Activity) (Attention) LED LED (green) (amber) Flashing slowly Flashing rapidly Flashing slowly Flashing slowly Eject button Push the eject button to remove cartridges from the tape drive. The drive performs the following Unload sequence: 1.
Page 49: System Displays
System Displays The V-Class servers provide two means of displaying status and error reporting: an LCD and an Attention light bar. Figure 17 System displays LCD display Attention light bar Chapter 2 Indicators, switches, and displays System Displays IOLM010 9/18/97...
Page 50: Lcd (Liquid Crystal Display)
When the operator panel key switch is turned on, the LCD powers up but 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:...
Page 51: Table 3 Processor Initialization Steps
Table 3 Processor initialization steps Step 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.
Page 52: Message Display Line
Indicators, switches, and displays System Displays Status DECONFIG: processor has been deconfigured by POST or the user. EMPTY: Empty processor slot. UNKNOWN: processor slot status in unknown. Message display line The message display line shows the POST initialization progress. This is updated by the monarch processor.
Page 53: Attention Light Bar
Attention light bar 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.
Page 54: Environmental Errors
System Displays Environmental errors 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.
Page 55 Identifying a node with the blink command 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. Step 1.
Page 56 Indicators, switches, and displays System Displays Chapter 2...
Page 57: Ssp Operation
SSP operation This chapter describes the operation the SSP in conjunction with a V-Class server and includes: • SSP log-on • Using the CDE (Common Desktop Environment) Workspace menu • Using the console • SSP file system • System log pathnames...
Page 58: Ssp And The V-Class System
V-Class server. The SSP has HP-UX installed and operates independently from the main server. HP-UX 10.20 is required to allow the workstation to function as the SSP. IMPORTANT Additional software has been added to the basic HP-UX 10.20 to provide all the necessary functions of the SSP.
Page 59: 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 root 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.
Page 60: Figure 19 Ssp User Windows For V2500/V2600 Servers With One Node
SSP operation SSP log-on Figure 19 SSP user windows for V2500/V2600 servers with one node Chapter 3...
Page 61: Figure 20 Ssp User Windows For V2500/V2600 Servers With More Than Two Nodes
SSP operation SSP log-on Figure 20 SSP user windows for V2500/V2600 servers with more than two nodes Chapter 3...
Page 62: Message Window
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”...
Page 63: Using The Cde (Common Desktop Environment) Workspace Menu
Using the CDE (Common Desktop Environment) Workspace menu Using the CDE (Common Desktop Environment) Workspace menu 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.
Page 64: Figure 21 Ssp Workspace Submenus For V2500/V2600
SSP operation Using the CDE (Common Desktop Environment) Workspace menu Figure 21 SSP Workspace submenus for V2500/V2600 Figure 22 SSP Workspace submenus for V2500/V2600 Chapter 3...
Page 65 V2500/V2600 Workspace menu options include: • V-Class Complex: 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. • Console—Creates a new console window for a list of available node/complexes.
Page 66 SSP operation Using the CDE (Common Desktop Environment) Workspace menu • Restart Workspace Manager—Stops and restarts the Workspace Manager. • logout—Closes all open windows and stops Workspace Manager. Chapter 3...
Page 67: Using The Console
Using the console The console serves as the communication device for the V-Class server. Virtual consoles are also used to monitor specific operations, like a system software crash dump. Creating new console windows Console windows can also be created using the sppconsole and xterm commands from the SSP;...
Page 68: Starting The Console From The Workspace Menu
SSP operation Using the console Starting the console from the Workspace menu To start the console using the Workspace menu, complete the following steps: Step 1. Move the pointer over the CDE workspace backdrop. Step 2. Press and hold down any mouse button. The Workspace (root) menu appears.
Page 69: Starting The Console Using Ts_Config
For example: COMPLEX_NAME = [Select from colossus, guardian] Step 3. Start the console. Enter: sppconsole NOTE Running sppconsole without any additional parameters defaults to Node 0 in the current complex. sppconsole 2 would start a console on Node 2. The new sppconsole window appears. In the example above, even if the user’s "default complex"...
Page 70: Starting The Console Using The Consolebar
SSP operation Using the console Step 5. Enter the root password. Refer to “Starting ts_config” on page 92 for information on starting ts_config from a local or remote shell. Step 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.
Page 71: Starting The Console By Logging Back On
Step 3. Drag the mouse pointer to the logout menu option. Step 4. Release the mouse button to select the option. The SSP closes all open windows and returns a HP-UX login prompt. Step 5. Log into the SSP as sppuser. The new sppconsole window displays.
Page 72: Watching The Console
SSP operation Using the console Example: Performing a ^E command To execute the ^Ecf 1. Press the key and the Cntrl 2. Release the Cntrl 3. Press the key. 4. Press the key. Watching the console 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.
Page 73: Assuming Control Of The Console
CTRL- The period is part of the command. Assuming control of the console 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.
Page 74: Changing A Console Connection
SSP operation Using the console Changing a console connection 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- To change an active console window to watch window, enter: CTRL-...
Page 75: Targeting Commands To Nodes
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_config and assigned a complex name before it can be accessed. Targeting commands to nodes Use the jf-ccmd_info command to determine what names or IP addresses the JTAG interfaces have been set to on an SPP.
Page 76: Ssp File System
SSP operation SSP file system 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. Figure 23 SSP file system for V2500/V2600 servers /spp...
Page 77: Spp/Bin
The console-server that directs RS-232 console traffic conserver from the Utility Board to the various sppconsole sessions. /spp/bin In the /spp/bin directory are specific commands and daemons that manage a V-Class node. Some of these are: The command (Exemplar Scan Test) to initiate scan testing.
Page 78: Spp/Firmware
SSP operation SSP file system A file containing all the console activity on the system, consolelogX where X is the node ID. The scan testing log. est.log Log of all hard failure information. Logs the output of hard_hist all suspected ASIC (Application Specific Integrated Circuits).
Page 79: Device Files
Device files Table 8 shows the differences in the device files between the HP B180L and HP 712 SSPs. Table 8 Device file differences Device Private/diagnostic LAN Global/customer LAN Node 0 console port Terminal mux configuration port Remote modem Chapter 3...
Page 80: System Log Pathnames
SSP operation System log pathnames System log pathnames To separate the configuration and log files for each complex, several files have been moved to complex-specific directories. In Table 9, complex denotes specific complex names. These are assigned by the operator using ts_config.
Page 81: Firmware (Obp And Pdc)
Firmware (OBP and PDC) This chapter discusses the boot sequence and the commands available from the boot menu. Chapter 4...
Page 82: Boot Sequence
Boot sequence Boot sequence OpenBoot PROM (OBP) and SPP Processor Dependent Code (SPP_PDC) make up the firmware on HP V-Class servers that makes it possible to boot HP-UX. Once a machine powers on, the firmware controls the system until the operating system (OS) executes.
Page 83: Figure 24 Boot Process
Prompt displays: Processor is starting the autoboot process. To discontinue, press any key within 10 seconds. Chapter 4 Autoboot Enabled? Continue Automatically? HP-UX boots Firmware (OBP and PDC) Boot sequence Boot menu displays Press any key to display boot menu...
Page 84: Boot Process Output
Firmware (OBP and PDC) Boot process output Boot process output 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.
Page 85 Keyboard path = 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 PDC_ENTRY version 4.2.0.4 POST Revision: 1.0.0.2...
Page 86: Hp Mode Boot Menu
Firmware (OBP and PDC) HP mode boot menu HP mode boot menu 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: •...
Page 87: Table 10 Boot Menu Commands
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. Initiates the boot sequence. A default or specified path to the boot device can be used.
Page 88 Firmware (OBP and PDC) HP mode boot menu Command PAth [PRI|ALT|CON] [path] PDT [CLEAR|DEBUG] PIM_info [cpu#] [HPMC|TOC|LPMC] RemoteCommand node# command RESET [hard|debug] RESTrict [ON|OFF] SCSI [INIT|RATE] [bus slot val] SEArch [path] SECure [ON|OFF] TIme [cn:yr:mo:dy:hr:mn[:ss]] VErsion Description Displays or sets primary, alternate, console, and keyboard hardware paths.
Page 89: Enabling Autoboot
Enabling Autoboot AUto displays 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.
Page 90: Examples
Firmware (OBP and PDC) Enabling Autoboot Examples This command displays the status of the Autoboot and Autosearch flags. Autoboot:ON Autosearch:ON This command displays the current setting of the au bo Autoboot flag. Autoboot:ON This command sets the Autoboot flag ON. au bo on Autoboot:ON Chapter 4...
Page 91: Help Command
HElp command The help command displays help information for the specified command or redisplays the boot menu. Syntax HElp [command] Used alone, HElp displays the boot menu. Specifying command displays the syntax and description of the named command. Examples The following example illustrate use of this command: This command displays information for the auto help au command.
Page 92 Firmware (OBP and PDC) HElp command Chapter 4...
Page 93: Configuration Utilities
Configuration utilities This chapter describes server configuration management and includes: • ts_config • ccmd • xconfig • Configuration utilities Two utilities, sppdsh and 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.
Page 94: Ts_Config
• 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. Starting ts_config...
Page 95: Ts_Config Operation
Configuration utilities ts_config For example: $ DISPLAY=myws:0; export DISPLAY (sh/ksh/sppdsh) % setenv DISPLAY myws:0 (csh/tcsh) Also, the -display start-up option may be used as shown below: For example: # /spp/bin/ts_config -display myws:0 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.
Page 96: Table 11 Ts_Config Status Values
Configuration utilities ts_config ts_config automatically 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_config window indicates whether a node has been selected.
Page 97: Configuration Procedures
Configuration Status Active The node is configured and answering requests on the Diagnostic LAN. 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.
Page 98: Figure 26 Ts_Config Showing Node 0 Highlighted
Configuration utilities ts_config Figure 26 ts_config showing node 0 highlighted Notice that after the node has been highlighted that ts_config displays information concerning the node. In this step, it tells the user what action to take next, “This node’s JTAG firmware must be upgraded. Select “Actions,”...
Page 99: Configure A Node
Figure 28 Upgrade JTAG firmware confirmation panel Step 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. Figure 29 ts_config power-cycle panel When the node is powered up, the “Configuration Status”...
Page 100: Figure 30 Ts_Config Indicating Node 0 As Not Configured
Configuration utilities ts_config Figure 30 ts_config indicating Node 0 as not configured Step 2. Select “Actions” and then click “Configure Node,” as shown in Figure 31. Figure 31 ts_config “Configure Node” selection. After invoking ts_config to configure the node, a node configuration panel appears as the one in Figure 32.
Page 101: Figure 32 Ts_Config Node Configuration Panel
Figure 32 ts_config node configuration panel Step 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: Step 4.
Page 102: Figure 33 Ts_Config Restart Workspace Manager Panel
Configuration utilities ts_config Figure 33 ts_config restart workspace manager panel. Step 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. Figure 34 ts_config indicating Node 0 is configured Step 7.
Page 103: Configure The Scub_Ip Address
Configure the scub_ip address Step 1. Select the desired node from the list of available nodes. Step 2. In the ts_config display panel, select “Actions” and then “Configure ‘scub_ip’ address,” as shown in Figure 35. Figure 35 ts_config “Configure ‘scub_ip’ address” selection ts_config checks the scub_ip address stored in NVRAM on the SCUB in the node.
Page 104: Reset The Node
Configuration utilities ts_config Figure 37 ts_config scub_ip address configuration confirmation Step 4. A panel as the shown in Figure 38 appears confirming that the scub_ip address is set. Click OK. Figure 38 ts_config scub_ip address set confirmation panel Initiate a node reset to activate the new scub_ip address. Reset the Node Step 1.
Page 105: Figure 39 Ts_Config "Reset Node" Selection
Figure 39 ts_config “Reset Node” selection A panel as the one shown in Figure 40 appears. Figure 40 ts_config node reset panel Step 3. In the Node Reset panel, select the desired “Reset Level” and “Boot Options,” then click Reset.” Chapter 5 Configuration utilities ts_config...
Page 106: Deconfigure A Node
Configuration utilities ts_config Deconfigure a Node 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. Step 1.
Page 107: Remove Terminal Mux
Figure 42 Terminal mux IP address panel Remove terminal mux ts_config does not remove the terminal mux if any node consoles are assigned to terminal mux ports. Step 1. Select “Actions,” then “Configure Terminal Mux.” Step 2. Select “Remove Terminal Mux,” then click “Yes.” Console sessions ts_config may also start console sessions by selecting the desired node(s) and then selecting the “Start Console Session”...
Page 108: Figure 43 "Start Console Session" Selection
Configuration utilities ts_config Figure 43 “Start Console Session” selection Figure 44 Started console sessions Chapter 5...
Page 109: V2500/V2600 Sca (Multinode) Configuration
V2500/V2600 SCA (multinode) configuration ts_config can also configure a V2500/V2600 SCA system. An example to follow describes how. The example assumes that there are two active 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_config as described in “Starting ts_config”...
Page 110: Figure 46 Ts_Config Configure Multinode Complex Selection
Configuration utilities ts_config Figure 46 ts_config Configure Multinode complex selection Step 3. When “Configure Multinode complex” is selected, a configuration dialog appears as shown in Figure 57. Figure 47 Configure Multinode Complex dialog window Chapter 5...
Page 111 Step 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. •...
Page 112: Figure 48 Configure Multinode Complex Dialog Window With Appropriate Values
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.
Page 113 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. •...
Page 114: V2500/V2600 Split Sca Configuration
Configuration utilities ts_config Figure 50 ts_config showing newly configured complexes 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.
Page 115: Figure 51 Ts_Config Split Multinode Complex Operation
Figure 51 ts_config Split Multinode complex operation Figure 52 ts_config Split Multinode complex panel Step 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.
Page 116: Figure 53 Ts_Config Split Multinode Complex Panel Filled In
Configuration utilities ts_config Figure 53 ts_config Split Multinode complex panel filled in The message shown in Figure 54 appears indicating the configuration is taking place. Figure 54 Split Multinode confirmation panel Figure 55 shows the main ts_config display after the split multinode operation has completed.
Page 117: Ts_Config Files
ts_config files ts_config either reads or maintains the following SSP configuration files: The standard system hosts file, includes entries for the /etc/hosts cabinet related IP addresses. /etc/services Service definitions for the console interface. /etc/ Contains entries for starting console related processes inetd.conf /spp/data/ nodes.conf...
Page 118 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).
Page 119: Ssp-To-System Communications
A layer of firmware between HP-UX and OBP (Open Boot PROM) called spp_pdc allows 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.
Page 120: Lan Communications
Configuration utilities SSP-to-system communications LAN communications 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 JTAG port is used for scanning, and the NFS-FWCP port is used for downloading system firmware via nfs using the fwcp utility, via tftp using the pdcfl utility, downloading disk firmware using the dfdutil utility...
Page 121: Serial Communications
Serial communications 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 sppconsole and ttylink utilities and the consolelogx log file.
Page 122: Ccmd
Configuration utilities ccmd ccmd ccmd (Complex Configuration Management Daemon) is a daemon that maintains a database of information about the V2500/V2600 hardware. ccmd also 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.
Page 123 Configuration utilities ccmd If started with no options, ccmd disassociates 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 ccmd is sent a SIGHUP, it regenerates the database. All scan-based operations require ccmd.
Page 124: Xconfig
% 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.
Page 125: Figure 57 Xconfig Window-Physical Location Names
Configuration utilities xconfig Figure 57 xconfig window—physical location names Chapter 5...
Page 126: Figure 58 Xconfig Window-Logical Names
Configuration utilities xconfig Figure 58 xconfig window—logical names As buttons are clicked, the item selected changes state and color. There is a legend on the screen to explain the color and status. The change is recorded in the 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.
Page 127: Menu Bar
The main xconfig window 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. Menu bar The menu bar appears at the top of the xconfig main window.
Page 128: Node Configuration Map
Configuration utilities xconfig Node configuration map The node configuration map is a representation of the left and right side views of a node as shown in Figure 60. Figure 60 xconfig window node configuration map Chapter 5...
Page 129: Node Control Panel
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. •...
Page 130: Figure 61 Xconfig Window Node Control Panel
Configuration utilities xconfig Figure 61 xconfig window node control panel The node number is shown in the node box. A new number can be selected by clicking on the node box and selecting the node from the pull- down menu. A new complex can be selected by clicking on the complex box and selecting it from the pull-down.
Page 131 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.
Page 132: Configuration Utilities
Configuration utilities Configuration utilities Configuration utilities V2500/V2600 diagnostics provides utilities that assist the user with configuration management. autoreset autoreset allows the user to specify whether ccmd should automatically reset a complex after a hard error and after the hard logger error analysis software has run. autoreset occurs if a ccmd_reset file does not exist in the complex-specific directories Arguments to autoreset arguments include <complex_name>...
Page 133: Report_Cfg
(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 Show all details...
Page 134: Effects Of Hardware And Software Deconfiguration
Configuration utilities Configuration utilities Effects of hardware and software deconfiguration report_cfg counts 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.
Page 135: Report_Cfg Asic Report
report_cfg ASIC report To obtain a report on the ASICs in a complex, use the -A option. The following is a sample ASIC report by report_cfg: report_cfg -A Complex |Node#| ====================+=====+=======================+======================= hw2a hw2a Complex |Node| Slot ====================+====+=======+======+======+======+======+ hw2a hw2a hw2a hw2a hw2a hw2a...
Page 136: Report_Cfg Memory Report
Configuration utilities Configuration utilities report_cfg memory report To obtain a report on the memory in a complex, use the -m option. The following is a sample memory report by report_cfg: report_cfg -m Complex |Node#| ====================+=====+=======================+======================= hw2a hw2a |Mem. | Complex |Node|Board| ============+====+=====+=======================+===+===+===+===+===+==== hw4a...
Page 137: Report_Cfg Processor Report
report_cfg processor report To obtain a report on the processor in a complex, use the -p option. The following is a sample processor report by report_cfg: report_cfg -p Complex |Node#| ====================+=====+=======================+======================= hw2a hw2a Complex |Node#|Processor | COP ====================+=====+==========+=======================+======== hw2a hw2a hw2a hw2a hw2a...
Page 138 Configuration utilities Configuration utilities If the command line [-on | -off | -check] options are used, xsecure does not use the GUI interface. These options allow the user to turn the secure mode on, off or allow the user to check the secure mode status.
Page 139: Hp-Ux Operating System
HP-UX Operating System Different versions of the HP-UX operating system run on a V-Class server and its Service Support Processor. This section covers issues related to using HP-UX V11.0 and HP-UX V11.10 on V-Class servers. Multiple-cabinet server configurations and HP-UX SCA features require that HP-UX V11.10 be installed.
Page 140: Hp-Ux On The V2500/V2600
HP-UX on the 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.
Page 141: Table 13 Hardware Path Numbering For V2500/V2600 Cabinets
Hardware Component 0–7 PCI I/O bus bridges (card cages) Memory Core utilities board 16–47 Processors (PA-RISC CPUs) 64–71 PCI I/O bus bridges (card cages) Memory Core utilities board 80–111 Processors (PA-RISC CPUs) HP-UX Operating System HP-UX on the V2500/V2600 Description of...
Page 142: Configuring Hp-Ux For V-Class Servers
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.
Page 143: Multiple-Cabinet Kernel Configurations
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.
Page 144: Process And Thread "Gang Scheduling
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 ON or OFF.
Page 145: Hp-Ux Sca Features
Both traditional system architectures as well as SCA systems are supported by the HP-UX 11.10 enhancements. HP-UX SCA Features HP-UX V11.10 SCA programming and launch features provide the following capabilities.
Page 146 “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. Chapter 6...
Page 147: Starting Hp-Ux
• 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.
Page 148: Power-On Sequence
(cabinet ID 0). This helps ensure that all cabinets synchronize following power on self test. Step 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.
Page 149: Boot Variables
Step 4. Issue the OBP menu’s BOOT command 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.
Page 150: Reviewing The State Of The File System
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.
Page 151 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 HP-UX Operating System Starting HP-UX...
Page 152: Stopping Hp-Ux
Stopping 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.
Page 153 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...
Page 154: Rebooting The System
To shutdown HP-UX and reboot the V-Class server, perform the following steps: Step 1. If the server is running HP-UX, log in to the server as root. Step 2. Check activity on the server and warn users of the impending server reboot.
Page 155: Shutting Down The System
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 Step 5. Shut down and halt HP-UX using the shutdown or reboot command. Enter: shutdown -h reboot -h Progress messages detailing system shutdown activities print to the terminal.
Page 156: Resetting The V2500/V2600 Server Hardware
Processor. Before running do_reset from the Service Support Processor you NOTE 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).
Page 157 -h command. 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.
Page 158 HP-UX Operating System Stopping HP-UX Chapter 6...
Page 159: Recovering From Failures
Recovering from failures 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.
Page 160: Collecting Information
Collecting information 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.
Page 161: Performance Problems
Step 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...
Page 162: System Hangs
SSP. See “Resetting the V2500/ V2600 server hardware” on page 134. Step 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.
Page 163: System Panics
System panics 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.
Page 164: Peripheral Problem
• Data Segmentation Fault • Instruction Segmentation Fault Step 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.
Page 165: Interface Card And System Problem
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. Step 3. Check to ensure the device address or ID is correct. Step 4.
Page 166: File System Problem
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. Chapter 7...
Page 167: Logical Volume Manager (Lvm) Related Problem
Recovering from failures System panics Logical Volume Manager (LVM) related problem 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.
Page 168: Rebooting The System
Rebooting the system Once a problem has been corrected, reset and reboot the system. Step 1. Reset the V-Class server. See “Resetting the V2500/V2600 server hardware” on page 134. Step 2. If the system panicked due to a corrupted file system, fsck will report the errors and any corrections it makes.
Page 169: Abnormal System Shutdowns
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.
Page 170: Overview Of The Dump And Save Cycle
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...
Page 171: New Sca-Extended Crash Dump Format
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.
Page 172: Configuration Criteria
These factors are discussed in the following sections. Dump 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.
Page 173 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.
Page 174: Crash Information Integrity
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.
Page 175 Recovering from failures Abnormal system shutdowns Dump definitions built into the kernel vs. defined at runtime 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/fstab file) 3.
Page 176: Disk Space Needs
155. Compressed save vs. noncompressed save 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. Chapter 7...
Page 177: Defining Dump Devices
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.
Page 178: Kernel Dump Device Definitions
Recovering from failures Abnormal system shutdowns CLASS PAGES INCLUDED IN DUMP -------- ---------- ---------------- UNUSED 2036 USERPG 6984 BCACHE 15884 KCODE 1656 USTACK yes, by default FSDATA yes, by default KDDATA 2860 yes, by default KSDATA 3062 yes, by default Total pages on system: Total pages included in dump: DEVICE...
Page 179 Step 5. Boot the system from the new kernel file to activate the new dump device definitions. Using HP-UX commands to configure dump devices into the kernel The system file can be edited and the config program used to build the new kernel.
Page 180: Runtime Dump Device Definitions
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...
Page 181 Abnormal system shutdowns The /etc/fstab file Define entries in the fstab file to activate dump devices during the HP- UX initialization (boot) process or when crashconf reads the file. The format of a dump entry for /etc/fstab looks like the following:...
Page 182: Dump Order
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.
Page 183: Operator Override Options
The dump 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).
Page 184: The Reboot
What to do after the system has rebooted? 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.
Page 185: Using Crashutil To Complete The Saving Of A Dump
HP-UX file system area has been configured before doing 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.
Page 186: Analyzing Crash Dumps
Analyzing crash dumps 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.
Page 187: Appendix A: Led Codes
LED codes 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.
Page 188: Power On Detected Errors
LED codes Power on detected errors 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.
Page 189 Fault FPGA not OK 1. Core Utilities Board (CUB) 2. MUC cannot get correct dc OK error 1. Power supply is reporting (Upper Left) 2. This is the first of two or more dc OK error 1. Power supply is reporting (Upper Right) 2.
Page 190 LED codes Power on detected errors Fault 08-11 48V error 1. Error occurs when 48 volt NPSUL failure PWRUP=0-9 2. Excessive load on 48 volts due 3. Possible node power supply 12-1B 48V error 1. Error occurs when 48 volt NPSUR failure PWRUP=0-9...
Page 191 Fault 1C-25 48V error 1. Error occurs when 48 volt NPSLL failure PWRUP=0-9 2. Excessive load on 48 volts due 3. Possible node power supply 26-2F 48V error 1. Error occurs when 48 volt NPSLR failure PWRUP=0-9 2. Excessive load on 48 volts due 3.
Page 192 LED codes Power on detected errors Fault 30-39 48V error 1. Error occurs when 48 volt (maintenance) no supply failure reported PWRUP=0-9 2. Excessive load on 48 volts due 3. Possible node power supply 48V Yo Yo 1. Core utilities board (CUB) error 2.
Page 193: Cub Detected Memory Power Fail
CUB detected memory power fail This describes covers memory errors detected by the monitoring utilities chip (MUC) on the core utilities board after power-on. Table 16 CUB detects memory power fail Fault MB0L Power Fail MB1L Power Fail MB2R Power Fail MB3R Power Fail MB4L Power Fail MB5L Power Fail...
Page 194: Cub Detected Processor Error
LED codes CUB detected processor error CUB detected processor error This section describes processor errors detected by the monitoring utilities chip (MUC) on the core utilities board after power-on. Table 17 CUB detects processor power fail Fault PB0L Power Fail PB1R Power Fail PB2R Power Fail PB3R Power Fail...
Page 195: Cub Detected I/O Error
CUB detected I/O error This section describes I/O errors detected by the monitoring utilities chip (MUC) on the core utilities board after power-on. Table 18 CUB detects I/O (IOB) power fail Fault Left Front I/O Board failure Left Rear I/O Board failure Right Front I/O Board failure Right Rear...
Page 196: Cub Detected Fan Error
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. Table 19 CUB detects fan power fail...
Page 197: Cub Detected Ambient Air Errors
CUB detected ambient air errors This section describes air errors detected by the monitoring utilities chip (MUC) on the core utilities board after power-on. Table 20 CUB detects ambient air error Fault Ambient hot 1. Ambient air too hot. 2. Core utilities board (CUB) powers 3.
Page 198: Cub Detected Hard Error
LED codes CUB detected hard error CUB detected hard error This section describes hard errors detected by the monitoring utilities chip (MUC) on the core utilities board after power-on. Table 21 Hard error Fault Hard error 1. Hard error lines to core utilities (RAC) (PAC) (MAC) (TAC) (SAGA)
Page 199: Cub Detected Intake Ambient Air Error
CUB detected intake ambient air error This section describes air intake errors detected by the monitoring utilities chip (MUC) on the core utilities board after power-on. Table 22 Ambient air (intake) error Fault Ambient air too warm is an environmental warning Appendix A Symptoms...
Page 200: Cub Detected Dc Error
LED codes CUB detected dc error CUB detected dc error This section describes dc errors detected by the monitoring utilities chip (MUC) on the core utilities board after power-on. Table 23 dc error Fault NPSUL 1. Node power supply (Viewed from failure (warning) 2.
Page 201 HP-UX – utilities conserver console see also SSP assuming control changing connection commands controlling remotely creating windows HP-UX, runs on – starting commands starting from ts_config switch modes using watching console port multiple-cabinet connections consolelog core dump Core Utility Board (CUB)
Page 202 Web site gang scheduler ioscan command model command rebooting after a system panic shut down procedure starting stopping system calls top command tuned parameter sets HP-UX system interruptions HP-UX, runs on test station HVD FWD SCSI Index...
Page 203 HyperPlane Crossbar controllers listing multiple-cabinet numbering numbering physical access supported cards indicator LEDs DVD-ROM indicators DAT drive LEDs dc on LED light bar installation conditions interconnecting hardware interleaving of memory ioscan command IP address IT power system xviii jf-ccmd_info JTAG kernel configuration threads...
Page 204 IDs configurations console and diagnostic connections CTI cable connections CTI controller I/O numbering memory configuration numbering Scalable Computing Architecture server configurations NASTRAN network cache. see CTI cache memory node see also complex – configure deconfigure reset node routing board...
Page 205 VCCI xvii SAM utility savecore savecrash see also multiple-cabinet configuration – split HP-UX support kernel configuration Scalable Coherent Interface Scalable Computing Architecture.see SCA SCSI scub_ip address configure server configurations Service Support Processor connections to V2500/V2600 server...
Page 206 Service Support Processor connection technical assistance V2200 server V2250 server V2500/V2600 server volume group zero (vg00) warning, defined Web site white paper HP-UX SCA Programming and Process Management White Paper windows workspace menu – V2500 workstation B180L differences –...

This manual is also suitable for:

9000 v2600 sca

HP 9000 V2500 SCA Operator's Manual

Preface

1 Overview

2 Indicators, Switches, and Displays

3 SSP Operation

4 Firmware (OBP and PDC)

5 Configuration Utilities

6 HP-UX Operating System

7 Recovering from Failures

Appendix A: LED Codes

Quick Links

Related Manuals for HP 9000 V2500 SCA

Summary of Contents for HP 9000 V2500 SCA