topic Re: NO_HW in Operating System - HP-UX

NO_HW

Sanjiv Sharma_1 — Fri, 07 May 2004 01:18:15 GMT

Hi All,

I have a N4000/HP-UX 11.00 with A3740A FC Controller. I have connected the A3740A FC controller to A Tape Library A4853A(consisting 3 DLT7000 drives) through a brocade FC switch and HP Surestore Bridge fc 4/2 (A3511AZ).

A3740A driver is in kernel for HP-UX 11.00
http://docs.hp.com/hpux/onlinedocs/J6374-90013/fc_support_matrix.pdf

My ioscan is not showing the NO_HW for the 3 drives and robotic arm of the tape library A4853A.

# ioscan
ba 5 0/8 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
fc 1 0/8/0/0 fcT1 CLAIMED INTERFACE HP Fibre Channel Mass Storage Adapter
lan 2 0/8/0/0.5 fcT1_cntl CLAIMED INTERFACE HP Fibre Channel Mass Storage Cntl
fcp 1 0/8/0/0.8 fcp CLAIMED INTERFACE FCP Protocol Adapter
ext_bus 3 0/8/0/0.8.0.3.0 fcparray NO_HW INTERFACE FCP Array Interface
target 7 0/8/0/0.8.0.3.0.0 tgt NO_HW DEVICE
target 8 0/8/0/0.8.0.3.0.1 tgt NO_HW DEVICE
target 9 0/8/0/0.8.0.3.0.2 tgt NO_HW DEVICE
target 10 0/8/0/0.8.0.3.0.3 tgt NO_HW DEVICE
target 11 0/8/0/0.8.0.3.0.4 tgt NO_HW DEVICE
target 12 0/8/0/0.8.0.3.0.5 tgt NO_HW DEVICE
target 13 0/8/0/0.8.0.3.0.6 tgt NO_HW DEVICE
target 14 0/8/0/0.8.0.3.0.7 tgt NO_HW DEVICE
target 15 0/8/0/0.8.0.3.0.8 tgt NO_HW DEVICE
target 16 0/8/0/0.8.0.3.0.15 tgt NO_HW DEVICE
ext_bus 4 0/8/0/0.8.0.255.0 fcpdev NO_HW INTERFACE FCP Device Interface
target 17 0/8/0/0.8.0.255.0.3 tgt NO_HW DEVICE

What needs to be done to make it claimed?

Thanks in advance.

Re: NO_HW

Sanjiv Sharma_1 — Fri, 07 May 2004 01:23:28 GMT

Do I need to install some driver for A Tape Library A4853A (consisting 3 DLT7000 drives) and HP Surestore Bridge fc 4/2 (A3511AZ)?

Re: NO_HW

Steven E. Protter — Fri, 07 May 2004 01:24:30 GMT

Start with drivers, but it might be in the wrong slot. You may need to move the card to a different slot.

Or,

It may be dead. test with xstm,mstm,cstm

SEP

Re: NO_HW

Bharat Katkar — Fri, 07 May 2004 01:30:08 GMT

I don't think there is need to install driver for Tape Library A4853A but something has to be done for:
brocade FC switch and HP Surestore Bridge fc 4/2 (A3511AZ).

Re: NO_HW

Sanjiv Sharma_1 — Fri, 07 May 2004 02:04:48 GMT

Hello,

stm shows the driver state to be "DEAD". What should I do next to make it "READY"? The FC controller is connected to the Brocade switch.

-- Information Tool Log for Fibre Channel Interface on path 0/8/0/0 --
Log creation time: Fri May 7 14:57:57 2004 Hardware path: 0/8/0/0 Product ID: Fibre Channel Interface Hardware Path: 0/8/0/0 Slot Number: 0 Hard Physical Address:g 0x91eff000 EIM of Card: 0xffffffff Topology: M Topology is Unknown (65535)
N_Port_ID: 1 N_Port Port World Wide Name:0x1000001083B94644 N_Port Node World Wide Name:0x1000001083B94644 Speed: 1062500000 (bps) Driver State: DEAD (0) Number of EDB's in use: 0 Number of OIB's in use: 0 Active Outbound Exchanges: 1 Active Login Sessions: 0

Re: NO_HW

Andris Mednis — Fri, 07 May 2004 02:53:15 GMT

Have you tried cold restart of tape library, FC bridge, a HP-UX server (in this order)?
Do you see devices immediately after cold reboot of everything, then after "ioscan" ? I suppose "NO_HW" means that the device was seen sometimes ago and became unaccessible/unresponsive. It could be a problem with tape library (try to powercycle it, see what library diagnostics show), Brocade configuration (zoning ?), some access control based on FC adapter's WWN.

Re: NO_HW

Elmar P. Kolkman — Fri, 07 May 2004 03:06:29 GMT

Start by checking your cables. Since all targets give NO_HW, it seems to me your cable is broken.

If the cable is good, but you replaced all devices on the controller, the contoller has problems with detecting the new hardware, because the WWN has changed. We ran into a similar problem here after a fibrecard change in a taperobot.

What you could try is do the ioscan with -fn, search for the /dev/td? device file.

With this, use fcmsutil:
/opt/fcms/bin/fcmsutil get remote all

Then do:
/opt/fcms/bin/fcmsutil replace_dsk you got for a NO_HW device from the get remote call in the previous step.

Then do the ioscan -f to check if it gets better.

BTW: rebooting the HP-UX system could solve this too, but who wants to reboot a HP-UX system if it can be prevented ?!

Re: NO_HW

Matti_Kurkela — Fri, 07 May 2004 03:21:54 GMT

As far as I know, A3740A is not fabric-capable, meaning that it does not work with FC switches. Hubs would be OK, though.

A newer card (A5158A, at least) would be better when working with FC switches.

However, HP FC Fabric Migration Guide says that things like "translative mode" or "QuickLoop mode" at the FC switch might allow you to use your existing card. I'm not a SAN guru, but I understand this might require configuring the switch port(s) explicitly for this: it won't be just "plug and play".

Re: NO_HW

Sanjiv Sharma_1 — Fri, 07 May 2004 03:35:44 GMT

Hi,

I have another A3740A installed in path 0/4 which gives the device file as /dev/fcms1 not /dev/td?

But I am not getting any device file from the 0/8 card.

fc 0 0/4/0/0 fcT1 CLAIMED INTERFACE HP Fibre Channel Mass Storage Adapter
lan 1 0/4/0/0.5 fcT1_cntl CLAIMED INTERFACE HP Fibre Channel Mass Storage Cntl
/dev/fcms1
fcp 0 0/4/0/0.8 fcp CLAIMED INTERFACE FCP Protocol Adapter

Re: NO_HW

Elmar P. Kolkman — Fri, 07 May 2004 03:45:50 GMT

/dev/fcms? devices should work to. The device name depends on the driver being used. In our situation (11i) it was /dev/td?

Perhaps you should do an insf for the controler. The command should be something like:
insf -H 0/8/0/0.5

Re: NO_HW

Sanjiv Sharma_1 — Fri, 07 May 2004 03:54:55 GMT

insf -H 0/8/0/0.5 didn't create the device file.

Re: NO_HW

Sanjiv Sharma_1 — Fri, 07 May 2004 04:01:55 GMT

Hi Matti,

Can you attach a copy of HP FC Fabric Migration Guide?

Re: NO_HW

Matti_Kurkela — Fri, 07 May 2004 05:51:17 GMT

I had the Fabric Migration Guide only in paper form, but a quick search in docs.hp.com located the electronic version:

http://docs.hp.com/hpux/onlinedocs/J2635-90017/J2635-90017.html

Re: NO_HW

Ashwani Kashyap — Fri, 07 May 2004 11:20:15 GMT

The A3740A is an FC_AL card and doesnot support swithed Fabric . Its succesor 5158A does .

either plug this card directly into the FC_scsi bridge or if you want to use the switch then set the brocade ports whenre these cards connect to , to quick loop .

On firther ioscan and insfe -e , you should see your device file and fcmsutil should work .

For this card the bridge should be at firmware version 3917 and the brocade2800 at firware 2.1.3 .

Re: NO_HW

generic_1 — Fri, 07 May 2004 18:37:31 GMT

Check your documentation to see what driver you need and make sure it is loaded. Also, it would not hurt to install your tape software to give you some more trouble shooting tools. Make sure your your scsci id and cables are all in place. then run your ioscan and insf.

Good luck

Re: NO_HW

Navid Hussain_1 — Sat, 08 May 2004 06:37:15 GMT

Hi,

Since Library is connected with Fiber channel to host via FC Switch,
Basically, you need to configured E12000 Router port in the library.
Here is the procedure

These instructions provide instructions for configuring and testing the library,

First ensure that stape drive (tape) amd schgr driver (robotic control) is loaded in the kernel. If not then load and it will ask to reboot, Reboot manually, if not the case.

If you want to use FC to connect an MSL, then you are supposed to have an E1200
storage router FC controller card seated on the back of MSL Library.

This board comes equipped with a FC port, two LVD SCSI and a 10 BaseT LAN card and a serial connection.

As s standard IP address is set to 1.1.1.1 (255.255.255.0). Simply configure your laptop/PC with IP address 1.1.1.2/255.255.255.0 and tie it to E1200 router through crossover LAN cable.

(Please note that IP address is different than RMC IP Address)

Either use Internet explorer to browser http://1.1.1.1 or telnet 1.1.1.1 User name is root and password is password to log in.

Then configure FC controller on MSL like the following -
System Menu > Active Fabric
Server Free backup mode set to DISABLED
Number of Controller LUNS set to 0
Submit and reboot
Main > Ports > FC port
Port Mode set to N_port (for Fiber switches)
Use Hard AL_PA set to Disabled
Discovery mode set to Auto discovery on Reboot
Buffered Tape Writes set to Disabled
Buffer Tape Queue Depth set to 1
Default Map set to Auto Assigned
Performance Mode depends on FC switch capability and your FC adapter on the host. (2GB)
Force FCP Response Code set to Disabled
Submit (SAVE)
Primary Initiator ID set to 7
Discovery set to Enabled
Discovery Delay (seconds) set to 30
Submit

Do a manual discovery from main Menu and you should be able to see all drives
Reboot MSL and reboot hosts.
That is it. It should be able to recognize.

Cheers...

NAVID