Manuals / HP / Computer Equipment / Network Card

HP NonStop NS Identifying Tape Drive Problems, Monitoring the Status of Labeled-Tape Operations

Models: NonStop NS

1 266

Download 266 pages 1.32 Kb

Page 157

Tape Drives: Monitoring and Recovery

Monitoring the Status of Labeled-Tape Operations

Monitoring the Status of Labeled-Tape Operations

Use the MEDIACOM STATUS TAPEDRIVE and STATUS TAPEMOUNT commands to determine the current status of labeled-tape operations on your system.

For additional information about MEDIACOM, the listings it generates, and the tasks it enables you to perform:

•

•

•

DSM/Tape Catalog Operator Interface (MEDIACOM) Manual

DSM/Tape Catalog User’s Guide

Guardian User’s Guide

Identifying Tape Drive Problems

Table 11-1 lists some of the most common tape drive problems and their possible causes. Additionally, OSM alarm repair actions, degraded attribute values, and EMS event details can help you determine the appropriate cause of action

Table 11-1. Common Tape Drive Problems

Symptom	Problem	Possible Causes

File-system error	A security violation has	An attempted operation was not
48	occurred.	allowed.

File-system error	Various	An unexpired labeled tape was used.
49

File-system error	A runaway tape has been	The system has tried to read a blank
51	detected.	tape.

File-system error	Various	A hardware failure has occurred, or
66		the tape drive has been purposely
		brought down.

File-system error	A device is not ready.	A tape drive has been brought down,
100		or the drive is not online.

File-system error	An operation requires use of	$ZSVR has been purposely stopped.
195	$ZSVR, but it is not running.
	Tape operation is not allowed.

File-system error	An interrupt timeout occurs. An	A ServerNet addressable controller
218	I/O process cannot	(SAC) has failed.
	communicate with a tape drive.

No error	A tape label record is missing	An attempt was made to access a
	or incorrect.	tape with a missing or incorrect label.

No error	A tape fails to respond to a	A tape with an inappropriate label
	BACKUP command.	type was mounted in error.

No error	A tape continues to spin	The load point has fallen off.
	beyond the load point.

No error	Every time a tape is mounted, it	A labeled tape is being mounted in a
	is unloaded.	drive that is open for unlabeled use.

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

11-7

Image 157

HP NonStop NS manual Identifying Tape Drive Problems, Monitoring the Status of Labeled-Tape Operations

Contents

Abstract Product Version Supported Release Version Updates RVUsPart 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 SaveabendEnter RUN Code Notation for MessagesCode 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 Facts Possible Causes Problem-Solving WorksheetSituation 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 DocumentationLogging On to an Integrity NonStop Server Task 4 Prevent Future ProblemsSystem 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 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 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 Functions of Monitoring Working With a Daily ChecklistMonitoring 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 Additional Monitoring Tasks Daily Tasks ChecklistGeneral 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 page 1 SCF Object StatesState 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 Status LEDs and Their Functions page 1 Using the Status LEDs to Monitor the SystemLocation 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 MessagesTypes of Processes Processes Monitoring RecoverySystem 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 Supported for the subsystem manager processes Recovery Operations for 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 Related Reading for Communications Lines and Devices page 1 Recovery Operations for Communications SubsystemsFor 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 ConnectivityMonitoring the Status of the ServerNet Fabrics System I/O ServerNet ConnectionsIntegrity 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 Fibre Channel ServerNet Adapter Fcsa Adapters and ModulesGigabit Ethernet 4-Port Adapter G4SA Port ServerNet Extender 4PSE Monitoring I/O Adapters and ModulesSCF Status Adapter $ZZSTO.#FCSA*, Detail Monitoring the FCSAsState 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 ProcessorsReloading 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 Noswitch Noswitch Primenoprime fabric Omitblade ABCPrimenoprime FabricSelect Reload, click Perform action Using the OSM Service Connection to Perform ReloadRecovery 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 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 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 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, DetailPossible Causes of Common Disk Drive Problems Identifying 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 $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 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 terminalMediacom Status Tapedrive Monitoring Tape Drive Status With MediacomMediacom 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 DrivesSCF Command Description Recovery Operations Using SCFRelated 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 Monitoring TMF Applications Monitoring and RecoveryTMF 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 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 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 Stopping Application, Devices, and Processes Minimizing the Frequency of Planned OutagesAnticipating 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 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 Info Subsys $ZZKRN Recovering From a System Load FailureRecovering From a Reload Failure Getting a Corrupt System Configuration File AnalyzedBackup $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 FilesAutomating System Startup and Shutdown Managed Configuration Services MCSStartup Shutdown Processes That Represent the System ConsoleFor More Information $ZHOME Alternative Example Command FilesCiin File Modifying a Ciin File Establishing a Ciin FileConftext Ciin Entry If a Ciin File Is Not Specified or Enabled in OSMCiin 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 InterventionTips for Startup Files How Process Persistence Affects Configuration and StartupInvestigate Product-Specific Techniques System Startup File Startup File ExamplesObey $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 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 Shutdown File Examples Tips for Shutdown FilesObey $SYSTEM.SHUTDOWN.STOPSYS System Shutdown FileATP6100 Lines Shutdown File CP6100 Lines Shutdown FileLines Shutdown File Expand-Over-IP Line Shutdown File Printer Line Shutdown FileDirect-Connect Line Shutdown File TMF Shutdown File Spooler Shutdown FileObey $SYSTEM.SHUTDOWN.SPLDRAIN Tmfcom / in $SYSTEM.SHUTDOWN.TMFSTOP, OUT $ZHOME16-24 Checking Air Temperature and Humidity Preventive MaintenanceMonitoring 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 AppendixDisk Compression Program Dcom Event Management Service Analyzer EmsaDisk Space Analysis Program Dsap Measure File Utility Program FUPNonStop NET/MASTER Nskcom and the Kernel-Managed Swap Facility KmsfSubsystem Control Facility SCF PathcomWeb ViewPoint HP Tandem Advanced Command Language TaclViewPoint ViewSys Table C-1. Related Reading for Tools and Utilities page 1 Related ReadingTool 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 Table D-1. Descriptions of Number Systems Overview of Numbering 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 B101100010Step Division Quotient Decimal to OctalDecimal Value Octal Value Decimal Hexadecimal Decimal to 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 System shutdown file 16-20 TMF Lines SACs SCF B-4 commandsSpooler 16-14 Startup files Tacl 9-22,16-5,B-5 Special CharactersIndex-8