Users Guide

• Veries the encryption environment.
• Does not require special device drivers.
• Is available for most major platforms.
Note: Be sure that you have the most current version of ITDT if you are updating rmware on a recent
drive type. Before ITDT is used, verify that your library host operating system is at the current released
level. This action ensures optimum read/write operations for diagnostic tests.
Event codes
Events are used in the library Ticket and Event system to store all types of events with a unique event
code and event description.
Event Reporting System
These event codes are shown on the user interfaces as the resulting code for any type of event at the
highest level of information. No internal error code is shown at this level.
Events are sent by the library to different recipients like SNMP targets or email notication. These events
have a common structure and unique codes for every type of event.
The event code system is used for the following events:
• Error event (2XXX)
• Warning event (4XXX)
• Conguration event (8XXX)
• Informational event (9XXX)
Event code structure
Example event code
Event: 2057 - Robotics shipping lock in incorrect position
The event log with the library also includes a date and time stamp for each event. Press the associated
time stamp to see the event code and a description of the event. The date and time format can be
changed in the Date/Time Format section in the Management GUI.
• mm.dd.yyyy
• dd.mm.yyyy
• yyyy.mm.dd
The time format can be set for 12 hours or 24 hours.
• 12 hour: hh.mm.ss am/pm
• 24 hour: hh.mm.ss
Where
• yyyy is the year.
• mm is the month.
• dd is the current day.
• hh is hours.
• mm is minutes.
• ss is seconds.
Chapter 5. Troubleshooting
81