![]() | Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type FAB (standard) Sure Solution 1302433.1 : Solution Interface Control Check issue on T10000A/B/C Drives.
In this Document
Oracle Confidential (PARTNER). Do not distribute to customers
Applies to:StorageTek T10000C Tape Drive - Version: Not Applicable to Not Applicable - Release: N/A to N/ASun StorageTek T10000B Tape Drive - Version: Not Applicable to Not Applicable [Release: N/A to N/A] Sun StorageTek T10000A Tape Drive - Version: Not Applicable to Not Applicable [Release: N/A to N/A] Information in this document applies to any platform. __________ SUNBUG: 7022224 SymptomsIOS000I message with IFCC, SIM, MIH Timer Pop in the message. Only certain files on tapes with specific blocksizes will fail. (blocksize 8160 or any multiples of this size).Impact The customer job may fail as described above when tapes with these specific blocksizes are read. Improper CRC presentation to IBM hosts may cause IFCC, job hangs, and job abends during restore (read) operations when reading block sizes from tape that are exactly 8160 in length or a multiple of 8160 in length. This is a T10000 "read" (input) issue only. Any data on tape is not impacted and therefore should be correct and intact. The problem does not affect the 9x40 (9840 and 9940) family of drives. ChangesContributing FactorsThis problem only affects T10000A/B/C drives that are set into FICON mode. Files on tape having 8160 blocksize or multiples of 8160 blocksizes expose the problem. This is discussed further in the Symptoms and Impact sections above. IBM's channel code level "Driver 86" for FICON 8 cards have the new CRC checks that cause this issue. CauseRoot Cause:Some IBM processor channels do not correctly check for proper CRC on read operations for the 8160 (or multiples) block size. When new channel code is installed on these processor channels (that does check for proper CRC values) IFCC and job abends may occur. SolutionWorkaroundInstall special build code Re46.109 (T10KA) and Re26.209 (T10KB) to address the problem. Special build Rj46109/209 also contains this change. Special drive code builds listed above have been created for T100000A/B FICON version drives. This code is being distributed through Tape Technical Support. Special drive code builds listed above have been created for T100000A/B FICON version drives. This code is being distributed through Tape Technical Support. There is no special build for T10000C FICON drives as GA released code is available that has the needed change in it. Resolution Once this code change is GA, install the GA version. T10000C code containing this change is 1.51.318 which is targeted for GA release in April 2011. T10000A/B code target is 1.48.xxx which is currently planned for GA release in CYQ3 of 2011. Comments Tape Drive Engineering believes the exposure to this issue is generally low due to the specific and unique 8160 block size factor. Some customers will want to be proactive about installing this code change before the customer upgrades to a Z196 processor or before installing maintenance packages (MCL Bundle 46) affecting Driver 79 (for the FICON adapter) in a Z9 or Z10 processor. Some customers may choose to wait for the GA releases of T10000 drive code(s). If your equipment is installed on any Z196 processor or if the customer is running on a Z9 / Z10 processor and is considering upgrading to MCL Bundle 46 installed against Driver 79, the same options apply and need to be considered before this maintenance is installed. Contact Tape Technical Support for any questions by opening an SR under My Oracle Support to get assistance from technical support. You can also use IM/Chat to contact Tape Support. The chat room information is located at: https://tapesupport.us.oracle.com/main.shtml For information about FAB documents, its release processes, implementation strategies and billing information, go to the following (Internal Only) URL: https://sunspace.sfbay.sun.com/display/Onestop/FAB+(Field+Action+Bulletin) In addition to the above you may email: [email protected] Contacts Contributor: [email protected] Responsible Engineer: [email protected] Responsible Manager: [email protected] Business Unit Group: Network Storage Attachments This solution has no attachment |
||||||||||||
|