Unsolved

This post is more than 5 years old

86 Posts

795

December 10th, 2009 06:00

Reconfiguration Library - drives are swapped

This log from networker server. In fact when I tried to reconfigure library for that specific storage node . it fails with the  following message included. I have included the output of inquire command, which clearly indicates that I have problem that my tape drives are swapped. The OS is windows server 2003, and in HBA it does not use persistant binding. I do not know how to fix that problem myself with HBA. I am looking for temporary solution. Do I need to several times restart services on my storage node and possibly they will be fixed and recognised both by OS and networker? Any idea?

Jukebox `ADIC@4.4.1', operation 27]. Initiated operation `reconfig library : Add Device servermine.local:\\.\Tape0 D:000256'. Cannot start operation. drive D:000256 is currently associated with hardware ID Serial Numbers:WWNN=500308C175E80423:ATNN=IBM     ULTRIUM-TD3     1210266406:WWPN=500308C175E80424:1210266406 and the new device hardware ID is Serial Numbers:WWNN=500308C175E80426:ATNN=IBM     ULTRIUM-TD3     1210266394:WWPN=500308C175E80427:1210266394

The output of inquire is :

scsidev@0.0.0:DGC     RAID 5          0326|Disk, \\.\PHYSICALDRIVE0                                            S/N: CK200071900247                                            WWNN=6006016049AD1C00A2CECBF1713BDC11                                            PORT=00000001 scsidev@0.1.0:DGC     RAID 5          0326|Disk scsidev@0.2.0:DGC     RAID 5          0326|Disk scsidev@0.3.0:DGC     RAID 5          0326|Disk scsidev@0.4.0:IBM     ULTRIUM-TD3     64D0|Tape, \\.\Tape1                                            S/N: 1210266394                                            ATNN=IBM     ULTRIUM-TD3     12102663 94                                            WWNN=500308C175E80426                                           WWPN=500308C175E80427                                            PORT=00000001 scsidev@4.0.0:DGC     RAID 5          0326|Disk scsidev@4.1.0:DGC     RAID 5          0326|Disk scsidev@4.2.0:DGC     RAID 5          0326|Disk scsidev@4.3.0:DGC     RAID 5          0326|Disk scsidev@4.4.0:IBM     ULTRIUM-TD3     64D0|Tape, \\.\Tape0                                            S/N: 1210266406                                            ATNN=IBM     ULTRIUM-TD3     12102664 06                                            WWNN=500308C175E80423                                            WWPN=500308C175E80424                                            PORT=00000001 scsidev@4.4.1:ADIC    Scalar 24       310A|Autochanger (Jukebox), \\.\Changer0

Any idea? Networker 7.4

1 Rookie

 • 

66 Posts

December 10th, 2009 08:00

Here's the link to my other post which goes into this in much detail

https://community.emc.com/message/357768#357768

1 Rookie

 • 

66 Posts

December 10th, 2009 08:00

I will make a guess here.  Fiber drives?

I have an Dell ML6030 which is a rebranded ADIC i500 scalar tape library myself with the same drives.  Used to have this problem where the drives would switch there locations around etc.  usually occurred after either a system reboot or library reboot. But I finally fixed this problem and stopped the constat reconfiguration of the tape drives.

Since you are using Windows you need to do 2 things.

1) In the HBA card you need to set persistent binding. If it is a Qlogic card this is done through SANSurfer.

2) If you are using the IBM drivers for the tape drives. (If this is a Dell branded as well and you use the Dell drivers they are infact IBM's) Then you need to do some registry modifications to set persistent naming as well.  Wether you use the IBM or MS drivers for the tape drives both sets of drivers have a method for setting this up in the registry. There are articles on how to do both.  Should be one on MS website for there drivers. And I believe EMC has articles about it as well.  If you search this forum you will find a past post from me as well with instructions on how this is done as well.

But after you set this up, reboot the servers and then remove and re-discover the tape drives, and configuration you will find that they no longer will have this issue you are having.

Thanks

Paul

No Events found!

Top