Sun Microsystems, Inc.  Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1357772.1
Update Date:2011-09-20
Keywords:

Solution Type  Problem Resolution Sure

Solution  1357772.1 :   VTL - What do the SCSI reservation conflicts in event log or messages file mean?  


Related Items
  • Sun StorageTek VTL Prime System
  •  
  • Sun StorageTek VTL Value System
  •  
  • Sun StorageTek VTL Plus Storage Appliance
  •  
  • Sun StorageTek VTL Storage Appliance
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Virtual Tape>SN-TP: VTL
  •  
  • .Old GCS Categories>Sun Microsystems>Storage - Tape>Tape Virtualization
  •  




In this Document
  Symptoms
  Changes
  Cause
  Solution


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 Storage Appliance - Version: 4.0 - Build 1221 to 4.0 - Build 1221   [Release: 4.0 to 4.0]
Sun StorageTek VTL Prime System - Version: 1.0 - Build 1813 to 1.1 - Build 2076   [Release: 1.0 to 1.0]
Sun StorageTek VTL Value System - Version: 1.0 - Build 1323 to 1.0 - Build 1323   [Release: 1.0 to 1.0]
Oracle Solaris on x86-64 (64-bit)

Symptoms

SCSI reservation conflict on VID 10313. Requested client 10006. Reserved client 10021

Sep 12 00:13:54 VTL_1 kipstor: [ID 188213 kern.notice] IOCORE1 SCSI reservation conflict on VID 10313. Requested client 10006. Reserved client 10021.

Changes

Clients configured to share the same virtual devices

Cause

Below is an example of clients taken from the xray that share the same virtual devices.  An easy way to find this information is by opening the VTL console.

Client ID 10021 has VID 10313 reserved and client ID 10006 is trying to access the VID 10313 thus resulting in a scsi reservation conflict.  This is normal when clients share virtual devices.

Information found in the SAN Client section of the console.

1. Open up the SAN Client object, go through the clients until you locate the Client IDs displayed on the right side of the screen. 
2. Open up the Client>Fibre Channel and the Virtual Devices should be listed.  Sometime you will need to drill down a little more depending upon how the system was configured. 
3. Go through the virtual devices and find the virtual IDs obtained from the messages file.  They will be shared by the the clients having the reservation conflicts.

Client ID Client 1
Client ID Number 10021

LUN 0
Initiator WWPN 10-00-00-00-c9-71-b3-07
Target WWPN 21-00-00-1b-32-81-a1-a2
HBA # qla2x00fs_8 Adapter 9
Virtual ID 10313

Client ID Client 2
Client ID Number 10006

LUN 0 
Initiator WWPN 10-00-00-00-c9-80-91-3d 3365 
Target WWPN 21-00-00-1b-32-81-a1-a2 3365
HBA # qla2x00fs_8 Adapter 9
Virtual ID 10313

Solution


1. Configure the VTL system so that Clients are not sharing the same virtual resources.
OR
2. Adjust backup policies so that the clients that share virtual resources are not scheduled to run at the same time.

Attachments
This solution has no attachment
  Copyright © 2012 Sun Microsystems, Inc.  All rights reserved.
 Feedback