After applying all of the March - May patches and 3 reboots my iSCSI HBAs no longer have IP addresses. When I click "Properties..." and set the IP the console reports success, but the address remains 0.0.0.0
Hardware= IBM Blade 8843-45U, Qlogic QMC4052, Bios 1.04, Firmware 2.00.00.07.
When using the Q during boot both adapters have proper addresses but can not PING anything in the subnet, not even themselves.
I called IBM support to get the bios and fw updated, but they said VMware might want the older versions.
Does anyone know what versions VMware desires?
Any other ideas?
Thanks,
Greg.
http://www.vmware.com/pdf/vi3_io_guide.pdf
page 13 -
2 QLogic iSCSI adapters require minimum BIOS v1.09 and minimum
firmware v2.00.00.38.
By us all hbas have a bios 1.09 - none problems at all - running with EQL.
I know that with the older version you can't run jumbo frames (e.g.)
http://www.vmware.com/pdf/vi3_io_guide.pdf
page 13 -
2 QLogic iSCSI adapters require minimum BIOS v1.09 and minimum
firmware v2.00.00.38.
Christian, Thanks very much for finding the "fine print" for me.
I found the FW and BIOS at IBM/Qlogic, but they want me to run "SANSurfer" on the local box. Can you do this on an ESX server?
I am 400 miles away from the server and hoping to upgrade remotely via the BladeCenter management module.
Cannot flash through the BladeCenter management console.
Qlogic has a dos utility on the same page where the files are.
All I had to do was get someone to put a floppy in the drive at the remote site.
Flashing the server now... we will see what happens.
Well, we are half way there.
In the VI client / Configuration / Storage Adapters.
I gave the first HBA a static address and it took it fine.
Did a rescan and it saw the storage.
I tried to give the 2nd HBA a static address and a window popped twice that says,
"A configuration change requiring a reboot has occurred. Please restart the host."
When I restarted the host neither adapter shows an IP address inside VI Client. They both show an address at the Q screen.
I can run with one adapter, but there is no redundancy, and it looks like I must manually config the HBA after a reboot.
Now that I am at the "preferred" bios and fw I will call tech support.