msa1000 detection problem with hp-ux

[mahan_1]

Hi all
I have 2 rack with the same equipment
in both I have 2 rp3440 server with combo fiber card ( A9784A) and one msa1000 with san swith 2/8
I installed hp-ux v1 on all of four servers
in rack A I dont have any problem and both servers detected the msa1000 and disks , but in rack B both server do not detect the msa1000 and both hba card blinking green and yellow.
I changed the fiber cable and also the msa san switch and also hba card with a new one but still i have problem.
both rack configuration is same and i have no error or failuer .
is need necessery if i use any command in hp-ux to detect the msa1000 or anything else?
Please advice me

[Torsten.]

Did you already check the MSA configuration?
Are there LUNs configured?
Is SSP set to on?

[mahan_1]

yes i configured the LUN and ACL is disable , both msa have same setting and one work by two rp3440 in rack A and another one do not detected by two rp3440 in rack B

[mahan_1]

Is the any command on hp-ux I have to use for hba card to start comunicate with san ?

[Torsten.]

There is no command to start "SAN", but there are some things to check and double-check:

- current drivers installed on the host?
(use swlist/ioscan/fcmsutil)
- do you have a link?
- any zoning configured on the switch?
- if SSP is used on the MSA, check WWN's and presentation mode

[mahan_1]

- current drivers installed on the host? Yes

(use swlist/ioscan/fcmsutil)

- do you have a link? yes cable is intalled and when i connect it to a hba on a prolient server it is work

- any zoning configured on the switch?
No

- if SSP is used on the MSA, check WWN's and presentation mode
There is no ssp , It is disabled.

[Torsten.]

In most cases there is still a problem with the mentioned points that needs double checking (don't forget the host mode setting for the LUN).

What do you see if you run these commands?

# ioscan -fn
# fcmsutil /dev/
e.g. /dev/td0 or /dev/fcd0

[mahan_1]

it is the complete story:
I have two MSA1000 with 8 port SAN switch and four RP machines with HPUX.11.11. I followed the setup procedure on the installation manual and connected two of my RP machines to one of the SAN machine successfully. When I did the same procedure on the last set of machines, I encounter a connectivity problem.
I get no light message on the san switch and awaiting link up message on the HBA. Since both sets are identical (Hardware, Driver and firmware), I checked the FC cables and also SFP to make sure they are working by connecting the SAN system to HP DL580 and everything just works fine.
I like to know if there is anything else I should do to make this work. I am looking forward to hear from you.

Best Regards

P.S.
System configuration is as
Controller firmware is 4.48.b342
HBA cared is A9784A (Driver installation is correct based on fcmsutil report)
OS is HP-UX 11.11 (installed freshly from December 2006 media)
There are no ZONE and ACL configuration on SAN
There is one LUN
The result of ioscan â fn is
ba 3 0/2/1/0 PCItoPCI CLAIMED BUS_NEXUS PCItoPCI Bridge
fc 0 0/2/1/0/4/0 fcd CLAIMED INTERFACE HP A9784-60002 PCI/PCI-X Fibre Channel FC/GigE Combo Adapter (FC Port 1)
/dev/fcd0
lan 1 0/2/1/0/6/0 igelan CLAIMED INTERFACE HP A9784-60002 PCI/PCI-X 1000Base-T FC/GigE Combo Adapter
ba 4 0/3 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)
lan 2 0/3/1/0 iether CLAIMED INTERFACE HP A7012-60001 PCI/PCI-X 1000Base-T Dual-port Adapter
lan 3 0/3/1/1 iether CLAIMED INTERFACE HP A7012-60001 PCI/PCI-X 1000Base-T Dual-port Adapter
ba 5 0/4 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)
ba 6 0/6 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)
lan 4 0/6/1/0 iether CLAIMED INTERFACE HP AD331-60001 PCI/PCI-X 1000Base-T Adapter
ba 7 0/7 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)
tty 0 0/7/1/0 asio0 CLAIMED INTERFACE PCI SimpleComm (103c1290)
/dev/diag/mux0 /dev/mux0 /dev/tty0p0
tty 1 0/7/1/1 asio0 CLAIMED INTERFACE PCI Serial (103c1048)
/dev/GSPdiag1 /dev/diag/mux1 /dev/mux1 /dev/tty1p0 /dev/tty1p2 /dev/tty1p4
unknown -1 0/7/2/0 UNCLAIMED UNKNOWN PCI Display (10025159)
memory 0 8 memory CLAIMED MEMORY Memory
ipmi 0 16 ipmi CLAIMED INTERFACE IPMI Controller
/dev/ipmi
processor 0 128 processor CLAIMED PROCESSOR Processor
processor 1 129 processor CLAIMED PROCESSOR Processor
processor 2 152 processor CLAIMED PROCESSOR Processor
processor 3 153 processor CLAIMED PROCESSOR Processor
#
Result of fcmsutil is
# fcmsutil /dev/fcd0

Vendor ID is = 0x001077
Device ID is = 0x002312
PCI Sub-system Vendor ID is = 0x00103c
PCI Sub-system ID is = 0x0012c7
PCI Mode = PCI-X 133 MHz
ISP Code version = 3.3.166
ISP Chip version = 3
Previous Topology = UNINITIALIZED
Link Speed = UNKNOWN
Local N_Port_id is = None
Previous N_Port_id is = None
N_Port Node World Wide Name = 0x50060b000085daa9
N_Port Port World Wide Name = 0x50060b000085daa8
Switch Port World Wide Name = 0x0000000000000000
Switch Node World Wide Name = 0x0000000000000000
Driver state = AWAITING_LINK_UP
Hardware Path is = 0/2/1/0/4/0
Maximum Frame Size = 2048
Driver-Firmware Dump Available = NO
Driver-Firmware Dump Timestamp = N/A
Driver Version = @(#) libfcd.a HP Fibre Channel ISP 23xx & 24xx Driver B.11.11.10 /ux/kern/kisu/FCD/src/common/wsio/fcd_init.c:Sep 14 2006,17:45:41

#

[Ramesh S]

Hi

From the fcmsutil output

Previous Topology = UNINITIALIZED
Link Speed = UNKNOWN
Local N_Port_id is = None
Previous N_Port_id is = None
.
.
Driver state = AWAITING_LINK_UP

If "Driver state = AWAITING_LINK_UP", there is no link between the HBA and Disk array.It could be FC cacle issue, HBA issue, SAN switch side...

If you have FC loopbacks with you, you could connect it on HBA and check the HBA end.

Please check the physical link side.

Thanks & Regards

Ramesh

[mahan_1]

If "Driver state = AWAITING_LINK_UP", there is no link between the HBA and Disk array.It could be FC cacle issue, HBA issue, SAN switch side...

I chaneged the cable and also do not forget when i connect it to a hba on dl580 it is work

If you have FC loopbacks with you, you could connect it on HBA and check the HBA end:

i will check it , but also do not forget that i have two rp3440 and i have problem on both , also I change one of hba (a9784a) to a spare one

Please check the physical link side:

I change the sfp , cables and hba card.

[Torsten.]

Sounds strange ...

cable, hba, switch all checked and still not working? The HBA is 2Gb/s, please check if the switch (what model is it?) is fixed to 4Gb/s.

[mahan_1]

I also replace my san swich and controller with spare ,but still I have the problem.

[mahan_1]

I replace the san with that one work with another two rp3440 , so my san is fine , the problem is on anothe two rp3440 as I said i replaced the hba card too .
So i think my hardware is fine , and i should set something on rp3440 or hp-ux.

[mahan_1]

I replace the san with that one work with another two rp3440 and it worked so my san is fine , the problem is on anothe two rp3440 as I said i replaced the hba card too .
So i think my hardware is fine , and i should set something on rp3440 or hp-ux.

[Khairy]

this is strange.

since you say you didn't have any zoning, log in to san switch and perform reset to factory default.

disable the switch
> switchDisable

Change to factory default and then reboot
> configDefault
> reboot

Once the san switch is up, post the following output. At least we can see what actually been detected at san switch.
> nsallshow

Connect the black serial cable (which come with msa) to msa storage controller and post the following output:

CLI> show version
CLI> show units
CLI> show disks
CLI> show connections
CLI> show tech_support
CLI> show acl
CLI> show this_controller
CLI> show other_controller

[mahan_1]

As I said when I have two rack , in each rack is 2 rp3440 and one msa1000
my both msa1000 works with 2 rp3440 in rack A , and both do not work with 2 rp3440 in rack B , so something is wrong in this couple RP3440 , in addition I replace rp3440 hba cards (a9774a) with a spare one , so the cards and cables are right.

[mahan_1]

at last , i chage hba card with the on of hba card's work with san in rack A , the server on rack B worked , so i am sure the problem is hba card , i have no fail for cards and it is impossible if three cards have problem , may be they need firmware update or a command in hp-ux to active them to start negotiate to san.
Please advice me.

[Torsten.]

If I understand you right, you installed a card from the working server in the non-working server and this worked?

So the card is the only thing that was changed, right?

Let's compare a working and a non-working card:

# fcmsutil /dev/fcd0 vpd

And just for fun

# swlist | grep -i fib
(on the working and the non-working server)

[Steven E. Protter]

Shalom,

Sorry to re-hash.

Could be a bad switch, cable or card(s).

Also to work with an msa1000 and more than 1 HP-UX machine a firmware update was required.

This should be done anyway as firmware is the source of many hassles in storage.

SEP

[mahan_1]

the only thig I changed and problem solved is hba card , but it is unbelievable if I have 3 hba card (A9784A) with no failuer and do not work wiht msa1000
Please Advice Me.

[Khairy]

hi,

it seems you had answered your questions.

Assuming all the rp3440s are on same patch level and os version and same setup (hba etc), then uou should not have any problem with the MSA. This is based on the other 2xrp3440 (rack A) work well with the msa.

For rp3440s in rack B, you changed HBA and it works. Your question now, is it possible 3 units of HBA failed in the other rp3440? Based on my experience, yes, it is possible. If this server is still under warranty/maintenance, you may want to log a case with HP now....

[mahan_1]

But why I do not have any failuer on card and os claimed the hba?

[mahan_1]

Is it possible if HBA card firmware update solve my problem? if yes , which version of firmware?

[Torsten.]

You should not only ask, but answer questions you get too
;-)
(see postings above).

Within a HP9000 server (RISC-based) the firmware on a FC card is only used if you boot from this HBA over fiber channel.
If the OS is up and running, the driver will overlay the cards firmware.
So it is unlikely that a firmware update will change anything.

In case you have a bad or poor laser light, the card is not aware of this.
So it may be you have just some bad HBAs.

If you swap the HBAs from a working to a non working server and the problem will stay with the HBA you can be quite sure.

[mahan_1]

anyway tnx for your advice, it seems I should replace them with another new.