Integrity NonStop NS16000 ServerNet Connectivity

ServerNet Resources: Monitoring and Recovery

ServerNet Communications Network

simultaneously to improve performance, and to ensure that no single failure disrupts communications among the remaining system components.

A ServerNet adapter provides the interface between a ServerNet fabric and the Fibre Channel and Ethernet links. A ServerNet adapter contains a ServerNet bus interface (SBI) and one or more ServerNet addressable controllers (SACs).

Integrity NonStop NS16000 ServerNet Connectivity

An Integrity NonStop NS16000 system uses the ServerNet fabric for interconnections between the LSUs, p-switches, and IOAMs, enabling an Integrity NonStop system to be connected to legacy NonStop S-series enclosures. Figure 7-1 shows a logical representation of a complete system with the X and Y ServerNet fabrics.

Figure 7-1. Integrity NonStop NS16000 System

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

7-2

Page 98

Image 98

HP manual Integrity NonStop NS16000 ServerNet Connectivity, Integrity NonStop NS16000 System

Contents

Part Number Published Product Version Supported Release Version Updates RVUsAbstract Document History Part Number Product Version Published HP Integrity NonStop NS-Series Operations Guide Introduction to Integrity NonStop NS-Series Operations Determining Your System Configuration Monitoring EMS Event Messages ServerNet Resources Monitoring and Recovery 10-4 10-210-3 10-5 11-5 11-111-2 11-8 Power Failures Preparation and Recovery 15-21 15-1915-20 15-22 Preventive Maintenance Related Reading Converting Numbers Examples Figures Tables New and Changed Information What’s New in This ManualManual Information Document History Xiv About This Guide Who Should Use This Guide What Is in This Guide Converting Numbers Where to Get More Information ServerNet Cluster Manual Hypertext Links Support and Service LibraryNotation Conventions General Syntax Notation Allowsu on OFF MaxattachInterrupts Inspect OFF on Saveabend Code Received Notation for MessagesEnter RUN Code Proc-nametrapped in SQL in SQL file system Backup UpEvent number = number Subject = first-subject-value Operator Change 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 Maintenance Problem-Solving Worksheet Determining the Cause of a Problem a Systematic ApproachResponding to Spooler Problems Updating Firmware Situation Facts Escalation Decision Problem-Solving WorksheetProblem Facts Possible Causes Task 1b Determine the Facts About the Situation Task 1a Determine the Facts About the ProblemTask 1 Get the Facts Category Questions to Ask Task 2 Find and Eliminate the Cause of the Problem Task 2a Identify the Most Likely Cause Task 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 Documentation System Consoles Task 4 Prevent Future ProblemsLogging On to an Integrity NonStop Server Opening a Tacl Window From the Low-Level Link Opening a Tacl WindowOpening a Tacl Window Directly From OutsideView Select StartProgramsOutsideView32 Overview of OSM Applications Launching OSM Applications Service Procedures Determining Your System Configuration Modular Hardware Components Integrity NonStop NS16000 Systems Integrity NonStop NS14000 Systems Integrity NonStop NS1000 Systems Device Recording Your System ConfigurationTerms Used to Describe System Hardware Components System Resource or Object SCF System Naming Conventions Using SCF to Determine Your System ConfigurationSCF Configuration Files SCF Assume WS $L1.#TERM1 Using SCF to Display Subsystem Configuration InformationSave Configuration SCF Listdev Example 2-1. SCF Listdev Command OutputSCF Listdev Listing the Devices on Your System Subsystem Name Logical Name Device Type Description Backup processor number and PIN of the specified deviceSpecified device SCF Assume Process $ZTCO Displaying SCF Configuration Information for SubsystemsTCP/IP Subsystem Displaying Information for the TCP/IP Subsystem $ZTCO SCF Assume Process $ZZKRN Kernel SubsystemStorage Subsystem Displaying Information for the Kernel Subsystem $ZZKRN Mirrorlocation 11,1,12 Example 2-2. SCF ADD Disk Command OutputInfo Disk $SYSTEM,OBEYFORM Cbpoollen Info Tape $*,OBEYFORM ServerNet LAN Systems Access Slsa SubsystemADD Adapter $ZZLAN.E0154 Location Type G4SA Accesslist SCF Assume Process $ZZLAN Displaying Information for the WAN Subsystem $ZZWAN WAN SubsystemAdditional Subsystems Controlled by SCF Subsystem Objects Controlled by SCF page 1 Subsystem Objects Controlled by SCF page 2 X25AM Example 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, Detail Overview of Monitoring and Recovery Monitoring Tasks Working With a Daily ChecklistFunctions of Monitoring Tools for Checking the Status of System Hardware Task Operator’s name Date & time Monitored Using These Resource Tools See Monitoring System Components ServerNet Cluster 6770 Hardware General Tasks Specific Tasks For More Information, See Daily Tasks ChecklistAdditional Monitoring Tasks Using the OSM Service Connection Monitoring and Resolving Problems-An ApproachUsing OSM to Monitor the System Top-Down Approach OSM 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 Tab Using Alarm and Problem Summaries Alarm Summary Dialog Box Recovery Operations for Problems Detected by OSM Using SCF to Monitor the SystemSuppressing Problems and Alarms Monitoring Problem Incident Reports Example 3-1. SCF Status Tape Command Determining Device States State Substate Explanation SCF Object StatesSCF Object States page 1 SCF Object States page 2 Servicing Special Example 3-2. System Monitoring Command File Automating Routine System Monitoring Example 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 Location LED Name Color Function Using the Status LEDs to Monitor the SystemStatus LEDs and Their Functions page 1 Status LEDs and Their Functions page 2 FC-AL I/O Related Reading for Monitoring Related ReadingStatus LEDs and Their Functions page 3 Task Tool For information, see Tools for Monitoring EMS Event Messages What Is the Event Management Service EMS?Monitoring EMS Event Messages ViewPoint on Web ViewPoint OSM Event ViewerViewPoint Related Reading for Monitoring EMS Event Messages System Processes Processes Monitoring RecoveryTypes of Processes Processes IOPs Generic Processes Monitoring Processes Monitoring System Processes Monitoring the Status of $ZZKRN Monitoring IOPsMonitoring Generic Processes Monitoring the Status of All Generic Processes CLCI-TACL $CLCI Stopped PID Initiates the operation of a generic process Recovery Operations for ProcessesSupported for the subsystem manager processes Communications Subsystems Monitoring and Recovery Communications Subsystems Local Area Networks LANs and Wide Area Networks WANs LAN Service Provider Subsystems Supported Object Connectivity By Monitoring the Status of an Adapter and Its Components Monitoring Communications Subsystems and Their ObjectsMonitoring the Slsa Subsystem To monitor the status of an adapter SCF Status SAC $ZZLAN.G11123 SCF Status Adapter $ZZLANSCF Status SAC sac-name SCF Status PIF pif-name SCF Status PIF $ZZLAN.G11123 Monitoring the WAN SubsystemMonitoring Status for a Swan Concentrator SCF Status LIF $ZZLAN.L11021A , Detail SCF Status Adapter $ZZWAN Monitoring Status for a Data Communications DeviceSystem displays a listing similar to SCF Status Device $ZZWAN.#device-name Monitoring WAN Processes To monitor a single WANBoot process, typeSCF Status Process $ZZWAN.#boot-process SCF Status Process $ZZWAN Monitoring the NonStop TCP/IP Process Monitoring CLIPsMonitoring the NonStop TCP/IP Subsystem SCF Listdev Tcpip Monitoring Line-Handler Process Status Monitoring NonStop TCP/IP RoutesMonitoring NonStop TCP/IP Subnets SCF Status Route $ZTCO SCF Status Line $LHCS6S, Detail Info Process $NCP, Lineset Tracing a Communications Line For Information About Refer to Recovery Operations for Communications SubsystemsRelated Reading for Communications Lines and Devices page 1 WAN Subsystem Configuration and Management Manual Related Reading for Communications Lines and Devices page 2 ServerNet Resources Monitoring and Recovery ServerNet Communications Network Integrity NonStop NS16000 ServerNet Connectivity Integrity NonStop NS16000 System Integrity NonStop NS14000 ServerNet Connectivity Integrity NonStop NS14000 System with Ioam Enclosure Integrity NonStop NS1000 ServerNet Connectivity System I/O ServerNet ConnectionsMonitoring the Status of the ServerNet Fabrics Monitoring the ServerNet Fabrics Using OSM Monitoring the ServerNet Fabrics Using SCF SCF Status Servernet $ZSNET Identifying ServerNet Fabric Problems Normal ServerNet Fabric States Recovery 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 Processor Adapters and Modules Monitoring and Recovery Gigabit Ethernet 4-Port Adapter G4SA Adapters and ModulesFibre Channel ServerNet Adapter Fcsa Monitoring I/O Adapters and Modules Port ServerNet Extender 4PSE State Description Monitoring the FCSAsSCF Status Adapter $ZZSTO.#FCSA*, Detail Monitoring the G4SAs SCF Status Adapter $ZZLAN.G1123 Service, Device, and Enabled States for the G4SA page 1 Recovery Operations for I/O Adapters and Modules Monitoring the 4PSEs Related Reading for I/O Adapters and Modules ServerNet/DA Manual Processors 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 Description Monitoring Processor Status Using the OSM Low-Level Link Processor Status Display OSM Representation of Processor Complex Processor or System Hangs Identifying Processor ProblemsMonitoring Processor Performance Using ViewSys Viewsys Halt code = %nnnnnn OSM Alarms and Attribute ValuesProcessor Halts Freeze code = %nnnnnn Recovery Operations for Processors Recovery Operations for a Processor Halt Select Processor ActionsHalt Click Perform action Halting One or More ProcessorsReloading a Single Processor on a Running Server Reload / run-option , run-option Using Tacl Reload to Perform ReloadSelect FileStart Terminal Emulator Primenoprime Noswitch Primenoprime fabric Omitblade ABCNoswitch Fabric Using the OSM Service Connection to Perform Reload Select Reload, click Perform action Recovery Operations for a System Hang Dumping a Processor to Disk Freezing the System and Freeze-Enabled ProcessorsEnabling/Disabling Processor and System Freeze See Using Rcvdump to Dump a Processor to Disk on FUP Purgedata dumpfile Using Rcvdump to Dump a Processor to DiskBefore You Begin FUP Info dumpfile Blade Element ReintegrationCPU n has been dumped to dumpfile Backing Up a Processor Dump to Tape Troubleshooting and Recovery Operations for Disk DumpsSubmitting Information to Your Service Provider Replacing Processor Memory Backup $tape, CPU0,$SYSTEM.SYS00.CONFTEXT Submitting Tapes of Configuration and Operations FilesOther Files to Submit to Your Service Provider Submitting Tapes of Processor Dumps Additional Information Required by Your Service Provider For Information About Tool See Disk Drives Monitoring and Recovery For information about Overview of Disk DrivesInternal Scsi Disk Drives For information about See M8xxx Fibre Channel Disk DrivesEnterprise Storage System ESS Disks Task See Monitoring Disk DrivesMonitoring Disk Drives With OSM Monitoring Disk Drives With SCF Status Disk $*, SUB Magnetic Status $DATA01 Status Disk $DATA09, DetailTo display the status of the disk $DATA01 Status $DATA02-M To 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 $DATA00 Monitoring 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 Files To check the size of the file DATA1.MEMOS Monitoring Disk Configuration and PerformanceExample FUP Info DATA1.MEMOS, Detail Problems Possible Symptoms Identifying Disk Drive ProblemsPossible Causes of Common Disk Drive Problems Common Recovery Operations for Disk Drives page 1 Recovery Operations for Disk DrivesThese SCF commands control Disk objects Command Description Common Recovery Operations for Disk Drives page 2 Customer Support Center or your service provider Reset Disk $WD8 Recovery Operations for a Down Disk or Down Disk PathReset Disk $volume Start Disk $volume Report such as this one is sent to your home terminal Recovery Operations for a Nearly Full Database FileFUP Alter MEMOS, Maxextents Info MEMOS, Detail 10-16 Tape Drives Monitoring and Recovery Overview of Tape Drives Monitoring Tape Drives Monitoring Tape Drive Status With OSM OSM 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 terminal Mediacom Status Tapedrive $TAPE0 Monitoring Tape Drive Status With MediacomMediacom Status Tapedrive Symptom Problem Possible Causes Identifying Tape Drive ProblemsCommon Tape Drive Problems Monitoring the Status of Labeled-Tape Operations Performing 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 Drives Related Reading for Tapes and Tape Drives page 1 Recovery Operations Using SCFSCF Command Description Related Reading for Tapes and Tape Drives page 2 Printers and Terminals Monitoring and Recovery Overview of Printers and Terminals Monitoring Collector Process Status Monitoring Printer and Collector Process StatusMonitoring Printer Status Spoolcom DEV $LASER Recovery Operations for Printers and Terminals Recovery Operations for a Full Collector Process 12-4 TMF States on Applications Monitoring and RecoveryMonitoring TMF Tmfcom Monitoring Data VolumesMonitoring the Status of TMF ~ Status TMF TMF subsystem can be in any of the states listed in Table TMF StatesTmfcom responds with output similar to TMF States page 1 Status *, Prog $*.*.PATHMON Monitoring the Status of PathwayTMF States page 2 = Status Pathway = Status Pathmon Pathmon StatesPathcom responds with output such as Request is waiting for a RUN Program to finish Request is waiting for an object that has been locked byAnother requester Power Failures Preparation and Recovery ESS Cabinets on NonStop S-Series I/O Enclosures System Response to Power FailuresNonStop NS-Series Cabinets Modular Cabinets External Devices ESS Cabinets Preparing for Power FailureConfigure OSM Power Fail Support Air Conditioning Monitor Batteries Power Failure RecoveryMonitor Power Supplies Maintain Batteries Procedure to Recover From a Power Failure Setting System Time 14-6 Starting and Stopping the System Alerts on Powering 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 Action 15-4 Alerts Starting a SystemLoading the System Normal System Load System Load to a Specific Processor System Load Disks Disk Drive Enclosure System Load Paths for a Normal System LoadSystem Load Paths in Order of Use Path Group Module Slot Configuration File Data Travels Starting Other System Components Performing a System Load System Load Dialog Box Click Start system Performing a System Load From a Specific Processor Reloading Processors Reloading Processors Using the Reload CommandReloading Processors Using OSM Reload 01 15, Prime Logical Processor Reload Parameters Anticipating and Planning for Change Minimizing the Frequency of Planned OutagesStopping Application, Devices, and Processes Stop DSM/SCM = SHUTDOWN2, Mode OrderlyVolume $DSMSCM.ZDSMSCM RUN Stopscm Spoolcom supervisor-name, SPOOLER, Drain Halting All Processors Using OSMStopping the System Tmfcom Stop TMF System Power-Off Using SCF Powering Off a SystemSystem Power-Off Using OSM From the Processors Actions menu, select Halt Fans Are Not Turning Troubleshooting and Recovery OperationsEmergency Power-Off Procedure Green LED Is Not Lit After POSTs Finish System Does Not Appear to Be Powered OnComponents Fail When Testing the Power Recovering From a System Load Failure Info Subsys $ZZKRN Backup $TAPE, $SYSTEM.ZSYSCONF.CONFSAVE, Listall Getting a Corrupt System Configuration File AnalyzedRecovering From a Reload Failure Exiting the OSM Low-Level Link Opening Startup Event Stream and Startup Tacl Windows 15-23 NonStop NS-Series Hardware Installation Guide Related Reading for Starting and Stopping a System Creating Startup and Shutdown Files Startup on Shutdown on Startup Managed Configuration Services MCSAutomating System Startup and Shutdown For More Information Processes That Represent the System ConsoleShutdown Example Command Files $ZHOME Alternative Ciin File Establishing a Ciin File Modifying a Ciin File Ciin File Option Results If a Ciin File Is Not Specified or Enabled in OSMConftext Ciin Entry 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, TERM6 Avoid Manual Intervention Use Parallel Processing Investigate Product-Specific Techniques How Process Persistence Affects Configuration and StartupTips for Startup Files Obey $SYSTEM.STARTUP.STRTSYS Startup File ExamplesSystem Startup File 16-13 TMF Warm-Start File TCP/IP Stack Configuration and Startup FileSpooler Warm-Start File Obey $SYSTEM.STARTUP.SPLWARM 16-15 16-16 Lines Startup File CP6100 Lines Startup FileATP6100 Lines Startup File Expand Direct-Connect Line Startup File Printer Line Startup FileExpand-Over-IP Line Startup File Tips for Shutdown Files Shutdown File Examples System Shutdown File Obey $SYSTEM.SHUTDOWN.STOPSYS Lines Shutdown File CP6100 Lines Shutdown FileATP6100 Lines Shutdown File Direct-Connect Line Shutdown File Printer Line Shutdown FileExpand-Over-IP Line Shutdown File Obey $SYSTEM.SHUTDOWN.SPLDRAIN Spooler Shutdown FileTMF Shutdown File Tmfcom / in $SYSTEM.SHUTDOWN.TMFSTOP, OUT $ZHOME 16-24 Monitoring Physical Facilities Preventive MaintenanceChecking Air Temperature and Humidity Cleaning System Components Cleaning Tape Drives Handling and Storing Cartridge Tapes 17-4 HP Integrity NonStop NS-Series Operations Guide-529869-005 Page When to Use This Appendix Tools and Utilities for Operations Disk Space Analysis Program Dsap Event Management Service Analyzer EmsaDisk Compression Program Dcom NonStop NET/MASTER File Utility Program FUPMeasure Nskcom and the Kernel-Managed Swap Facility Kmsf Pathcom Subsystem Control Facility SCF ViewPoint HP Tandem Advanced Command Language TaclWeb ViewPoint ViewSys Tool Documentation Description Related ReadingTable C-1. Related Reading for Tools and Utilities page 1 Table C-1. Related Reading for Tools and Utilities page 2 NET/MASTER MS Table C-1. Related Reading for Tools and Utilities page 3 Management Manual Recovery Guide Table C-1. Related Reading for Tools and Utilities page 4 Table C-1. Related Reading for Tools and Utilities page 5 OutputPage Converting Numbers Number System Base Description Overview of Numbering SystemsTable D-1. Descriptions of Number Systems Binary to Decimal Binary Value Decimal Value Octal to Decimal Octal Value Decimal Value 1375 765 Hexadecimal to Decimal Hexadecimal Decimal Figure D-3. Hexadecimal to Decimal Conversion Hexadecimal Value Decimal Value HBA10 47632 Step Division Quotient Remainder Decimal to BinaryResult is Decimal Value Binary Value 354 B101100010 Decimal Value Octal Value Decimal to OctalStep Division Quotient Decimal Value Hexadecimal Value Decimal to HexadecimalDecimal Hexadecimal Page FCC Compliance Safety and ComplianceRegulatory Compliance Statements Canadian Compliance Statements-2 European Union Notice Laser Compliance Safety Caution Important Safety Information Waste Electrical and Electronic Equipment Weee Statements-6 Port ServerNet Extender 4PSE IndexNumbers See Conftext file Dcom 10-15,B-2 FUP Nskcom B-3 Index-5 Spooler 16-14 Startup files SACs SCF B-4 commandsSystem shutdown file 16-20 TMF Lines Special Characters Tacl 9-22,16-5,B-5 Index-8