Manuals / HP / Computer Equipment / Network Card

HP NonStop NS Blade Element Reintegration, CPU n has been dumped to dumpfile, FUP Info dumpfile

Models: NonStop NS

1 266

Download 266 pages 1.32 Kb

Page 130

Processors and Components: Monitoring and	Dumping a Processor to Disk
Recovery

cpuNum

is the number of the logical processor from which a processor element is to be dumped. Specify cpuNum as an integer in the range from 0 through 15.

BLADE bladeId

is the identification of the Blade Element from which the processor element is to be dumped. Valid values are A or B or C or ALL. Note that ALL may not be used with the parallel method of dumping.

START n...

is the byte address where the dump will start. The default value is 0.

END n...

is the byte address where the dump will stop. Using a value of -1 is the same as specifying the end of memory. The default value is -1.

ONLINE

If this option is specified, a dump can be taken of a processor while it is running. You may use either PARALLEL or ONLINE but not both.

PARALLEL

If this option is specified, a dump may be taken of a single processor element while the other PEs in that logical processor are reloaded and continue normal operations. You may use either PARALLEL or ONLINE but not both.

For more information, see the HP NonStop TACL Reference Manual.

3.Monitor the dump to make sure that it finishes successfully:

a.Wait for this message to appear:

CPU n has been dumped to dumpfile

b.Check the size of dumpfile to verify that the end-of-file pointer (EOF) is not equal to zero.

>FUP INFO dumpfile

When a processor is dumped to disk, the RCVDUMP utility begins copying the dump in a compressed format from the specified processor into a disk file called dumpfile. If dumpfile does not exist, the RCVDUMP utility creates it. As the dump proceeds, the status of the processor being dumped changes in the Processor Status dialog box to indicate that a dump is in progress. When the dump is finished, the status of the selected processor in the Processor Status dialog box changes to indicate the completion of the dump.

Blade Element Reintegration

Whether TFDS or RCVDUMP was used to dump the PE for an individual Blade Element, reintegration should take place automatically upon completion of the dump.

HP Integrity NonStop NS-Series Operations Guide—529869-005

9-18

Image 130

HP NonStop NS manual Blade Element Reintegration, CPU n has been dumped to dumpfile, FUP Info dumpfile

Contents

Abstract Product Version Supported Release Version Updates RVUsPart Number Published Document History Part Number Product Version Published HP Integrity NonStop NS-Series Operations Guide Introduction to Integrity NonStop NS-Series OperationsDetermining Your System Configuration Monitoring EMS Event Messages ServerNet Resources Monitoring and Recovery 10-4 10-210-3 10-511-5 11-111-2 11-8Power Failures Preparation and Recovery 15-21 15-1915-20 15-22Preventive Maintenance Related Reading Converting Numbers Examples FiguresTables New and Changed Information What’s New in This ManualManual Information Document HistoryXiv About This Guide Who Should Use This GuideWhat Is in This Guide Converting NumbersWhere to Get More Information ServerNet Cluster ManualHypertext Links Support and Service LibraryNotation Conventions General Syntax NotationAllowsu on OFF MaxattachInterrupts Inspect OFF on SaveabendEnter RUN Code Notation for MessagesCode Received Proc-nametrapped in SQL in SQL file system Backup UpEvent number = number Subject = first-subject-value OperatorChange Bar Notation Introduction to Integrity NonStop NS-Series Operations Understanding the Operational Environment When to Use This SectionMonitoring the System and Performing Recovery Operations What Are the Operator Tasks?Powering On and Starting the System Preparing for and Recovering from Power FailuresStopping and Powering Off the System Performing Preventive MaintenanceProblem-Solving Worksheet Determining the Cause of a Problem a Systematic ApproachResponding to Spooler Problems Updating FirmwareProblem Facts Possible Causes Problem-Solving WorksheetSituation Facts Escalation Decision Task 1b Determine the Facts About the Situation Task 1a Determine the Facts About the ProblemTask 1 Get the Facts Category Questions to AskTask 2 Find and Eliminate the Cause of the Problem Task 2a Identify the Most Likely CauseTask 3a Determine Whether You Need to Escalate the Problem Task 2b Fix the Most Probable Cause of the ProblemTask 3 Escalate the Problem If Necessary Task 3b Provide DocumentationLogging On to an Integrity NonStop Server Task 4 Prevent Future ProblemsSystem Consoles Opening a Tacl Window From the Low-Level Link Opening a Tacl WindowOpening a Tacl Window Directly From OutsideView Select StartProgramsOutsideView32Overview of OSM Applications Launching OSM ApplicationsService Procedures Determining Your System Configuration Modular Hardware Components Integrity NonStop NS16000 SystemsIntegrity NonStop NS14000 Systems Integrity NonStop NS1000 SystemsDevice Recording Your System ConfigurationTerms Used to Describe System Hardware Components System Resource or ObjectSCF Configuration Files Using SCF to Determine Your System ConfigurationSCF System Naming Conventions Save Configuration Using SCF to Display Subsystem Configuration InformationSCF Assume WS $L1.#TERM1 SCF Listdev Listing the Devices on Your System Example 2-1. SCF Listdev Command OutputSCF Listdev Specified device Backup processor number and PIN of the specified deviceSubsystem Name Logical Name Device Type Description SCF Assume Process $ZTCO Displaying SCF Configuration Information for SubsystemsTCP/IP Subsystem Displaying Information for the TCP/IP Subsystem $ZTCOSCF Assume Process $ZZKRN Kernel SubsystemStorage Subsystem Displaying Information for the Kernel Subsystem $ZZKRNMirrorlocation 11,1,12 Example 2-2. SCF ADD Disk Command OutputInfo Disk $SYSTEM,OBEYFORM CbpoollenInfo Tape $*,OBEYFORM ServerNet LAN Systems Access Slsa SubsystemADD Adapter $ZZLAN.E0154 Location Type G4SA Accesslist SCF Assume Process $ZZLANDisplaying Information for the WAN Subsystem $ZZWAN WAN SubsystemAdditional Subsystems Controlled by SCF Subsystem Objects Controlled by SCF page 1Subsystem Objects Controlled by SCF page 2 X25AMExample 2-4. SCF Info SAC Command Output Displaying Configuration Information-SCF ExamplesExample 2-3. SCF Info Process Command Output Info Proc $ZZKRN.#Info Process $ZZWAN Example 2-5. SCF Info Process $ZZWAN Command OutputExample 2-6. SCF Info Line Command Output Info Line $line-name, DetailOverview of Monitoring and Recovery Functions of Monitoring Working With a Daily ChecklistMonitoring Tasks Tools for Checking the Status of System Hardware Task Operator’s name Date & timeMonitored Using These Resource Tools See Monitoring System ComponentsServerNet Cluster 6770 Hardware Additional Monitoring Tasks Daily Tasks ChecklistGeneral Tasks Specific Tasks For More Information, See Using the OSM Service Connection Monitoring and Resolving Problems-An ApproachUsing OSM to Monitor the System Top-Down ApproachOSM Management System Icons Indicate Problems Within Expanding the Tree Pane to Locate the Source of Problems Using System Status Icons to Monitor Multiple Systems Attributes TabUsing Alarm and Problem Summaries Alarm Summary Dialog BoxRecovery Operations for Problems Detected by OSM Using SCF to Monitor the SystemSuppressing Problems and Alarms Monitoring Problem Incident ReportsExample 3-1. SCF Status Tape Command Determining Device StatesSCF Object States page 1 SCF Object StatesState Substate Explanation SCF Object States page 2 Servicing SpecialExample 3-2. System Monitoring Command File Automating Routine System MonitoringExample 3-3. System Monitoring Output File page 1 Example 3-3. System Monitoring Output File page 2 Example 3-3. System Monitoring Output File page 3 Status LEDs and Their Functions page 1 Using the Status LEDs to Monitor the SystemLocation LED Name Color Function Status LEDs and Their Functions page 2 FC-AL I/ORelated Reading for Monitoring Related ReadingStatus LEDs and Their Functions page 3 Task Tool For information, seeTools for Monitoring EMS Event Messages What Is the Event Management Service EMS?Monitoring EMS Event Messages ViewPoint onWeb ViewPoint OSM Event ViewerViewPoint Related Reading for Monitoring EMS Event MessagesTypes of Processes Processes Monitoring RecoverySystem Processes Processes IOPs Generic ProcessesMonitoring Processes Monitoring System ProcessesMonitoring the Status of $ZZKRN Monitoring IOPsMonitoring Generic Processes Monitoring the Status of All Generic ProcessesCLCI-TACL $CLCI Stopped PID Supported for the subsystem manager processes Recovery Operations for ProcessesInitiates the operation of a generic process Communications Subsystems Monitoring and Recovery Communications SubsystemsLocal Area Networks LANs and Wide Area Networks WANs LAN Service Provider Subsystems Supported Object Connectivity ByMonitoring the Status of an Adapter and Its Components Monitoring Communications Subsystems and Their ObjectsMonitoring the Slsa Subsystem To monitor the status of an adapterSCF Status SAC $ZZLAN.G11123 SCF Status Adapter $ZZLANSCF Status SAC sac-name SCF Status PIF pif-nameSCF Status PIF $ZZLAN.G11123 Monitoring the WAN SubsystemMonitoring Status for a Swan Concentrator SCF Status LIF $ZZLAN.L11021A , DetailSCF Status Adapter $ZZWAN Monitoring Status for a Data Communications DeviceSystem displays a listing similar to SCF Status Device $ZZWAN.#device-nameMonitoring WAN Processes To monitor a single WANBoot process, typeSCF Status Process $ZZWAN.#boot-process SCF Status Process $ZZWANMonitoring the NonStop TCP/IP Process Monitoring CLIPsMonitoring the NonStop TCP/IP Subsystem SCF Listdev TcpipMonitoring Line-Handler Process Status Monitoring NonStop TCP/IP RoutesMonitoring NonStop TCP/IP Subnets SCF Status Route $ZTCOSCF Status Line $LHCS6S, Detail Info Process $NCP, LinesetTracing a Communications Line Related Reading for Communications Lines and Devices page 1 Recovery Operations for Communications SubsystemsFor Information About Refer to WAN Subsystem Configuration and Management Manual Related Reading for Communications Lines and Devices page 2ServerNet Resources Monitoring and Recovery ServerNet Communications NetworkIntegrity NonStop NS16000 ServerNet Connectivity Integrity NonStop NS16000 SystemIntegrity NonStop NS14000 ServerNet Connectivity Integrity NonStop NS14000 System with Ioam EnclosureMonitoring the Status of the ServerNet Fabrics System I/O ServerNet ConnectionsIntegrity NonStop NS1000 ServerNet Connectivity Monitoring the ServerNet Fabrics Using OSM Monitoring the ServerNet Fabrics Using SCF SCF Status Servernet $ZSNETIdentifying ServerNet Fabric Problems Normal ServerNet Fabric StatesRecovery Operations for a Down Path Between Processors Recovery Operations for the ServerNet FabricsRecovery Operations for a Down Disk Due to a Fabric Failure Recovery Operations for a Down ProcessorAdapters and Modules Monitoring and Recovery Fibre Channel ServerNet Adapter Fcsa Adapters and ModulesGigabit Ethernet 4-Port Adapter G4SA Monitoring I/O Adapters and Modules Port ServerNet Extender 4PSESCF Status Adapter $ZZSTO.#FCSA*, Detail Monitoring the FCSAsState Description Monitoring the G4SAs SCF Status Adapter $ZZLAN.G1123Service, Device, and Enabled States for the G4SA page 1 Recovery Operations for I/O Adapters and Modules Monitoring the 4PSEsRelated Reading for I/O Adapters and Modules ServerNet/DA ManualProcessors and Components Monitoring and Recovery Overview of the NonStop Blade Complex LSU CPU Summary, these terms describe the Nsaa processor Monitoring Processors Automatically Using TfdsMonitoring and Maintaining Processors Term DescriptionMonitoring Processor Status Using the OSM Low-Level Link Processor Status DisplayOSM Representation of Processor Complex Processor or System Hangs Identifying Processor ProblemsMonitoring Processor Performance Using ViewSys ViewsysHalt code = %nnnnnn OSM Alarms and Attribute ValuesProcessor Halts Freeze code = %nnnnnnRecovery Operations for Processors Recovery Operations for a Processor HaltReloading a Single Processor on a Running Server Halting One or More ProcessorsSelect Processor ActionsHalt Click Perform action Select FileStart Terminal Emulator Using Tacl Reload to Perform ReloadReload / run-option , run-option Primenoprime Noswitch Primenoprime fabric Omitblade ABCNoswitch FabricUsing the OSM Service Connection to Perform Reload Select Reload, click Perform actionRecovery Operations for a System Hang Enabling/Disabling Processor and System Freeze Freezing the System and Freeze-Enabled ProcessorsDumping a Processor to Disk See Using Rcvdump to Dump a Processor to Disk on Before You Begin Using Rcvdump to Dump a Processor to DiskFUP Purgedata dumpfile CPU n has been dumped to dumpfile Blade Element ReintegrationFUP Info dumpfile Backing Up a Processor Dump to Tape Troubleshooting and Recovery Operations for Disk DumpsSubmitting Information to Your Service Provider Replacing Processor MemoryBackup $tape, CPU0,$SYSTEM.SYS00.CONFTEXT Submitting Tapes of Configuration and Operations FilesOther Files to Submit to Your Service Provider Submitting Tapes of Processor DumpsAdditional Information Required by Your Service Provider For Information About Tool See Disk Drives Monitoring and Recovery Internal Scsi Disk Drives Overview of Disk DrivesFor information about Enterprise Storage System ESS Disks M8xxx Fibre Channel Disk DrivesFor information about See Monitoring Disk Drives With OSM Monitoring Disk DrivesTask See Monitoring Disk Drives With SCF Status Disk $*, SUB MagneticStatus $DATA01 Status Disk $DATA09, DetailTo display the status of the disk $DATA01 Status $DATA02-MTo display the status of all disks Status Disk $To display status of all paths for $DATA00 To display the detailed status of the disk $DATA01Status $DATA01, Detail Status Disk $DATA00Monitoring the State of Disk Drives Monitoring the Use of Space on a Disk VolumePrimary and Backup Path States for Disk Drives Monitoring the Size of Database FilesTo check the size of the file DATA1.MEMOS Monitoring Disk Configuration and PerformanceExample FUP Info DATA1.MEMOS, DetailPossible Causes of Common Disk Drive Problems Identifying Disk Drive ProblemsProblems Possible Symptoms Common Recovery Operations for Disk Drives page 1 Recovery Operations for Disk DrivesThese SCF commands control Disk objects Command DescriptionCommon Recovery Operations for Disk Drives page 2 Customer Support Center or your service providerReset Disk $WD8 Recovery Operations for a Down Disk or Down Disk PathReset Disk $volume Start Disk $volumeFUP Alter MEMOS, Maxextents Info MEMOS, Detail Recovery Operations for a Nearly Full Database FileReport such as this one is sent to your home terminal 10-16 Tape Drives Monitoring and Recovery Overview of Tape DrivesMonitoring Tape Drives Monitoring Tape Drive Status With OSMOSM Monitoring Tape Drives Connected to an Fcsa OSM Monitoring Tape Drives Connected to an IOMF2 SCF Status Tape $TAPE0 Monitoring Tape Drive Status With SCFListing similar to this one is sent to your home terminal Listing such as this one is sent to your home terminalMediacom Status Tapedrive Monitoring Tape Drive Status With MediacomMediacom Status Tapedrive $TAPE0 Symptom Problem Possible Causes Identifying Tape Drive ProblemsCommon Tape Drive Problems Monitoring the Status of Labeled-Tape OperationsPerforming an OSM Action on a Tape Drive Recovery Operations for Tape DrivesRecovery Operations Using the OSM Service Connection Performing an OSM Action on a Multiple Tape DrivesSCF Command Description Recovery Operations Using SCFRelated Reading for Tapes and Tape Drives page 1 Related Reading for Tapes and Tape Drives page 2 Printers and Terminals Monitoring and Recovery Overview of Printers and TerminalsMonitoring Collector Process Status Monitoring Printer and Collector Process StatusMonitoring Printer Status Spoolcom DEV $LASERRecovery Operations for Printers and Terminals Recovery Operations for a Full Collector Process12-4 Monitoring TMF Applications Monitoring and RecoveryTMF States on Tmfcom Monitoring Data VolumesMonitoring the Status of TMF ~ Status TMFTMF subsystem can be in any of the states listed in Table TMF StatesTmfcom responds with output similar to TMF States page 1Status *, Prog $*.*.PATHMON Monitoring the Status of PathwayTMF States page 2 = Status PathwayPathcom responds with output such as Pathmon States= Status Pathmon Another requester Request is waiting for an object that has been locked byRequest is waiting for a RUN Program to finish Power Failures Preparation and Recovery ESS Cabinets onNonStop S-Series I/O Enclosures System Response to Power FailuresNonStop NS-Series Cabinets Modular Cabinets External DevicesESS Cabinets Preparing for Power FailureConfigure OSM Power Fail Support Air ConditioningMonitor Batteries Power Failure RecoveryMonitor Power Supplies Maintain BatteriesProcedure to Recover From a Power Failure Setting System Time14-6 Starting and Stopping the System Alerts onPowering On a System Select Power On System Powering On the System From a Low Power StatePowering On the System From a No Power State Select Hard Reset Click Perform Action15-4 Alerts Starting a SystemLoading the System Normal System LoadSystem Load to a Specific Processor System Load DisksDisk Drive Enclosure System Load Paths for a Normal System LoadSystem Load Paths in Order of Use Path Group Module SlotConfiguration File Data TravelsStarting Other System Components Performing a System LoadSystem Load Dialog Box Click Start systemPerforming a System Load From a Specific Processor Reloading Processors Reloading Processors Using the Reload CommandReloading Processors Using OSM Reload 01 15, PrimeLogical Processor Reload Parameters Stopping Application, Devices, and Processes Minimizing the Frequency of Planned OutagesAnticipating and Planning for Change Stop DSM/SCM = SHUTDOWN2, Mode OrderlyVolume $DSMSCM.ZDSMSCM RUN StopscmSpoolcom supervisor-name, SPOOLER, Drain Halting All Processors Using OSMStopping the System Tmfcom Stop TMFSystem Power-Off Using SCF Powering Off a SystemSystem Power-Off Using OSM From the Processors Actions menu, select HaltEmergency Power-Off Procedure Troubleshooting and Recovery OperationsFans Are Not Turning Components Fail When Testing the Power System Does Not Appear to Be Powered OnGreen LED Is Not Lit After POSTs Finish Recovering From a System Load Failure Info Subsys $ZZKRNRecovering From a Reload Failure Getting a Corrupt System Configuration File AnalyzedBackup $TAPE, $SYSTEM.ZSYSCONF.CONFSAVE, Listall Exiting the OSM Low-Level Link Opening Startup Event Stream and Startup Tacl Windows15-23 NonStop NS-Series Hardware Installation Guide Related Reading for Starting and Stopping a SystemCreating Startup and Shutdown Files Startup on Shutdown onAutomating System Startup and Shutdown Managed Configuration Services MCSStartup Shutdown Processes That Represent the System ConsoleFor More Information Example Command Files $ZHOME AlternativeCiin File Establishing a Ciin File Modifying a Ciin FileConftext Ciin Entry If a Ciin File Is Not Specified or Enabled in OSMCiin File Option Results Example Ciin Files Reload /TERM $ZHOME, OUT $ZHOME= Start Term Writing Efficient Startup and Shutdown Command FilesCommand File Syntax = Start Term TERM1, TERM2, TERM3, TERM4, TERM5, TERM6Avoid Manual Intervention Use Parallel ProcessingTips for Startup Files How Process Persistence Affects Configuration and StartupInvestigate Product-Specific Techniques System Startup File Startup File ExamplesObey $SYSTEM.STARTUP.STRTSYS 16-13 TMF Warm-Start File TCP/IP Stack Configuration and Startup FileSpooler Warm-Start File Obey $SYSTEM.STARTUP.SPLWARM16-15 16-16 ATP6100 Lines Startup File CP6100 Lines Startup FileLines Startup File Expand-Over-IP Line Startup File Printer Line Startup FileExpand Direct-Connect Line Startup File Tips for Shutdown Files Shutdown File ExamplesSystem Shutdown File Obey $SYSTEM.SHUTDOWN.STOPSYSATP6100 Lines Shutdown File CP6100 Lines Shutdown FileLines Shutdown File Expand-Over-IP Line Shutdown File Printer Line Shutdown FileDirect-Connect Line Shutdown File Obey $SYSTEM.SHUTDOWN.SPLDRAIN Spooler Shutdown FileTMF Shutdown File Tmfcom / in $SYSTEM.SHUTDOWN.TMFSTOP, OUT $ZHOME16-24 Checking Air Temperature and Humidity Preventive MaintenanceMonitoring Physical Facilities Cleaning System Components Cleaning Tape Drives Handling and Storing Cartridge Tapes17-4 HP Integrity NonStop NS-Series Operations Guide-529869-005 Page When to Use This Appendix Tools and Utilities for OperationsDisk Compression Program Dcom Event Management Service Analyzer EmsaDisk Space Analysis Program Dsap NonStop NET/MASTER File Utility Program FUPMeasure Nskcom and the Kernel-Managed Swap Facility KmsfPathcom Subsystem Control Facility SCFWeb ViewPoint HP Tandem Advanced Command Language TaclViewPoint ViewSys Table C-1. Related Reading for Tools and Utilities page 1 Related ReadingTool Documentation Description Table C-1. Related Reading for Tools and Utilities page 2 NET/MASTER MSTable C-1. Related Reading for Tools and Utilities page 3 Management ManualRecovery Guide Table C-1. Related Reading for Tools and Utilities page 4Table C-1. Related Reading for Tools and Utilities page 5 OutputPage Converting Numbers Table D-1. Descriptions of Number Systems Overview of Numbering SystemsNumber System Base Description Binary to Decimal Binary Value Decimal ValueOctal to Decimal Octal Value Decimal Value 1375 765Hexadecimal to Decimal Hexadecimal DecimalFigure D-3. Hexadecimal to Decimal Conversion Hexadecimal Value Decimal Value HBA10 47632Step Division Quotient Remainder Decimal to BinaryResult is Decimal Value Binary Value 354 B101100010Step Division Quotient Decimal to OctalDecimal Value Octal Value Decimal Hexadecimal Decimal to HexadecimalDecimal Value Hexadecimal Value Page FCC Compliance Safety and ComplianceRegulatory Compliance Statements Canadian ComplianceStatements-2 European Union Notice Laser ComplianceSafety Caution Important Safety Information Waste Electrical and Electronic Equipment WeeeStatements-6 Port ServerNet Extender 4PSE IndexNumbers See Conftext fileDcom 10-15,B-2 FUP Nskcom B-3 Index-5 System shutdown file 16-20 TMF Lines SACs SCF B-4 commandsSpooler 16-14 Startup files Special Characters Tacl 9-22,16-5,B-5Index-8