Sun StorageTek SL3000 Modular Library System
 

PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: TAPE-CAP VCAP
 

In this Document

Goal

Solution

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: FRU CAP

Applies to:

Goal

How to Upgrade Microcode in SL3000 Library:ATR:1363544.1:2

Solution

DISPATCH INSTRUCTIONS
- WHAT SKILLS DOES THE ENGINEER NEED:
Oracle/Storagetek SL3000 Product Knowledge.

TASK COMPLEXITY: 2

TIME ESTIMATE: 120 minutes

For each additional library, firmware upgrade will need 1 additional hour. i.e. 1 library = 120 minutes, 2 libraries =180 minutes, 3 libraries = 240 minutes, etc.

FIELD ENGINEER INSTRUCTIONS:
- PROBLEM OVERVIEW
Firmware upgrade needed on SL3000 library.

- WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE
RESOLUTION ACTIVITY?
There are 3 parts to a code upgrade process.. Loading/Unpacking the code to the library can be done with the library online... Activating can be done while the library is still online but rebooting after the activation will require that the library be offline to the host.

- WHAT ACTION DOES THE ENGINEER NEED TO TAKE:
Acquire current level of firmware from: https://sac.us.oracle.com/download/index.html
-Upgrade library firmware using Install instructions included in the firmware release notes. Failure to do so will greatly increase your chances of an unsuccessful code upgrade activity.

Following information comes from the microcode release notes/instructions:

Loading code to the SL3000 is done from versions 3.0 and above using the StreamLine Library Console (SLC; remote and web launch versions only).

NOTE:
The loading, unpacking, and activation phases of the code load can be performed non-disruptively. However, to avoid possible mount cleanup and recovery actions after the reboot phase, it is highly recommended to vary “Offline” all drives in the library, before the library reboot. The drives have been reported as being affected by the HBT card reboot and this is particularly true for all RTD drives connected to VSM. Additionally, it is highly recommended that the ACS be varied “Offline” from all SCSI hosts, ACSLS and/or HSC for the duration of the reboot.

Non RE Instructions.
1. IMPORTANT FIRST STEP BEFORE UPGRADE:
- Prior to updating the code, using the CLI network print command to determine if the netmask is set. If not, you MUST set the netmask BEFORE upgrading to 3.00+. (Note CLI must be used, not SLConsole to determine if the netmask is set.)
Contact your network administrator for the correct netmask should you need to configure it.
2. Load and Unpack the Code
- Loading code is non-disruptive and can be done while host jobs are in progress.
- There are 2 steps to code load – load code and unpack code:
- Load code puts the firmware archive file (*.jar) into flash memory on the HBCR card.
- Unpack (similar to unzip) puts the archive file into individual files in flash memory on HBCR
- Approximate time – 10 minutes, +/- 5 minutes
3. Activate Code
- Code activation is also non-disruptive and can be done while host jobs are in progress.
- Code activation pushes code from flash memory onto the HBCR and HBT cards..
- Caution!!!!:
Do not open the door or power-cycle the SL3000 or Robots during this phase, or potential damage can be done to the PCB/PWAs (i.e. HBCR, HBT, HBB).
- Note:
Detailed status of which file is being updated, which device is being updated, and status (i.e. successful, failed, skipped) is provided on SLConsole during entire activation process. Please observe!
- Approximate time – 45 minutes, +/- 15 minutes.
4. Reboot
- The library and drives should be taken “Offline” via the control path before pressing the reboot button. Please see the note above at the start of the Code Download section of this document for more details.
- Reboot is the final step of loading new code. New code is now in flash memory on all SL3000 cards, but is not running until after the reboot.
- Host jobs should be quiesced prior to rebooting the library.
- Approximate time – 10 minutes, (IF the front access doors have not been opened. Otherwise, a full audit is automatically triggered, which can take 20 to 60 minutes, depending on the number of tape cartridges in the SL3000).
5. Re-login to SLC
- Robots may show not installed at this time. Continue on, as the second reboot (step 7 below) will correct the issue.
6. Load and Unpack the Code again
- This is necessary to extract missing manifest signature files.
7. Activate the 3.00 code again
- In this second pass, you will verify that all files are skipped.
8. Reboot again
- This is necessary because another load/unpack will not be allowed unless the system has been rebooted.

Note:
After this procedure is complete, only one level of code, the lnew one, will be left on the machine.
Additional Notes:
To return to the previous code level, the CSE must load and unpack that level of code.

II. Instructions for upgrading from non-Redundant Electronics 2.05+ code levels to a Redundant Electronic (RE) code level and add cards.
NOTE: Upgrade to a Redundant Electronic library is DISRUPTIVE. Thus, Host jobs should be quiesced prior to upgrading the library.

1. IMPORTANT FIRST STEP BEFORE UPGRADE:
- Prior to updating the code, using the CLI network print command to determine if the netmask is set. If not, you MUST set the netmask BEFORE upgrading. (Note CLI must be used, not SLConsole to determine if the netmask is set.)
Contact your network administrator for the correct netmask.
2. Ensure the B slot HBC/HBT cards are NOT present in the library.
- If they are present, they should be ejected via CLI command and then physically removed before starting this procedure.
3. Load and Unpack the Code
- Loading code is non-disruptive and can be done while host jobs are in progress.
- There are 2 steps to code load – load code and unpack code:
- Loads firmware archive file (*.jar) into flash memory on the HBCR card.
- Unpack (similar to unzip)puts the archive file into individual files in flash memory on HBC
- Approximate time – 10 minutes, +/- 5 minutes
4. Activate Code
- Code activation pushes code from flash memory onto the HBCR and HBT.
- Note: detailed status of which file is being updated, which device is being updated, and status (i.e. successful, failed, skipped) is provided on SLC during entire activation process. Please observe!
- Approximate time – 45 minutes, +/- 15 minutes.
5. Reboot
- Reboot is the final step of loading new code. New code is now in flash memory on all SL3000 cards, but is not running until after the reboot.
- Approximate time – 20 minutes. (Leave library door open at this time.)
6. Your SLC session will time out... Re-login to SLC
7. After the robots finish the audit you can reseat the Standby HBCR and HBT cards

Note:
After this procedure is complete, only one level of code, the new one, will be left on the machine.
Additional Notes:
To return to the previous code level, the CSE must load and unpack that level of code.
12. To add the second set of cards in the B slots, follow the instructions included with the RE installation kit to finish the installation and configuration.


OBTAIN CUSTOMER ACCEPTANCE
- WHAT ACTION DOES THE CUSTOMER NEED TO TAKE TO RETURN THE SYSTEM TO
AN OPERATIONAL STATE:
Application should have library and drives in an online state. Customer should perform a backup to confirm proper operation.

REFERENCE INFORMATION:
SL3000 - Downgrading Firmware to a Release Prior to 3.00 May Cause Licensed Features to be Lost (Doc ID 1319429.1).
SL3000 - Feature License Expiring Notification (Doc ID 1131384.1)
SL500/SL3000/SL8500 - E-Delivery Hardware Activation Information (Doc ID 1299169.1)

This solution has no attachment