ESX 3.02 and MSA1000 installation Problem

[mesut]

I try to test ESX server 3.02 on and Tyan Transport TX46,

I have 4 CPU's at 2400 Mhz 16 GB RAM.

Fibere Channel HP1142SR and MS1000.

Each time I try to install from the CD Qlogic drivers gives and error

"qla24xx_abort_command" and tries to reset the driver then never regicnose the HBA card.

My question is what should be the possible settings for Fast!util and settings for MSA1000 to get EXS installation to not to reset the card driver?

In normal windows envoriment I have no problem with MSA1000.

HBA is set to poin-to-point communication and the connection is in F_port mode.

Thanks,

[oreeh]

You can't use Linux drivers with ESX.

If the HBA is not supported (check the HCL) you are out of luck.

Regarding the MSA1000 configuration check the SAN configuration guide.

Basically you need to set the connection profile to Linux and create the appropriate connections and ACLs.

[mesut]

Thanks for your answer,

But it is on the HCL list.

I found this document

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100230...

My be may problem is that.

Is thare a way to corret that problem from the booting installation CD ?

[oreeh]

But it is on the HCL list.

I didn't verify this.

My be may problem is that.

Not very likely, since you are not running a MSCS.

[mesut]

My product is

http://www.qlogic.com/Products/SAN_products_FCHBA_QLE2460.aspx

seems to be on HCL.

During the installation ESX installation routines finds the card. Bu at the end gives and error eh_abort and rescans the adapter and finally doesn't find any Fibre channel controller.

[Texiwill]

Hello,

You will need to verify that the ACLs on the MSA1000 and switch zoning allow for your ESX server to see the LUN. In general if the hardware is supported and at the proper firmware level, then it is a SAN Presentation/Zoning issue.

My suggestion is to check the presentation from the MSA see if the connection has been properly added with a OS of Linux, verify your ACLs, and the Switch zoning. then lastly the cables. I have an MSA1000 that works with no issues.

Best regards,

Edward L. Haletky, author of the forthcoming 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', publishing January 2008, (c) 2008 Pearson Education. Available on Rough Cuts at http://safari.informit.com/9780132302074

[mesut]

Thanks for your answer,

I check the ACL:

ACL is enabled:

Connection WWPN Units

virtualserver1 500110A0-0016E252 0, 1

Inaccessible Units: None

So seems to be ACL is ok.

Any suggestion?

[Texiwill]

Hello,

In general all problems with SANs are really in the fabric when connecting to an ESX server. Check the Connection definition, Check the Unit, check the zoning in the switch, check the cables, etc.

I would also make a call into HP Storage Support and verify the firmware on your SAN, QLE, etc. If things are presented properly then ESX will see them. You could also have a bad FC-HBA card. Verify the hardware, etc and then see what is left.

Best regards,

Edward L. Haletky, author of the forthcoming 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', publishing January 2008, (c) 2008 Pearson Education. Available on Rough Cuts at http://safari.informit.com/9780132302074

[mesut]

Hello,

Thanks for your concern. May be this picture will help more to figure aout what is wrong.

Regards,