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-71-1008482.1
Update Date:2012-07-30
Keywords:

Solution Type  Technical Instruction Sure

Solution  1008482.1 :   L180/L700 - Impact of Drive Address Resequencing in Oracle/StorageTek L700/L180 with Veritas NetBackup  


Related Items
  • Sun StorageTek L180 Tape Library
  •  
  • Sun StorageTek L700 Tape Library
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: STK Legacy Drive and Library
  •  
  • .Old GCS Categories>Sun Microsystems>Storage - Tape>Libraries - L-Series
  •  

PreviouslyPublishedAs
211595


Applies to:

Sun StorageTek L180 Tape Library - Version: Not Applicable and later   [Release: N/A and later ]
Sun StorageTek L700 Tape Library - Version: Not Applicable and later    [Release: N/A and later]
All Platforms
Checked for relevance on 11-Jan-2012.

Goal

Impact of Drive Address Resequencing in Oracle/StorageTek L700/L180 with Veritas NetBackup.

Solution

Description
Impact of Drive Address Resequencing in Sun StorageTek L700/L180 with Veritas NetBackup
When the L700/L180 Library is powered on and an attached drive fails to initialize and does not communicate with the Library Controller the sequential addressing of the attached drives will change.

Steps to Follow
Impact of Drive Address Re-sequencing in Oracle/StorageTek L700/L180 with Veritas NetBackup
When the L700/L180 Library is powered on and an attached drive fails to initialize and does not communicate with the Library Controller the sequential addressing of the attached drives will change.
Example: Original drive 0, did not initialize properly and lost communication with the Library Controller; the original drive 1 will now became drive 0 and the remaining drives addresses will increment by one.

The Dynamic WWN assignments will not be impacted and does not get overridden by the re-sequencing of the drive addresses. Recommend customers bind the port on the switch to drive's Dynamic WWN.
Binding the switch port to the Dynamic WWN provides more flexibility in the host addressing options and greatly reduces host configuration impact of drive initialization errors and configuration changes in the advent of replacing a failed drive.

If the customer's configuration does not have a switch between the host and drive, and the drive addresses are re-sequenced it may be necessary to issue a "re-discover" command from NBU to re-address the drives.

There is also an "auto_path_correction" option in NBU but we have found inconsistent results when used with Solaris operating systems. This option seems to be more consistent when used with Linux and Window operating systems under NBU 7.0.



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