Manuals / HP / Computer Equipment / Network Card

HP NonStop NS manual System Load Paths for a Normal System Load, System Load Paths in Order of Use

Models: NonStop NS

1 266

Download 266 pages 1.32 Kb

Page 183

Starting and Stopping the System

Loading the System

You can choose these system load disks:

•An FCDM-Load attempts to load the system from a system disk in the disk drive enclosure connected to IOAM enclosure group 110:

		IOAM		FCSA	Disk Drive Enclosure
Path	Group	Module	Slot	SAC	Shelf	Bay
Primary	110	2	1	1	1	1
Backup	110	3	1	1	1	1
Mirror	110	3	1	2	1	1
Mirror Backup	110	2	1	2	1	1

•

•

•

Note. For Integrity NonStop NS14000 and NS1000 servers, Fibre Channel disks are connected to IOAMs or VIO enclosures located in group 100. For more information, see the NonStop NSxxxx Hardware Installation Manual for your Integrity NonStop NS14000 or NS1000 server, or the Versatile I/O (VIO) Manual.

A SCSI-Load attempts to load the system from a disk in group, module, slot 11.1.11 of a NonStop S-series I/O enclosure.

A load from $SYSTEM attempts to load the system from a disk in group, module, slot 11.1.11 of a NonStop S-series I/O enclosure, by default.

You can configure additional alternate system disks to load from. To create an alternate system disk, see the NonStop NSxxxx Hardware Installation Manual for your Integrity NonStop NS16000, NS14000, or NS1000 server. Then use OSM to make the disk available in the Configuration Drop-down menu in the System Load dialog box.

System Load Paths for a Normal System Load

16 paths are available for loading. Table 15-1 describes each load path in order of use. The system load task attempts to use each path until the system load is successful or all possible paths have been tried. If the system load fails along all paths, refer to Troubleshooting and Recovery Operations on page 15-18.

Table 15-1. System Load Paths in Order of Use

		Data Travels
Load Path	Description	From	To Processor	Over ServerNet Fabric
1	Primary	$SYSTEM-P	0	X
2	Primary	$SYSTEM-P	0	Y
3	Backup	$SYSTEM-P	0	X
4	Backup	$SYSTEM-P	0	Y
5	Mirror	$SYSTEM-M	0	X

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

15-7

Image 183

HP NonStop NS manual System Load Paths for a Normal System Load, System Load Paths in Order of Use, Disk Drive Enclosure

Contents

Product Version Supported Release Version Updates RVUs AbstractPart Number Published Document History Part Number Product Version Published Introduction to Integrity NonStop NS-Series Operations HP Integrity NonStop NS-Series Operations GuideDetermining Your System Configuration Monitoring EMS Event Messages ServerNet Resources Monitoring and Recovery 10-5 10-210-3 10-411-8 11-111-2 11-5Power Failures Preparation and Recovery 15-22 15-1915-20 15-21Preventive Maintenance Related Reading Converting Numbers Figures ExamplesTables Document History What’s New in This ManualManual Information New and Changed InformationXiv Who Should Use This Guide About This GuideConverting Numbers What Is in This GuideServerNet Cluster Manual Where to Get More InformationGeneral Syntax Notation Support and Service LibraryNotation Conventions Hypertext LinksInspect OFF on Saveabend MaxattachInterrupts Allowsu on OFFNotation for Messages Enter RUN CodeCode Received Operator Backup UpEvent number = number Subject = first-subject-value Proc-nametrapped in SQL in SQL file systemChange Bar Notation Introduction to Integrity NonStop NS-Series Operations What Are the Operator Tasks? When to Use This SectionMonitoring the System and Performing Recovery Operations Understanding the Operational EnvironmentPerforming Preventive Maintenance Preparing for and Recovering from Power FailuresStopping and Powering Off the System Powering On and Starting the SystemUpdating Firmware Determining the Cause of a Problem a Systematic ApproachResponding to Spooler Problems Problem-Solving WorksheetProblem-Solving Worksheet Problem Facts Possible CausesSituation Facts Escalation Decision Category Questions to Ask Task 1a Determine the Facts About the ProblemTask 1 Get the Facts Task 1b Determine the Facts About the SituationTask 2a Identify the Most Likely Cause Task 2 Find and Eliminate the Cause of the ProblemTask 3b Provide Documentation Task 2b Fix the Most Probable Cause of the ProblemTask 3 Escalate the Problem If Necessary Task 3a Determine Whether You Need to Escalate the ProblemTask 4 Prevent Future Problems Logging On to an Integrity NonStop ServerSystem Consoles Select StartProgramsOutsideView32 Opening a Tacl WindowOpening a Tacl Window Directly From OutsideView Opening a Tacl Window From the Low-Level LinkLaunching OSM Applications Overview of OSM ApplicationsService Procedures Determining Your System Configuration Integrity NonStop NS16000 Systems Modular Hardware ComponentsIntegrity NonStop NS1000 Systems Integrity NonStop NS14000 SystemsSystem Resource or Object Recording Your System ConfigurationTerms Used to Describe System Hardware Components DeviceUsing SCF to Determine Your System Configuration SCF Configuration FilesSCF System Naming Conventions Using SCF to Display Subsystem Configuration Information Save ConfigurationSCF Assume WS $L1.#TERM1 Example 2-1. SCF Listdev Command Output SCF Listdev Listing the Devices on Your SystemSCF Listdev Backup processor number and PIN of the specified device Specified deviceSubsystem Name Logical Name Device Type Description Displaying Information for the TCP/IP Subsystem $ZTCO Displaying SCF Configuration Information for SubsystemsTCP/IP Subsystem SCF Assume Process $ZTCODisplaying Information for the Kernel Subsystem $ZZKRN Kernel SubsystemStorage Subsystem SCF Assume Process $ZZKRNCbpoollen Example 2-2. SCF ADD Disk Command OutputInfo Disk $SYSTEM,OBEYFORM Mirrorlocation 11,1,12SCF Assume Process $ZZLAN ServerNet LAN Systems Access Slsa SubsystemADD Adapter $ZZLAN.E0154 Location Type G4SA Accesslist Info Tape $*,OBEYFORMSubsystem Objects Controlled by SCF page 1 WAN SubsystemAdditional Subsystems Controlled by SCF Displaying Information for the WAN Subsystem $ZZWANX25AM Subsystem Objects Controlled by SCF page 2Info Proc $ZZKRN.# Displaying Configuration Information-SCF ExamplesExample 2-3. SCF Info Process Command Output Example 2-4. SCF Info SAC Command OutputInfo Line $line-name, Detail Example 2-5. SCF Info Process $ZZWAN Command OutputExample 2-6. SCF Info Line Command Output Info Process $ZZWANOverview of Monitoring and Recovery Working With a Daily Checklist Functions of MonitoringMonitoring Tasks Task Operator’s name Date & time Tools for Checking the Status of System HardwareMonitoring System Components Monitored Using These Resource Tools SeeServerNet Cluster 6770 Hardware Daily Tasks Checklist Additional Monitoring TasksGeneral Tasks Specific Tasks For More Information, See Top-Down Approach Monitoring and Resolving Problems-An ApproachUsing OSM to Monitor the System Using the OSM Service ConnectionOSM Management System Icons Indicate Problems Within Expanding the Tree Pane to Locate the Source of Problems Attributes Tab Using System Status Icons to Monitor Multiple SystemsAlarm Summary Dialog Box Using Alarm and Problem SummariesMonitoring Problem Incident Reports Using SCF to Monitor the SystemSuppressing Problems and Alarms Recovery Operations for Problems Detected by OSMDetermining Device States Example 3-1. SCF Status Tape CommandSCF Object States SCF Object States page 1State Substate Explanation Servicing Special SCF Object States page 2Automating Routine System Monitoring Example 3-2. System Monitoring Command FileExample 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 Using the Status LEDs to Monitor the System Status LEDs and Their Functions page 1Location LED Name Color Function FC-AL I/O Status LEDs and Their Functions page 2Task Tool For information, see Related ReadingStatus LEDs and Their Functions page 3 Related Reading for MonitoringViewPoint on What Is the Event Management Service EMS?Monitoring EMS Event Messages Tools for Monitoring EMS Event MessagesRelated Reading for Monitoring EMS Event Messages OSM Event ViewerViewPoint Web ViewPointProcesses Monitoring Recovery Types of ProcessesSystem Processes Generic Processes Processes IOPsMonitoring System Processes Monitoring ProcessesMonitoring the Status of All Generic Processes Monitoring IOPsMonitoring Generic Processes Monitoring the Status of $ZZKRNCLCI-TACL $CLCI Stopped PID Recovery Operations for Processes Supported for the subsystem manager processesInitiates the operation of a generic process Communications Subsystems Communications Subsystems Monitoring and RecoveryLocal Area Networks LANs and Wide Area Networks WANs Object Connectivity By LAN Service Provider Subsystems SupportedTo monitor the status of an adapter Monitoring Communications Subsystems and Their ObjectsMonitoring the Slsa Subsystem Monitoring the Status of an Adapter and Its ComponentsSCF Status PIF pif-name SCF Status Adapter $ZZLANSCF Status SAC sac-name SCF Status SAC $ZZLAN.G11123SCF Status LIF $ZZLAN.L11021A , Detail Monitoring the WAN SubsystemMonitoring Status for a Swan Concentrator SCF Status PIF $ZZLAN.G11123SCF Status Device $ZZWAN.#device-name Monitoring Status for a Data Communications DeviceSystem displays a listing similar to SCF Status Adapter $ZZWANSCF Status Process $ZZWAN To monitor a single WANBoot process, typeSCF Status Process $ZZWAN.#boot-process Monitoring WAN ProcessesSCF Listdev Tcpip Monitoring CLIPsMonitoring the NonStop TCP/IP Subsystem Monitoring the NonStop TCP/IP ProcessSCF Status Route $ZTCO Monitoring NonStop TCP/IP RoutesMonitoring NonStop TCP/IP Subnets Monitoring Line-Handler Process StatusInfo Process $NCP, Lineset SCF Status Line $LHCS6S, DetailTracing a Communications Line Recovery Operations for Communications Subsystems Related Reading for Communications Lines and Devices page 1For Information About Refer to Related Reading for Communications Lines and Devices page 2 WAN Subsystem Configuration and Management ManualServerNet Communications Network ServerNet Resources Monitoring and RecoveryIntegrity NonStop NS16000 System Integrity NonStop NS16000 ServerNet ConnectivityIntegrity NonStop NS14000 System with Ioam Enclosure Integrity NonStop NS14000 ServerNet ConnectivitySystem I/O ServerNet Connections Monitoring the Status of the ServerNet FabricsIntegrity NonStop NS1000 ServerNet Connectivity Monitoring the ServerNet Fabrics Using OSM SCF Status Servernet $ZSNET Monitoring the ServerNet Fabrics Using SCFNormal ServerNet Fabric States Identifying ServerNet Fabric ProblemsRecovery Operations for a Down Processor Recovery Operations for the ServerNet FabricsRecovery Operations for a Down Disk Due to a Fabric Failure Recovery Operations for a Down Path Between ProcessorsAdapters and Modules Monitoring and Recovery Adapters and Modules Fibre Channel ServerNet Adapter FcsaGigabit Ethernet 4-Port Adapter G4SA Port ServerNet Extender 4PSE Monitoring I/O Adapters and ModulesMonitoring the FCSAs SCF Status Adapter $ZZSTO.#FCSA*, DetailState Description SCF Status Adapter $ZZLAN.G1123 Monitoring the G4SAsService, Device, and Enabled States for the G4SA page 1 Monitoring the 4PSEs Recovery Operations for I/O Adapters and ModulesServerNet/DA Manual Related Reading for I/O Adapters and ModulesProcessors and Components Monitoring and Recovery Overview of the NonStop Blade Complex LSU CPU Term Description Monitoring Processors Automatically Using TfdsMonitoring and Maintaining Processors Summary, these terms describe the Nsaa processorProcessor Status Display Monitoring Processor Status Using the OSM Low-Level LinkOSM Representation of Processor Complex Viewsys Identifying Processor ProblemsMonitoring Processor Performance Using ViewSys Processor or System HangsFreeze code = %nnnnnn OSM Alarms and Attribute ValuesProcessor Halts Halt code = %nnnnnnRecovery Operations for a Processor Halt Recovery Operations for ProcessorsHalting One or More Processors Reloading a Single Processor on a Running ServerSelect Processor ActionsHalt Click Perform action Using Tacl Reload to Perform Reload Select FileStart Terminal EmulatorReload / run-option , run-option Fabric Noswitch Primenoprime fabric Omitblade ABCNoswitch PrimenoprimeSelect Reload, click Perform action Using the OSM Service Connection to Perform ReloadRecovery Operations for a System Hang Freezing the System and Freeze-Enabled Processors Enabling/Disabling Processor and System FreezeDumping a Processor to Disk See Using Rcvdump to Dump a Processor to Disk on Using Rcvdump to Dump a Processor to Disk Before You BeginFUP Purgedata dumpfile Blade Element Reintegration CPU n has been dumped to dumpfileFUP Info dumpfile Replacing Processor Memory Troubleshooting and Recovery Operations for Disk DumpsSubmitting Information to Your Service Provider Backing Up a Processor Dump to TapeSubmitting Tapes of Processor Dumps Submitting Tapes of Configuration and Operations FilesOther Files to Submit to Your Service Provider Backup $tape, CPU0,$SYSTEM.SYS00.CONFTEXTAdditional Information Required by Your Service Provider For Information About Tool See Disk Drives Monitoring and Recovery Overview of Disk Drives Internal Scsi Disk DrivesFor information about M8xxx Fibre Channel Disk Drives Enterprise Storage System ESS DisksFor information about See Monitoring Disk Drives Monitoring Disk Drives With OSMTask See Status Disk $*, SUB Magnetic Monitoring Disk Drives With SCFStatus $DATA02-M Status Disk $DATA09, DetailTo display the status of the disk $DATA01 Status $DATA01Status Disk $ To display the status of all disksStatus Disk $DATA00 To display the detailed status of the disk $DATA01Status $DATA01, Detail To display status of all paths for $DATA00Monitoring the Size of Database Files Monitoring the Use of Space on a Disk VolumePrimary and Backup Path States for Disk Drives Monitoring the State of Disk DrivesFUP Info DATA1.MEMOS, Detail Monitoring Disk Configuration and PerformanceExample To check the size of the file DATA1.MEMOSIdentifying Disk Drive Problems Possible Causes of Common Disk Drive ProblemsProblems Possible Symptoms Command Description Recovery Operations for Disk DrivesThese SCF commands control Disk objects Common Recovery Operations for Disk Drives page 1Customer Support Center or your service provider Common Recovery Operations for Disk Drives page 2Start Disk $volume Recovery Operations for a Down Disk or Down Disk PathReset Disk $volume Reset Disk $WD8Recovery Operations for a Nearly Full Database File FUP Alter MEMOS, Maxextents Info MEMOS, DetailReport such as this one is sent to your home terminal 10-16 Overview of Tape Drives Tape Drives Monitoring and RecoveryMonitoring Tape Drive Status With OSM Monitoring Tape DrivesOSM Monitoring Tape Drives Connected to an Fcsa OSM Monitoring Tape Drives Connected to an IOMF2 Listing such as this one is sent to your home terminal Monitoring Tape Drive Status With SCFListing similar to this one is sent to your home terminal SCF Status Tape $TAPE0Monitoring Tape Drive Status With Mediacom Mediacom Status TapedriveMediacom Status Tapedrive $TAPE0 Monitoring the Status of Labeled-Tape Operations Identifying Tape Drive ProblemsCommon Tape Drive Problems Symptom Problem Possible CausesPerforming an OSM Action on a Multiple Tape Drives Recovery Operations for Tape DrivesRecovery Operations Using the OSM Service Connection Performing an OSM Action on a Tape DriveRecovery Operations Using SCF SCF Command DescriptionRelated Reading for Tapes and Tape Drives page 1 Related Reading for Tapes and Tape Drives page 2 Overview of Printers and Terminals Printers and Terminals Monitoring and RecoverySpoolcom DEV $LASER Monitoring Printer and Collector Process StatusMonitoring Printer Status Monitoring Collector Process StatusRecovery Operations for a Full Collector Process Recovery Operations for Printers and Terminals12-4 Applications Monitoring and Recovery Monitoring TMFTMF States on ~ Status TMF Monitoring Data VolumesMonitoring the Status of TMF TmfcomTMF States page 1 TMF StatesTmfcom responds with output similar to TMF subsystem can be in any of the states listed in Table= Status Pathway Monitoring the Status of PathwayTMF States page 2 Status *, Prog $*.*.PATHMONPathmon States Pathcom responds with output such as= Status Pathmon Request is waiting for an object that has been locked by Another requesterRequest is waiting for a RUN Program to finish ESS Cabinets on Power Failures Preparation and RecoveryExternal Devices System Response to Power FailuresNonStop NS-Series Cabinets Modular Cabinets NonStop S-Series I/O EnclosuresAir Conditioning Preparing for Power FailureConfigure OSM Power Fail Support ESS CabinetsMaintain Batteries Power Failure RecoveryMonitor Power Supplies Monitor BatteriesSetting System Time Procedure to Recover From a Power Failure14-6 Alerts on Starting and Stopping the SystemPowering On a System Select Hard Reset Click Perform Action Powering On the System From a Low Power StatePowering On the System From a No Power State Select Power On System15-4 Normal System Load Starting a SystemLoading the System AlertsSystem Load Disks System Load to a Specific ProcessorPath Group Module Slot System Load Paths for a Normal System LoadSystem Load Paths in Order of Use Disk Drive EnclosureData Travels Configuration FilePerforming a System Load Starting Other System ComponentsClick Start system System Load Dialog BoxPerforming a System Load From a Specific Processor Reload 01 15, Prime Reloading Processors Using the Reload CommandReloading Processors Using OSM Reloading ProcessorsLogical Processor Reload Parameters Minimizing the Frequency of Planned Outages Stopping Application, Devices, and ProcessesAnticipating and Planning for Change RUN Stopscm = SHUTDOWN2, Mode OrderlyVolume $DSMSCM.ZDSMSCM Stop DSM/SCMTmfcom Stop TMF Halting All Processors Using OSMStopping the System Spoolcom supervisor-name, SPOOLER, DrainFrom the Processors Actions menu, select Halt Powering Off a SystemSystem Power-Off Using OSM System Power-Off Using SCFTroubleshooting and Recovery Operations Emergency Power-Off ProcedureFans Are Not Turning System Does Not Appear to Be Powered On Components Fail When Testing the PowerGreen LED Is Not Lit After POSTs Finish Info Subsys $ZZKRN Recovering From a System Load FailureGetting a Corrupt System Configuration File Analyzed Recovering From a Reload FailureBackup $TAPE, $SYSTEM.ZSYSCONF.CONFSAVE, Listall Opening Startup Event Stream and Startup Tacl Windows Exiting the OSM Low-Level Link15-23 Related Reading for Starting and Stopping a System NonStop NS-Series Hardware Installation GuideStartup on Shutdown on Creating Startup and Shutdown FilesManaged Configuration Services MCS Automating System Startup and ShutdownStartup Processes That Represent the System Console ShutdownFor More Information $ZHOME Alternative Example Command FilesCiin File Modifying a Ciin File Establishing a Ciin FileIf a Ciin File Is Not Specified or Enabled in OSM Conftext Ciin EntryCiin File Option Results Reload /TERM $ZHOME, OUT $ZHOME Example Ciin Files= Start Term TERM1, TERM2, TERM3, TERM4, TERM5, TERM6 Writing Efficient Startup and Shutdown Command FilesCommand File Syntax = Start TermUse Parallel Processing Avoid Manual InterventionHow Process Persistence Affects Configuration and Startup Tips for Startup FilesInvestigate Product-Specific Techniques Startup File Examples System Startup FileObey $SYSTEM.STARTUP.STRTSYS 16-13 Obey $SYSTEM.STARTUP.SPLWARM TCP/IP Stack Configuration and Startup FileSpooler Warm-Start File TMF Warm-Start File16-15 16-16 CP6100 Lines Startup File ATP6100 Lines Startup FileLines Startup File Printer Line Startup File Expand-Over-IP Line Startup FileExpand Direct-Connect Line Startup File Shutdown File Examples Tips for Shutdown FilesObey $SYSTEM.SHUTDOWN.STOPSYS System Shutdown FileCP6100 Lines Shutdown File ATP6100 Lines Shutdown FileLines Shutdown File Printer Line Shutdown File Expand-Over-IP Line Shutdown FileDirect-Connect Line Shutdown File Tmfcom / in $SYSTEM.SHUTDOWN.TMFSTOP, OUT $ZHOME Spooler Shutdown FileTMF Shutdown File Obey $SYSTEM.SHUTDOWN.SPLDRAIN16-24 Preventive Maintenance Checking Air Temperature and HumidityMonitoring Physical Facilities Cleaning System Components Handling and Storing Cartridge Tapes Cleaning Tape Drives17-4 HP Integrity NonStop NS-Series Operations Guide-529869-005 Page Tools and Utilities for Operations When to Use This AppendixEvent Management Service Analyzer Emsa Disk Compression Program DcomDisk Space Analysis Program Dsap Nskcom and the Kernel-Managed Swap Facility Kmsf File Utility Program FUPMeasure NonStop NET/MASTERSubsystem Control Facility SCF PathcomHP Tandem Advanced Command Language Tacl Web ViewPointViewPoint ViewSys Related Reading Table C-1. Related Reading for Tools and Utilities page 1Tool Documentation Description NET/MASTER MS Table C-1. Related Reading for Tools and Utilities page 2Management Manual Table C-1. Related Reading for Tools and Utilities page 3Table C-1. Related Reading for Tools and Utilities page 4 Recovery GuideOutput Table C-1. Related Reading for Tools and Utilities page 5Page Converting Numbers Overview of Numbering Systems Table D-1. Descriptions of Number SystemsNumber System Base Description Binary Value Decimal Value Binary to DecimalOctal Value Decimal Value 1375 765 Octal to DecimalHexadecimal Decimal Hexadecimal to DecimalHexadecimal Value Decimal Value HBA10 47632 Figure D-3. Hexadecimal to Decimal ConversionDecimal Value Binary Value 354 B101100010 Decimal to BinaryResult is Step Division Quotient RemainderDecimal to Octal Step Division QuotientDecimal Value Octal Value Decimal to Hexadecimal Decimal HexadecimalDecimal Value Hexadecimal Value Page Canadian Compliance Safety and ComplianceRegulatory Compliance Statements FCC ComplianceStatements-2 Laser Compliance European Union NoticeSafety Caution Waste Electrical and Electronic Equipment Weee Important Safety InformationStatements-6 See Conftext file IndexNumbers Port ServerNet Extender 4PSEDcom 10-15,B-2 FUP Nskcom B-3 Index-5 SACs SCF B-4 commands System shutdown file 16-20 TMF LinesSpooler 16-14 Startup files Tacl 9-22,16-5,B-5 Special CharactersIndex-8