LTO Tape Drive
 
HP LTO5 Tape Drive
 
Sun StorageTek T10000 Tape Drive
 

PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: OEM Drive and Library
 

On a new installation or if DWWN is not provided by the Library, the WWN change does not get picked up by the CommVault solution for the Solaris configuration.

In this Document

Symptoms

Changes

Cause

Solution

References

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Oracle Confidential (Distribution). Do not distribute to customers.
Created from <SR 3-10595807262>

Applies to:

Symptoms

Drive 4 sn HUE41311EY, library address 0,2,2,9 did not get back a valid custom WWN from the library at some point since Port A and B are displayed with the same WWName out of the WWName base value in a Drive Details generated on : Fri Apr 10 10:15:40 CEST 2015
In addition this is the only drive in the library with FW version I67S. All other drives FW is I6BS.


Device Id : 0,2,2,9
  
  General
  Drive Type : HpUltrium5
  Code Version : I67S/017.929
  Vendor : HP
  Serial Number : HUE41311EY
  Interface Type : Fibre
  Tray Serial Number : SN 578000206780
  Drive Configuration ***THE DRIVE MUST BE IN A CONFIGURABLE STATE***
  LVD Target ID : n/a
  World Wide Name Node : 50:01:43:80:26:69:c4:16
  Port A World Wide Name : 50:01:43:80:26:69:c4:14
  Port A Enabled : true
  Port A Loop ID (use 126 for soft addressing) : 126
  Port A Speed (GB) : 4
  Port A Link Status : Initialized
  Port B World Wide Name : 50:01:43:80:26:69:c4:14
  Port B Enabled : false
  Port B Loop ID (use 126 for soft addressing) : 126
  Port B Speed (GB) : Auto
  Port B Link Status : Uninitialized

One other thing I noticed in the Library Information is there is a pending change needing a reboot to take effect. Don't even know what change this is but a reboot is needed to clear this with the fact it will take any pending change into effect.

Library Host Interface *** REBOOT LIBRARY FOR CHANGES TO TAKE AFFECT ***

There are three different sn for drive 4 in the mapping history. sn HUE41311EY that got the wrong customer WWName has a mapping date of April 09th 12:22:26. There is some matching events in the library log related to this drive 4 (but not only this one) having trouble on the TTI interface.


Version 1.0
  1, 2010-02-13T12:10:12, 0.1.1.9, HUL4B05593
  1, 2010-03-08T04:07:17, 0.1.1.9, HU1202LEKV
  2, 2010-03-08T04:07:17, 0.1.2.9, HU1202LEKY
  3, 2010-03-08T04:07:17, 0.2.1.9, HU1201LBYM
  4, 2010-03-08T04:07:17, 0.2.2.9, HU1202LEP9
  5, 2010-03-08T04:07:17, 0.2.3.9, HU1202LEHW
  6, 2010-03-08T04:07:17, 0.2.4.9, HU1202LEJR
  7, 2010-03-08T04:07:17, 0.3.1.9, HU1201LC19
  8, 2010-03-08T04:07:17, 0.3.2.9, HU1202LENL
  9, 2010-03-08T04:07:18, 0.3.3.9, HU1202LEND
 10, 2010-03-08T04:07:18, 0.3.4.9, HU1202LEP4
  4, 2015-04-09T12:22:26, 0.2.2.9, HUE41311EY
  4, 2015-04-14T10:30:42, 0.2.2.9, HUE50618ME


2015-04-09T12:16:58.577 warn 0.0.0.0.0 0000 "ADI: Timed out waiting for msg! drive 4"
2015-04-09T12:17:05.587 warn 0.0.0.0.0 0000 "ADI: Timed out waiting for msg! drive 4"
2015-04-09T12:17:12.597 warn 0.0.0.0.0 0000 "ADI: Timed out waiting for msg! drive 4"
2015-04-09T12:17:29.543 error 0.0.0.0.0 0000 "VMonitorDriveInit driveInfo::issueCommand(): Drive Get Info Response Bad Result Code = 6414 For Drive ID 4"
2015-04-09T12:25:59.489 warn 0.0.0.0.0 0000 "SensorDriveFuncs:handleDrvTempChanges - Module 2 Drive 4 is not present. "
2015-04-09T12:26:06.385 warn 0.0.0.0.0 6408 "GetDriveStatus: Firing DriveHealthEvent for DriveId 6 Old health state: 4, New health state: 3"
2015-04-09T12:26:34.983 error 0.0.0.0.0 8033 "SensorDriveFuncs: doDrivePresent - Module 2 Drive 4 has been removed"
2015-04-09T12:30:44.127 warn 0.0.0.0.0 6408 "GetDriveStatus: Firing DriveHealthEvent for DriveId 4 Old health state: 2, New health state: 3"
2015-04-09T12:31:02.645 error 0.0.0.0.0 8033 "SensorDriveFuncs: doDrivePresent - Module 2 Drive 2 has been removed"
2015-04-09T12:33:39.917 warn 0.0.0.0.0 0000 "ADI: Timed out waiting for msg! drive 4"

Changes

Cause

DWWN doe s not get send to tape drive in Library.
 
n/a
 

Solution

Order a pre-programmed RLM card and schedule replacement.

Follow Doc-ID as approved by Ryan Lucas.
SL500 - Procedure to Order a Programmed Replacement RLM Card (Doc ID 1013985.1)
For replacement of a Programmed RLM Card.

After the RLM replacement all tape drives are having new WWNs (assigned by the SL500 as DWWNs) this required following fix in CommVault.

============================================================
It was necessary to configure the CV WA datapath driver.
http://documentation.commvault.com/commvault/v10/article?p=features/library_drive_config/library_drive_configuration_faq.htm

How to detect devices in Solaris?
To attach the wa drivers when the library is attached to QLOGIC FC HBA by SUN

The WA drives setup needed to be implemented in each Solaris server connected to this SL500.
============================================================
 

References

This solution has no attachment