Replacing Tape Drive Configuration

[Bala C]

Hi,

I have replaced the HP Ultrium tape drive in QUANTUM:PX500 Library as my Old tape drive was throwing H/W errors. But ioscan doesn't detect the new tape drive showing it as NO_HW.

Is there any reconfiguration required for the tape drive? I guess not.When I put back my old tape drive it is detecting and ioscan shows it as claimed.

Any Ideas. Folks?

[Eemans Dany · Accepted solution]

Hi,

I have no expirance with Quantum libs.
But does your library detects the new drive.

Is there something installed like secure manager (I know it HP soft), but it regulates the access to the drives by serial number or wwn number (if san connected).

If something simular is installed you need to update his configuration before the new drive is visible for servers.

If you have a san connected drive, check if the san zoning is correctly configured.
A new drive comes with a new WWN number and it could be needed to update the san config with the new WWN number.

Dany

[Michael A. McKenney]

I would check to see if the controller detects it first. Check the cables and power first. At post, check the controller setup to see if its detected in it. Verify the jumper settings.

[Bala C]

Yes, It is a SAN library(connected to 5100 Brocade switch) and the drives are zoned to the hosts and to other clients.

How do I change the wwn no. in the alias? Will my switch detect the new drives wwn number?

I see some option like replace wwn?

Please help.

[Marino Meloni_1]

first suggestion is to contact Quantum as the product is Quantum

second it depend what kind of drive you have, SCSI or FC, and if there is some router in the middle or if the drive is directly FC connected

Third it depend how you have created the zone, if per port of per WWN, if the first methode is used, you have nothing to do, if the mapping is per WWN, you should replace the WWN in the zone configuration of the switch

Fourth, you should reboot the host or issue a rescan in order to identify the new Drive that will have a new WWN, then you have to configure your backup application in order to use this drive instead of the previous one

these are general rules, a specialist with knowledge on your environment should be able to give you the correct way to proceed.

here below the Quantum user guide

http://downloads.quantum.com/px500/PX500_Series_Users_Guide_81-81290-05_B01.pdf

[Bala C]

Marino/Emans,

These drives are with FC interface and the FC Controller is zoned to the SAN switch. Hence, the device port wwn will not change. Hence, the existing zone configuration will stand good.

It is just that these new drives are not detected by the host. ioscan says NO_HW.

SAN switch detects the changed tape drive's serial no.

These drives are zoned to other servers too. But none of the other servers detect these drives.

Does rebooting hosts means rebooting even the other other hosts where it is zoned?

But will reboot do the trick?

What about this command:-

fcmsutil /dev/td0 replace_dsk 0x10435(Remote N portID)

When I issued this command, host display that the authentication will not be done next time.

Soon after that, ioscan -fnC tape detected or showed that the tape device as CLAIMED.

Not sure this will do the trick. But I need to rollback to the Old drives as the backups need to kick off.

[Bala C]

By the way, I'm getting a bunch of errors in the syslog saying use fcmsutil with the replace_dsk option.

Any Idea?

[Torsten.]

>> What about this command:-

fcmsutil /dev/td0 replace_dsk 0x10435(Remote N portID)



This will do the trick.

A reboot will do it too.

[Marino Meloni_1]

Not an Unix specialist, but got this we use for VLS LTO drives:


Solution
Rebooting the systems that attach to the VLS9000 device is the easiest way to resolve the issue. While this is not always possible, there are possibilities to resolve the problem online.

For HP-UX 11.11 and 11.23 the fcmsutil replace_dsk changed status of tape devices from NO_HW to CLAIMED .

For 11.31 to be able to bring the devices back into the online state you will need to remove the target path for the persistent device in the following way:
#rmsf ?H 2/0/6/1/0.0x5001060158e1e010
#rmsf ?H 1/0/6/1/0.0x5001060158e1e000
#ioscan



We obviously need to replace the hardware path with the one for your device in the NO_HW state. The numbers given here are just a example. After these steps the device should be shown in CLAIMED state again without the need to reboot the system.


--------------------------------------------------------------------------------

[Bala C]

Thanks for the input guys.

Acutally, I did run the fcmsutil /dev/td0 replace_dsk Remote N-port ID and after that Ioscan showed the device status from No_HW to Claimed. But since the down time was lapsed, we reverted back to the old drives.

What does this fcmsutil replace_dsk command actually does?

Can some explain me in detail about this replace_dsk option?

Thanks for all your help.

[Torsten.]

The driver detects a new WWN for the same nPartID and prevents a login for safety reasons.

With the fcmsutil command you disable this check, hence the login is successful and you can use the device.

After a reboot the driver does not remember the old WWN, so this works too.

[Ralf Loehmann_2]

Hello Bala,
All good answers, here something I added to a similar question and also to a thread explaining the way better and I want to give the credit to that people:
In HP-UX under 11.31 the device file for a Device in the SAN uses a combination of the WWN and the Serial number of the Device (inquiry page 83). This means if one or the other is changed the device file identification is changed. The idea behind this is HP-UX is always on and you want to change for example your tape library to a different switch in the SAN you just change zoning and than move the device to the new ports. On HP-UX you might not need to change something in that case. Bad thing on a repair the one or the other is changing and you need to fix that.
Here is a better thread which explains what to do and also there is background information about the command in the whitepaper link. Also it works to reboot, but that is something an HP-UX customer does not like.
http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1294224152320+28353475&threadId=1373467
Regards,
Ralf.

[Bala C]

Hi Folks,

fcmsutil replace_disk was awesome and it detected the changed drives in 11.23 servers.

I have two 11.31 servers, I faced issue in one server using the scsimgr replace_wwid -D dsf

whereas the other this command fixed.

64000/0xfa00/0x18
0/0/6/1/1.0x500e09e00aef7310.0x0 0/0/6/1/1.1.19.255.0.0.0

# scsimgr -f replace_wwid -H 64000/0xfa00/0x18
scsimgr: Successfully validated binding of LUN paths with new LUN.

# ioscan -fnC tape |grep stape
tape 11 0/0/6/1/1.1.19.255.0.0.0 stape NO_HW DEVICE HP Ultrium 3-SCSI

As you see the above output, the scsimgr replace_wwid command hasn't fixed the issue.

I also ran scsmgr replace_leg_dsf


# avoriaz:root /root# scsimgr replace_leg_dsf -D /dev/rtape/tape6_BEST
Do you really want to replace? (y/[n])? y
scsimgr: Legacy device file '/dev/rmt/c31t0d0BEST' binding to LUN changed successfully

# avoriaz:root /root# ioscan -fnC tape |grep stape
tape 11 0/0/6/1/1.1.19.255.0.0.0 stape NO_HW DEVICE HP Ultrium 3-SCSI


Is there any other option? Or Am I doing a mistake somewhere?

Kindly help.

Or Reboot the only option?

Thanks.