Storage Boards Cleanup
To make it easier to find information about HPE Storage products and solutions, we are doing spring cleaning. This includes consolidation of some older boards, and a simpler structure that more accurately reflects how people use HPE Storage.
Tape Libraries and Drives
cancel
Showing results for 
Search instead for 
Did you mean: 

LIbrary & Tape Tools not finding FC attached devices

LIbrary & Tape Tools not finding FC attached devices

Hello,

I have a HP DL380G4 running NetWare 6.5 sp8 and Arcserve 11.1 SP3. It has a QLogic card (QL2x00.HAM = v7.00.01) connected to an MSA4000 and an MSL6030.

I'm having hard drive problems during backups (tapes stay tuck in drive, server abends when tape formatting, etc.) and one thing I know is that my tape drive and changer have old firmware. I've downloaded and copied LTT to the proper folder, but I can't get it to scan for devices without error.

For example, I load the .nlm, choose (1) for a Hardware Scan, and the X moves to hardware scan. I don't know what to do from there, so I press Enter to get into the command help screen. I then press (3) to start the specified scan. At that point, I get the following error:

OC_Exception_c caught: Internal error (oc_deviceaccess_nw.cpp, 484, Unable to retrieve device handle)

So, I can't scan devices which, of course, prevents me from upgrading firmware.

Can any of you help me? I've attached the latest LTT log file.
12 REPLIES
Steven Clementi
Honored Contributor

Re: LIbrary & Tape Tools not finding FC attached devices

1. Did you mean an EVA4000?

2. How is your SAN Switch zoning set up?

3. What other devices are on the SAN? (Server wise)


Steven
Steven Clementi
HP Master ASE, Storage and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5)
RHCE
NPP3 (Nutanix Platform Professional)

Re: LIbrary & Tape Tools not finding FC attached devices

Steven,

Yes, EVA!! We do have an old MSA1000 in a different facility - I was typing too fast.

I'm not sure about the zoning, I'm not a "SAN Guy", but he does sit across from me. I'll find out.

There are 12 NetWare boxes running producting file/print and one Windows box that runs Command View and other SAN management applications. All the data that is presented to the production file/print is snapcloned. That snapcloned data is presented to the NetWare backup server running Arcserve. So, the data (vDisks? Containers?) being backed up are only visible to the one server. I hope that makes sense and answers your question.
Steven Clementi
Honored Contributor

Re: LIbrary & Tape Tools not finding FC attached devices

"...only visible to the one server. I hope that makes sense and answers your question."

My concern is not with the visibility of the virtual disks, but rather the "traffic to and from" the EVA, tape library and other servers on the SAN.

The SAN, after all, is like 1 big shared SCSI bus.


Steven
Steven Clementi
HP Master ASE, Storage and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5)
RHCE
NPP3 (Nutanix Platform Professional)

Re: LIbrary & Tape Tools not finding FC attached devices

SAN Guy says:

"We have a dual SAN setup, single switch each, between the MSL and the host. One switch has the MSL port 29:7f and backup server port 20:00:00:e0:8b:83:3e:8b in a zone together. Both are logged into the
fabric. The other switch has the backup server port 20:00:00:e0:8b:83:3e:8b in the fabric, but it's not in a zone with any
port that looks like it's on the MSL."

The MSL only has one FC interface, so that makes sense to me that it would only be in one zone.
Steven Clementi
Honored Contributor

Re: LIbrary & Tape Tools not finding FC attached devices

I am asking because zoning can lead to SAN related issues that can not be explained easily. It sounds like the zoning might be ok, but to check, can you have your SAN guy output the commands..

Brocade based switches:
zoneshow
cfgshow

Cisco based switches:
show running

these are telnet or ssh commands.


One of the things you can do, depending on if you feel comfortable with it, is zone the Command View server and the tape library's nsr togetther and run the windows version of ltt and see if you can diag it that way.


"The MSL only has one FC interface, so that makes sense to me that it would only be in one zone."

Yep, the library comes standard with a single fibre port nsr with 2 scsi ports(usually). It can only be connected to one fabric (one san switch), but it can be zones to multiple servers.


Steven
Steven Clementi
HP Master ASE, Storage and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5)
RHCE
NPP3 (Nutanix Platform Professional)

Re: LIbrary & Tape Tools not finding FC attached devices

I'm getting closer. CA Arcserve wants to use it's own hardware drivers, so we rename NWTAPE.CDM when installing it. I renamed it back to normal and loaded it. It now starts to scan for devices, then after a few moments comes up with that same error I put in my initial post. I think this is all driver related. I'll look for NetWare library/changer drivers.
LTT Team
Valued Contributor

Re: LIbrary & Tape Tools not finding FC attached devices

Hi,

I noticed the log files were not attached in the first thread. Can you upload the log files? The Eventlog.ltt can be found in sys:\system\hp_ltt\logs directory.

The error message indicates LTT is unable to get an handle to a HBA adapter for some reason.

Please let us know the list of SCSI/FC adapters connected in the system.

Regards,
Satya
LTT Team

Re: LIbrary & Tape Tools not finding FC attached devices

Sorry about the attachment. I hope it works this time.
LTT Team
Valued Contributor

Re: LIbrary & Tape Tools not finding FC attached devices

The log wasn't much of a help however I noticed there are three unbound device objects at
3.2.0 -> [V599-A3-D2:0]
3.2.2 -> [V599-A3-D2:2]
3.2.1 -> [V599-A3-D2:1]
and
3.2.3 -> [V599-A3-D2:3] HP NS E1200-160. Using the last entry, I believe the above unbound device objects are related to the MSL library. Would it be possible to display the output of 'list storage adapters'? Please check if the tape drives are listed. Generally, the robotics will be listed as the unbound device object but the drives would be listed with their names.

Alternatively, we could try entering the physical address manually. The steps would be
- load hp_ltt
In LTT UI,
enter command> 2 ! to select saved/manual scan
enter command> continue
enter command> enterHWAddrManual ! to enter the manual scan
- in the dialog box enter the physical address of any of the unbound objects.
enter command> 1 ! if the device is listed
enter command> firmware ! to enter firmware session

Regards,
Satya

Re: LIbrary & Tape Tools not finding FC attached devices

Unbound storage devices - this goes back to my statement earlier about this being a driver issue.

Basically, LTT directions say to unload your backup software before running LTT. With CA Arcserve, the tape drive and FC board drivers are their drivers, not Novell's. So, I know NWTAPE is the Novell tape drive driver, but what's their FC Board driver? If I could load those, then I could run LTT and get some bound devices and move forward.

Re: LIbrary & Tape Tools not finding FC attached devices

I have the backup software up/running right now, so the SCSI devices will be displayed. LTT requires that I unload the backup software before runnign LTT, so the drivers for these devices unload and LTT can't find anything and errors out.

I need to know what Novell drivers I need for the hardware.

Here's the output from List Storage Adapters:

WI-BACKUP:list storage adapters
0x00 [V024-A0] Legacy FLOPPY Controller [slot 0]
0x01 [V024-A0-D1:0] Legacy Floppy
0x02 [V100-A100] USB UHCI Controller [slot 0]
0x03 [V100-A101] USB UHCI Controller [slot 0]
0x04 [V100-A102] USB EHCI Controller [slot 0]
0x05 [V025-A1] Novell IDE/ATA/ATAPI/SATA Host Adapter Module [slot 0]
0x08 [V025-A1-D0:0] HL-DT-ST DVD-ROM GDR8084N f/w:3.00
0x06 [V504-A2] HP Unified RAID Driver [slot 10017]
0x07 [V504-A2-D0:0] HP Smart Array 6i Slot 0 ID 0 LUN 0
0x0E [V599-A3] QL2X00.HAM on QLA2342 [slot 101]
0x100 [V599-A3-D1:3C] HP HSV200 506617005007552C (6100)
0x56 [V599-A3-D0:0] HP HSV200 50001FE15007552C (6100)
0x57 [V599-A3-D0:15] HP HSV200 50001FE15007552C (6100)
0x58 [V599-A3-D0:16] HP HSV200 50001FE15007552C (6100)
0x59 [V599-A3-D0:17] HP HSV200 50001FE15007552C (6100)
0x5A [V599-A3-D0:18] HP HSV200 50001FE15007552C (6100)
0x5B [V599-A3-D0:19] HP HSV200 50001FE15007552C (6100)
0x5C [V599-A3-D0:1A] HP HSV200 50001FE15007552C (6100)
0x5D [V599-A3-D0:1B] HP HSV200 50001FE15007552C (6100)
0x5E [V599-A3-D0:1C] HP HSV200 50001FE15007552C (6100)
0x5F [V599-A3-D0:1D] HP HSV200 50001FE15007552C (6100)

0x5E [V599-A3-D0:1C] HP HSV200 50001FE15007552C (6100)
0x5F [V599-A3-D0:1D] HP HSV200 50001FE15007552C (6100)
0x60 [V599-A3-D0:1E] HP HSV200 50001FE15007552C (6100)
0x61 [V599-A3-D0:1F] HP HSV200 50001FE15007552C (6100)
0x62 [V599-A3-D0:66] HP HSV200 50001FE15007552C (6100)
0x63 [V599-A3-D1:0] HP HSV200 506617005007552C (6100)
0x64 [V599-A3-D1:15] HP HSV200 506617005007552C (6100)
0x65 [V599-A3-D1:16] HP HSV200 506617005007552C (6100)
0x66 [V599-A3-D1:17] HP HSV200 506617005007552C (6100)
0x67 [V599-A3-D1:18] HP HSV200 506617005007552C (6100)
0x68 [V599-A3-D1:19] HP HSV200 506617005007552C (6100)
0x69 [V599-A3-D1:1A] HP HSV200 506617005007552C (6100)
0x6A [V599-A3-D1:1B] HP HSV200 506617005007552C (6100)
0x6B [V599-A3-D1:1C] HP HSV200 506617005007552C (6100)
0x6C [V599-A3-D1:1D] HP HSV200 506617005007552C (6100)
0x6D [V599-A3-D1:1E] HP HSV200 506617005007552C (6100)
0x6E [V599-A3-D1:1F] HP HSV200 506617005007552C (6100)
0x6F [V599-A3-D1:66] HP HSV200 506617005007552C (6100)
0x70 [V599-A3-D2:0] HP MSL6000 Series 051
0x71 [V599-A3-D2:1] HP ULTRIUM 3-SCSI G65
0x72 [V599-A3-D2:2] HP ULTRIUM 3-SCSI G24
0x73 [V599-A3-D2:3] HP NS E1200-160 506600005007552C (593d)
0x92 [V599-A3-D0:51] HP HSV200 50001FE15007552C (6100)
0x93 [V599-A3-D0:52] HP HSV200 50001FE15007552C (6100)

0x92 [V599-A3-D0:51] HP HSV200 50001FE15007552C (6100)
0x93 [V599-A3-D0:52] HP HSV200 50001FE15007552C (6100)
0x94 [V599-A3-D0:53] HP HSV200 50001FE15007552C (6100)
0x95 [V599-A3-D0:54] HP HSV200 50001FE15007552C (6100)
0x96 [V599-A3-D0:55] HP HSV200 50001FE15007552C (6100)
0x97 [V599-A3-D0:56] HP HSV200 50001FE15007552C (6100)
0x98 [V599-A3-D1:51] HP HSV200 506617005007552C (6100)
0x99 [V599-A3-D1:52] HP HSV200 506617005007552C (6100)
0x9A [V599-A3-D1:53] HP HSV200 506617005007552C (6100)
0x9B [V599-A3-D1:54] HP HSV200 506617005007552C (6100)
0x9C [V599-A3-D1:55] HP HSV200 506617005007552C (6100)
0x9D [V599-A3-D1:56] HP HSV200 506617005007552C (6100)
0xCA [V599-A3-D0:33] HP HSV200 50001FE15007552C (6100)
0xCB [V599-A3-D0:34] HP HSV200 50001FE15007552C (6100)
0xCC [V599-A3-D1:33] HP HSV200 506617005007552C (6100)
0xCD [V599-A3-D1:34] HP HSV200 506617005007552C (6100)
0xF1 [V599-A3-D0:35] HP HSV200 50001FE15007552C (6100)
0xF2 [V599-A3-D0:36] HP HSV200 50001FE15007552C (6100)
0xF3 [V599-A3-D0:37] HP HSV200 50001FE15007552C (6100)
0xF4 [V599-A3-D0:38] HP HSV200 50001FE15007552C (6100)
0xF5 [V599-A3-D0:39] HP HSV200 50001FE15007552C (6100)
0xF6 [V599-A3-D0:3A] HP HSV200 50001FE15007552C (6100)
0xF7 [V599-A3-D0:3B] HP HSV200 50001FE15007552C (6100)
0xF8 [V599-A3-D0:3C] HP HSV200 50001FE15007552C (6100)

0xF7 [V599-A3-D0:3B] HP HSV200 50001FE15007552C (6100)
0xF8 [V599-A3-D0:3C] HP HSV200 50001FE15007552C (6100)
0xF9 [V599-A3-D1:35] HP HSV200 506617005007552C (6100)
0xFA [V599-A3-D1:36] HP HSV200 506617005007552C (6100)
0xFB [V599-A3-D1:37] HP HSV200 506617005007552C (6100)
0xFC [V599-A3-D1:38] HP HSV200 506617005007552C (6100)
0xFD [V599-A3-D1:39] HP HSV200 506617005007552C (6100)
0xFE [V599-A3-D1:3A] HP HSV200 506617005007552C (6100)
0xFF [V599-A3-D1:3B] HP HSV200 506617005007552C (6100)
0x0F [V599-A4] QL2X00.HAM on QLA2342 [slot 102]
0xDD [V599-A4-D1:3C] HP HSV200 506717005007552D (6100)
0x10 [V599-A4-D0:0] HP HSV200 50001FE15007552D (6100)
0x11 [V599-A4-D0:15] HP HSV200 50001FE15007552D (6100)
0x12 [V599-A4-D0:16] HP HSV200 50001FE15007552D (6100)
0x13 [V599-A4-D0:17] HP HSV200 50001FE15007552D (6100)
0x14 [V599-A4-D0:18] HP HSV200 50001FE15007552D (6100)
0x15 [V599-A4-D0:19] HP HSV200 50001FE15007552D (6100)
0x16 [V599-A4-D0:1A] HP HSV200 50001FE15007552D (6100)
0x17 [V599-A4-D0:1B] HP HSV200 50001FE15007552D (6100)
0x18 [V599-A4-D0:1C] HP HSV200 50001FE15007552D (6100)
0x19 [V599-A4-D0:1D] HP HSV200 50001FE15007552D (6100)
0x1A [V599-A4-D0:1E] HP HSV200 50001FE15007552D (6100)
0x1B [V599-A4-D0:1F] HP HSV200 50001FE15007552D (6100)
0x1C [V599-A4-D0:66] HP HSV200 50001FE15007552D (6100)

0x1B [V599-A4-D0:1F] HP HSV200 50001FE15007552D (6100)
0x1C [V599-A4-D0:66] HP HSV200 50001FE15007552D (6100)
0x1D [V599-A4-D1:0] HP HSV200 506717005007552D (6100)
0x1E [V599-A4-D1:15] HP HSV200 506717005007552D (6100)
0x1F [V599-A4-D1:16] HP HSV200 506717005007552D (6100)
0x20 [V599-A4-D1:17] HP HSV200 506717005007552D (6100)
0x21 [V599-A4-D1:18] HP HSV200 506717005007552D (6100)
0x22 [V599-A4-D1:19] HP HSV200 506717005007552D (6100)
0x23 [V599-A4-D1:1A] HP HSV200 506717005007552D (6100)
0x24 [V599-A4-D1:1B] HP HSV200 506717005007552D (6100)
0x25 [V599-A4-D1:1C] HP HSV200 506717005007552D (6100)
0x26 [V599-A4-D1:1D] HP HSV200 506717005007552D (6100)
0x27 [V599-A4-D1:1E] HP HSV200 506717005007552D (6100)
0x28 [V599-A4-D1:1F] HP HSV200 506717005007552D (6100)
0x29 [V599-A4-D1:66] HP HSV200 506717005007552D (6100)
0x83 [V599-A4-D0:51] HP HSV200 50001FE15007552D (6100)
0x84 [V599-A4-D0:52] HP HSV200 50001FE15007552D (6100)
0x85 [V599-A4-D0:53] HP HSV200 50001FE15007552D (6100)
0x86 [V599-A4-D0:54] HP HSV200 50001FE15007552D (6100)
0x87 [V599-A4-D0:55] HP HSV200 50001FE15007552D (6100)
0x88 [V599-A4-D0:56] HP HSV200 50001FE15007552D (6100)
0x89 [V599-A4-D1:51] HP HSV200 506717005007552D (6100)
0x8A [V599-A4-D1:52] HP HSV200 506717005007552D (6100)
0x8B [V599-A4-D1:53] HP HSV200 506717005007552D (6100)

Re: LIbrary & Tape Tools not finding FC attached devices

So, you can see they are there:

0x70 [V599-A3-D2:0] HP MSL6000 Series 051
0x71 [V599-A3-D2:1] HP ULTRIUM 3-SCSI G65
0x72 [V599-A3-D2:2] HP ULTRIUM 3-SCSI G24
0x73 [V599-A3-D2:3] HP NS E1200-160 506600005007552C (593d)

When I unload CA Arcserve, they become unbound devices.