HP EML E-series Tape Libraries User Manual
Page 52
the library. Both platform problems and general tape drive errors display an error message or
event code on the OCP. Use the event codes listed later in this chapter to help determine a recovery
procedure.
The library depends on several other components to operate correctly. Errors that seem to be
caused by the library are often a result of issues on the host, the network cabling, or with the
application software. When troubleshooting the library, begin by ruling out these components.
Your application software may need to be reconfigured or, in some cases, reinstalled after you
have installed additional tape drives or slots into the library. Changing the number of load ports,
number of reserved slots, or type of tape drive, might require changes to software. Some application
software may require the purchase of additional add-on components or licenses when increasing
the number of storage slots or tape drives. Contact your application software provider for more
information, or if your application software does not recognize newly installed storage slots or
tape drives.
Command View TL should be the first tool used to diagnose a problem, followed by L&TT. These
two applications generally provide more detail than the OCP, but the OCP can be an aid in
determining the cause of errors. Support tickets from Command View TL or L&TT contain full log
events for all components. The OCP only shows summary information for robotic events. A support
ticket has to be generated to access the event logs.
Using the OCP, you can check the event log on the Status screen for the five most recent
informational, warning, or critical events. The last event listed on the screen is the most recent event
that occurred. Events have a date stamp, code numbers, a brief text description of the problem,
and usually a location of the module or slot where the error took place. The following is an example
of an OCP log event, and what information is included:
2005-04-06T10:07:57.068, 0.0.0.0.0, 3200, ifm, (null), error, 3000,
3312, "(re . . "
Code values are decoded with a support ticket from Command View TL and L&TT. This OCP
message decodes to:
Date/time, address, opstate, source, source, severity, activity, event ID or result, additional
information.
In this case, the opstate is Ifm is ok, the activity is Cartridge Move and result is Get Failed.
For general troubleshooting, use the following table after you isolate your problem to a category
or specific area of the library, and then go to the reference mentioned that describes a corrective
action.
Table 20 Fault isolation to a specific area
Where to find corrective action
Problem area or category
Go to
Startup problems
Go to
OCP problems
Go to
Robotics problems
Go to
Operating problems
Go to
Tape drive problems
Go to
and
Interface Manager card problems
Go to
Interface controller problems
52
Troubleshooting and event reporting