[dm-devel] Making failover work quickly with QLogic HBAs

[Duane Grigsby]

Lars,
Sorry for the late response. I would remove the "ql2xloginretrycount" parameter because it specifies how many times to re-login to the port once it returns.  Usually, OEMs set the correct value they need for their storage in the NVRAM and we get it from there. The qlport_down_retry is the main timer that affects how long we will keep the command before returning with DID_NO_CONNECT.  All the other parameters are ok as long as multipath can handle the fact that there are some targets can have no-paths available for a short period of time. 

Regards,
Duane

-----Original Message-----
From: dm-devel-bounces at redhat.com [mailto:dm-devel-bounces at redhat.com] On Behalf Of Lars Marowsky-Bree
Sent: Thursday, April 21, 2005 5:23 AM
To: dm-devel at redhat.com
Subject: [dm-devel] Making failover work quickly with QLogic HBAs

This will greatly speed up failover times; with the defaults, the
timeout values are just way too long for multipathing:

options qla2xxx ql2xfailover=0 ql2xioctltimeout=10 ql2xprocessnotready=0 ql2xloginretrycount=3 ql2xsuspendcount=3 ql2xretrycount=5 qlport_down_retry=3


Sincerely,
    Lars Marowsky-Brée <lmb at suse.de>

-- 
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business

--
dm-devel mailing list
dm-devel at redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel