»
Member icons
HP moderator
Expert in this area
Member status
ITRC Pro
250 points
ITRC Graduate
500 points
ITRC Wizard
1000 points
ITRC Royalty
2500 points
ITRC Pharaoh
7500 points
Olympian
20000 points
1-Star Olympian
40000 points
2-Star Olympian
80000 points
»
How to earn points
»
Support forums FAQs
Question status
Magical answer
Message with a response that solved the author's question
Favorites status
Add to my favorites
Delete from my favorites
Thread closed
compiler
Hi.
I have a working system with a dual port HBA connected to an HP MSA2000 storage solution. Both HBA ports are connected to the MSA2000.
I need to write a script to monitor that both fiber paths are ready and no path has been lost.
I have the following binary available:
[root@fe04 hp_fibreutils]# ./adapter_info
/proc/scsi/qla2xxx/1: STATE=READY WWNN=5001438003b0f997 WWPN=5001438003b0f996
/proc/scsi/qla2xxx/0: STATE=READY WWNN=5001438003b0f995 WWPN=5001438003b0f994
The above "STATE=READY" can be used to monitor both data paths? Or they just refer to the status of the hba-port itself?
If a fiber cable is removed from one of the HBA port's, the above command would reflect it? What would be the value of STATE= in that case?
If not, how can I monitor it? Maybe a /proc entry? The best "alternative" I've found is the following:
[root@fe04 hp_fibreutils]# grep -i state /proc/scsi/qla2xxx/*
/proc/scsi/qla2xxx/0:Host adapter:loop state = <READY>, flags = 0x1a13
/proc/scsi/qla2xxx/1:Host adapter:loop state = <READY>, flags = 0x1a13
Thanks a lot.
Note: If you are the author of this question and wish to assign points to any of the answers, please login first.For more information on assigning points ,click
here
Sort Answers By:
Date or Points
Bharath Pingali
Nov 6, 2009 03:42:06 GMT
Unassigned
Hello Compiler, adapter_info will display HBA port status only. As you are using both ports and OS is linux, i guess that you are using multipathing software (Device-Mapper). Which linux version are you running? multipath -ll | egrep -i "failed|faulty" should display if any paths fail or you can always grep for "failing" on "/var/log/messages". Hope this helps. -Thank You Bharath
compiler
Nov 6, 2009 07:50:30 GMT
N/A: Question Author
> As you are using both ports and OS > is linux, i guess that you are using > multipathing software (Device-Mapper). Multipathing software, AFAIK, is not needed with the QLA drivers shipped with HP Proliant Support Pack. You just configure the controllers as active-pasive failover: [root@fe04 ~]# cat /etc/modprobe.conf.hba options qla2xxx ql2xmaxqdepth=16 qlport_down_retry=30 ql2xloginretrycount=30 ql2xfailover=1 ql2xl bType=0 ql2xautorestore=0xa ConfigRequired=0 remove qla2xxx /sbin/modprobe -r --first-time --ignore-remove qla2xxx && { /sbin/modprobe -r --ign ore-remove qla2xxx_conf; } So I can't use multipathing software binaries to determine link's status ... Any other idea?
Santhosh Kumar Theyyan
Nov 6, 2009 13:21:05 GMT
Unassigned
Follwoign has been helpful for me cat /proc/scsi/qla2300/1|grep -i dropped Commands retried with dropped frame(s) = 0
Bharath Pingali
Nov 6, 2009 16:48:21 GMT
Unassigned
Hello Compiler, Check with your HP rep, MSA 2000 is not supported by Qlogic Failover. You have to use device Mapper. hope this helps. -Thank You Bharath
compiler
Nov 9, 2009 07:50:36 GMT
N/A: Question Author
> Check with your HP rep, MSA 2000 is not > supported by Qlogic Failover. > > You have to use device Mapper. How is that possible? I remember, when we installed the machine, to do a failover test while writing to the MSA, and after 20-30 seconds, the O.S. continued writing to the "alternate" path :-?
Uwe Zessin
Nov 9, 2009 09:53:29 GMT
Unassigned
"Unsupported" does not mean: "nothing works". I know one should not compare computers and cars, but think about this: Driving on a motorway in the wrong direction is "unsupported". But sometimes people can make it over quite a distance without something bad happens. In the computer world "Unsupported" often means: - the vendor did not test a certain combination and cannot guarantee that it (MSA2000 with QLogic failover driver) works properly - the vendor tested a certain configuration, found some problems and decided that he does not want to fix it, so he declares it "Unsupported"