My Oracle Support Banner

SL4000 - Library Firmware version 1.1.1.110 has been released (Doc ID 2872753.1)

Last updated on JUNE 24, 2022

Applies to:

StorageTek SL4000 Modular Library System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Details

Library Firmware version 1.1.1.110 has been released and is now available for download via MOS Patches and Updates

Patch 34146271

Actions

Under MOS Patches and Updates select the 1.1.1.110.0 version as shown below for the download. 

 

 Release Notes for 1.1.1.110.37439
---------------------------------------------------------

Release information for Oracle's StorageTek SL4000 library software version 1.1.1.110.37439.
    
WARNING: If the current library firmware version is 1.0.1.69 or less, you must first upgrade to version 1.0.2.75 or 1.0.2.76 before upgrading to version 1.1.1.110.37439

----------------------------------------
     Media Validation Enhancements
----------------------------------------
• Implemented full support of LTO Media Validation operations from the GUI by adding IBM LTO Standard and Complete Verify tests.
• Improved T10000 Media Validation.

----------------------------------------
              STA Support
----------------------------------------
• Added support for STA 2.4.0+. Refer to the STA documentation for more information: https://docs.oracle.com/en/storage/storage-software/storagetek-tape-analytics/
• Improved the SCI/OSCI interface to support STA.

----------------------------------------
           General Enhancements
----------------------------------------
• Enhanced support for IBM LTO9 Drives. See the section "Library Support of LTO9 Tape Calibration" below.
• Improved dual robot initialization:
  – If one robot fails any step of the initialization, the failed robot will be pushed out of the
    way and the library will complete the initialization.
  – Robots will be correctly identified in the GUI and logs, even if initialization fails,
    regardless of whether the database was cleared prior to initialization.
  – Improved handling of intermittent single robot failure in a two robot library with PEMs and AEMs.
  – Improved handling of robot initialization in a library with only a base after a clear database restart.
  – Improved addition, removal, and replacement of robots.
  – Since there is no library complex, the rail initialization job will no longer check the
    state of the library complex and will verify no other initialization jobs are running before initializing the rail.
• Added a library resource monitor to collect data on memory usage, load, queue sizes, etc. to aid in diagnosis of library health.
• Added support for multiple LOD2 FPGA versions: xc6slx4-2 and xc6slx4-3.
• Upgraded the following 3rd party components:
  – Apache Log4J to version 2.17.1.
  – Apache Mina’s to apache-sshd to version 2.8.0.
  – org.slf4j to version 1.7.32.
  – com.oracle.database.jdbc components to ojdbc8 version 12.2.0.1.
  – SNMP4J to version 2.8.8.
• Reduced database retention time to 15 days to minimize the size of the tables.
• Implemented a system monitor.
• Added new security algorithms for SNMP users and trap recipients.

----------------------------------------
               Bug Fixes
----------------------------------------
• Corrected a problem where some drives were not being audited after a Clean Db Restart or door open.
• The AEM CAP will now open without multiple button presses.
• The lock state of the AEM CAP is now preserved thru the use of the service key, opening then closing the AEM door.
• The AEM CAP wait LED will no longer blink if the CAP button is pressed when the AEM door is opened.
• If a robot fails during rail initialization, a fault report and associated support bundle will now always be generated.
• The sweeping robot will now back off the end stop or other robot to successfully read the frame labels.
• Corrected SNMP user recovery so the users are correctly added at boot time.
• Corrected several null pointer exceptions that caused communication issues between the library and ACSLS.

----------------------------------------
Library Support of LTO9 Tape Calibration
----------------------------------------
When LTO9 media is first loaded into the LTO9 drive, the drive automatically initiates
tape calibration, which includes initialization and characterization of the cartridge.
IMPORTANT: IBM has stated that LTO9 calibration may require 20 minutes to 2 hours
to complete.

With the 1.1.1.109 code release, the SL4000 library supports longer load times.
However, LTO9 tape calibration can well exceed these load times and limited
information is available from the library as to the status of this operation. Thus, with the
1.1.1.110 code release, library support has been modified to improve handling of tape
calibration, as follows:

Note: Contact service with any questions, especially with regard to the 1.1.1.109
code release.

• Load - When the library checks the status of the drive after a new cartridge is
  loaded, the library will report that the load is successful if the drive reports that a
  "calibration" is in process.
• Status: To determine if tape calibration is in process, access Drive Properties and
  select the Details tab. Display Characters: c indicates tape calibration is in process.
• Dismount Request: The drive ignores all requests to unload a cartridge while it is
  calibrating a tape. Thus, if a dismount request is received, the library will fail the request.
• Media Validation: Uninitialized cartridges are not currently compatible with Media Validation.
• Drive Power Cycle and Library Reboot: When a drive is power cycled while calibrating a
  tape, tape calibration resumes once drive initialization is complete. A library reboot does
  not power cycle the drive. Therefore, tape calibration continues during the library reboot.

-----------------------------------------
Minimum Requirements for Related Software
-----------------------------------------
ACSLS
• ACSLS 8.5.1+ is required to support SL4000 1.1.1.110.37439. (the feature card must also be at version 1.0.2 or higher).

STA
• STA 2.4.0+ is required to interact with SL4000 1.1.1.110.37439.

SDP
• SDP2 version 2.5.4 (Patch 33323391 or higher) is required for support of SL4000 1.1.1.110.37439 (Linux 6 and Linux 7).

----------------------------------------
               MIB Version
----------------------------------------
2.06

----------------------------------------
      LTO Drive Firmware Versions
----------------------------------------
The following LTO drive firmware versions have been verified in the SL4000 library. For the drives to work correctly,
ensure the drives are at the minimum versions specified in the table below. Lower drive firmware versions may work, but
have not been fully tested with 1.1.1.110.  For the IBM LTO drives to run in ADI mode, switch 5 must be on.

Drive Type         Drive Firmware    Encryption
HP Generation 5    I6PS              N/A
HP Generation 6    J5MS              N/A
IBM Generation 5   G360              Belisarius: 5.32.20
IBM Generation 6   JAX4              Belisarius: 5.32.20
IBM Generation 7   JAYE              LKM/D: 6.06.101
IBM Generation 8   JAYE              LKM/D: 6.06.101
IBM Generation 9   N7N0              LKM/D: 6.06.101  

----------------------------------------
      Firmware Component Versions
----------------------------------------
Component                     Version
Current Firmware Version      1.1.1.XX.YYYY
Library Platform Version      1.0.0.0.32000
WebLogic App Server Version   12.2.1.2.0 (22754279)
Oracle Clusterware Version    12.1.0.2.0
Oracle ADF Version            12.2.1.2.42.161008.1648
Database Server Version       Oracle Database 12c Release 12.1.0.1.0 - 64bit
                              Production With the Real Application Clusters and
                              Automatic Storage Management options
Database Driver Version       12.1.0.2.0
Library OS Information Linux  4.1.12-37.4.1.e16uek.x86_64 amd64
Java Runtime Version          Oracle Corporation 1.8.0_201 (64 bit)

NOTE: If the Java version does not match the version above, contact L2 support in Colorado for assistance.
This indicates that the library firmware was not updated in the correct order.

Contacts

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Details
Actions
Contacts
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.