VMware Cloud Community
MPCDI
Enthusiast
Enthusiast

ESX 4.0 QLogic HBA QLA4062c Settings?

I'm connecting 3 ESX 4.0 host to a Dell EqualLogic and am configuring the qla4xxx module for best I/O performance. The HBA cards are QLogic 4062c.

Does anyone know the proper settings for;

ql4xmaxqdepth

ql4xportdownretrycount

I have configured the following as well;

IP_ARP_Redirect = On

KeepAliveTO = 14

ExeThrottle = 128

Large_Frames = On (It's a Dual Port HBA)

0 Kudos
8 Replies
BenConrad
Expert
Expert

Your KATO should be 60-120 rather than 14.

AND

esxcfg-module -s 'ql4xmaxqdepth=200 ql4xportdownretrycount=60' qla4022

esxcfg-boot -p

esxcfg-module -g qla4022

Ben

0 Kudos
MPCDI
Enthusiast
Enthusiast

The KATO cannot be changed to anything higher than its current value.

I have attempted to change it via the following command;

iscli -n 0 KeepAliveTO 120

iscli -n 1 KeepAliveTO 120

or

iscli -n 0 KeepAliveTO 60

iscli -n 1 KeepAliveTO 60

But when I run;

iscli -c 0

iscli -c 1

It shows it still at 14.

Also the command of 'esxcfg-module -s 'ql4xmaxqdepth=200 ql4xportdownretrycount=60' qla4022' does not work with ESX 4. I tried it and the qla4xxx module fails to load with a "Bad Parameter". The module is now known as qla4xxx. The parameters of ql4xmaxqdepth and ql4xportdownretrycount are not valid in qla4xxx. They currently had me run;

esxcfg-module -s "ka_timeout=120" qla4xxx

Which seems to be working.

FYI:

The current valid parameters for qla4xxx are (you can get this by running “vmkload_mod -s qla4xxx”)

heap_max:

heap_initial:

ka_timeout:

recovery_tmo:

cmd_timeout:

extended_error_logging:

ql4xdontresethba:

ql4xdiscoverywait:

I hope this helps anyone else who is having issues.

0 Kudos
BenConrad
Expert
Expert

Thx for ka_timeout, have not implemented vSphere yet, waiting for Update1.

Does '/usr/local/bin/iscli 0 -n KeepAliveTO 120' not work properly on the QLA?

Ben

0 Kudos
glynnd1
Expert
Expert

Also the command of 'esxcfg-module -s 'ql4xmaxqdepth=200 ql4xportdownretrycount=60' qla4022' does not work with ESX 4. I tried it and the qla4xxx module fails to load with a "Bad Parameter". The module is now known as qla4xxx. The parameters of ql4xmaxqdepth and ql4xportdownretrycount are not valid in qla4xxx. They currently had me run;The ESX4 version of hte command is slightly different:

Old: esxcfg-module -s 'ql4xmaxqdepth=X ql4xportdownretrycount=Y' qla4022

New: esxcfg-module -s 'ql4xmaxqdepth=X' 'ql4xportdownretrycount=Y' qla4xxx

Note the extra ' marks.

I don't have a position on the values for X and Y.

0 Kudos
MPCDI
Enthusiast
Enthusiast

I also tried;

esxcfg-module -s 'ql4xmaxqdepth=32' qla4xxx

and

esxcfg-module -s ql4xmaxqdepth=32 qla4xxx

With the same "Bad Parameter" result

I tried your suggestion of esxcfg-module -s 'ql4xmaxqdepth=X' 'ql4xportdownretrycount=Y' qla4xxx (copied and pasted it) but the results were Invalid module name ql4xportdownretrycount=60

I even tried it withOUT the space between the two parameters. It accepted the command, but the end results were;

# esxcfg-module -g qla4xxx

qla4xxx enabled = 1 options = 'ql4xmaxqdepth=200ql4xportdownretrycount=60'

With the same "Bad Parameter" result during boot.

0 Kudos
MPCDI
Enthusiast
Enthusiast

The command of /usr/local/bin/iscli 0 -n KeepAliveTO 120 works to change it to 120 on 1 of the servers but it doesn't work on the other 2 ESX Host. It reverts them back to 14.

0 Kudos
joergriether
Hot Shot
Hot Shot

refreshing this one because i wonder if it was/is possible to enter the parameters in the interface, NOT in the command line one-time-shot.

like this:

enter iscli and....

4 (port level), 3 (edit configured..), 3 (port firmware setting), 7 (conf adv. settings)

ExeThrottle 128

IP_ARP_Redirect on

KeepAliveTO 130

does it work this way?

best regards

Joerg

0 Kudos
sevenp
Enthusiast
Enthusiast

How to install / use ISCLI on ESXi? We running vSphere 4.1 and want to configure our HBAs.

Regards

0 Kudos