VTL - FCP-2 (FCT) is enabled but not supported in Oracle VTL's.

Asset ID:	1-72-1350227.1
Update Date:	2016-02-25
Keywords:

Solution Type Problem Resolution Sure

Solution 1350227.1 : VTL - FCP-2 (FCT) is enabled but not supported in Oracle VTL's.

Applies to:

Sun StorageTek VTL Plus Storage Appliance - Version 1.0 - Build 1323 to 2.0 - Build 1656 [Release 1.0 to 2.0]
Sun StorageTek VTL Prime System - Version 1.0 - Build 1813 to 1.1 - Build 2076 [Release 1.0]
Oracle Solaris on x86-64 (64-bit)
FCP-2 (Fibre Channel Protocol for SCSI, second version) is enabled but not supported in Oracle-Sun VTL's. This creates a problem whereby a Tape Backup application can request FCP-2 usage with a VTL to correct for SAN error anomalies and believe that it is working correctly when, in fact, it is not. This could further create a situation where data is believed to have been written to virtual tape but has not.

Also referred to as FCT or FC Tape support (Fibre Channel Tape support)

Symptoms

Look for SRR_ in the messages log. Below is an example:
Apr 27 09:39:05 xxxxxxxx fsqltgt: [ID 636730 kern.notice] <<<>>>>
Apr 27 09:39:05 xxxxxxxx qla2x00fs: [ID 359633 kern.info] fffffe800054dc80 qla(1): [CTIO_24xx_TYPE] received with status SRR_RECV!
Apr 27 09:39:05 xxxxxxxx qla2x00fs: [ID 387086 kern.notice] DOING SRR [FALC_SRR_ctio_24xx_sg_iocb] scsi(1): RQ[ffffffffb472c040][recv_exch_addr:00120ed0] SRR_QUEUE[OX_ID: 0580, IU: 0007, ROFF: 00000000] index[52] seg_cnt[0]

Changes

Changes to the SAN infrastructure. It is possible that the cause is not actually seen by switch error reporting, and only seen by a Fibre Channel analyzer.

Cause

FCP-2 (Fibre Channel Protocol for SCSI, second version) is enabled but not supported in Oracle-Sun VTL's.

Solution

The permanent solution is to update to the Get Well Plan for you current build. Please see internal reference document. If you do not have access please contact your local field support organization.

A temporary solution may be utilized for emergency use only if performed by Oracle field engineers only. @That fix is below:

1) Edit the /kernel/drv/qla2x00fs.conf file.
2) Go to the line containing "hba0-fc-tape=1;"
3) Change "hba0-fc-tape=1;" to "hba0-fc-tape=0;"
4) Save
5) After suspending failover (where appropriate), reboot.

Attachments

This solution has no attachment