VTL+ 'Get Well Plan' to bring all VTL Plus 1.0 and 2.0 customers to the latest LSI firmware and VTL code levels to address data inconsistencies.

Asset ID:	1-73-1022143.1
Update Date:	2010-08-05
Keywords:

Solution Type FAB (standard) Sure

Solution 1022143.1 : VTL+ 'Get Well Plan' to bring all VTL Plus 1.0 and 2.0 customers to the latest LSI firmware and VTL code levels to address data inconsistencies.

Impact

Several Sun VTL patches and Sun LSI FW upgrade (Aurora FW) have been released to stabilize the VTL products, and Sun highly recommends all VTL customers implement these fixes. Due to the fact that we are moving to the LSI recommended HBA settings (set by applying VTL patch) and enabling write cache mirroring (set manually), performance may be degraded.

However, with the Aurora FW, the decrease is not as great as with older FW. Performance numbers are not provided, as there are many variables and this number can vary greatly from account to account. If after enabling WCM, the performance drop is too great to meet customers requirements, then WCM can be disabled. But the customer MUST agree to the possible data loss risk by disabling WCM, and Backline Support will need to provide feedback to VTL engineering when this happens, ie, create Bugtraq.

Also, although this plan is highly recommended, it is not mandatory. But be aware that any future fixes and enhancements will have this "Get Well Plan" as a pre-requisite. In other words, customers must upgrade according to this plan to get any future fixes or enhancements.

Contributing Factors

Affects all VTL Plus 1.0, VTL Plus 2.0, VTL Plus 2.0 Update 1 and VTL Plus 2.0 Update 2 configurations. A complete list of affected products are listed below;

Sun StorageTek Virtual Tape Library Plus (VTL Plus) System VTL1140BASE-Z
Sun StorageTek Virtual Tape Library Plus (VTL Plus) System VTL1200BASE-Z
Sun StorageTek Virtual Tape Library Plus (VTL Plus) System VTL1202BASE-Z
Sun StorageTek Virtual Tape Library Plus (VTL Plus) System VTL2540BASE-Z
Sun StorageTek Virtual Tape Library Plus (VTL Plus) System VTL2600BASE-Z
Sun StorageTek Virtual Tape Library Plus (VTL Plus) System VTL3540BASE-Z
Sun StorageTek Virtual Tape Library Plus (VTL Plus) System VTL3600BASE-Z

Symptoms

The following Symptoms have been observed.

With write cache mirroring (WCM) disabled, there have been instances of disk array controller issues causing virtual tape data corruption.

VTL server panics occurring for no apparent reason.

VTL server throughput gradually decreasing over time.

Impending drive failures.

Root Cause

Not applicable.

Corrective Action

Workaround:

No workaround available - see Resolution section below.

Resolution:

Sun Local support should work with all contracted customers to implement "Get Well Plan" (GWP) by verifying prerequisites are completed and then applying the steps outlined in the GWP Readme.

Refer to the README.txt and Array FW upgrade doc 820-7197-10-CM1UUG.pdf, provided in the code bundle on the USR via below link for more details (use "Get Well" for search);

https://dlrequest-zn-dlapps1.sfbay.sun.com/usr/search

Identification of Affected Parts (how to):

http://sdpsweb.central/FIN_FCO/FAB/276890/SPE/Get_Well_Plan_Matrix.xls

For information about FAB documents, its release processes, implementation strategies and billing information, go to the following URL:

http://tns.central/fab

For Sun Authorized Service Providers go to:

http://tns.central/SPE/fab/

In addition to the above you may email:

FAB-Manager@sun.com

Modification History
Changes made since initial publication.

15-Mar-2010:

Rewrote Symptoms and Resolution sections for clarity.

Internal Contributor/submitter
Bob.Schultz@Sun.COM, Dan.Spratt@Sun.COM

Internal Eng Responsible Engineer
Michael.Bondurant@Sun.COM Responsible Manager: Michael.P.Williams@Sun.COM

Internal Services Knowledge Engineer
Joe.Davis@Sun.COM

Internal Eng Business Unit Group
NWS (Network Storage)

Internal Sun Alert & FAB Admin Info
03-Feb-2010: Completed draft and sent to Extended Review.
05-Feb-2010: All feedback from Ext Rvw, sending to Publish.

Attachments

This solution has no attachment