n Class Manual

N4000 Support UpdateApril 2000

rranty

t

rt ofior

Notice

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

HEWLETT-PACKARD PROVIDES THIS MATERIAL “AS-IS” AND MAKES NO WARRANTY OF ANYKIND, EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIESOF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. HEWLETT-PACKARDSHALL NOT BE LIABLE FOR ERRORS CONTAINED HEREIN OR FOR INCIDENTAL ORCONSEQUENTIAL DAMAGES (INCLUDING LOST PROFITS) IN CONNECTION WITH THEFURNISHING, PERFORMANCE OR USE OF THIS MATERIAL WHETHER BASED ON WARRANTY,CONTRACT, OR OTHER LEGAL THEORY.

Some states do not allow the exclusion of implied warranties or the limitation or exclusion of liability forincidental or consequential damages, so the above limitations and exclusion may not apply to you. This wagives you specific legal rights, and you may also have other rights which vary from state to state.

Hewlett-Packard assumes no responsibility for the use or reliability of its software on equipment that is nofurnished by Hewlett-Packard Company.

This document contains proprietary information which is protected by copyright. All rights reserved. No pathis document may be photocopied, reproduced or translated to another program language without the prwritten consent of Hewlett-Packard Company.

Copyright © 1998 by HEWLETT-PACKARD COMPANY

Printing History

Edition 1.0.0 ..........April 17, 2000

N-Class Support Update Table of Contents

7

88

444

9

9

Chapter 1: OverviewPrelude Overview . . . . . . . . . . . . . . . . 6

Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6N4000 OVERVIEW . . . . . . . . . . . . . . 7

Dual System Busses . . . . . . . . . . . . . . . . . . . 8Hot-Swappable/Pluggable Devices . . . . . . . . 8

Internal Disk Drives . . . . . . . . . . . . . . . . . 8External SCSI Devices . . . . . . . . . . . . . . . 8PCI Cards . . . . . . . . . . . . . . . . . . . . . . . . . . 8

N+1 Redundancy . . . . . . . . . . . . . . . . . . . . . . 8Fans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Power Supplies . . . . . . . . . . . . . . . . . . . . . 9

Guardian Service Processor . . . . . . . . . . . . . 9Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Data Flow . . . . . . . . . . . . . . . . . . . . . 11Processors - PCXW . . . . . . . . . . . . . . . . . . . 11DEW - Do Echo on W . . . . . . . . . . . . . . . . 12Memory Subsystem . . . . . . . . . . . . . . . . . . . 13

SMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Memory Carrier . . . . . . . . . . . . . . . . . . . . 13

Core IO Board / GSP . . . . . . . . . . . . 15Management Features . . . . . . . . . . . . . 15

System Console . . . . . . . . . . . . . . . . . . . . 17Lan Console . . . . . . . . . . . . . . . . . . . . . 17Remote Console . . . . . . . . . . . . . . . . . . 18Local Console . . . . . . . . . . . . . . . . . . . 18GSP Internal Port . . . . . . . . . . . . . . . . . 18Logging . . . . . . . . . . . . . . . . . . . . . . . . 19

System LAN Port (10/100 Base T) . . . . . . . 20GSP SCSI Ports . . . . . . . . . . . . . . . . . . . . . . 20Serial UPS Port . . . . . . . . . . . . . . . . . . . . . . 20IO Subsystem . . . . . . . . . . . . . . . . . . . . . . . 21Power and Cooling . . . . . . . . . . . . . . . . . . . 23FRU ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25IO Pathing . . . . . . . . . . . . . . . . . . . . . . . . . . 27ioscan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Pathing as seen from the BCHINformation prompt: . . . . . . . . . . . . . . 30

Chapter 2: Functional UnitsTopics covered: . . . . . . . . . . . . . . . . . . . . . . 32

Sub-Systems: . . . . . . . . . . . . . . . . . . . . 32GSP . . . . . . . . . . . . . . . . . . . . . . . . . . 35

GSP Block Diagram . . . . . . . . . . . . . . . . . . 37PCI Bus Interface . . . . . . . . . . . . . . . . . . . . 39

DIVA1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 39DIVA2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Configuration Notes . . . . . . . . . . . . . . . . 40

Console Path . . . . . . . . . . . . . . . . . . . . . . . . 41Session Paths . . . . . . . . . . . . . . . . . . . . . . . . 43Internal Port Path . . . . . . . . . . . . . . . . . . . . 45

Chassis Codes . . . . . . . . . . . . . . . . . . 47

Sources and Reporting Entity Types ofChassis Codes . . . . . . . . . . . . . . . . . . . . . 4Definitions: . . . . . . . . . . . . . . . . . . . . . . . 48GSP Flow of Chassis Codes . . . . . . . . . . 4Disposition of Chassis Codes . . . . . . . . . 4

Misc. Utilities . . . . . . . . . . . . . . . . . . 49GSP Timers . . . . . . . . . . . . . . . . . . . . . . . . . 49

Gross Timers . . . . . . . . . . . . . . . . . . . . . . 50Chassis Timers . . . . . . . . . . . . . . . . . . . . . 50

Reflection and Boot Logs . . . . . . . . . . . . . . 50Timestamps . . . . . . . . . . . . . . . . . . . . . . . . . 50GSP Internal Clock . . . . . . . . . . . . . . . . . . . 50

Memory Subsystem . . . . . . . . . . . . . 51SMC - Stretch Memory Controller . . . . . . . 51Data Path From Merced bus to DIMMs . . . 53DMC Block Diagram . . . . . . . . . . . . . . . . . 55

Error Detection . . . . . . . . . . . . . . . . . . . . 56AMC - Address Memory Controller . . . . . . 57AMC Block Diagram . . . . . . . . . . . . . . . . . 59

Error Detection . . . . . . . . . . . . . . . . . . . . 60Error Severity Definitions . . . . . . . . . . . . . . 61

Chapter 3: GSPContent Overview . . . . . . . . . . . . . . 64

Console Setup . . . . . . . . . . . . . . . . . . . . . . . 6GSP Internal Access Port Setup . . . . . . . . . 6Stable Storage . . . . . . . . . . . . . . . . . . . . . . . 6

Console Setup . . . . . . . . . . . . . . . . . . 65Serial Console . . . . . . . . . . . . . . . . . . . . . . . 67

Configuring Reflection1 . . . . . . . . . . . . . 67Terminal Settings . . . . . . . . . . . . . . . . . . . 69

Web Console . . . . . . . . . . . . . . . . . . . . . . . . 71Connecting to a PC . . . . . . . . . . . . . . . . . 72Configuring via a Web Browser . . . . . . . 72Lost Password . . . . . . . . . . . . . . . . . . . . . 72Upgrading Web Console Firmware . . . . . 73

LAN Console . . . . . . . . . . . . . . . . . . . . . . . . 75Laptop to GSP LAN Console Configuration 76

GSP Command: ls . . . . . . . . . . . . . . . . 77GSP COmmand: er . . . . . . . . . . . . . . . . 78

Remote Console - Port (modem setup) . . . . 7Support Modem . . . . . . . . . . . . . . . . . . . . 79GSP Remote Port Configuration . . . . . . . 7

ca command . . . . . . . . . . . . . . . . . . . . . 80GSP Internal Port . . . . . . . . . . . . . . 81

Creating a device file for GSP Internal Port 82Edit the /usr/lib/uucp/Devices file . . . . . . . . 82Edit the /usr/lib/uucp/System file . . . . . . . . 82Accessing the Internal Port using “cu” . . . . 82Exiting the Internal Port . . . . . . . . . . . . . . . 82

Console Prompts . . . . . . . . . . . . . . . 83BCH Prompt . . . . . . . . . . . . . . . . . . . . . . . . 83GSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

April 2000 Hewlett-Packard Company Confidential iv

Table of Contents

4

0

ISL Prompt . . . . . . . . . . . . . . . . . . . . . . . . . .87HPUX prompt . . . . . . . . . . . . . . . . . . . . . . .88

Stable Storage . . . . . . . . . . . . . . . . . . 89Model_String and SW_ID . . . . . . . . . . . . . .91

Setting the SWID and Model String . . . . .91MODEL_STRING . . . . . . . . . . . . . . . .92

Viewing the model String . . . . . . . . . . .92Modifying the Model_String . . . . . . . . .92

SW_ID setting: 95SW_CAP setting: . . . . . . . . . . . . . . . . . . .95

Updating Firmware . . . . . . . . . . . . . 97GSP Firmware . . . . . . . . . . . . . . . . . . . . . . .97

Chapter 3: TroubleshootingContent Overview . . . . . . . . . . . . . 100

HPMCs . . . . . . . . . . . . . . . . . . . . . . . . . . . .100Initiating a TOC . . . . . . . . . . . . . . . 101

“tc” Command . . . . . . . . . . . . . . . . . . . . . .101Dump Screen . . . . . . . . . . . . . . . . . . . . . . .102

PIM Command . . . . . . . . . . . . . . . . 103Help pim . . . . . . . . . . . . . . . . . . . . . . .104

Web Based Pim Decoder . . . . . . . . 105Logging into the WEB Site . . . . . . . . . . . .105Enable Logging . . . . . . . . . . . . . . . . . . . . .106Decoding the PIM . . . . . . . . . . . . . . . . . . .108Analyzing the PIM Dump . . . . . . . . . . . . .109

Final Result . . . . . . . . . . . . . . . . . . . . . . .110

APPENDIXAppendix A:. . . . . . HPMC Chassis CodesAppendix B:. . . . . . . . . . . . . .Prelude FAQAppendix C:. . . . GSP Help - Full Listing

Guardian Service ProcessorCommand Help . . . . . . . . . . . . . . . 124

The GSP Help System . . . . . . . . . . . . . . . 12CHASSIS CODE . . . . . . . . . . . . . . . . . . . 126COMMANDS . . . . . . . . . . . . . . . . . . . . . 126CONSOLE MODE . . . . . . . . . . . . . . . . . 126HPTERM & VT100 . . . . . . . . . . . . . . . . . 127INTERNAL PORT . . . . . . . . . . . . . . . . . 127LIST OF COMMANDS . . . . . . . . . . . . . 127REMOTE/MODEM - PORT HELP . . . . 128GSP MODES . . . . . . . . . . . . . . . . . . . . . . 128Overview . . . . . . . . . . . . . . . . . . . . . . . . . 128PASSWORD RESET . . . . . . . . . . . . . . . . 129PORTS . . . . . . . . . . . . . . . . . . . . . . . . . . . 129SESSION MODE . . . . . . . . . . . . . . . . . . 130TOPICS . . . . . . . . . . . . . . . . . . . . . . . . . . 130

GSP Commands . . . . . . . . . . . . . . . . . . . . 13Command Description . . . . . . . . . . . . . . . 131

v Hewlett-Packard Company Confidential April 2000

Overview

asarize

Chapter 1: Overview

Prelude OverviewPrelude is the lead platform in the “Echo Family” of midrange Application/Internet server products. Knownthe N-Class or N4000 Server the Prelude platform utilizes the PCX-W processor. This document will summbasic Prelude features as an introduction to the chapters that follow.

Contents• System Overview• Data Flow• Processors• Memory• IO• Utilities Board/ GSP• Power and Cooling• FRU IDs• IO Pathing

April 2000 HP Confidential Overview-6

Overview

Overview-7

Ove

rvie

w

Notesainthe

AN

sive

ass

OV-L 2 -0 0 0

• Two System

• Eight Proces• Four Memor

• PCI Card Sl• Service Proc

• System Con• Chassis Log

• N+1 on pow• Online PCI

• Internal Disk

N4000 OVERVIEWPrelude Systems (N400 Severs) can contain up to 8 PCXW cpus and 16 Gig of mmemory. Along with a new system bus architecture some of the other features ofN4000 include:

• Dual IA64 system busses - Merced Bus.• Hot swappable disk drives and IO cards.• Redundant/ hot swapable fans and power supplies.• Guardian Service Processor providing access to the N4000 server via a L

console as well as rs232.• PCXW processors with ECC protested Dcache.

NOTE This overview is only a brief summary of some of the new featureof the Prelude system. For a complete overview and comprehensdetail of the N-Class server please refer back to the current N-ClEPSS CD_ROM.

Confident ial

Busses -Merced Bussors -4 per system bus

y Carries -8 DIMMs/Carrierots -10 4x slots, 2 2x slotsessor on Core IO Board -GSP

sole -4 physical portss -in ASCIIer and fans -hot swappablecard replacement -OLRAD

Drives -hot swappable

HP Confidential April 2000

Overview

Notes Overview

Dual System BussesAs will be seen later in this chapter the N4000 server has been designed with twosystem busses which support the IA64 architecture.

• Although they are termed the “Merced” bus they currently only support thPCXW cpus.

• The “DEW” chip interfaces the PCXW runway architecture onto the Mercebus. Other processors would require a different interface chip.

Hot-Swappable/Pluggable Devices

Internal Disk DrivesTwo internal disk drive located in the middle rear of the N4000 can be removed areplaced with power on, and with OS up and running.

• The “Disk Hot-Plug board” supplies the buffering necessary to hot-swapinternal disk drives.The N4000 will operate without the hot-plug board butmustbe installed in order to hot-swap disk drives.

• Software procedures must be followed before removing the disk drive (LVcommands).

• Refer to the N-Class EPSS CD-ROM module “System Removal andReplacement Procedures”, section “Replacing the Internal Disk Drives” fthe complete hot-swap procedure.

External SCSI DevicesHot-swapping external media devices connected to the N4000 Core IO External Sport is supported.

Requirements:• DVD(CD) or Tape Device• Power off device and exchange for identical unit.

PCI CardsPrelude IO utilizes a hot-plug system, not truly hot-swappable, as the power to IOis turned off while the card is being swapped.

OLRAD - online replacement and deletion.• Using “rad” (command line interface) or SAM boards can replaced or

deleted while the OS is online.• Addition is not supported at this time.• Driver must already be in the kernel. I.E. card must be replaced with the

same type.• Someday when DLMM (dynamically Loadable Kernel Module) is supporte

PCI cards can be added to the kernel online.

N+1 Redundancy

FansAny one of the six fans in the N4000 can be hot-swapped.

• Single fan failures are permitted, two fans failing at the same time will brindown system power.

• Fan RPM increases when a fan fails to compensate the air flow.• Fan failures are reported and the LED is illuminated on top of the failing fa

April 2000 HP Confidential

e

d

nd

it

M

or

CSI

slot

d

g

n.

Overview-8

Overview

Overview-9

Ove

rvie

w

edig-

sor”

r

he

nts to

Power Supplies• With a fully loaded system three power supplies are required for power

redundancy.• In a minimally configured system two supplies may provide redundancy.• The N4000 server will run on one supply after a failure in a system equipp

with two supplies, if enough current is still available for the system’s confuration.

• The SPU will not power up if only one supply is present or if it is the onlygood supply in the system.

Guardian Service ProcessorThe GSP is located on the Core IO board. Basically the GSP is a “Service Proceswhich operates total independent of the reset of the system.

• The GSP can be access via the system console with the “^b” command.• When logging into the console via remote serial or lan connection, a use

name and password are required by the GSP.• Because the GSP runs off of House Keeping voltage it does not require t

power switch on the front panel to be on in order to be energized.• There are four different ports on which the GSP can be accessed.

- Local Serial Port- Remote Serial- LAN Console Port- Internal GSP Port

NOTE Configuring and accessing these ports are detailed in Chapter 3“GSP”.

• Along with a set of configuration utilities the GSP provides a platform onwhich Chassis Codes are saved into local memory and later retrieved fordiagnosing system faults.

ProcessorThe PCX-W processor (360 and 440 MHZ) is the initial CPU supported on thisplatform. Future processors may include IA64 based cpus as well as enhancemethe PA-RISC line.

Notes


Overview

Notes Overview

Overview-10

Overview

Overview-11

Ove

rvie

w

Notess

two

m

vice

em

OV-L 2 -0 0 1

N40

PCXW

PCXW

PCXW

PCXW

Runway

Runway

Runway

Runway

PCI SlotELROY

PCI SlotELROY

PCI SlotELROY

Data FlowData flow in the N4000 server is illustrated above along with names of the variousystem components.

Processors - PCXWThe N4000 Consists of 8 PCXW processors.

• Each PCXU is attached to the system via a discreate DEW controller.• System architecture provides 2 system busses termed Merced.• Each Merced bus connects 4 CPUs to either memory or IO, thus creating

identical “mirrored” halves on each side of memory.• 360MHZ and 440MHZ CPUs are available.• CPU speeds are identified to the system via a switch setting on the syste

board. Factory default is 440MHZ.• CPU cleaning proceeds must be followed when replacing a CPU. See ser

note #A3639A-03 for replacement part numbers.

NOTE For CPU type switch settings refer to the N4000 EPSS CDROMmodule “Removal and Replacement Procedures”, Section “SystBoard Replacement”.

Confident ial

00 Overview - Data flow

AMC

DMC

X2

SDRAMS

DEW

DEW

DEW

DEW

IKE

PCXW

PCXW

PCXW

PCXW

DEW

DEW

DEW

DEW

Runway

Runway

Runway

Runway

IKE

GSP PCI SlotELROY

PCI SlotELROY

PCI SlotELROY

ELROY

Mer

ced

Bus

1

Mer

ced

Bus

0

LANDual SCSI


Overview

Notes Overview

NOTE For CPU cleaning procedures refer to the N4000 EPSS module“Adding Components”, section” Adding a CPU”.

DEW - Do Echo on WThe DEW chips interface the PCXW processors onto the Merced bus. The name“DEW” stands for do echo on W.

• The Merced bus is designed for IA64 architecture whereas the PCXW utlizes the runway bus architecture. Therefore upgrading to IA64 architectu(such as the Merced CPU) would require a system board change (ASICsthe system board are not FRUs).

• There is a total of 4 DEW chips on the system board.• Each DEW chip supports two CPUs. The DEW chip actually contains two

identical controllers, one for each of the CPUs supported.


i-reon

Overview-12

Overview

Overview-13

Ove

rvie

w

Notes

Cs

e.

l of

-

o

n

M

OV-L 2 -0 0 2

DEW

DEW

DEW

DEW

Runway

Runway

Runway

Runway

IKE

DI M M Pair s

MU I R

Memory Carrier 0

Memory Subsystem

SMCThe SMC “System Memory Controller” consists of three discrete ASICs. Two DMand one AMC. Via the SMC all CPUs and IO controllers have access to the 4Memory Carrier boards.

• DMC -The Data Memory Controller consists of two chips referred to as th“Euphrates” and resides on the system board. These parts are not FRUs

• AMC - The Address Memory Control is referred to as the Tigris chip. Thiscomponent resides on the system board and is not field replaceable.

Memory CarrierOne to four memory carrier boards can be installed in the N4000 server for a tota16 GIG of main memory. One ASIC called the MUIR and 8 DIMMs reside on thememory board.

• MUIR - functions as a data multiplexer/ demultiplexer on the memory carrier. This chip is not a FRU.

• DIMMs - must be installed in pairs of two. Dimm failures can be isolated ta single DIMM.

NOTE Refer to the N4000 EPSS module - “Adding Components”, sectio“Adding Memory” for details on memory configuration rules.

Confident ial

emory Subsystem

DEW

DEW

DEW

DEW

Runway

Runway

Runway

Runway

IKE

DI MM Pair s

MU I R

Memory Carrier 2

DI MM Pair s

MU I R

Memory Carrier 3

DI M M Pair s

MU I R

Memory Carrier 1

SMC

DMC AMC

(Euphrates)

(Tigris)


Overview

Notes Overview

Overview-14

Overview

Overview-15

Ove

rvie

w

Notesd on

al

even

OV-L 2 -0 0 3

C

LAN 10baseT

RS-232 Console

Modem

SERIAL UPS0/0/4/0.1

0/0/4/0.2

0/0/4/0.0

PCI Slot

PCI Slot

PCI Slot

1

Core IO Board / GSPThe GSP (Guardian Service Processor) is only one of several subsystems locatethe Core IO Board. As seen in the diagram above a single Elroy chip providesconnectivity to the reset of the system (HPUX) for the following devices:

• GSP• 10/100 LAN• External Ultra2 SCSI• Internal SCSI - 2 Internal Disk Drives mounted in the N4000 Server• Serial UPS Port

Management Features• System reset• Power Management and control - power on/off• Display status for fans, ambient temp• Automatic restart, based on specific alert levels

NOTE Future plans may include digital paging via the GSP remote seriport.

Since the GSP runs off house keeping power, the GSP prompt can be accessedwhen the front panel switch is off or the environmental monitoring system hasshutdown power to the rest of the system.

Confident ial

ore IO Board / GSP

IKEELROY

ELROY

ELROY

Internal Disks

Core I/O Board

0/100 BaseTxUltra2 SCSI

EXT

SCSILAN

Elroy

0/0/0/0

INTSCSI

GSP

0/0/2/0.6

0/0/2/1.6

0/0/1/0


Overview

Notes Overview

Guardian Service Processor features:• Provides a point of connectivity for local and remote console access.• Secure login, password protected.• Console mirroring between Remote and Local Console.• Provides functionality for manually executing a TOC or RESET.• Monitors system activity, boot process and errors.• Maintains logging information.• User and Admin security.• Firmware update over the network.

NOTE Information concerning user configurations and security optionscan be found in the following location on the N4000 EPSS: modu“Operating Instructions”, section “Booting Your Computer”.


le

Overview-16

Overview

Overview-17

Ove

rvie

w

Notes

• The GSP LANinterface isseparate from tSystem 10/100Base T LAN, asconnects directto the GSP.

• One or moreterminal clientsmay mirror theGSP Local SerPort Console vithe LAN port.

OV-L 2 -0 0 4

LA

System ConsoleThere are four separate port on the GSP for console access:

• LAN Console - 10 BaseT• Remote Console - Serial Modem• Local Console- Serial Port. (WEB Console attaches to this port)• Internal GSP Port - via HPUX

Lan ConsoleThe GSP Lan interface allows one or more terminal clients connected via LAN tomirror the console.

• Currently, each client will have complete control of the Console.• No one user can lock control of the console.

The LAN Console port is not configured from the factory. Two GSP com-mands are involved with configuring the LAN Console: “lc” and “er”- “lc” will set up IP parameters- “er “ used to enable/ disable lan access- Resetting the GSP defaults with the “dc” command will disable LAN

access.

NOTE For a complete list of GSP command reference the N400 EPSS,module “Hardware Overview/ Reference Information” section“Service Processor Commands”, or APPENDIX C.

Confident ial

GSP

System LAN Port

Customer LAN

10 Base T

10/100 Base T

Support LAN

GSP LAN Port

GSP LocalSerial Port

Local Console PC Client(System Admin. or Operator)

Prelude

he

itly

iala

N Console Connection


Overview

Notes Overview

Remote ConsoleIs used for remote access to the system console via a modem. Four GSP commaare associated with the remote serial port/ modem configuration:

• ca - configure asynchronous and modem parameters• mr -modem reset• cr - reserve modem for paging• ms - display modem status

Local ConsoleThe local serial port is the primary console port for the N4000 server. It provides adirect port into the GSP that can not be disabled.

• Connect to any ASCII terminal, PC, palmtop, etc.• Use the following settings when connecting to a PC: 9600,8,n,1.• WEB Console attaches to this port.

GSP Internal PortThis port is used to directly access the GSP from HPUX.

• Does not require a password.• Only way to reset GSP passwords if they are lost.


nds

Overview-18

Overview

Overview-19

Ove

rvie

w

Notes

n

OV-L 2 -0 0 5

Log Type

ÿþýüûúþùø÷üù

�� þ�ø�üü��ý�ú�ú��ø÷üù

�� úü��ø�üü��ý�ú�ú��ø÷üù

�� þ�ø�ý�ú�ú��÷üù

��ü�ø÷üù

LoggingAny of the following logs can be accessed form the GSP prompt using the “ls”command.

Console Logs - Contain console activity. ASCII log of everything that transpired othe console including:

• GSP handler• Boot condole handler (BCH) message.• and OS generated messages. Grows to about 20KB (20 pages).• Event Logs - Contains Chassis codes.

Incoming log• contains all the chassis code• is a circular que

Activity log• does not contain alert level zero entries• there are 3 separate activity logs:

- Current, circular buffer with 200 events- Current Boot, linear buffer with up to 800 events- Prior Boot, contains chassis codes from start of previous boot

Confident ial

GSP Logs

Contains Type oflog

Alert Levelsof Events

Size

� � � ��ø÷üù�þ��ø��ý�ú��

�ú�ý��

� � �ø÷üùø�þ��ú��

� � � � �ú�ø�ü��úþý�ø�� øü�ý��þ�ø�üü�

÷úþ��

� ��ø÷üùø�þ��ú��

� � � � �ú�ø�ü��úþý�ø�� øü��úü�ø�üü�

÷úþ��

� � �ø÷üùø�þ��ú��

��ý�þ�ø��þ�� ú�ý��

� � �ø÷üùø�þ��ú��

��ý�þ�ø��þ�� ú�ý�� ø÷üùø�þ��ú��


Overview

Notes Overview

Error log• Contains recent events and is typically the log retrieved when using the “

command at the GSP prompt.

System LAN Port (10/100 Base T)As viewed from the rear of the N4000 server the right most LAN port (10/100 BaseLAN Port) connects directly to HPUX via an “ELROY” IO controlled chip.

• Fixed path at 0/0/0/0.• Configured in HPUX, usually LAN 0.• Not accessible unless OS is booted.

GSP SCSI PortsThere are two discrete SCSI controllers on the Core IO Board.

• Internal Port - Dual Ultra2 SCSI port which attaches the two internal SCSdisks drives to the system.

• External port - DUAL SCSI port for attaching external devices such asCDROM, DDS, or other devices to the system. This SCIS port is auto seing and will automatically detect single ended or LVD devices and adjustaccordingly.

NOTE The default boot path is set to the upper disk drive in the internalenclosure (0/0/2/0.6)

Serial UPS Port• UPS connection.• Located at 0/0/04/0.1.


ls”

T

I

ns-

Overview-20

Overview

Overview-21

Ove

rvie

w

Notes

CIIO

e

OV-L 2 -0 0 6

Elroy

4xPCI

Elroy

2xPCI

Elroy4xPCI

4xPCI

Left I/O Backplane

2xPCI

Elroy

Elroy

4xPCI

Elroy

Slot

6

5

4

3

2

1

IO SubsystemThe IO subsystem consists of two “IKE” chips which provide connectivity to the IOBackplanes. Each IO backplane supports 6 PCI slots for a total of 12 available Pboard slots. Additionally, IKE 0 also supports an “Elroy” chip located on the Coreboard.

• Slot numbering with IO paths are located on the side of each IO card cagcover.

• Note that the slot number is different than that of the associated path!

Confident ial

IO Subsystem

Elroy

4xPCI

Elroy

4xPCI

Elroy 4xPCI

4xPCI

Right I/O Backplane

4xPCI

Elroy

IKE

1

Elroy

4xPCI

Elroy1/0

1/8

1/2

1/4

1/10

1/12

Path Slot

12

11

10

9

8

7

IKE

0

0/2

0/10

0/8

0/12

0/4

0/5

Path

Elroy

Core IO


Overview

Notes Overview

Overview-22

Overview

Overview-23

Ove

rvie

w

Notes

OV-L 2 -0 0 7

I/O Slot Power

Power Supply

Power Supply

Power Supp

AC

HKP 1

HKP 2

GSP

Power and CoolingThe above diagram illustrate the basic layout of the power monitoring systemincluding both power circuitry and cooling.

Confident ial

Power and Cooling

Power

Monitor

System

Voltages

Power

Switch

CPU DC-DC

Converters

System Firmware (Ralph)

SAS

Support Bus (Vol2ce)

Sys Brd Rev

FRU ID BUS

ly

Fan 0 Fan 7

Ambient Temp

(from sys brd)

CPU Present

MEM Pres


Overview

Notes Overview


Overview

Overview-25

Ove

rvie

w

Notesat

OV-L 2 -0 0 8

Informatio

FRU INFO

FRU NamPart NumSerial NuPhysical LEngineeriArt WorkScan RevFRU Spe

FRU IDFru Id can be attained from the N-Class Console by executing the “fru” commandthe Information Menu.

Confident ial

FRU ID

n Menu: Enter command > fru

RMATION

e: PRE_SYS_BDber: A3639-60006mber: 40110CF5A8ocation: 1ffff69

ng Date Code: 3922Revision: A4ision:cific Info: USM39343LR


OverviewO

verview

Information Usage Who writes FormatArt Work Rev SMO SMO MFG 1 alpha charEng. Date Code SMO Field SMO MFG 1 numericPart Number SMO Field MFG SMO MFG D0 D1 = yrs. >1960Serial Number SMO Field MFG SMO? MFG D2 D3 = wk of yearHistory SMO Field MFG SMO MFG 5 x 5 # given by product div.F R U Name Field MFGScan Revision Lab MFG SMO Lab MFG D0-D3 =DATE CODEFRU Specific Information Lab MFG Lab A =MFG D4-D8=#FRUID Definition Revision Lab MFG SMO MFG DEFINED BY MFG AND SMO

Ascii

D1 SCAN Revision

D0 Reserved

Ascii Data – FRU Specific

1 numeric char


Overview

Overview-27

Ove

rvie

w

Notes

e

IO

O V -L 2 -0 0 9

Boot Device: 0

IKEI

KE

0

El@

IO PathingThe I/O path is described as follows:

IKE - Elroy - PCI Controller Board - SCSI Cable ID

NOTE Note the format of the path as seen in the diagram above. Theformat does not change, wether it is OS using the “ioscan”command or at the Information Menu using the “IO” command, thformat for the path is identical.

Conf ident ial

Pathing -boot path

/0/0.6

#

roy

Core IO Board

External SCSIController @ 0/0/1

Internal SCSIController @ 0/0/2

Elroy

Ctlr# (Ex. Dual SCSI Ctlr)

SCSI Cable ID

0/0/

Internal Disks

0/0/2/0.6

0/0/2/1.6

0/0/2/0

0/0/2/1


Overview

Notes Overview

Overview-28

Overview

Overview-29

Ove

rvie

w

Notes

nd

# ioscanH/W Path=====================

00/00/0/0/00/0/1/00/0/1/0.60/0/1/0.6.00/0/1/0.70/0/1/0.7.00/0/2/00/0/2/0.60/0/2/0.6.0

OV-L 2 -0 1 0

IO

• CD-ROM on Extern• 10/100 Ethernet Po• Boot Drive on Inter

ioscanPathing is illustrated above with the “ioscan” command from the HPUX prompt.

It has been formatted to fit your screen.• System Bus Adaptor (SBA)- IKE chip• Local PCI Bus Adaptor (LBA) - Elroy chip

NOTE To equate PCI slot numbers with the logical pathing use the secoand third columns in the “IO Module Information” on the nextpage.

Confident ial

Class Description===================================================

rootioa System Bus Adapter (803)

ba Local PCI Bus Adapter (782)lan PCI Ethernet (10110019)ext_bus Ultra2 Wide SCSI

targetdisk HP DVD-ROM 6x/ 32xtarget

ctl Initiatorext_bus Ultra Wide SCSI

targetdisk SEAGATE ST39102LC

Pathing -ioscan

al Core IO SCIS Port:0/0/1/0.6.0rt on Core IO Port: 0/0/0/0

nal Core IO SCSI port:0/0/2/0.6.0


Overview

Notes Overview

Pathing as seen from the BCH INformation prompt:Information Menu: Enter command > io

I/O MODULE INFORMATION

Path Slot IODCType (dec) Number HVERSION SVERSION Vers---- ----- ------ -------- -------- ----System bus adapter 0 0x8030 0xc10 0x0Local bus adapter 0/0 Built_In 0x7820 0xa00 0x0Local bus adapter 0/1 Built_In 0x7820 0xa00 0x0Local bus adapter 0/2 6 0x7820 0xa00 0x0Local bus adapter 0/4 2 0x7820 0xa00 0x0Local bus adapter 0/5 1 0x7820 0xa00 0x0Local bus adapter 0/8 4 0x7820 0xa00 0x0Local bus adapter 0/10 5 0x7820 0xa00 0x0Local bus adapter 0/12 3 0x7820 0xa00 0x0System bus adapter 1 0x8030 0xc10 0x0Local bus adapter 1/0 12 0x7820 0xa00 0x0Local bus adapter 1/2 10 0x7820 0xa00 0x0Local bus adapter 1/4 9 0x7820 0xa00 0x0Local bus adapter 1/8 11 0x7820 0xa00 0x0Local bus adapter 1/10 8 0x7820 0xa00 0x0Local bus adapter 1/12 7 0x7820 0xa00 0x0

PCI DEVICE INFORMATIONPath Vendor Device Bus Slot

Description (dec) Id Id # #----------- ----- ---- ---- --- ---Ethernet cntlr 0/0/0/0 0x1011 0x19 0 Built_InSCSI bus cntlr 0/0/1/0 0x1000 0xc 0 Built_InSCSI bus cntlr 0/0/2/0 0x1000 0xf 0 Built_InSCSI bus cntlr 0/0/2/1 0x1000 0xf 0 Built_InComp. ser cntlr 0/0/4/0 0x103c 0x1048 0 Built_InComp. ser cntlr 0/0/5/0 0x103c 0x1048 0 Built_InSCSI bus cntlr 0/2/0/0 0x1000 0xf 16 6Ethernet cntlr 0/4/0/0 0x1011 0x19 32 2Ethernet cntlr 0/5/0/0 0x1011 0x19 40 1Fibre channel 0/8/0/0 0x107e 0x4 64 4Fibre channel 0/10/0/0 0x107e 0x4 80 5Fibre channel 0/12/0/0 0x107e 0x4 96 3SCSI bus cntlr 1/0/0/0 0x1000 0xf 128 12Fibre channel 1/2/0/0 0x107e 0x4 144 10Fibre channel 1/4/0/0 0x107e 0x4 160 9SCSI bus cntlr 1/8/0/0 0x1000 0xf 192 11Fibre channel 1/10/0/0 0x107e 0x4 208 8Ethernet cntlr 1/12/0/0 0x1011 0x19 224 7

Overview-30

Overview

Overview-31

Ove

rvie

w
Notes

FunctionalU

nits

ent islso

Chapter 2: Functional Units

A detailed description of all the functional units and system busses will be explained in this chapter. The intto give the 200 level trained engineer not only an enhanced understanding of system architecture but to aprepare learners for advanced training in HPMC analysis.

Topics covered:

Sub-Systems:• Utilities Board (GSP)• Memory Subsystem

AMCDMCMUIR

Topics not covered in this section, at this time only available in the L400 training materials:• IO subsystem

IKEELROY

• PCXW - DEW• Support Bus

DillonRalphI2C

April 2000 HP Confidential Functional Units-32

Functional Units

Functional Units-33

Fun

ctio

nalU

nits

Notes iar

U ni ts -0 0 1

In this chapter a more in-depth look at the individual functional units will beexamined on a near 300 level basis. The intent is for the learner to become familenough with system architecture in order to prepare for study in HPMC analysis.

Confidential


Functional Units

Notes

FunctionalU

nits

Functional Units-34

Functional Units

Functional Units-35

Fun

ctio

nalU

nits

Notes

� Syst em I� P CI I nt e� Console� I nt er nal� Chassis� M isc. U

U ni ts -0 0 2

GSPThe following is contained in this section.

- GSP Block Diagram- PCI Interfaces- Console Path- Session Path- Internal Port- Chassis Codes- Misc. Utilities

Confidential

nt er facesr faceP at hsP or t

Codest il it ies


Functional Units

Notes

FunctionalU

nits

Functional Units-36

Functional Units

Functional Units-37

Fun

ctio

nalU

nits

Notes

ver

-

�� ÿ øø� ��

�ÿ ��ø�

ÿþýüûúùøü÷

U ni ts -0 0 3

÷��ø�ü� �

��

GSP Block Diagram

The GSP interfaces to the rest of the over 5 interfaces:• PCI Bus -connects directly to the system via IKE 0.• I2C -communicates to PDC via the Ralph chip. Chassis codes are sent o

this interface.• Power -connects to the power monitor board.• Reset-operates through the Ralph chip.• SP Leds-the GSP leds are controlled by the SP, but operate from informa

tion that originates from chassis codes.

Confidential

��ø÷� �

ÿ� � �ü��

�ÿ ��ø�

��

� �� ÿ � ��

��ûü��ø�ü�� ø�üþ��ü�

� � � � �ú�ø�ü��

�� ûø��

�� ûøÿþú��ÿ�

öýõöýôüöóü÷ýöõúöýôüöòñ÷ýüð

üý��ø�ü��

� ��

��ûü��ü� � � �ü��û

��

÷� �ø�ü��

÷��


Functional Units

Notes

FunctionalU

nits

Functional Units-38

Functional Units

Functional Units-39

Fun

ctio

nalU

nits

Notes

ves

� �ÿöÿþýüûúùø

øø�ø� ø�ÿ�� øý�ú��ø� �

�ÿ�� ø �

� � � � � � �� ÷ �ø

��

� � � � � ýüþ�ü��

��

� � � � � � � � � ��

U ni ts -0 0 4

PCI Bus InterfaceThe PCI bus interface on the GSP connects to two DIVA chips. The diagram aboillustrates the hardware paths of each of the DIVAs along with the device paths aseen from HPUX.

DIVA1console - /dev/consoleUPS - /dev/tty0p1Remote Session /dev/tty0p2

DIVA2Internal Console Port - /dev/tty1p0Local Session Path -/dev/ttyd1p1

Confidential

ü

ø�� ø� �ý� �

��ÿø� ��

� �

�ÿ��

� � � � � � � � ��ûü��

ø�� úüþ

� � � � � � � � � � ��

÷üý� �ø

�� úüþø�� ø

� � � � � � � � � � ��

ÿþ� � �þ� �ø

�üþ�ü��ø�ü� �øø

� � � � � � � � � ��

�ü �ø��


Functional Units

Notes

FunctionalU

nits

Configuration Notes• Console Path: /dev/console (/dev/GSPdiag)

- /dev/console baud rate is not applicable.• UPS Path: - /dev/tty0p1- configure with SAM (straight through) up to 9600 Baud

• Local Console Session Path /dev/ttyd1p1- configure with SAM- must be BELL protocol - max speed 38400 baud

• Remote Console Session Path /dev/ttyd0p2- configure with SAM- if remote disabled - direct device file, CCITT, or BELL- if remote enabled - CCITT or BELL, but must match configuration in

CA command - max 38400 baud

Functional Units-40

Functional Units

Functional Units-41

Fun

ctio

nalU

nits

Notes

tes

f

�� ÿ � �

�üþ�ü��

�� ø �ü��ø��ú� � ��

��ø� �üü��üþ�ü��þ��

�õþ÷õ�üö�ùý

U ni ts -0 0 5

Console PathBoth the PDC (Boot Console Handler) or HPUX (console or tty driver) communicaacross the PCI Bus and through a UART on the DIVA to any one of the three portshown above:

• Local Console Serial Port• Remote Console Serial Port• LAN Console port

NOTE When using this interface, the three console ports are mirrored.They will all respond simultaneously and do not have any type ointerrupt that will allow individual control.

Problems may occur when using mirroring if the term type isHPTERM.

Confidential

÷üý��üþ�ü�� ú� �ø�ü� �

� ��

��ûü��üþ�ü�� ú� �ø�ü� �� ü��û�

÷� �ø��üþ�ü��ø�ü��

÷��

��ÿø� ��

� � �øÿ� �ø� � �úþùø�üü�� ø�� üþ�ü�� ø÷úûú�� ø�� ûúþ��øÿ� ��ûú� �ü� � �ø�� ø��øýüþ� úù�� úüþ� �

þ�ü��

÷üý�� úüþø��

��ûü�� úüþø��

ÿþ�� þ� �ø�üþ�ü��

�ü� �ø� ��

ô


Functional Units

Notes

FunctionalU

nits

Functional Units-42

Functional Units

Functional Units-43

Fun

ctio

nalU

nits

Notes

for

�� ÿ � �

�üþ�ü��

��

��ø ��ú� � �

òü÷÷�õþö�ù

U ni ts -0 0 6

Session PathsThe session paths enable a fully functional terminal I/O path in to the HPUX, onelocal and remote communications.

NOTE The LAN port does not allow a for a session connection.

Confidential

�� ø ��þý�úüþ��ø�� ûúþ��øÿ� �ø�þüýüþ�ü��øü�ø��ø�üü�� øø�þ�� ú� � �� ø� ü�ø�üý�� üþ�ø� ü�ø� �ûü��

��

��ø��ú� � �

� �� ÷��

��ÿø� ��




�ü� �ø� ��

÷üý��üþ�ü�� ú� �ø�ü� �

��ûü��üþ�ü�� ú� �ø�ü� �� ü��û�

÷� �ø�ü��

ýô÷


Functional Units

Notes

FunctionalU

nits

Functional Units-44

Functional Units

Functional Units-45

Fun

ctio

nalU

nits

Notes

he

�� ÿ � �

�üþ�ü��

��ø�� ÷� �

ÿþýüûþù�ö�õ

U ni ts -0 0 7

Internal Port Path• Internal Port: /dev/tty1p0 (/dev/GSPdiag1)• Supports both direct device file and BELL modem device files.• Cannot be configured with SAM.• See the Chapters 2 “GSP” for information on how to manually configure t

Internal Port.

NOTE BAUD rate is not applicable, since this only applies to GETTYdriver. Cu and Kermit can be used to access this port. (see cuconfiguration on next page)

Confidential

��ýú� �ø�ü� �ø�üø� � �ü�ø�� ø�üø�ýý�� ø� � ��ø ��þ�� ø � ��ü��øýüþ� úù�� úüþøü� ø��õö�÷üûöõûöõ�üûùýõûö�ù÷÷�õû�ûü�� ûü��ö ø��ü��ý�ø�ú� �ø��ø �ýý��

� �� ÷��

��ÿø� ��




�ü� �ø� �� ü

��

��ø ��ú� � �

� ��

ûý


Functional Units

Notes

FunctionalU

nits

Functional Units-46

Functional Units

Functional Units-47

Fun

ctio

nalU

nits

Notesam

am

er

� �õ�öõúö�ôù÷÷�÷

U ni ts -0 0 8

Chassis CodesChassis codes can originate from either one of four sources, as seen in the diagrabove.

Sources and Reporting Entity Types of Chassis CodesChassis codes can originate from either one of four sources (as seen in the diagrabove):

• PM2 -power monitor board, power/ environmental conditions (Fans / PowSupplies, etc.)Power Monitor=2

• Ralph - system processors, firmware or softwareFirmware=0HP-UX or boot loader=14Diagnostics=15

• CE - CE may input notes using the “ce “command at the GSP promptCE =7

• GSP Firmware =(1)

Confidential

��

ÿ � �øÿ��

�� ø� ��÷��

��üý�� ü�ø�

�ú �û��

��üý�� ü�ø�

�ú �û��

��üý�� ü�øø�

�ü� � � � � �

��üý�� ü�ø�

�ü� � � � � �

� �

ö�õ�ü÷


Functional Units

Notes

FunctionalU

nits

Definitions:• Chassis Code- a VOI2CE request message with message_type field of 0x

2 Double Words- First Word: Encoded Field- Second Word: Data Field

• Log EntryUsually 1 (but sometimes more- up to 5) chassis codes. The last chassiswill have the EOM bit set.

GSP Flow of Chassis Codes• Chassis codes flow into GSP asynchronously over I2C bus.• Mailbox for each “entity” that can log chassis codes.• Mailboxes assemble chassis codes into “log entries”• Once Log Entries are complete, they go on to the logs, vfp, and/or the

reflecting queue.

Disposition of Chassis Codes• One or more of the following:

- Thrown Away (Timer Request Log Entries)- VFP - System Alerts- SAS Logs (several different ones)- Reflection to O/S. Diagnostic Logs - Events- Paging (Phase V)


9.

code

Functional Units-48

Functional Units

Functional Units-49

Fun

ctio

nalU

nits

Notes

�ò�ö�ö� �÷ø�

� T imer s

� R ef lect ion

� T imestamp

� I nternal Cl

U ni ts -0 0 9

Note that outgoing to Ralph are complete log entries ONLY… no interleaved chassis codes from various entities.

Misc. Utilities

GSP Timers• Two Types of Timers

- Gross Timers (one per incoming queue) |To assure completion of chassis codesStarted by chassis codes without “EOM”

- Chassis Timers (Heartbeat)One per mailboxStarted/Stopped with chassis code of data type “Activity Level/Time-

out”Only after “Boot Complete”

Confidential

and B oot L ogs

s

ocks


Functional Units

Notes

FunctionalU

nits

Gross Timers• Always set to 60 seconds.• Started when a chassis code is received in a mailbox without EOM bit se• If expired, results in GSP firmware logging a chassis code. Source will be

to processor (source detail: processor general) or platform (source detaipower monitor), RET=Service Processor, Problem Detail=11 “Failed logentry follows”

• Will be followed by the failed log entry.

Chassis Timers• These become active after “boot complete” is set, and are started by soft• O/S is responsible for keeping them going for each processor.• Time set to 60 seconds or 180 seconds.• On expiration, a chassis code will be logged, which is identical to the last

“Activity Level/Timeout” chassis code received from the processor, onlyALERT LEVEL set to 13, and TIMEOUT value set to EXPIRED.

- If Auto Restart is enabled with default alert level (13), this will result inan automatic system restart (TC).

Reflection and Boot Logs• After O/S is up and running, log entries are sent through reflecting queue

back up to O/S.• During boot, events are saved in the current boot log.• At boot_complete signal from O/S, the Current boot log is sent up to the

S by the log reflector.• “Boot Complete” means O/S should be ready to read reflected boot code• GSP will begin reflecting complete log entries back up to Ralph.

Timestamps• GSP adds timestamps from its own internal clock to any log entries that d

not already contain timestamps.• GSP clock is not battery backed up.• GSP Clock can lose 8 minutes per day.• GSP clock is synced from system clock by PDC at boot (GMT)• Synced by HP-UX at initial boot (GMT)• After IPR 9906, diagmond will update GSP clock once an hour (Local tim

in 9906 - GMT time in 9909)

GSP Internal Clock• The GSP’s Internal Clock reverts to Jan. 1, 1970 when GSP is reset. Thi

happens when:• Housekeeping Power is first applied• GSP Firmware Update is done• XD command (Reset option)• GSP RESET button on the rear of the Core I/O.


t.setl:

ware

O/

s.

o

e

s

Functional Units-50

Functional Units

Functional Units-51

Fun

ctio

nalU

nits

Notes

tryd

he

.

N4

Objective

• ProvSubs

•Descdetec

mem001

Memory SubsystemIn this section memory subsystem architecture along with its error detectioncapabilities are covered. The level of detail is only deep enough to provide an enpoint for engineers who desire high level architectural knowledge to aid in 300 an400 level troubleshooting, such as HPMC analysis. Most of the information in thischapter has been pulled directly from level 400 training.

SMC - Stretch Memory ControllerThe SMC consist of:

• DMC - Data Memory Controller, 2 chips with two units each. Resides on tsystem board.

• AMC - Address Memory Controller, 1 chip. Resides on the system board• MUIR - Multiplexor/ Demultiplexer, resides on the memory carrier.

Confidential

000 Memory Subsystem

:

ide an overview of the Memoryystem

ribe in detail the memory subsystem errortion capabilities


Functional Units

Notes

FunctionalU

nits

Functional Units-52

Functional Units

Functional Units-53

Fun

ctio

nalU

nits

Notes

er

D

DIMM Pairs

MUIR

MUIR

DIMM Pairs

Memory Carrier

Memory Carrier

NL25002

Data Path From Merced bus to DIMMsDMC - Data Memory Controller(2 Euphrates chips)

Two Euphrates chips make up the DMC, they contain the circuitry whichreads/ writes data between DIMMs on the memory carriers and the DEW chips.

• The Merced bus connects the DMC to the DEW.• Data can be forward from one Merced bus to the other Merced bus in ord

to take data from one side of the system to the other without storing it inmain memory.

• Single and multiple bit ECC data errors (SBE and MBE) detected by theDMC are signaled to the AMC (Tigris) chip.

• The DMC contains a memory log for memory syndrome errors.

Confidential

ata Path Block Diagram

I/O

P

P DEW

P

P

DEW

I/O

P

P DEW

P

P

DEW

DIMM Pairs

MUIR

DMC

x2

(Euphrates)

Data-72b w/ECC

Data-72b w/ECC

Data-72b w/ECC

Data-72b w/ECC

Memory Carrier

DIMM Pairs

MUIR

Memory Carrier


Functional Units

Notes

FunctionalU

nits

Functional Units-54

Functional Units

Functional Units-55

Fun

ctio

nalU

nits

Notes

bus

M

NL25003

DMC Block DiagramNote that there are different data stores for memory and processor data storage.

• Memory data storage stores data for memory read transactions only.• Processor Data Storage stores data for both memory writes and Merced

forwarded transactions.

Confidential

DMC Block Diagram

ECCSyndrome

Processor DataStorage

MW MZMY

Port 0

erced Bus 0

Port 1

Merced Bus 1To OtherEuphrates

Carrier 0

MX

Carrier 1 Carrier 2 Carrier 3

Mem DataStorage

Mem DataStorage


Functional Units

Notes

FunctionalU

nits

Error DetectionAll data buses (Merced and DRAM) include ECC bits (8 for every 64). The ECCcode will be identical to that for the Merced bus; these bits enable single–bit errocorrection, and double–bit and nibble error detection.

• For the Merced ports, the DMC will do error detection and the AMC will lothe corresponding physical address to enable FRU isolation (but not to aDRAM chip).

• The DMC will not do error correction; this implies that only a single point ofailure in the system is correctable.

• Memory scrubbing is expected to be done by software.


r

g

f

Functional Units-56

Functional Units

Functional Units-57

Fun

ctio

nalU

nits

Notes

Addr

Add

MUIR

DIMM Pairs

Memory Carrier

MUIR

DIMM Pairs

Memory Carrier

NL25004

AMC - Address Memory Controller

The AMC consists of oneTigris chip, it performs the following functions:

Controls the DMC• Arbitrates for the Merced address and data busses for the SMC (Stretch

Memory Controller).• Maintains the “In-Order” Queue for Merced bus transactions.• Tracks transactions to be forwarded to a remote Merced bus.• Checks transaction's address for main memory, forwarded to a remote

Merced bus agent or be ignored.• Collects Coherency responses.• Monitors forward progress on both Merced busses.• Logs Merced bus errors.

NOTE The MUIR chip aboard the memory carrier will check parity oncontrol.

Confidential

ess/Control Block Diagram

I/O

P

P DEW

P

P

DEW

I/O

P

P DEW

P

P

DEW

AMC

(Tigris)

r Parity Error Addr Parity Error

Carrier 0 Control

Carrier 3 Control

Carrier 2 Control

Carrier 1 Control

DIMM Pairs

MUIR

Memory Carrier

DIMM Pairs

MUIR

Memory Carrier


Functional Units

Notes

FunctionalU

nits

Functional Units-58

Functional Units

Functional Units-59

Fun

ctio

nalU

nits

Notes

e out

dells.

InterMercABC

Coan

Me

ABCD bus toEuphrates MercedBus 0 port

ST(c

C

NL25005

AMC Block DiagramThe two Merced address buses enter the Tigris [AMC], and 2 address buses comeach going to two memory extender boards.

• Each of these addresses buses contains 2 independent time–multiplexeaddresses which provides addressing for the four independent memory c

Confidential

AMC Block Diagram

face toed andD busses

Interface toMerced andABCD busses

Merced Bus 1

herency Mapd Completeion

Queue

Coherency Mapand Completeion

Queue

CollisionDetect

rced Bus 0

MBAT MBAT

Status/ConfigRegisters

Bus 0 Bus 1

ABCD bus toEuphrates MercedBus 1 port

chedulers andrackerells W/X)

Schedulers andTracker(cells Y/Z)

arriers 0/1 Carriers 2/3


Functional Units

Notes

FunctionalU

nits

Error DetectionThe Merced address, request and other buses are protected by parity. The AMCcheck for parity on these buses and signal errors by initializing the bus.

• The DRAM address bus is also protected by parity.• Checking this parity is the responsibility of the memory subsystem (e.g. t

DIMM).• From the subsystem, the AMC can accept a parity error signal and reset

Merced buses.• The AMC will check for several improper transactions (e.g. coherent

writes), and incorrect usage mode (e.g. sub–cache line writes), protocolerrors (e.g. lock assertion on Merced bus) and signal fatal errors.

• For transactions to memory space not mapped to any DRAM or IO/memspace for which there is no response for a large time duration, the AMC wreturn a Hard Failure response and log them as uncorrectable errors.

NOTE The AMC will not detect non–completion of deferred transactionthis feature is a responsibility of the deferring agent (e.g. the IOAThere is no support for detecting or generating a special poisonvalue, since this feature is not found to be necessary.


will

he

the

oryill

;).

Functional Units-60

Functional Units

Functional Units-61

Fun

ctio

nalU

nits

Notes

s no

orn

hend

Merced Bus

Errors Detected• Address and Con• Single Bit Errors o• Multiple Bit Errors• Timeouts• Hard fail Respons• BERR and BINIT• Protocol errors

Logging• E• E• A• A• F• D• E

NL25006

Error Severity Definitions

• Corrected (corr)The SMC detects and corrects a hardware correctable error. There idamage to the memory subsystem.

• Uncorrected (unc)The damage has been contained to the modules detecting this err9the SMC and other modules that detect this error). The transactiothat resulted in the error did not complete correctly.

• Fatal Error (fe)The extent of the damage to the memory system is unknown. Thetransaction that resulted in the error did not complete correctly. As tcentral bus agent, the SMC generates a Machine Check interrupt amay shut down both Merced busses to prevent further damage.

• Containment Error (cw)The CW bit is set for fatal errors if the error is not contained. Theseerrors are unrecoverable.

Confidential

SMC Error Handling

trol Response parityn dataon data

e for Forwarded Transactionsassertion by Merced Agent

Registers:rror Statusrror OverflowERR Addr 1ERR Addr 2ERRERRCC Syndrome

Two sets of these registers; one each forMerced Bus 0 and Merced Bus 1.


Functional Units

Notes

FunctionalU

nits

Functional Units-62

GS

P

as well

Chapter 3: GSP

Content OverviewThis chapter will cover access and configuration of the Guardian Service Processor, GSP. Console setupas stable storage will be the main topics.

Console Setup• Serial Console• WEB Console• LAN Console• Remote (Modem) Console

GSP Internal Access Port Setup

Stable Storage• Setting the SWID• Updating PDC• Updating the Web Console Firmware• Updating GSP Firmware• Updating IODC/ SCSI Controller Firmware/ Disk Drive Firmware? (might be done form OS)

April 17, 2000 HP Confidential GSP-64

GSP

GSP-65

GS

P

Notese0

ges.

GSP-L 2 -0 0 1

Guar d

Console SetupThe GSP provides support for the system console via 3 discrete ports. From thesthree ports there are four possible ways to connect a system console to the N400server:

• local serial console port - RS232 comparable terminal or emulator- Web Console

• lan console port - IP connection via RJ45 Ethernet• remote serial console port - modem port

Configuring and connecting to each of these ports is covered on the following pa

Conf ident ial

ian Ser vice Pr ocessorConsoles


GSP

Notes

GS

P


GSP

GSP-67

GS

P

Notes.

l

ing

GSP-L 2 -0 0 4

SConnect

Serial ConsoleThere is little no configuration required to use the Serial Console port on the GSP

Port configuration is set at the factory to the following default values:• 9600 bits/s• Software flow control• 8,n,1

NOTE From the GSP menu only the baud rate and flow control can bemodified.

Configuring Reflection1In order to access the N-Class Console from the laptop computer connect a seriacable from “Local Serial Port” on the GSP to the com port on the laptop.

In the following example com1 was utilized, this may not always be the case. Durthe Refelction1 setup available com ports will be display in the “New Connection”window.

Confident ial

erial Consoleing via Reflection1


GSPG

SP

“New’window.

Start Reflection1• Select “New” from the Connection Directory window

• Give the new session a name, then select Serial Port from the “New Contion” window, as seen above.available com ports will appear

• Next, save the configuration and run it from the Connection Directory window

With the version 5.21 of Reflection1 no other setup was required. On the next twopages screen grabs of terminal and keyboard parameters are displayed in the cawhere they may differ on other PCs.

Conf ident ial

Start Reflection1 and selectfrom the connection Directory

GSP-L 2 -0 0 5

April 17, 2000 HP Confidential

Notes

nec-

-

se

GSP-68

GSP

GSP-69

GS

P

Notes

Set

From thReflec

GSP-L 2 -0 0 6

Terminal SettingsTerminal setting may vary. The settings shown on these pages worked quiteeffectively.

Confident ial

up T er minal

e Toolbar on top of thetion1 Window select:


GSPG

SP

Confident ial

T erminal Setup K eyboard

GSP-L2-007

Confident ialGSP-L2-00 8

T erminal Setup Display


GSP

GSP-71

GS

P

Notesss:that-to

d

GSP-L 2 -0 1 4

Web Con

Web ConsoleConfiguring the Web Console for use on a customers network is a two step proce

• First the Web Console must be configured to the pre-assigned IP addresswill enable access to the local area network. This is accomplished by connecting a laptop computer via a point to point lan cable (crossover cable)the Web Console and modifying its default parameters.

• After the new IP address is loaded into the Web Console it must then beattached to the customers network and configured with user accounts anchecked for firmware upgrades.

NOTE Although comprehensive install instructions are bundled with theWeb Console, key points concerning the install will be covered inthis section to provide customer engineers with an insight to thecomplexity involved. Which is really quite limited!

Confident ial

sole: LAN Setup on Laptop


GSP

Notes

GS

P

Connecting to a PCThe default IP address of the Web Console is 192.0.0.192. Follow these 5 stepsenable access of the Web Console from the PC.

• Set the IP address on the PC to 192.0.0.193• Set the gateway IP on the PC to the same IP: 192.0.0.193• Reboot the PC• After rebooting the PC, open a DOS window and execute the route com-

mand as follows:route add 192.0.0.192 192.0.0.193

• Ping the Web Console:ping 192.0.0.192- if successful you are finished using the PC- if not execute the following command:arp -s 192.0.0.192 <mac address of the web console>

NOTE Using the arp command should not be necessary in most cases.problems still exist after using arp to load the mac address into tharp cache it will be necessary to verify the PC’s hardware(including the crossover cable) and network software.For more information on configuring the Web Console andtroubleshooting procedures use the following web site:

http://eproducts.hp.com/servers/class_console/index.html

Configuring via a Web Browser• After successfully executing the ping command, open a web browser and

to the URL: http://192.0.0.192. Supported web browser are Netscape anversions 4.0 and greater. For details on all supported browsers go to thesite:http://eproducts.hp.com/servers/class_console/support/browsers.htm

• Once the Web Console page loads modify parameters to match the custers network and assigned IP address.

• Setup an account for administration.• Exit the Web Console and disconnect the crossover cable form the PC.• Connect the customers LAN and verify Web Console configuration from

any node on the LAN using a supported web browser.

Lost PasswordIf the password is lost to Web Console it will be necessary to execute a manual re

Disconnect the power plug.• Depress the button on top of the console while reinserting the power plug• Release the button after a couple of seconds.


to

Ife

god IEweb

om-

set

.

GSP-72

GSP

GSP-73

GS

P

Notes

WEB Co

GSP-L 2 -0 1 5

Upgrading Web Console FirmwareAn upgrade may be required after installing the Web Console.

From the Web Console program select the upgrade option.

Next, enter the IP and file path where the firmware can be found.

Confident ial

nsole - F/W Upgrade


GSP

Notes

GS

P

GSP-74

GSP

GSP-75

GS

P

Notesss the

SP

in

m-

e

Confi

GSP-L 2 -0 1 0

GSP Setup

1) Login to theusing the Lo

2) Execute theprompt.• Set the IP Ad

as your lap• Set the hostn• Set the netm• Set the gatew• Reset the GS

LAN ConsoleThe lan console enables system administrates and other authorized users to acceN-Class system console and GSP prompts via a local area network connection.

To configure the LAN Console port simply connect the laptop PC directly to the GLocal Console port with a 9 pin RS232 serial cable.

• Open reflections1 on the laptop and configure a serial port as describedthe previous section pertaining to Local Serial port configuration.

• Using the “lc” command at the GSP prompt configure the GSP LAN paraeters to match values assigned by the customers.

• Using the “er” command enable access to the LAN Console.• Connect the customers LAN cable to the LAN Console port on the GSP.

NOTE The GSP must be reset for changes to the GSP hostname to takeffect.

Confident ial

guring the LANConsole

N4000 Console from the laptopcal Serial Port on the GSP.“LC” command from the GSP

dress to something on the same subnettopame to anythingask to 255.255.248.0ay to match the IP address of the GSPP


GSPG

SP

Laptop to GSP LAN Console ConfigurationIf problems develop while connecting to the customers network it may beadvantageous to connect your laptop PC lan port directly to the GSP LAN Consoport.

• This will verify GSP functionality and the configuration process.• A point to point (crossover) cable will be needed.

In the picture above a screen shot of laptop networking TCP/IP properties is featuFrom this screen either modify the gateway to match the IP address alreadyconfigured or modify both IP address and gateway address to be on the same suas the GSP LAN Console.

If all else fails:• Set the IP address on the PC to 192.0.0.193.• Set the Gateway address on the PC to 192.0.0.193.• Connect a point to point LAN cable from laptop to the LAN Console port.• Reboot the PC.• Via the serial console set the LAN Console IP address on the GSP to

192.0.0.192.• Set the Gateway on the GSP LAN Console to 192.0.0.192• Reset the GSP• Open a reflection1 window on the laptop and configure a network connec

tion to attach to 192.0.0.192 and connect!

Confident ial

Laptop IP Configuration

GSP-L 2 -0 1 1


Notesle

red.

bnet

-

GSP-76

GSP

GSP-77

GS

P

Notesask

GSP L

GSP> ls

LS

LAN config. MAC. IP ad. GSP. Subne. Gatew

GSP-L 2 -0 1 2

GSP Command: lsThe “ls” command is used to configure the IP address, GSP Host Name, subnet mand gateway address of the GSP LAN Console port.

• Is reset when the “dc” command is executed on the GSP.• Changes will take effect immediately.

Confident ial

AN Configuration

uration:Address : 0x0010837c53f9dress : 192.0.0.192Host Name : GSPt mask : 255.255.248.0ay address : 192.0.0.192


GSPG

SP

n

GSP COmmand: erBefore the GSP port can be accessed the “er” command must be executed to enthe port.

• AT the GSP prompt enter “er” to enable the LAN port.• Access will be immediate after enabling the port, there is no need to rese

Conf ident ial

GSP> er

ER

Current Remote Console access state:Remote Console: DisabledLAN Console: Disabled

Do you want to modify this configuration? (Y/[N]) yy

Do you want to Enable the Remote Console? (Y/[N])n

Do you want to Enable the LAN Console? (Y/[N]) yy

-> LAN Console Enabled

New Remote Console access state:Remote Console: Disabled

LAN Console: Enabled ÿÿÿÿ

Enabling the LANConsole - “er”

GSP-L 2 -0 1 3


Notesable

t.

GSP-78

GSP

GSP-79

GS

P

Notes

SP.

ineters

6

GSP-L 2 -0 1 6

Remote

Modem Setup

1) Attach the 56to the Remo

2) From the GScommand toserial port.

3) From the GScommand to

Remote Console - Port (modem setup)

Support Modem• 56.6K support link modem (5184-0852)• Web URL for configuration:

http://slick2.atl.hp.com/hwrcweb/modems/Default.htm

GSP Remote Port ConfigurationThe 56K support link modem attaches directly to the remote console port on the GConfiguring the remote console port for use with a modem is a two step process:

• ca - configures port parameters• er - enables access to the port

Although the GSP defaults should supply the correct values for the 56K modem,some cases it may necessary to modify them. Check the remote serial port paramwith the “ca” command and modify if necessary. At GSP firmware release A.01.0the default parameters are the recommend settings for the 56K modem.

NOTE Always check the “Support Modems” web site (given above) forcurrent guidelines concerning support modem configurations.

Conf ident ial

Console Port - Modem

K Support Link Modem (5184-0852)

te Console Serial Port on the GSP.

P prompt executes the “ca”configure the GSP remote console

P prompt execute the “er”enable access to the port.


GSP

Notes

GS

P

ca commandBelow is an example of executing the “ca” command. Note the values of each setas they are the defaults/ recommended settings for version A.01.06 of GSP firmw

GSP> ca

CAThis command allows you to modify the local and remote modem serial portconfigurations. Current configuration settings:

Local Console Serial Port bit rate: 9600 bits/sLocal Console Serial Port Flow Control: SoftwareLocal Console Serial Port Terminal Type: vt100Remote Console Serial Port Modem Protocol: CCITTRemote Console Serial Port Modem bit rate: 19200 bits/sRemote Console Serial Port Modem Flow Control: SoftwareRemote Console Serial Port Modem Transmit Configuration Strings:

EnabledRemote Console Serial Port Modem Presence: always connected

Do you want to modify the Local Console Serial Port settings? (Y/[N]) nn

Do you want to modify the Remote Console Serial Port Modem settings? (Y/[N]) yy

Current Remote Console Serial Port Modem Protocol: CCITTDo you want to modify it? (Y/[N]) n

nCurrent Modem bit rate: 19200 bits/sDo you want to modify it? (Y/[N]) n

nCurrent Flow Control: SoftwareDo you want to modify it? (Y/[N]) n

nTransmit Configuration Strings: EnabledDo you want to modify it? (Y/[N]) n

nModem Presence: always connectedDo you want to modify it? (Y/[N]) n

n

NOTE Max speed supported at first release is only 19200!

er commandGSP> er

ERCurrent Remote Console access state:

Remote Console: DisabledLAN Console: Enabled

Do you want to modify this configuration? (Y/[N]) yy

Do you want to Enable the Remote Console? (Y/[N]) yy

-> Remote Console EnabledCommand execution may take 25 seconds.

New Remote Console access state:Remote Console: EnabledLAN Console: Enabled


tingare.

GSP-80

GSP

GSP-81

GS

P

Notesse

GSP-L 2 -0 0 9

ConfiIn

1) Create devcd /devmknod tty1p0

2) Edit the /usgspiport tty1p0

3) Edit the /usgspiport Any;5ogin: uucp ass

GSP Internal PortThe N-Class system console can be accessed via the GSP Internal Port in the cawhere the customer has lost the GSP login password.

• Is not password protected!• Several GSP commands can only be executed from this port.• Very useful if the GSP password is lost.• The GSP internal Port is /dev/tty1p0.• Must be manually configured at the HPUX prompt.• Via this port the GSP is accessed with the “cu” command.

In order to use the GSP Internal Port a three step configuration task must beperformed.

Confident ial

guring the GSPternal Port

ice file tty1p0:

-c 1 0x0100000

r/lib/uucp/Devices file:- 9600 direct

r/lib/uucp/Systems File:gspiport,f 9600 - "" \r\d\r\d\r ogin:-BREAK-wrd: uucp-BREAK-ogin: uucp asswrd: uucp


GSP

Notes

GS

P

Creating a device file for GSP Internal PortUse the “mknod” command to create a device file for /dev/ttyp10:

• cd /dev• mknod tty1p0 -c 1 0x0100000

NOTE Be sure to change directories to the /dev directory before executthe mknod command. Failure to do so will result in the “cu”command failing.

Edit the /usr/lib/uucp/Devices fileAdd this line to the bottom of the Devices file:

• gspiport tty1p0 - 9600

Edit the /usr/lib/uucp/System fileAdd the following two lines to the bottom of the Systems file:

• gspiport Any;5 gspiport,f 9600 - "" \r\d\r\d\r ogin:-BREAK-• ogin: uucp asswrd: uucp-BREAK-ogin: uucp asswrd: uucp

NOTE The spelling my look unusual, but enter it exactly as seen above

WARNING! The Internal GSP Port Does not require a passwd. Be sure thatthe port is secure to prevent open access!

Accessing the Internal Port using “cu”From the HPUX prompt enter the following command to access the GSP InternaPort:

• cu -l /dev/tty1p0

***The character after “cu”” is the letter L!***The character after “tty” is the number one!

Exiting the Internal Port• Use the “~.” command to exit the GSP Internal port.


ing

!

l

GSP-82

GSP

GSP-83

GS

P

Notes

theotdo

/IPL

Processor is booting from

To discontinue, press any

Boot terminated.---- Main Menu -------------

Command-------BOot [PRI|ALT|<patPAth [PRI|ALT] [<paSEArch [DIsplay|IPL

COnfiguration menuINformation menuSERvice menu

DIsplayHElp [<menu>|<comRESET

----Main Menu: Enter comma

GSP-L 2 -0 0 1 a

Console Prompts• BCH - Boot Console Handler• GSP - Guardian Service Processor• ISL• HPUX

BCH PromptThe boot console handler is started when the system is power-up and will displayPOST sequence until it completes. The default for the N-Class is to have auto-boenabled. In order to reach the BCH menu you must hit any key when prompted toso, else the system will auto-boot to HPUX

From the BCH prompt a set of familiar menus can be accessed as well as the ISLprompt, as shown on the following page.

Confident ial

first available device.

key within 10 seconds.

-------------------------------------------

Description-----------

h>] Boot from specified pathth>] Display or modify a path

] [<path>] Search for boot devices

Displays or sets boot valuesDisplays hardware information

Displays service commands

Redisplay the current menumand>] Display help for menu or command

Restart the system

nd or menu >

BCH Prompt


GSP

Notes

GS

P

GSP-84

GSP

GSP-85

GS

P

Notesontrol

GSP

and

GSP> he

HEHardware Revision 8

AC : Alert Display ConfiguraAR : Config. Automatic SystCA : Configure serial port pCE : Log repair info in histCL : Display console historyCO : Return to Console MoDC : Default configurationDI : Disconnect remote or LDR : Disable remote or LANER : Enable remote or LANHE : Display the available cIT : Modify GSP inactivity tiLC : Configure LAN consoleLS : Display LAN console sMR : Modem ResetMS : Display the status of

GSP-L 2 -0 0 2

GSPThe Guardian Service Processor can be accessed at anytime by depressing the cand b keys together. (̂b)

Some of the frequently used utilities within the GSP environment are:• LC - setting the LAN Console IP• ER - enabling the LAN Console• SL - viewing system faults• AC - alert configuration• CA - remote port config• PC - power control• PS - power system monitor• SO - access control• XU - upgrade GSP firmware

A full list of GSP utilities can be viewed (as seen above) by executing the “he”command at the GSP prompt. These commands will be further discussed in the “Utilities” section of the “Diagnostics and Utilities” chapter.

NOTE The GSP prompt does not require the system to be powered upcan be accessed after a power failure.

Conf ident ial

Firmware Revision X.17.04 May 10 1999,12:05:16tion PC : Remote Power Controlem Restart PS : Power Management Module statusarameters RP : Reset password configurationory buffer RS : System reset through RST signal

SDM: Set Display Mode (hex or text)de SE : Activate a system session

SL : Display SPU status logsAN console SO : Security options & access control

console SS : System's processor statusconsole TC : System reset through INIT signal

ommands TE : Sends a message to other terminalsmeouts VFP: Activates Alert Log Display

WHO: Display list of GSP connected userstatus XD : GSP Diagnostics and Reset

XU : Upgrade the GSP Firmwarethe Modem

GSP Menu


GSP

Notes

GS

P

GSP-86

GSP

GSP-87

GS

P

Notes

s

l

Main Menu: Enter command

Interact with IPL (Y, N, or

Booting...Boot IO Dependent Code (IHARD Booted.

ISL Revision A.00.38 OCT

ISL> heHELP HelpLS List IAUTOBOOT SetAUTOSEARCH SetPRIMPATH ModiALTPATH ModifCONSPATH ModDISPLAY DisplaLSAUTOFL ListFASTSIZE Sets800SUPPORT Boot700SUPPORT BootREADNVM DispREADSS DispLSBATCH ListBATCH ExecLSEST List cEST Execu

GSP-L 2 -0 0 3GSP-L 2 -0 0 3

ISL PromptAs shown above the ISL prompt can be access by entering “boot” from the BCHprompt and then answering “y” when asked to interact with IPL.

The “Help Facility” menu can be reached by entering “he” from the ISL prompt (aseen above).

NOTE ODE can be executed from the ISL by simple tying “ode”. This wilcovered in detail in the “Diagnostic and Utility “chapter.

Conf ident ial

or menu > bootCancel)?> y

ODC) revision 1

26, 1994

FacilitySL utilitiesor clear autoboot flag in stable storageor clear autosearch flag in stable storage

fy primary boot path in stable storagey alternate boot path in stable storageify system console path in stable storagey boot and console paths in stable storage

contents of autoboot fileor displays FASTSIZEs the s800 Support Kernel from the boot device

the s700 Support Kernel from the boot devicelays contents of one word of NVM

lays contents of one word of stable storagecontents of batch fileute commands in batch fileontents of EST (Extended Self Test) filete commands in EST (Extended Self Test) file

ISL Menu


GSP

Notes

GS

P

HPUX promptAuto boot on is set as a default from the factory. Without any intervention the N40server should boot to the HPUX prompt when power is applied to the system viapower switch.

• While at the HPUX prompt the GSP prompt can still be reached with the“^b” keyboard sequence.

• HPUX provides an “Internal GSP” access port that can used without apasswd, in the case of a forgotten GSP passwd!


00the

GSP-88

GSP

GSP-89

GS

P

Notes

re:

S

GSP-L 2 -0 1 9

• Setting Mod• Setting the P• Setting the S• SW_CAP

Stable StorageThis section provides information on how to modify stable storage on the N4000server beyond the context of basic configuration and boot parameters. Included a

• Model String• Product number• SWID• SW_CAP

Conf ident ial

table Storage

el Stringroduct NumberWID


GSP

Notes

GS

P

GSP-90

GSP

GSP-91

GS

P

Notes

will

s

ID

e

up

Login to the GSP and NService Processor login:Service Processor passw

Hewlett-P9000/800

Execute the “in pr” Com

Main Menu: Enter commPROCESSOR INFORMAT

Processor Speed--------- -------- -------

1 360 MH3 360 MH

Central Bus Speed (inSoftware ID (dec)Software ID (hex)Software Capability

Verifying

GSP-L 2 -0 2 0

Model_String and SW_ID

Setting the SWID and Model StringOn some new units shipped from distributors or when replacing a system board itbe necessary to modify the Model string and/or SWID. Depending on weather thesystem is factory direct or shipped from a HP distributor the factory default settingfor these variables may vary, as seen below:

• Direct Shipment customer orders should have the Model String and SW_properly set to match the customers ordered configuration.

• Base units shipping from HP to Distributors will ALWAYS be set up for440MHz operation. The System Board switches, the HVERSION, and thModel String will all be set for a 440MHz system.The SW_ID will beUNSET.

• System Boards shipping via GSL for field repairs will also always be setfor 440MHz operation.

Conf ident ial

ote the Model_String

ord:ackard Guardian Service Processor/N4000-36 System Name: Andover-GSP

mand from the BCH Main Menu

and or menu > in prION

HVERSION SVERSION ProcessorModel Model/Op CVERSION State

- -------- -------- -------------z 0x05be 0x0491 2. 3 Activez 0x05be 0x0491 2. 3 Idle

MHz) : 120: 665329303: 0x27a81e97

: 0x01f0

the Model String


GSP

Notes

GS

P

MODEL_STRING

The N-Class server has the Model_String variable automatically set by PDC to

one of two possible values:• 9000/800/N4000-36 (for systems with 360 MHz processors)• 9000/800/N4000-44 (for systems with 440 MHz processors)

NOTE “SS_CONFIG” does not run on the N4000 and therefore is not usto set the model string.

Viewing the model StringThere are two methods for checking the current Model_String setting on a Prelud

• Via the HP-UX "model" command.• The other is via the GSP interface. Upon entering the GSP the following

banner will be printed:

Hewlett-Packard Guardian Service Processor9000/800/N4000-44 System Name:xxxxxxx

NOTE If the Model_String is changed via the BCH commandsdocumented below, the GSP banner will not be updated until thesystem is reset.

In order to verify that the model string has been properly set:• Record the Model_String from one of the two aforementioned methods.• From the BCH Main Menu execute this command: “in pr”• Verify that the processors reported by the “in pr” command match the pro

cessor speed reported in the Model_String.

Modifying the Model_StringThe following steps will insure that the Model_String is set correctly.

0) Check the dipswitch settings.On new systems shipped from HP Distributors or on replacement systemboards where 360 MHZ CPUs are being utilized the processor dipswitchspeed setting should be verified. This dipswitch is located along the frontedge of the System Board and is labeled "S1".

• 360 MHz CPUs -> Switches 1,2,3,6 ON / Switches 4,5,7,8 OFF• 440 MHz CPUs -> Switches 1,2,6 ON / Switches 3,4,5,7,8 OFF

A) Verify the Original Product Number setting from the BCH Main Menu:Main Menu: Enter command >ser pn oThe Original Product Number is : A3639A

NOTE There are reports that this command does not work properly onPDC revision 124 (39.25) - it returns an error when executed. If thhappens, go to step C.


ed

e:

-

is

GSP-92

GSP

GSP-93

GS

P

Notes

CH

ll

zero

Setting th

Main Menu

Defaultin

Initializin

GSP-L 2 -0 2 1

B) If the Product Number is incorrect modify as follows:Main Menu: Enter command or menu > ser pn o A3639AThe Original Product Number is : A3639A

C) In order to force the PDC to generate a new Model_String execute the BConfiguration Menu's "Default" command:Main Menu: Enter command or menu > co de

Defaulting to 800 series/HP UX valuesInitializing ...

CAUTION The Configuration Menu command “DEfault” causes PDC to set adefaults properly (including Model String and SWID). Documentany site specific parameters such as the pri/alt boot paths beforeexecuting the DEfault command.

D) To verify the proper settings, execute theINformation PRocessorcommandfrom the Boot Command Handler's Main Menu and verify that the CPU'sspeeds are all reporting properly and that the SWID is reported as a non-value.

Conf ident ial

e the Model String

: Enter command or menu > co de

g to 800 series/HP UX values

g ...


GSP

Notes

GS

P

GSP-94

GSP

GSP-95

GS

P

Notes

.

he

ror

r-

From the BCH PromptMain Menu: Enter com

Lockword :Zc

Enter Password (H

Enter the System S

This action cannot

Confirm System Se

The system has be

Original Product NuTo change enter th

Settin

GSP-L 2 -0 2 2

SW_ID setting:

The SW_ID is set via the "hidden" BCH Service Menu command “ss_update.Thecorrect procedure for setting the SW_ID is shown above.

• Computed from the Original Product Number and System Serial Number• The SW_ID is stored on system board.• Replacing the system board will require the SW_ID to be modified.• SSKEY or an equivalent tool will be needed to generate a password for t

ss_update command.• If an invalid System Serial Number is set, there will be a Chassis Code er

alerting you to this problem.

SW_CAP setting:• The SW_CAP value is set automatically to 0x01f0 by PDC and is not use

changeable.• This SW_CAP setting is proper for HP-UX Multi-User licensing.

NOTE Again, SS_Config is not used to set the SW_ID value.

Conf ident ial

:mand or menu > ser ss_update

53e192d

ex): .........

erial Number USM3924321

be undone.

rial Number USM3924321 [Y/N/Q(uit)]? y

en initialized with Serial Number USM3924321

mber is:A3639Ae Original Product Number otherwise press Return

g the the SW_ID


GSP

Notes

GS

P

GSP-96

GSP

GSP-97

GS

P

Notes

to a

fo

Updat

GSP firmware is ufrom the GSP prom

- “XU” must be exPort or from HP

- The LAN Consolfirmware files, thLAN Console wh

- Both an IP addre

GSP -L 2 -0 2 3

Updating Firmware

GSP FirmwareThe GSP “XU” command can be used to update the GSP firmware. The latestfirmware can be found on-line and downloaded directly to the GSP. If the HPnetwork is not accessible FTP can be used to download the firmware temporarilyportable PC and then transferred to the N-Class server at the customers site byconnecting the portable PC either directly to the N-Class or the customers LAN. Iattach9ing to the customers LAN the N-Class “Local Console LAN” port must alsbe connected to the same network.

- “XU” must be executed form the local serial port of from the internal GSP port.

- The current GSP firmware revision can be determined by executing “he”.• At the time this document was written GSP firmware could be found at

“192.151.11.37”, with a file path of “ /dist/webconsole/A1.8” for the latestrevision.

NOTE ALLWAYS c heck the WEB site:http://www.docs.hp.com/hpux/content/swc_support/download.htm#Upgrade Processfor the latest instructions onupgrading WEB Console firmware!

Conf ident ial

ing GSP Firmware

pdated with the “XU” commandpt.

ecuted from either the Local SerialUX using the Internal GSP Port .e Port is used for FTP access to the remoteerefore users are disconnected from theile “XU” is running.ss and directory name are required.


GSP

Notes

GS

P

GSP-98

GSP

GSP-99

GS

P

Notes

GSP> xu

XU

This command activatesnetwork will be stopped,will be dropped.

Please, confirm your intey

Enter source system IP15.8.149.21

Enter file path : /sa/sasDepot/current

Do you wish to use they

-> GSP firmware upg

-> GSP firmware upg

GSP -L 2 -0 2 5

Executing

total 20946

-rw-r----- 1 ftp other 1286608 Aug 6 10:05 APPLICATION.ROM

-rw-r----- 1 ftp other 131072 Aug 6 10:05 BOOTSTRAP.ROM

-rw-r----- 1 ftp other 40473 Aug 6 10:05 readme

-rw-r----- 1 ftp other 127 Aug 6 10:05 upgrade.cnf

-rw-r----- 1 ftp other 5242190 Aug 6 10:05 vxWorks_roma0106

-rw-r----- 1 ftp other 3976321 Aug 6 10:06 vxWorks_roma0106.hex

Conf ident ial

the upgrade mode. All connections will be closed, thethe session will be aborted and the modem connection

ntion to activate the upgrade mode (Y/[N]) : y

address : 15.8.149.21

sDepot/current

default login : anonymous / [email protected] (Y/[N]) : y

rade in progress....

rade complete - GSP will now reset....

the “XU” Command


Troubleshooting

Chapter 3: Troubleshooting

Content OverviewTroubleshooting the N4000 server. The following topic will be covered in this chapter.

HPMCs• Initiating the PIM Dump• Collecting PIM Information• Using the on-line WEB based PIM Decoder

Example of a HPMC caused by PCI slots

April 17, 2000 HP Confidential Troubleshooting-100

Troubleshooting

Troubleshooting-101

Trou

bles

hoot

ing

Notesoes

T S-L 2 -0 0 1

In

GSP> tc

TC

Execution of this comI/O activity and resta

Type Y to confirm yoy

-> SPU hardware

GSP Host Name: GGSP>************* SYSTEMSYSTEM NAME: GSPDATE: 10/29/1999 TIMALERT LEVEL: 12 =

REASON FOR ALERTSOURCE: 1 = procesSOURCE DETAIL: 1PROBLEM DETAIL: 0

LEDs: RUN AON F

GSP - TC Co

Initiating a TOCIn the event that the N4000 servers becomes hung or enters a fault state which dnot transition into a TOC, executing the “tc” command from the GSP prompt willmanually initiate a TOC and therefore lead to PIM being saved and an interactivecrash dump menu being displayed in the Console Window.

“tc” Command

• Access the GSP prompt by entering “^b” from the console window.• At the GSP prompt execute the “tc” command.

Confident ial

itiating a HPMC (1 of 2)

mand irrecoverably halts all the system processing andrt the computer system.

ur intention to restart the system : (Y/[N]) y

was successfully reset.

SP_NCL1

ALERT **************_NCL1E: 10:57:54Software failure

sor= processor general SOURCE ID: 0

= no problem detail

TTENTION FAULT REMOTE POWERLASH FLASH ON ON

mmand

HP Confidential April 17, 2000

TroubleshootingTroubleshooting

assis-code999 10:58:31

key:

2 of 2)

Dump Screen

• Multiple lines of System Alert messages will appear before the Crash Dumenu is reached.

• Select which type of dump is to be executed, or none, and system will reafterwards, rebooting to HPUX if Auto Boot is turned on.

Confident ial

SOURCE DETAIL: 1 = processor general SOURCE ID: 0PROBLEM DETAIL: 0 = no problem detail

LEDs: RUN ATTENTION FAULT REMOTE POWERON FLASH FLASH ON ON

0xF8E058301100E000 00000000 0000E000 - type 31 = legacy PA HEX ch0x58E058301100E000 00006309 1D0A3A1F - type 11 = Timestamp 10/29/1A: ack read of this entry - X: Disable all future alert messagesAnything else skip redisplay the log entry->Choice:a*****************************************

*** Select one of the following dump types, by pressing the correspondingN) There will be NO DUMP performed.S) The dump will be a SELECTIVE dump: 66 of 512 megabytes.F) The dump will be a FULL dump of 512 megabytes.

*** Enter your selection now.*** Proceeding with full dump.

*** The dump may be aborted at any time by pressing ESC.*** Dumping: 100% complete (512 of 512 MB).*** System rebooting.

Initiating a HPMC (

T S-L 2 -0 0 2

Crash Dump Screen


Notesmp

set

Troubleshooting-102

Troubleshooting

Troubleshooting-103

Trou

bles

hoot

ing

Notesenu.

r-

T S-L 2 -0 0 3

R

Service Menu: Enter co

PROCESSOR PIM INFO

----------------- Processo

Timestamp = Fri Oc

HPMC Chassis Codes

Chassis Code------------0x0000084000ff0x180008401100x0000084000ff

BCH Prompt: se

PIM CommandAfter a pim has been saved execute the “pim” command from the BCH Service m

• Terminate the boot process by hitting any key at the appropriate time.• At the BCH prompt transition to the Service Menu by entering “ser”.• At the ser menu prompt “help pim” can be executed to acquire more info

mation on executing the pim command.

Confident ial

etrieving PIM

mmand > pim 5 hpmc

RMATION

r 5 HPMC Information ------------------

t 29 14:16:40 GMT 1999 (19:99:10:29:14:16:40)

Extension---------

6242 0x000000000000000056322 0xcba18000000000006462 0x0000000000000000

r pim


Troubleshooting

Notes

Troubleshooting

Help pim

Service Menu: Enter command > help pim

---- PIM Help ---------------------------------------------------------

PIM displays the contents of Processor Internal Memory (PIM) loggedon the first, most severe occurrence of a High Priority MachineCheck (HPMC) or a Low Priority Machine Check or a Transfer ofControl (TOC) for any processor present in the system. Error loginformation is also displayed with the PIM information.

PIM Display HPMC, LPMC and TOC information for allprocessors present in system and the error logs

PIM [<proc>] Display the first, most severe HPMC informationon processor number <proc> and the error logs

PIM [<proc>] HPMC Display the first, most severe HPMC informationon processor number <proc> and the error logs

PIM [<proc>] LPMC Display the first, most severe LPMC informationon processor number <proc>

PIM [<proc>] TOC Display the first, most severe TOC informationon processor number <proc>

Troubleshooting-104

Troubleshooting

Troubleshooting-105

Trou

bles

hoot

ing

Notes

thebe

. Ofhis

y

ht t p://hp

T S-L 2 -0 0 4

Web Based Pim Decoder

Logging into the WEB SiteThe WEB site shown above can be accessed from the main FESWEB site at

http://fesweb.cup.hp.com/home/by navigating these links:• HPMC Analyzers• Link to Web-based tool for N-Class systems.

The next few pages will describe how to capture the PIM dump from memory onGSP, and then save it to a file on the PC. After the file has been saved it can thenuploaded to the WEB site via Netscape.

In order to perform this task as described, Reflection 1 must be installed on the PCcourse there are other ways in which the PIM can be captured, but for simplicity tmethod was chosen as the example.

NOTE If Reflection 1 is not already installed, it can be loaded via AIM benabling the package found under “K:\r1win”.

Conf ident ial

r fes. rose.hp.com/nclassdecode.2



g (1 of 2)

Enable LoggingAfter logging into the GSP and entering into console mode, go to the service menand prepare to capture the PIM information.

• Select “Logging” from the Files Menu.

Conf ident ial

Reflection1 - Enable Loggin

T S-L 2 -0 0 5


Notesu

Troubleshooting-106

Troubleshooting

Troubleshooting-107

Trou

bles

hoot

ing

Notes

u

E

T S-L 2 -0 0 6

• Check “Logging On”.• Check “Disk” and chose a location on your PC to save the file.• After closing the Logging Menu enter “pim” at the Service Menu on the

N-Class console.• After the PIM dump completes go back to the Reflection 1 “Logging” men

and turn logging off.

Conf ident ial

nable Logging (2 of 2)



)

Decoding the PIMBy selecting one of the 2 decoding methods,Full PIM Decoderor Summary PIMDecoder, a screen similar to the one seen above will appear.

Enter the full path name of the captured PIM, then just hit the Process button!

Conf ident ialT S-L 2 -0 0 7

N -Class P im Decoder ( 1 of 3


Notes

Troubleshooting-108

Troubleshooting

Troubleshooting-109

Trou

bles

hoot

ing

Notes

the

O

a

T S-L 2 -0 0 8

N -Class

Analyzing the PIM DumpIn this example the “Summary PIM Decoder” option was chosen. In this case thedecoder only reported information that was inconstant or obviously in error. Hadother option “Full PIM Decoder” been choose the complete PIM dump would hadbeen reported in the output.

On this page CPU 1 runway bus registers can be seen.• The decoder has decode the CPU Status registers as a “Runway Data I/

Fetch Timeout”.• Registers on the other CPUs were not displayed, due to the fact this was

Summary decode and not a Full decode.

Conf ident ial

P im D ecoder ( 2 of 3 )



)

Final ResultQuite a few lines were displayed between what is shown on this page and the prevpage. This only illustrates how the decoder can point directly to a failed part.

In the system this PIM dump came from there was a defective fibre card in slot 12,decoder was 10% accurate!

NOTE Please keep in mind that this example was not intended to beanything more that an exercise in capturing the PIM and runningthrough the decoder. Reading and understanding HPMC analysia 400 level task that requires a high level of data flow and errorhandling knowledge, that which is acquired from 300 and/or 400level training.

Conf ident ialT S-L 2 -0 0 9

N -Class P im Decoder ( 3 of 3


Notesious

the

its is

Troubleshooting-110

HP

MC

Ch

assisC

odes

ting

urce

ecode

this

Appendix A HPMC Chassis Codes

Prelude Machine Check Chassis CodesThese chassis codes all comes from Firmware (Reporting Entity Type = 0, System Firmware). The ReporEntity ID will be the CPU that is processing the Machine Check.

• Each CPU will do some of these, and the Crash Monarch will do many more than the others.• Note that all of these codes have a caller ID of 6 (machine check).

To look up a chassis code from an HPMC dump:

1) Look up the last four digits of the chassis code in the first three columns of this table.

Since there is more than one entry for ”6062” you will need to further qualify this by source and sodetail.

2) The Source and source detail are digits 8 and 7 from the right, respectively. In this example they dto “13” which equates to “DEW Error Status”.

3) To find out which DEW it is decode the sourceID, decode the 6th and 5th digits from the right. Forexample the sourceID=01.

Example:The chassis code “7000384013016062” is decoded as follows:

• source=1• source detail=3• sourceID=01• caller Activity=6• caller subactivity=06• activity stasus=2.

NOTE This table should ONLY be used to look at HPMC chassis codes. Chassis codes for mostselftest and boot forward progress codes will have different caller activities.

Codes inbold are ones we have either seen or believe we are likely to see.

Codes inItalics are ones we have reason to believe are not being used, and are unlikely to be

seen.

April 2000 HP Confidential APPENDIX-112

HPMC Chassis CodesH

PM

CC

has

sis

Co

de

s

APPENDIX-113 HP Confidential April 2000

HPMC Chassis CodesH

PM

CC

hassis

Cod

es


HPMC Chassis CodesH

PM

CC

has

sis

Co

de

s


HPMC Chassis CodesH

PM

CC

hassis

Cod

es


Prelude FAQP

relu

deFA

Q

M

Appendix B Prelude FAQ

For the latest copy of Prelude FAQs see the following URL:

http://desktv.hp.com/n4000/n4000_faq.htm

1. What means 2X PCI and 4X PCI in the block diagram.?A: "2x" and "4x" PCI refers to the bandwidth of the PCI slot. There are 10 PCI slots which are capable of

running at a 4x rate and 2 slots capable of running at only 2x. The 2x rate is 240MBs, 4x is 480MBs.Additionally, a card designator of 2x would refer to a 33Mhz @ 32 bit card, while a card designator of 4xwould refer to a PCI card capable of running at 66MHz @ 64 bits.

2. What is the service processor Login and Passwd?A: Default configuration from the factory is no login and no passwd, they must be assigned during

installation.

3. Why is the N-Class with 1-4 Proc. working with 360MHz, and the N-Class with 8 Proc. workingwith 330MHz?

A: This was a typo in the 1st N4000 EPSS CD. The processor speeds are 360MHz and 440MHz.

4. Can you explain the 2 10mb interfaces on the core io for what reason are those 2 interfaces?A: The 10BaseT lan interface is connected directly to the GSP and be used to access the GSP when the

N-Class is down. The 10/100BaseT lan interface is for the system (hpux) and is connected though a PCIcontroller chip to the N-Class, same as any other 2x PCI I/O slot.

5. What does cfm means?A: Cubic Feet/Minute

6. Please explain in more detail the two system buses?A: The N4000 system has 2 main system busses, called the Merced bus. The Merced bus connects the CPU

controllers to main memory. The N4000 is divided into two halfs each half having its own Merced bus. Thetwo Merced busses are connected through main memory.

7. What happens with the system logs, when i have to replace the service processor?A: System logs are stored on the Core IO board. When replaced, the logs are lost.

8. Are the PCI cards hot swappable?A: PCI cards will be Hot-Pluggable in the future, this is referred to OLRAD. You will be able to replace a PCI

board with the OS up and running OS when OLDAR is implemented in the N4000. When HP-UX supports DKLthere will exist the possibility of adding IO controllers to the kernel while it is running.


Prelude FAQP

relud

eFA

Q

-

9. Is it necessary to use the ss key tape to reconfigure the system when a processor is replaced?A: No.

10. Do you have to remove or fully extend the N-class box from the rack to gain access for exchanging PCI cards?

A: Yes. The SPU must be extended out the rear enough to gain access to remove the IO cage cover.

11. What is the IP Address for the LAN-Console? Is this a fix address, like you find in the V-Class?A: The IP is not fixed for the LAN-Console. It must be configures at the time of installation.

Note: The IP address is fixed for the WEB Console at 192.0.0.192.

12. I have heard that the N-Class system works on the PA8500 and IA64 CPUs. When is the IA64cpu available?

A: The release date is not yet set for when the IA64 CPUs will be released for Prelude. Stay tuned!

13.When we upgrade into the IA64 CPU, we just replace the CPU with IA64 or other chip or sys-tem board need to be replaced?

A: It is still not clear whether or not the upgrade to IA64 will require a box swap. If not, at least one otherchip besides the processor will have to be replaced, the CPU controlled (DEW) would require replacement.

14.Will the system boot without the console?A: Yes, if the autoboot and other applicable parameters have been set.

15.Which end does the WEB Console go on, computer or terminal end?A: Computer end. The WEB Console has a serial port that attaches via a RS232 cable to the Core I/O board's

local console port, and a 10BoaseT port for attaching the WEB Console to the customers LAN.

16.Can we support a different brand of modems w/c a customer has?A: No.

17.How and when will the web site passwd be distributed?A: This will be decided at a latter date.

18.What hp-ux version supported?A: HP-UX 11.0

19.What stand of LCD? (What does LCD stand for?)A: Least Common Denominator. This means that at the factory level a system will be configured with the

minimum amount of parts possible. LCD will be shipped and later configured to match the customer order atconfig sites around the world. This will greatly increase how fast we can fill the customers order.

20.What is the minimum configuration, in order to troubleshoot?A: - one memory carrier w/ 2 DIMMs

- 2 power supplies

- one CPU

- I/O necessary to boot OS, one internal disk drive (no PCI controllers necessary)

- console connected


Prelude FAQP

relu

deFA

Q

21. How many N-Class servers can you put on one PDU or do I need per N-Class one PDU?A: One PDU per N-Class is required in a non-HA environment. HA environments require more than one PDU

per N-Class. Check the site prep section on the EPSS for more details.

22. How does floor to ceiling HVAC air flow affect system placement. Is it different than explainedduring the presentation/why/why not?

A: Floor to ceiling air flow is OK., just remember to put an air vent in front of each N4000 rack to ensure

reasonable intake air temperatures and flow. The worst problem in any installation is when the exhaust from

one N-Class (or other piece of equipment) feeds the intake of another N-Class. Clearance around the N-Class

remains the same.

23. Should the psc cable and the LAN cable be on different segments?A: If "psc" is referring to the GSP 10BaseT LAN and the LAN cable is referring to the 10/100 BaseT system LAN

and segment is the router, then the answer is no.

24. With the emphasis on site prep shouldn't there be a DVM as a required tool? We should alwayscheck the power before plugging in anything!

A: Yes, always check for proper grounding as well as voltage levels and if applicable proper wiring of L1, L2and L3 phases, and neutral.

25. Are the GSP> prompt and the CM> prompt the same, just added features for the N-Class?A: Yes, the GSP> prompt on the N4000 is similar to the CM> prompt on other 9000 series systems. ^b will

access the GSP prompt, and as stated in the question there are many more commands available at the GSPprompt than the CM prompt. The GSP prompt is serviced by a microprocessor apart from the N4000, whichmay be different from previous 9000 systems. Because of this the GSP prompt can be accessed even whenthe N-Class is down due to a fan or power supply failure.

26. Will whoever sends the support link modem PLEASE send them pre-programmed? This hasbeen a problem for YEARS!

A: No, because configurations may vary. The support link modems can be easily configured in field. Ifproblems exist, use the string AT&F8&8 to reset the modem to factory defaults (thus turning local echo on).Then use the WEB or install documentation to access the proper configuration commands for your specificapplication.

27. How often will the N4000 EPSS CD be made available to the CEs. Is a special subscriptionrequired?

A: The EPSS CD will be made available to the CEs via the Learning Centers once or twice a year., whenupdated new are available. The second revision is due out on 6/28/99. Contact your nearest learning centerfor a copy at any time.

28. If CEs use their laptops as a console (many times a network connection is not available atinstall), do we use Reflections1 one or Reflections2? I heard Reflections 2 is going away.

A: If Reflections1 goes away, use Reflections2. Any telnet application should work when connecting to thelan console, and any serial application should work when connecting to the serial lan. Also, hyperterm couldbe an alternative to reflections.


Prelude FAQP

relud

eFA

Q

h

29. Does N systems have internal CD_ROM and tape drive? If yes, where?A: Yes, there is a four way rack mounted tray located in the upper slots of the cabinet which may contain

the tape drive and cdrom plus two other devices. In a fully loaded rack without room for this IO tray, anadjacent cabinet will be required for installing the tape drive and cdrom for all the N-Class SPUs. Cables areavailable for this type of application.

30. As there are 8 fans on the PM board, is there any redundant fan of them?A: First of all, each of the 8 fans does have an associated LED on the Power Monitor board. These LEDs will

indicate which fan has failed if a fan error does occur. Yes, there is redundancy and fans are hot-swappable.

31. Is the power supply hot-swappable?A: Yes.

32. What is the difference between Remote Console, Local Console, and Console LAN, and for eacone used for what circumstance?

A: Remote console is for a modem connection, local console is a RS232 port to any local terminal (or laptop),and the console lan is for connecting a console via the customers LAN. One more console, WEB Consoleprovides for a secure LAN connection and connects to the GSP via the local console port. All console portshave access to both the GSP (using ^b) and the BCH or OS prompt as a direct login. The only advantage ofany console port would that of the WEB Console, I.E if a LAN connection is desired the WEB Console willprovide security.

33. OSHA standards require a hard hat if employee is off the floor. Is there a part number or prod-uct to order for the ladder and hard hat?

A: No HP part number will be assigned as these items are readily available from stores.

34. How tall is the ladder that is required for working on the upper SPU in the N4000 rack and willthe customer be required to supply it? If not how will the CE carry it?

A: A six foot ladder should suffice. We recommend a type III fiberglass.

35. There is an Ultra 2 SCSI 2 out in the marketplace, purported to transfer at 160 MBPS. Is HPgoing to provide this higher throughput capability?

A: We can’t say at this time.

36. Is ssconfig used on the N4000? Is it used to change the MAC network address?A: SSConfig is not used on the N4000. SSUpdate is used in conjunction with SSKey

37. Will PDC updates be sent out on CDROM, a lot of customers do not have a tape locally?A: This is not the current plan on record. If a customer requires a CD, then we recommend they purchase a

CD Writer.

38. In regards to changing the system board, it was mentioned that new connectors were required.What are they?

A: These "connectors" are probably the interposers which are used to mate the CPU socket to the systemboard. Some of the contact material on the interposers can stick to the system board and cause theinterposer to fail. Please note that if a CPU is being changed (and not the system board) the system boardmust be thoroughly cleaned.

Note: cleaning kit part number is A3639-70001


Prelude FAQP

relu

deFA

Q

e

t.

39. What is the suggested line of action in reference to doing site preps if do not see the order beforshowing up for the install?

A: We (Field Engineering Support) have no way of addressing this. What is done for K Class?

40. On the N4000 CD-ROM beta release copy, under add compotents, the CPU Support Modulesbegin with number zero in the diagram and the text begins with number one. Which is correct?

A: CPUs and Support modules begin with 0.

41. If Omin books are not allowed on-site and/or CDROMs restricted how will we be able to trans-late fault codes?

A: A complete list of fault codes can be printed from the CD from the following location:file:///E|/nclass-docs/fpdecoder/allleds.htmfile:///E|/nclass-docs/pciodecode/allleds.htm

42. Are CD-ROM and DAT drives optional; or required?A: Optional.

43. What is the URL for answering questions installation questions concerning the WEB Console?A: The N4000 EPSS references the URL: "http://eproducts.hp.com/webconsole/frame_service.html".

44. What type of backup media does the N4000 utilize?A: This is customer dependent. See the System Configuration Guide for supported devices.

45. When replacing the service processor, is SSKEY necessary?A: NO.

46. When a CPU fails will the system crash? How does CPU deallocation and reboot after a CPUfailure work on the N4000?

A: When a CPU fails the system will HPMC (crash). If that CPU fails its selftest, it will be deallocated and the

system will reboot.

47. When the N4000 is on the pallet the power supplies must be removed before using the Genie lifDoes the packing material allow you to extract the power supplied while the SPU is on the pal-let?

A: Yes.

48. When will the fiber channel on the core IO board be supported?A: We don’t know at this time.

49. How is PDC firmware updated?A: Same as K Class?

50. What is the difference between PPP and LAN console?A: PPP does not exist on the N4000.

51. The WEB Console uses PPP, does it use chap or pap?A: WEB console does not use PPP!


Prelude FAQP

relud

eFA

Q

52. Will NT and MPE ever be supported on the N4000?A: This is up to marketing

53. When will the Hot-Pluggable functionality be available? What is OLAR??A: 11.1? time frame.

54. Is it possible to extend a SPU will the HP-UX is running on a HA system?A: Extending an operating SPU should ONLY be done to replace fans and add/remove PCI I/O cards. The CE

needs to pay close attention so that the SPU is not bumped hard enough to cause the internal disk to crash.Testing was done to ensure that the disk can take the G forces under normal service conditions.

55. Does the Genie lift come with an add-on SPU, if not what is the part number?A: No the Genie lift is not included with an add-on SPU. Reference the Genie WEB site for ordering:

http://www.genielift.com/index2.html

56. Where are the external CD-ROM and DAT drives kept if there are 4 N4000 Servers rackmounted into one cabinet?

A: The CD ROM or DAT drive could be connected to a system and accessed by another via the LAN. TheN4000 can perform LAN boots, thus enabling a system to boot the offline diagnostics over a LAN. So toanswer your question, the external media can reside anywhere.

57. Where do we plug in the power cord for the support modem, considering the PDU is rated at208?

A: Use a modem rated at 220V and then plug it into the PDU.

58. Is there a built in DAT or CD?A: No, these are external devices

59. Are there any off-line diagnostics for the N4000?A: Yes ODE works for N4000

60. Is there any priority for loading PCI slots?A: For maximum performance PCI cards should be evenly divided on both the left and right card cages. Don’t

forget that slots 1 & 2 (the bottom two slots of the left card cage) operate at a slower speed that the otherslots.

61. What type IO devices can we hook up to the N-Class, (I.E> autoraid, nike, jamaica, etc.)A: Please reference the System Configuration Guide.

62. Is it possible to disabled a faulty processor on-line?A: NO. Processors can only be disabled from the Boot Console Handler (BCH).

63. Which UPS is suggested for the N4000 connection?A: Either the 3.0 KVA or the 5.5KVA UPS will support the N4000.


Prelude FAQP

relu

deFA

Q

64. Is there a WEB site to download a manual?A: N4000 manuals can be found at

http://fesweb.corp.hp.com/download/download/manframe.htmlhttp://eproducts.hp.com/webconsole/frame_service.html

Webcast presentation:http://desktv.hp.com/n4000

65. Are the 60A PDUs available yet, if not when?A: Project canceled. No business case.

66. Can an extender kit be added to existing Rosebowl II cabinets (field add-on)?A:Yes. The product numbers are:

A5541A (Kit for a 1.2 meter cabinet)A5542A (Kit for a 1.6 meter cabinet)A5543A (Kit for a 2.0 meter cabinet)

67. Are the P.O.S.T codes documented anywhere?A: Yes. The P.O.S.T. for the N4000 is PDC selftest and is documented in the chassis code decoding section.

68. Can I deconfigure any slave cpu or memory dimm at the BCH prompt, if so what is the com-mand?

A: You can deconfigure CPUs, but not memory at the BCH prompt. In the Service menu, type CPU.

69. Can you please clarify the CPU support modules to cpu numbering? The figure in the EPSSlabels the support modules 0-3, the text has them 1-4. Which is it?

A: these are the correct associations:module 0 - cpu 0 and 2module 1 - cpu 1 and 3module 2 - cpu 4 and 6module 3 - cpu 5 and 7


GSP Help - Full ListingG

SP

Help

-F

ullListin

g

Appendix C GSP Help - Full Listing

Guardian Service Processor Command Help

NOTE The commands listed in this section are effective as of February 29, 2000.

The GSP Help System

Information is available for both GSP functional areas and individual commands

through a menu-based help system. The help menus are accessed by entering he at

the GSP command prompt:

GSP> he==== GSP Help ============================================(Administrator)===

Hardware Revision 6 Firmware Revision A.01.07 Feb 02 1999,10:45:37

GSP Help System

Enter a command at the help prompt:

OVerview : Launch the help overview

LIst : Show the list of GSP commands

<COMMAND > : Enter the command name for help on individual command

TOPics : Show all GSP Help topics and commands

HElp : Display this screen

Q : Quit help

====

GSP HELP:The menu options at the top level of the help system are largely self-explanatory.

OVerview provides a synopsis of the GSP's features. LIst launches a menu of all

available GSP commands. <COMMAND> generates help information for an

individual command. TOPics shows the list of general help topics pertaining to GSP

functions as well as a list of abbreviated command names. HElp returns you to this

top level menu from anywhere else within the help system. Q(uit) exits the help

system and returns you to the GSP prompt.



SP

Hel

p-

Fu

llLi

stin

g

GSP General Topic Help

The TOPic command produces the following menu of help areas:

==== GSP Help ==============================================================

HELP TOPICS

The following topics can be entered for general information:

* ADMINistrator * INTernal port PASSword resetting

* CHASsis codes LIst of commands * PORT summary

* COMmand summary * MODEM * SESsion

* CONSole * MODES of the GSP * TOPics

* HPterm and VT100 * OVERview

(* topics which are included in the OVERview)

The following commands can be entered for help on the command:

AC AR CA CL CO CSP DC DI EL ER HE IT LC LS MR MSPC PG PS RS SDM SE SL SO SS TC TE VFP WHO XD XU

====

The following detailed help is provided for each of these topic areas:

Topic

Help Information

OPERATOR /

ADMINISTRATOR

Administrators have more capabilities than Operators:

1) Administrator-Only Commands:

AR (Automatic server Restart), DC (Default Configuration), IT (Inactivity

Timeout), LC (LAN Configuration), PG (PaGing), SO (Security Options)

2) The internal port can only be used by an Administrator

The GSP Command interface permission/access level:

The GSP Command interface permission/access level is set by the first

user that types CTRL-B to initiate it. If that user is an operator-

user, then the command interface runs in operator mode. Even if an

administrator-user logs in later or if the operator-user disconnects, the

mode stays the same. The mode will only change when the GSP command

interface is left (to go to COnsole, for instance), and CTRL-B is typed

again to return.



SP

Help

-F

ullListin

g

CHASSIS CODEChassis codes are encoded data that provide system information to the user.

Some well-known names for similar data would be Event Logs or Post Codes.

Chassis codes are produced by intelligent hardware modules, the O/S, and

system firmware.• Use VFP to view the live chassis codes.• Use SL to view the chassis code log.

The following severity (or alert) levels are defined:0) No failure 6) Pending failure 11) (Reserved)

1) Information only 7) (Reserved) 12) Software Failure

2) Non-urgent attention req. 8) Performance Impaired 13) System hang

3) System blocked 9) (Reserved) 14) Fatal power failure

4) Unexpected configuration 10) Loss of Functionality 15) Fatal HW failure

5) Environmental problem

SEE ALSO: SL, VFP (Show Logs, Virtual Front Panel)

COMMANDSThe GSP commands can be grouped into the following categories:• STATUS COMMANDS- Provide status on the server and the GSP.

CL, LS, MS, PS, SL, SS, VFP• SERVER CONTROL- Alter the state of the server

MR, PC, RS, TC• GENERAL GSP CONFIGURATION

AC, AR, DC, IT, RP, SDM, SO, XD, XU• GSP PORT CONFIGURATION- Configure LAN, remote/modem, and local ports

CA, EL, ER, LC, PG• CONNECTIONS- Examine and make connections or change mode

CO, CSP, DI, SE, TE, WHO, VFP

CONSOLE MODETyping CO from the GSP Command interface provides a mirrored version of

the OS console. All mirrored users see the same output. Only one of the

mirrored users has write access at a time to the console. To take control

of the console, type CTRL-e c f (not CTRL-e CTRL-c CTRL-f).

SEE ALSO: CO (COnsole)



SP

Hel

p-

Fu

llLi

stin

g

HPTERM & VT100

NOTE Do not mix HP and vt100 terminal types at the same time.

The GSP provides the system console, mirroring it to the GSP local,

remote/modem, and LAN ports. One console output stream is reflected to all

of the connected console users. If several different terminal types are

used simultaneously by the users, some may see strange results.

Applications which care about the terminal type (install, SAM, vi, etc.)

running on HP-UX use three methods to determine the terminal type:

1) The application takes the terminal information from the OS. This

value is set in the CA command and takes effect for all GSP ports.

2) The $TERM shell environment variable

3) The application directly queries the terminal (in this case, the

terminal who has write permission to the console during the query will

establish the terminal type.)

Make sure that settings #1 and #2 agree with your terminal type.

INTERNAL PORTThe GSP internal port can be used to upgrade the GSP firmware from HP-UX (XU

command). It also comes in handy for enabling LAN access. The internal port

needs to be configured in HP-UX before it can be used. It is password

protected and only allows GSP administrator access. It is not mirrored.

Example of HP-UX setup:

1. On the system, the GSP internal port should be /dev/tty1p0.

2. SAM does not configure the GSP internal port.

3. If the device file is not present, it can be created by root as follows:

#cd/dev

#mknod tty1p0 c 1 0x010000

4. Configure cu for the port, for example in /usr/lib/uucp/Devices add:

Direct tty1p0 - 9600 direct

5. Access is via terminal emulators such as cu, if configured properly:

cu -l /dev/tty1p0

6. To terminate the cu session, use ~ [return]

7. Kermit can also be used to access the special device file.

LIST OF COMMANDS(Refer to the section following)



SP

Help

-F

ullListin

g

REMOTE/MODEM - PORT HELPThe modem is used for dial-in access to the GSP or the OS, and can be

configured so that the OS or the GSP can activate a pager.

The remote/modem port is configured via the CA command. The ER command

enables/disables the port and gives the modem control over to the GSP or

the OS. See the help on those commands for more details.

SEE ALSO: CA, ER, DI, MR, MS, PG (Configure Asynchronous, Enable Remote,

DIsconnect remote or LAN, Modem Reset, Modem Status, PaGing)

GSP MODESTHE MIRRORED GSP SESSION:

When first logging on, the user is part of the mirrored GSP session. The

mirrored GSP session has three major modes:

1) GSP Command Mode 2) Console Mode 3) VFP or Alert Mode

You are in the GSP command mode right now; it is where all the GSP

commands can be executed, and typically is entered by typing CTRL-B from

console mode. The CO command switches the mirrored session to view

the console. The VFP command switches the mirrored session to view

the virtual front panel. See the help on those commands for more

information.

LEAVING THE GSP MIRROR:From the local or remote/modem ports, it is also possible to leave the

mirrored GSP session and connect to either the OS (see the SE command)

or to another GSP on the network (see the CSP command).

OverviewThe Guardian Service Processor is an independent support processor for the

system console that provides some major system manageability features:

* Always-on capability: The GSP is alive if the power cord is plugged in.

* User/password access control: Supports operator and administrator users

* Multiple access methods to the GSP:

Local Port - use terminal or laptop computer for direct connect

Remote/modem Port - use dedicated modem RS-232 port and external modem

LAN - use telnet to access GSP LAN port from anywhere

Internal Port - use cu command from the HP-UX system

* Mirrored console: the system console output stream is reflected to all

of the connected console users, and any user can provide input.

* Display and/or logging of:

The system console, System event logs (chassis codes), Virtual

Front Panel (VFP), and system power and configuration status



SP

Hel

p-

Fu

llLi

stin

g

* On local and modem ports, an independent, non-mirrored session can be

started, either to connect to a GSP (CSP), or login to the OS (SE).

* The GSP provides power control, system reset, and TOC capabilities.

PASSWORD RESETThere are several ways to reset passwords in the GSP:

1) In the SO command, change individual users

2) In the DC command, choose 'Reset Security configuration'

3) If all passwords have been forgotten, they can be reset by hitting the

reset button on the back panel of the GSP. After the GSP reboots, the

local console terminal will display a message for five seconds.

Responding to this message in time will allow a local user to reset the

passwords.

Note that the user information as well as the passwords are erased in

methods 2 & 3.

SEE ALSO: DC, SO (Default Configuration, Security Options)

PORTSThe word 'Port' is used to refer to a method of access into the GSP. The

local, remote/modem, and LAN ports are actual connections on the back of

the server. All ports except the internal port can be used even when the

server is non-functional.

* Local port : Provides serial port terminal access. To configure,

see the CA (Configure Asynchronous) command.

* Remote/Modem port: Provides external modem access. Related commands

are ER, MS, and MR (Enable Remote/modem, Modem

Status, Modem Reset)

* LAN port : Provides telnet access into the GSP. Related

commands are EL, LC, and LS (Enable LAN, LAN

Configuration, and LAN Status).

* Internal port : Provides /dev/tty1p0 access from HP-UX system into

the GSP.



SP

Help

-F

ullListin

g

SESSION MODETyping SE from the GSP Command interface provides a non-mirrored,

normal OS login. The session is not the console; it is a separate login to

the OS, and the special output that the OS sends to the console will not be

seen.

RECOMMENDATION:

Use the session for ASCII screen-oriented applications (SAM) or file

transfer programs (ftp) from the local or modem ports. To use these

applications from the LAN, telnet directly to the system for a private

login.

TOPICSThe current help menu

GSP CommandsWith the HP-UX 11.00ACE release, the following changes have occurred in the

GSP commands:• New commands: CSP, EL, PG• Modified command: ER• Commands no longer supported: DR, LR, RP, UR

Following is the list of available GSP commands as shown in the help system:

==== GSP Help ============================================(Administrator)===

AC : Alert display Configuration PC : Remote Power Control

AR : Automatic System Restart config. PG : PaGing parameter setup

CA : Configure asynch/serial ports PS : Power management module Status

CL : Console Log- view console history RS : Reset System through RST signal

CO : COnsole- return to console mode SDM : Set Display Mode (hex or text)

CSP : Connect to remote Service Proc. SE : SEssion- log into the system

DC : Default Configuration SL : Show Logs (chassis code buffer)

DI : DIsconnect remote or LAN console SO : Security options & access control

EL : Enable/disable LAN access SS : System Status of proc. modules

ER : Enable/disable Remote/modem TC : Reset via Transfer of Control

HE : Display HElp for menu or command TE : TEll- send a msg. to other users

IT : Inactivity Timeout settings VFP : Virtual Front Panel display

LC : LAN configuration WHO : Display connected GSP users

LS : LAN Status XD : Diagnostics and/or Reset of GSP

MR : Modem Reset XU : Upgrade the GSP Firmware

MS : Modem Status

The Administrator has some commands (AR, DC, IT, LC, PG, and SO)

not available to the Operator.



SP

Hel

p-

Fu

llLi

stin

g

Command DescriptionAC

Alert display Configuration

The GSP will automatically activate the ALERT DISPLAY when a chassis code

with an alert level greater than or equal to the configured threshold is

received. Users in console mode or GSP command mode when an alert is

displayed will be returned to console mode after it is acknowledged. Users

in VFP mode when the alert is displayed will be returned to VFP mode.

Alerts with level 2 or greater will go into the Error Log. If an alert is

acknowledged in the ALERT DISPLAY, that alert will not light the Attention

LED. Any unacknowledged alert in the Error Log will light the Attention

LED. To turn off the LED, read the Error Log. Since level 2 alerts can

never activate the ALERT DISPLAY, they must always be acknowledged by

reading the Error Log.

The setting in AC has no affect on the automatic early boot VFP. During

boot, level 3 alerts and greater will always be displayed.


ARAutomatic System Restart configuration

The AR command allows the operator to enable, disable, and configure the

Automatic System Restart (ASR). ASR is triggered by each alert level value

that is configured. For instance, for levels 12 and higher, you would

specify alerts '12 13 14 15' for the triggering condition.

The default is level 13. Setting ASR for alert levels below 10 is strongly

discouraged.

(ADMINISTRATOR level command.)

SEE ALSO: DC (Default Configuration)

CAConfigure Asynchronous local and remote/modem parameters

BAUD RATES: Input and output data rates are the same. The value returned

by the stty command on HPUX is the local serial port console speed.

FLOW CONTROL: Hardware uses RTS/CTS; Software uses Xon/Xoff.

TERMINAL TYPE: See subject 'HPterm', (next page)



SP

Help

-F

ullListin

g

TRANSMIT CONFIGURATION STRINGS: Disable this setting whenever the modem

being used is not compatible with the supported modem (MT5634ZBA).

MODEM PRESENCE: Set this to 'not always connected' when the modem may not

always be connected. For example: A modem attached through a switch. In

mode 'not always connected', no dial-out functions are allowed: DIAL-BACK

is disabled, and PAGING is not possible.

MODEM PROTOCOL: CCITT is a European standard; RTS/CTS signaling is used,

as well as the Ring signal. Bell is a U.S. or simple mode.

SEE ALSO: ER (Enable Remote/modem)

CEChassis Entry- Put a repair log entry in the log history

Allows a CE to add an entry to the chassis logs, usually to indicate a

firmware update or repair. The command prompts for a one-line text

message. The message will be logged to the Error Log.

SEE ALSO: AC, SL (Alert Configuration, Show Logs)

CLConsole Log- view the history of the Console output

This command displays up to 20 Kilobytes of logged console data (about 20

pages of display in text mode) sent from the system to the Console path.

SEE ALSO: CO (COnsole)

COCOnsole- leave command mode and return to console

This command exits the GSP command interface, and connects to the system

console. All mirrored users are switched. Type CTRL-B to return to the GSP

command interface.

VT100 and HPTERM: Verify that the GSP setting in the CA command is correct

and all mirrored consoles are of the same terminal type for proper

operation.

To run an ASCII screen-oriented application (SAM) or a file transfer

program (ftp), the console is not the recommended connection. On the local

or remote/modem ports, it is recommended that the SE command be used to

start a private system session, so that console output and mirroring do not

disrupt the application. On the LAN, connecting directly via telnet to the

system over the system LAN is recommended.

SEE ALSO: SE (SEssion)



SP

Hel

p-

Fu

llLi

stin

g

CSPConnect to another Service Processor

This command allows the local or remote/modem user to connect over the GSP

LAN to another GSP on the network. The user that launches the command is

given a private connection to the other GSP over the LAN. To return to the

original GSP, type 'CTRL-]' to disconnect the CSP session.

Other mirrored GSP users are placed in console mode when this command is

executed. The CSP user returns to the mirrored GSP session after ending

the CSP session.

SEE ALSO: LC, SE (LAN Configuration, SEssion)

DCDefault Configuration- reset individual or multiple parameters

This command sets various GSP parameters back to their default values and

also clears out GSP status log entries.

The user may reset all or a subset of the following parameters: IP

configuration, modem configuration, paging configuration, command interface

configuration, disable remote access, command interface configuration,

security configuration, session configuration. For example: setting the

security configuration to default will erase all of the users and

passwords.


SEE ALSO: CA, EL, ER, IT, LC, PG, SO (Configure Asynchronous, Enable

LAN, Enable Remote, Inactivity Timeouts, LAN Configuration,

PaGing, Security Options)

DIDIsconnect remote/modem or LAN console

This command disconnects the remote/modem or LAN users from the GSP. It

does not disable the ports. To disable the ports, see the ER command for

remote/modem and the EL command for LAN access. The TE and WHO commands

are useful to identify the connected users before running this command.

SEE ALSO: ER, EL, TE, WHO (Enable Remote/modem, Enable LAN, TEll, Who)

DLDL COMMAND NOT SUPPORTED

For Display Logs, use the SL (Show Logs) command.

For Disable LAN, use the EL (Enable/disable LAN) command.

SEE ALSO: SL, EL (Show Logs, Enable LAN)



SP

Help

-F

ullListin

g

DRDR COMMAND NOT SUPPORTED

Please use:

ER : Enable/disable Remote console serial port modem access

The DR command has been replaced by the ER command. The ER command

offers a selection of configurations for the remote console serial

port modem, including disabling the port.

SEE ALSO: ER (Enable Remote/modem)

ELEnable/disable LAN console access

The EL command is used to set access permissions for users logging into the

GSP over the LAN. It does not affect the IP configuration or the ability of

the CSP command to connect over the LAN. It also does not affect the

ability of the GSP to perform upgrades over the LAN (XU).

SEE ALSO: LC, LS (LAN Configuration, LAN Status)

EREnable/disable Remote console serial port modem access

The following modes are available for the remote/modem port:

LOCKED-OUT: Lock out all dial-in access

GSP: Exclusive GSP access

SESSION: Modem controlled by OS; both dial-in and dial-out

Dial-in to the modem results in:

Access denied under the mode: LOCKED-OUT

A GSP login under the mode: GSP

A session with the OS under the mode: SESSION

(The OS must be properly configured to use the modem.)

Dial-out (paging) by the OS is allowed under the mode: SESSION.

(The OS must be properly configured to use the modem.)

Paging by the GSP can be done under all modes. (Make sure that paging is

enabled in the PG command.) GSP pages will wait until the modem is idle.

Translation from older versions of the GSP:

Enable Remote = GSP

Disable Remote = SESSION



SP

Hel

p-

Fu

llLi

stin

g

(LOCKED-OUT was not available)

To enable/disable LAN access, use the EL command.

SEE ALSO: CA, EL, MR, MS, PG (Configure Asynchronous, Enable LAN, Modem

Reset, Modem Status, PaGing)

HEThe top-level Help menu

ITInactivity Timeout settings

SESSION INACTIVITY TIMEOUT: up to 1440 minutes - typically 60 minutes

This timeout prevents sessions to the system from being inadvertently left

open. A session can be started by the SE command. An open session can

prevent users from logging onto the GSP through a port and can also prevent

system applications from initiating an outbound connection.

GSP INACTIVITY TIMEOUT: up to (24x60) minutes - typically 60 minutes

This timeout prevents a user from inadvertently keeping the GSP locked in a

GSP Command Interface mode preventing other users from looking at the console

output. The GSP Command Interface inactivity timeout may not be deactivated.


SEE ALSO: ER, SE (Enable Remote/modem, SEssion)

LCLAN configuration (IP address, etc.)

This command modifies the LAN configuration.

The GSP Host Name set in this command is displayed at the GSP command

interface prompt. Typically the DNS name for the LAN IP is entered.

This field can be programmed to any useful name or phrase. For clarity,

it is useful to enter: 'GSPNAME-on-SYSTEM' as the GSP Host name, so

both names show up in the prompt (limit 20 chars, no spaces allowed.)


SEE ALSO: EL, LS (Enable Remote/modem, LAN Status)

LRLR and UR COMMANDS ARE NOT SUPPORTED

Please use:


The legacy commands LR and UR have been replaced by the ER command.



SP

Help

-F

ullListin

g

The ER command offers a selection of configurations for the remote

console serial port modem, including configurations for dialing in and

out.

SEE ALSO: ER, PG (Enable Remote/modem, Paging)

LSThis command displays all parameters and the current status of connections

of the GSP LAN. The LAN parameters are not modified by the execution of

this command.

SEE ALSO: EL, LC (Enable LAN, LAN Configuration)

MRModem Reset

This command makes the GSP send an AT Z command to the modem, which will

reset it. Any modem connections will be lost. The initialization results

can be viewed via the MS command.

SEE ALSO: MS (Modem Status)

MSModem Status- show modem signals and status

The MS command displays the state of the modem lines connected to the

remote/modem serial port. The display can be updated by hitting a Carriage

Return <CR>. The current state of the status signals DCD, CTS, DSR, RI and

the last state of the control signals DTR, RTS set by the firmware are

displayed. The text under 'modem state' is an interpretation of these

signals.

SEE ALSO: ER, MR (Enable Remote/modem, Modem Reset)

PCRemote Power Control - turn system power on and off

For proper system shutdown, shut down the OS before issuing this command.

This command allows the user to switch the system power ON or OFF, or Power

Cycle the machine. The user can have the action take place immediately, or

after a specified delay.

Note this is roughly equivalent to turning the system power off at the

front panel switch- there is no signal sent to the OS to bring the

software down before power is turned off. To turn the system off properly,

the operator must ensure that the OS is in the proper shutdown state

before issuing this command, by using the proper OS commands.

SEE ALSO: PS (Power Status)



SP

Hel

p-

Fu

llLi

stin

g

PGPaGing parameter setup

When a chassis code arrives in the GSP, the paging list is checked to see

if any pagers are enabled for that alert level. If so, the GSP will send a

page to those pagers. Part of the alpha-numeric pager message is the

string configured in this command, describing the alert level that

caused the page.

If the modem is in use by either a dial-in connection to the GSP, a dial-in

session to the OS, or a dial-out by the OS, all pages will queue up and

wait until the modem is idle. Also, the modem presence in the CA command

must be configured for 'always connected' for paging to be possible.


SEE ALSO: CA, ER (Configure Asynchronous, Enable Remote/modem)

PSPower Status- display the status of the Power Management Module

This command displays on the console the status of the power management

module. The firmware revision listed is the power management module

firmware.

SEE ALSO: PC, SS (Power Control, System Status)

RPRP COMMAND NOT SUPPORTED

Please use:

DC : Default Configuration- reset individual or multiple parameters

SEE ALSO: DC, SO (Default Configuration, Security Options)

RSReset System through RST signal

Under normal operation, shut down the OS before issuing this command.

This command causes the system to be reset through the RST signal.

Execution of this command irrecoverably halts all system processing and

I/O activity and restarts the computer system. The effect of this command

is very similar to cycling the system power- the OS is not notified, no

dump is taken on the way down, etc.

SEE ALSO: TC (Transfer Control)



SP

Help

-F

ullListin

g

SDMSet Display Mode (hex or text)

PARAMETERS: hex, text

This command is used to set the default display mode for chassis codes. It

will affect the Virtual Front Panel (plus alerts), and the log viewer.


SESEssion- log into the system on local or remote port

Only valid from the local or remote/modem port, SE allows the user to leave

the GSP Command Interface and enter a system session. Other mirrored GSP

users are placed in console mode. The session user returns to the mirrored

GSP session on exit.

The GSP regularly checks the activity of the session and will close the

connection with the system and return the port to mirroring if the timeout

period has elapsed. The timeout period is set in the IT command.

DEVICE FILES: For proper operation, the HP-UX device files for the session

must be configured (the CA command should be set to match).

Local Session: /dev/ttyd1p1 Remote Session: /dev/ttyd0p2

BAUD RATE: If the system and the GSP Command Interface local or remote

ports have been configured with different port speeds, the baud rate

changes to the rate specified by the OS for the duration of the session.

SEE ALSO: CA, ER, IT (Configure Asynch., Enable Remote, Inactivity Timeouts)

SLShow Logs- view the chassis codes in the log history

This command displays the contents of the chassis codes and events that

have been stored in non-volatile memory.

Incoming : All chassis codes as they come in except for activity

updates codes from the OS.

Activity : All chassis codes of level 1 or greater

Error : All chassis codes of level 2 or greater

Current Boot : All between 'start of boot' and 'boot complete' chassis codes

Last Boot : The codes from the previous boot

Reading the Error Log turns off the Attention LED. Accessing this buffer

is the only way to turn off the attention LED when it is flashing and

alerts have not been acknowledged at the alert display level.

SEE ALSO: AC, SDM, VFP (Alert Configuration, Set Display Mode, Virtual

Front Panel)



SP

Hel

p-

Fu

llLi

stin

g

SOSecurity options & access control (users, passwords, etc.)

This command is used to modify the security parameters of the GSP. These

include user accounts, login timeouts, allowed password faults, etc. Most

of the parameters are familiar; the following require some extra explanation:

DIAL-BACK: If configured, when the user accesses the GSP via the modem

port, the GSP will hang up and dial the user back. Will not work if

'Modem Presence' is set to 'not always connected' in the CA command.

MODE: Single/Multiple. If the mode is Single, the State will be changed to

disabled after the first login.

USER'S STATE: Enabled/Disabled. A disabled user's login will not be

accepted.


SEE ALSO: CA, PG (Configure Asynchronous, PaGing)

SSSystem Status- display the status of the system processors

The SS command displays the status of the system processors and which

processor is the monarch.

The GSP learns the system configuration through the chassis codes it

receives from the system. Therefore, there will likely be a delay between

any processor configuration change and what is displayed by this command.

A more reliable way to get the processor configuration information is at

the BCH prompt.

SEE ALSO: PS (Power Status)

TCSystem reset through INIT or TOC (Transfer of Control) signal

Under normal operation, shut down the OS before issuing this command.

This command causes the system to be reset through the INIT (or TOC) signal.

Execution of this command irrecoverably halts all system processing and

I/O activity and restarts the computer system. It is different from the

RS command in that the processors are signaled to dump state on the way

down.

SEE ALSO: RS (ReSet)



SP

Help

-F

ullListin

g

TETEll- sends a message to other terminals

Up to 80 characters can be typed in and the message is broadcast to the

other mirrored clients. Users in a session or CSP are not shown the

message.

SEE ALSO: WHO

URLR and UR COMMANDS ARE NOT SUPPORTED

Please use:


The legacy commands LR and UR have been replaced by the ER command.

The ER command offers a selection of configurations for the remote

console serial port modem, including configurations for dialing in and

out.

SEE ALSO: ER, PG (Enable Remote/modem, Paging)

VFPVirtual Front Panel display (all ports except internal port)

When invoked, the VFP will display the LED state with a text decode and the

most recent Chassis Code received. At that point, the user can then

proceed with the live-mode VFP display of chassis codes, or quit back to

the GSP prompt.

There are two ways that the live display of chassis codes can be started:

LIVE MODE: Invoked from the VFP command at the GSP prompt. To

exit, you must type Q to quit to the console.

EARLY BOOT MODE: When the boot sequence for the system begins, the live

VFP is invoked automatically. When boot finishes, users

are automatically switched to console mode.

The LED state reflects the state of the front panel LED's. When system

power is off, the remote LED will show 'OFF' even though remote access may

be enabled in the EL or ER commands.

SEE ALSO: AC, SL (Alert Configuration, Show Logs)

WHODisplay a list of GSP connected users

This command display the login name of the connected console client users

and the port on which they are connected. For the LAN console clients the

remote IP address is also displayed.



SP

Hel

p-

Fu

llLi

stin

g

There is always one user listed for the local serial port. This is a

default user name ('local user') if the local console client user didn't

originate the GSP Command Interface session. If the local console operator

typed CTRL-B, then the login name that the local operator typed is

displayed instead.

SEE ALSO: TE (TEll)

XDDiagnostics and/or Reset of GSP

This command allows the user to perform some simple checks to confirm the

GSP's health and its connectivity status. The following tests are

available:

* Parameters checksum

* I2C bus test

* LAN connectivity test using 'ping'

* Modem self-tests

Also, the GSP can be reset from this command. A GSP reset can be safely

performed without affecting the operation of the server.

XUUpgrade the GSP Firmware

The upgrade is performed using ftp over the GSP LAN, which must therefore

be operational. The user must enter the ftp server IP address, login,

password, and the directory in which the upgrade files reside.

LAN and modem connections will be dropped. The XU command can only be

run from the local or internal ports. If the upgrade is successful, the

GSP will reboot and come up using the new software.

If the upgrade fails, the GSP will return to the prompt with instructions

on what went wrong, and what to do next.

Upgrading the GSP software and rebooting the GSP can be safely performed

without affecting the operation of the server.

The version of GSP firmware is displayed at the top of the main help menu.


Date post:	24-Oct-2015
Category:	Documents
Upload:	sun-gary
View:	41 times
Download:	0 times

n Class Manual

Documents