Manuals / HP / Computer Equipment / Network Card

HP NonStop NS manual OSM Monitoring Tape Drives Connected to an Fcsa

Models: NonStop NS

1 266

Download 266 pages 1.32 Kb

Page 153

Tape Drives: Monitoring and Recovery

Monitoring Tape Drive Status With OSM

Figure 11-1. OSM: Monitoring Tape Drives Connected to an FCSA

VST316.vsd

4. If an alarm or degraded conditions exist, the tape drive probably requires either:

•

•

Operator intervention. For more information, see Recovery Operations for Tape Drives on page 11-8.

Service or replacement. Contact your service provider and refer to the Support and Service Library on page 1-12for the replacement procedure.

An alternative (to the method described above) for monitoring tape drives in OSM is to use the Multi-Resource Actions dialog box (available from the Display menu). In this dialog box, select the Tape Drive object to see a list of all tape drives on the system, along with their attribute values. From this list, you can:

•

•

•

Sort by column headings

View Alarms (for tape drives displaying a bell-shaped alarm icon) by right-clicking on the tape drive and selecting Alarms.

Perform actions on one or more tape drives (as described in Recovery Operations Using the OSM Service Connection on page 11-8)

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

11-3

Image 153

HP NonStop NS manual OSM Monitoring Tape Drives Connected to an Fcsa

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-3 10-210-4 10-511-2 11-111-5 11-8Power Failures Preparation and Recovery 15-20 15-1915-21 15-22Preventive Maintenance Related Reading Converting Numbers Figures ExamplesTables Manual Information What’s New in This ManualNew and Changed Information Document HistoryXiv Who Should Use This Guide About This GuideConverting Numbers What Is in This GuideServerNet Cluster Manual Where to Get More InformationNotation Conventions Support and Service LibraryHypertext Links General Syntax NotationInterrupts MaxattachAllowsu on OFF Inspect OFF on SaveabendNotation for Messages Enter RUN CodeCode Received Event number = number Subject = first-subject-value Backup UpProc-nametrapped in SQL in SQL file system OperatorChange Bar Notation Introduction to Integrity NonStop NS-Series Operations Monitoring the System and Performing Recovery Operations When to Use This SectionUnderstanding the Operational Environment What Are the Operator Tasks?Stopping and Powering Off the System Preparing for and Recovering from Power FailuresPowering On and Starting the System Performing Preventive MaintenanceResponding to Spooler Problems Determining the Cause of a Problem a Systematic ApproachProblem-Solving Worksheet Updating FirmwareProblem-Solving Worksheet Problem Facts Possible CausesSituation Facts Escalation Decision Task 1 Get the Facts Task 1a Determine the Facts About the ProblemTask 1b Determine the Facts About the Situation Category Questions to AskTask 2a Identify the Most Likely Cause Task 2 Find and Eliminate the Cause of the ProblemTask 3 Escalate the Problem If Necessary Task 2b Fix the Most Probable Cause of the ProblemTask 3a Determine Whether You Need to Escalate the Problem Task 3b Provide DocumentationTask 4 Prevent Future Problems Logging On to an Integrity NonStop ServerSystem Consoles Opening a Tacl Window Directly From OutsideView Opening a Tacl WindowOpening a Tacl Window From the Low-Level Link Select StartProgramsOutsideView32Launching OSM Applications Overview of OSM ApplicationsService Procedures Determining Your System Configuration Integrity NonStop NS16000 Systems Modular Hardware ComponentsIntegrity NonStop NS1000 Systems Integrity NonStop NS14000 SystemsTerms Used to Describe System Hardware Components Recording Your System ConfigurationDevice System Resource or ObjectUsing 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 TCP/IP Subsystem Displaying SCF Configuration Information for SubsystemsSCF Assume Process $ZTCO Displaying Information for the TCP/IP Subsystem $ZTCOStorage Subsystem Kernel SubsystemSCF Assume Process $ZZKRN Displaying Information for the Kernel Subsystem $ZZKRNInfo Disk $SYSTEM,OBEYFORM Example 2-2. SCF ADD Disk Command OutputMirrorlocation 11,1,12 CbpoollenADD Adapter $ZZLAN.E0154 Location Type G4SA Accesslist ServerNet LAN Systems Access Slsa SubsystemInfo Tape $*,OBEYFORM SCF Assume Process $ZZLANAdditional Subsystems Controlled by SCF WAN SubsystemDisplaying Information for the WAN Subsystem $ZZWAN Subsystem Objects Controlled by SCF page 1X25AM Subsystem Objects Controlled by SCF page 2Example 2-3. SCF Info Process Command Output Displaying Configuration Information-SCF ExamplesExample 2-4. SCF Info SAC Command Output Info Proc $ZZKRN.#Example 2-6. SCF Info Line Command Output Example 2-5. SCF Info Process $ZZWAN Command OutputInfo Process $ZZWAN Info Line $line-name, DetailOverview 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 Using OSM to Monitor the System Monitoring and Resolving Problems-An ApproachUsing the OSM Service Connection Top-Down ApproachOSM 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 SummariesSuppressing Problems and Alarms Using SCF to Monitor the SystemRecovery Operations for Problems Detected by OSM Monitoring Problem Incident ReportsDetermining 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 2Status LEDs and Their Functions page 3 Related ReadingRelated Reading for Monitoring Task Tool For information, seeMonitoring EMS Event Messages What Is the Event Management Service EMS?Tools for Monitoring EMS Event Messages ViewPoint onViewPoint OSM Event ViewerWeb ViewPoint Related Reading for Monitoring EMS Event MessagesProcesses Monitoring Recovery Types of ProcessesSystem Processes Generic Processes Processes IOPsMonitoring System Processes Monitoring ProcessesMonitoring Generic Processes Monitoring IOPsMonitoring the Status of $ZZKRN Monitoring the Status of All Generic ProcessesCLCI-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 SupportedMonitoring the Slsa Subsystem Monitoring Communications Subsystems and Their ObjectsMonitoring the Status of an Adapter and Its Components To monitor the status of an adapterSCF Status SAC sac-name SCF Status Adapter $ZZLANSCF Status SAC $ZZLAN.G11123 SCF Status PIF pif-nameMonitoring Status for a Swan Concentrator Monitoring the WAN SubsystemSCF Status PIF $ZZLAN.G11123 SCF Status LIF $ZZLAN.L11021A , DetailSystem displays a listing similar to Monitoring Status for a Data Communications DeviceSCF Status Adapter $ZZWAN SCF Status Device $ZZWAN.#device-nameSCF Status Process $ZZWAN.#boot-process To monitor a single WANBoot process, typeMonitoring WAN Processes SCF Status Process $ZZWANMonitoring the NonStop TCP/IP Subsystem Monitoring CLIPsMonitoring the NonStop TCP/IP Process SCF Listdev TcpipMonitoring NonStop TCP/IP Subnets Monitoring NonStop TCP/IP RoutesMonitoring Line-Handler Process Status SCF Status Route $ZTCOInfo 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 Disk Due to a Fabric Failure Recovery Operations for the ServerNet FabricsRecovery Operations for a Down Path Between Processors Recovery Operations for a Down ProcessorAdapters 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 Monitoring and Maintaining Processors Monitoring Processors Automatically Using TfdsSummary, these terms describe the Nsaa processor Term DescriptionProcessor Status Display Monitoring Processor Status Using the OSM Low-Level LinkOSM Representation of Processor Complex Monitoring Processor Performance Using ViewSys Identifying Processor ProblemsProcessor or System Hangs ViewsysProcessor Halts OSM Alarms and Attribute ValuesHalt code = %nnnnnn Freeze 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 Noswitch Noswitch Primenoprime fabric Omitblade ABCPrimenoprime FabricSelect 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 Submitting Information to Your Service Provider Troubleshooting and Recovery Operations for Disk DumpsBacking Up a Processor Dump to Tape Replacing Processor MemoryOther Files to Submit to Your Service Provider Submitting Tapes of Configuration and Operations FilesBackup $tape, CPU0,$SYSTEM.SYS00.CONFTEXT Submitting Tapes of Processor DumpsAdditional 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 SCFTo display the status of the disk $DATA01 Status Disk $DATA09, DetailStatus $DATA01 Status $DATA02-MStatus Disk $ To display the status of all disksStatus $DATA01, Detail To display the detailed status of the disk $DATA01To display status of all paths for $DATA00 Status Disk $DATA00Primary and Backup Path States for Disk Drives Monitoring the Use of Space on a Disk VolumeMonitoring the State of Disk Drives Monitoring the Size of Database FilesExample Monitoring Disk Configuration and PerformanceTo check the size of the file DATA1.MEMOS FUP Info DATA1.MEMOS, DetailIdentifying Disk Drive Problems Possible Causes of Common Disk Drive ProblemsProblems Possible Symptoms These SCF commands control Disk objects Recovery Operations for Disk DrivesCommon Recovery Operations for Disk Drives page 1 Command DescriptionCustomer Support Center or your service provider Common Recovery Operations for Disk Drives page 2Reset Disk $volume Recovery Operations for a Down Disk or Down Disk PathReset Disk $WD8 Start Disk $volumeRecovery 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 similar to this one is sent to your home terminal Monitoring Tape Drive Status With SCFSCF Status Tape $TAPE0 Listing such as this one is sent to your home terminalMonitoring Tape Drive Status With Mediacom Mediacom Status TapedriveMediacom Status Tapedrive $TAPE0 Common Tape Drive Problems Identifying Tape Drive ProblemsSymptom Problem Possible Causes Monitoring the Status of Labeled-Tape OperationsRecovery Operations Using the OSM Service Connection Recovery Operations for Tape DrivesPerforming an OSM Action on a Tape Drive Performing an OSM Action on a Multiple Tape DrivesRecovery 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 RecoveryMonitoring Printer Status Monitoring Printer and Collector Process StatusMonitoring Collector Process Status Spoolcom DEV $LASERRecovery Operations for a Full Collector Process Recovery Operations for Printers and Terminals12-4 Applications Monitoring and Recovery Monitoring TMFTMF States on Monitoring the Status of TMF Monitoring Data VolumesTmfcom ~ Status TMFTmfcom responds with output similar to TMF StatesTMF subsystem can be in any of the states listed in Table TMF States page 1TMF States page 2 Monitoring the Status of PathwayStatus *, Prog $*.*.PATHMON = Status PathwayPathmon 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 RecoveryNonStop NS-Series Cabinets Modular Cabinets System Response to Power FailuresNonStop S-Series I/O Enclosures External DevicesConfigure OSM Power Fail Support Preparing for Power FailureESS Cabinets Air ConditioningMonitor Power Supplies Power Failure RecoveryMonitor Batteries Maintain BatteriesSetting System Time Procedure to Recover From a Power Failure14-6 Alerts on Starting and Stopping the SystemPowering On a System Powering On the System From a No Power State Powering On the System From a Low Power StateSelect Power On System Select Hard Reset Click Perform Action15-4 Loading the System Starting a SystemAlerts Normal System LoadSystem Load Disks System Load to a Specific ProcessorSystem Load Paths in Order of Use System Load Paths for a Normal System LoadDisk Drive Enclosure Path Group Module SlotData Travels Configuration FilePerforming a System Load Starting Other System ComponentsClick Start system System Load Dialog BoxPerforming a System Load From a Specific Processor Reloading Processors Using OSM Reloading Processors Using the Reload CommandReloading Processors Reload 01 15, PrimeLogical Processor Reload Parameters Minimizing the Frequency of Planned Outages Stopping Application, Devices, and ProcessesAnticipating and Planning for Change Volume $DSMSCM.ZDSMSCM = SHUTDOWN2, Mode OrderlyStop DSM/SCM RUN StopscmStopping the System Halting All Processors Using OSMSpoolcom supervisor-name, SPOOLER, Drain Tmfcom Stop TMFSystem Power-Off Using OSM Powering Off a SystemSystem Power-Off Using SCF From the Processors Actions menu, select HaltTroubleshooting 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 FilesCommand File Syntax Writing Efficient Startup and Shutdown Command Files= Start Term = Start Term TERM1, TERM2, TERM3, TERM4, TERM5, TERM6Use 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 Spooler Warm-Start File TCP/IP Stack Configuration and Startup FileTMF Warm-Start File Obey $SYSTEM.STARTUP.SPLWARM16-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 TMF Shutdown File Spooler Shutdown FileObey $SYSTEM.SHUTDOWN.SPLDRAIN Tmfcom / in $SYSTEM.SHUTDOWN.TMFSTOP, OUT $ZHOME16-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 Measure File Utility Program FUPNonStop NET/MASTER Nskcom and the Kernel-Managed Swap Facility KmsfSubsystem 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 ConversionResult is Decimal to BinaryStep Division Quotient Remainder Decimal Value Binary Value 354 B101100010Decimal to Octal Step Division QuotientDecimal Value Octal Value Decimal to Hexadecimal Decimal HexadecimalDecimal Value Hexadecimal Value Page Regulatory Compliance Statements Safety and ComplianceFCC Compliance Canadian ComplianceStatements-2 Laser Compliance European Union NoticeSafety Caution Waste Electrical and Electronic Equipment Weee Important Safety InformationStatements-6 Numbers IndexPort ServerNet Extender 4PSE See Conftext fileDcom 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