The following controls are used to alleviate certain issues with the Tape library.
Reboots the library node cards. While resetting, the library will be unable to process move commands issued by the hosts through control path drives. However, access to the data on the currently mounted drives will not be impeded.
Saves the library configuration external to the library so that it can be restored later if any corruption occurs.
The library's configuration information is stored in a database on an LCC. If there is an issue with the library's LCC or internal compact flash memory, the configuration can be restored from a saved configuration file. Otherwise, the library may need to be completely reconfigured.
Restores the library configuration using a library configuration data exported earlier. When restoring, you should restore using a file taken from this library at its current code level.
After the restore is complete, an inventory of all tiers should be run if any moves have occurred since the configuration was saved. A recalibration may be required if any hardware was serviced during this time. If an NTP server is not in use, then a reset of the library time/date may be needed as well.
Reset to factory conditions
Removes all configuration and settings of the library resetting it to the original factory shipped condition. This means that all user settings will be removed, and the library will be put into the “Not configured” state.
This action drives a reset of the library which can take up to 5-10 minutes and might require that you reconnect to the web server once complete. After the library reboots, log in using the default credentials (admin/admin) and complete the initial configuration wizard.
Resetting a drive sometimes clears transient errors seen with that drive. This can be done through the Drives or Drives by Logical Library page by clicking the “Reset” action on the selected drive.
Reset LCC node card
Resetting an LCC node card sometimes clears transient errors seen with that node card.
Export and send logs to IBM
Exporting logs can help IBM Support better establish root cause for any issues encountered
Export usage data
This command gathers usage data from all around the library including the Library Usage Data, the Library Usage Statistics, the System Summary file, Drive Usage Statistics, and Cartridge Mount History.