T10000C - Changes in RC362.109 Code
(Doc ID 1990604.1)
Last updated on JUNE 15, 2018
Applies to:StorageTek T10000C Tape Drive - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
Changes in RC362.109. Note that RC362.109 is the replacement for 3.62.109 code due to the fact that when a drive takes a 3F21 error, 3.62.109 code would put the drive into maintenance mode and the customer could not dismount the tape from the drive.
Fix SNO 505C for some 505C errors with new servo code change.
VSM-6 RTD performance improvement by eliminating extra Command Responses during write transfers. Replaces Special Build RA61.301.
Fix for SNO 3780 seen at multiple sites with 1.61.301 code.
Upgrade Qlogic Code to 7.03.00
Fix for SDP reported FSC 379c running w 1.61.301 code.
Fix for an STA site reported T10KC drive hang running Media Validation. Analysis of the dump showed the drive hung after encountering a prior write perm on the customer tape and therefore no EOD mark. Now, rather than hang the drive will clearly report a Media Validation failure.
Change where any STA mounts trying to rebuild a MIR on a legacy written tape (T10KA/B format tapes) on a T10KC drive - The code will now pass DSC = 0x15 along with this new FSC = 40D3.
Customer requested that 10KC drives not reset the Ethernet hardware when zero packets have been received in 60 sec. This code puts in a new VOP switch option to turn these resets OFF if that is the Customer’s desired scenario. The Factory Default setting is on (because that’s the way it has always been in prior releases of T10KC drive code). This replaces Special Build RB361101.
Fix for OAM error message CBR9103I. This replaces Special Build RD361101.
Upgrade TTI version to 5.50 level. This change supports the new library trays (Vail & Keystone) where 18 character tray serial Page 4 of 5 II - 7307886 Rev: 01
numbers comes into play. STA customers may temporarily need RA32108 special code until STA changes support TTI 5.50.
Remove SSL v3.0 for CVE-2014-3566, Poodle Vulnerability.
4.1 Drive changes since 3.62.108 Release. Note: Plus single change here in RC362109.
Fixes a serious compatibility code problem where Emulex HBA’s (4Gb or 8Gb only) could not tolerate an interface timing change introduced with Qlogic code version 7.02.00. This Qlogic bug causes jobs to fail/hang with FSC 2B5C SNO as a result tapes that are associated to File System applications such as SAM/FS will have serious positioning issues on subsequent mounts of the tape. In some instances customers have experienced data loss. In reaction to this, Oracle Engineering had to pull 3.62.108 code from the factory, MOS and the SAC using Urgent EC0023748. Note: this is resolved here by down-grading Qlogic FC code to 5.08.00 version (same as what was used in 1.61.301 code)
Fixes a serious VSM issue where - The customers were seeing ECAM error cc=5 RC=108 on blank tapes. Oracle Engineering had to pull 3.62.108 code from the factory, MOS and the SAC using Urgent EC0023748.
3.62.108 was supposed to incorporate an automatic library retry to address the intermittent 5535 load errors. A bug in that change prevented the intended library retry. This release of 3.62.109 resolves that bug and retries now completed successfully as intended.
This is a new internal drive monitoring code change where Excessive SOT events on consecutive mounts of different tape. RC362109 has one change associated to this change. The drive/s will not wait until the library puts the tape away before the drive will go down and post the 3F21 FSC. The drive/s will then need replaced..
5.0 Known Issues:
Some unknown percentage of the 36BA write perm errors attributed to physical media defect problems have not and will not be resolved in code. 36BA perm write errors that are seen with this code and higher codes indicates the tape has a defect and needs to be investigated further. It is very possible subsequent write attempts in these areas will succeed.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!