Sun StorageTek SL3000 Modular Library System
 
Sun StorageTek SL8500 Modular Library System
 

PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: SL3000-8500 Library
 

In this Document

Symptoms

Changes

Cause

Solution

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: adding new knowledge
Created from <SR 3-17307912891>

Applies to:

Symptoms

 ASR alert with a Result code of 3260.  Accompanying log snapshot revealed HBK has gone into Secure Key grace period countdown with XX day's left for replacement of the HBK or PUK

Changes

 Library firmware upgrade was performed

Cause

 A library upgrade or reboot was performed that initiated the updating of files to the HBK/PUK card which caused flash memory file corruption resulting in Secure Key grace period activation countdown.

Solution

On SL3000 running firmware version 4.50 or higher or SL8500 running firmware version 8.60 or higher you have the ability to re-format the HBK card.

Use the following instructions:

Once the library is running on the idcard mirror, here are some steps that can be taken to correct the problems and restore the use of the HBK card:
- Execute the CLI command hbk format.
o This command is only available when the library is running on the idcard mirror.
o The command is non-disruptive and may be executed while the library is in production.
o It can take up to 15 minutes to complete.
- Progress status is displayed during execution.
- If an error occurs during the format, a new HBK card should be ordered and a service window scheduled for card replacement.
- The customer can continue to use the library in production while running on the idcard mirror.
- No code activations can occur while the library is running on the idcard mirror.
o Once the format command is complete, the library must be rebooted to re-mount the HBK card.
- An automatic reboot after the HBK format completes was not implemented. This allows the CSE to schedule the reboot at a time that is acceptable to the customer.
- NOTE: After the format and reboot, it can take up to 10 minutes before a CLI session can be established.
o After the format has completed and the library is rebooted, the HBK card will be mounted.
- The data from the mirror will be restored to the HBK card as part of the initialization process.
If the library is not running on the mirror, but non-critical file errors have been detected, the HBK card can be cleaned up. The following steps will need to be performed:
- Execute the CLI command hbk useMirror.
o The library is set to use the mirror on the next startup.
o The library is automatically rebooted.
o The library will be running on the idcard mirror after the initialization.
- Next, the CSE will follow the steps above for the Cli hbk format command.
If the library is running on the mirror, yet there is a need to force it to run on the HBK card:
- Execute the CLI command hbk ignoreCriticalFile.
o The library will set a flag to ignore critical file errors.
o The library is automatically rebooted.
o The library will attempt to mount the HBK card.
o If the mount is successful, critical file errors will be logged.
o The library will remain on the idcard until a subsequent reboot.

If the SL3000 firmware is below 4.50 or the SL8500 is below 8.60 the HBK card will need to be replaced..

See the attached KB's for additional information regarding HBK/PUK card replacement

This solution has no attachment