-
Problems with QLA2462
Hello,
i wrote already that i have the problem with the "No Cable", but now i installed the current RC (or Beta? Ver. 2956) and in the "Setup / Fibre Chennel" the DSS told me that there is no FC HBA.
After upgrade the Kernel is switched back to 32 Bit, so i changed it to 64 Bit but then the controller will be shown in "Status / Hardware" but not in "Setup / Fibre Channel". :confused:
Has anybody some ideas?
I will try what happens when i switch back to 32 Bit and then back to Initiator mode, if i remember right i switched to Target mode with the 32 Bit kernel. Perhaps i must change this when the 64 Bit kernel is running... I tested already with the normal kernel and with the testing kernel.
Best regsrds
Stefan
-
As i wrote i tested the scenarios... In 64 Bit only the Initiator Mode works, when switching to Target i got a message that no FC HBA is installed...
Best regards
Stefan
-
I was trying to see if I could duplicate the problem from my end and was not able too - I have the same Qlogic HBA's "ISP2432-based 4Gb Fibre Channel to PCI Express HBA (rev 03)" with version 2956. On the Target I have set to use 32bit single and SMP with TESTING (kernel 2.6.23) also I did a direct connection between the 2 DSS and still was able to connect them both. Both HBA's are at configuration defaults and the only system reboot was the Target system after setting as Target in: SETUP -> Fibre Channel -> Function: QLOGIC Target. So everything was configured from defaults.
-
Since when is the QLE2462 supported in Target mode? On the Open-E Web-Site this is not listed and because this i got a QLA2462 (PCI-X).
And have you tested with a 64 Bit kernel? In 32 Bit the controller was found in Target mode...
Best regards
Stefan
-
It is listed.
http://open-e.com/data_storage_solution/server/service_and_support.php?lang=en&subserv=prodcomp&h ardkind=Fibre%20Channel%20HBA<br>%20(target%20mode )
-
Call me stupid, but i see only QLA Controllers and not a QLE...
QLA2462 -> PCI-X
QLE2462 -> PCI-Express
Best regards
Stefan
-
-
Typo on my end, I meant my target is a QLA2462 and initiator QLE2462 tested with directly attached and with the Sanbox 5600.
-
O.k. ;) Please can you check with a 64 Bit kernel in Initiator mode? In the Build before (2922) the controller was found...
Best regards
Stefan
-
I'll be out for the holidays and will test when I get back - any one else that can test this with 64bit and build 2854.
-
o.k. i wish you and all the others a merry christmas!
Stefan
-
Yesterday in activated the previous version and FC in Target mode works. But i can't access te LUN from ESX. I can't create a vmfs or a rdmp...
- When i want to create a VMFS, igot a message that tha partition can't be read.
- When i want to create a RDMP i got this messages in the log:
Task Created : haTask-1344-vim.VirtualMachine.reconfigure-1785
State Transition (VM_STATE_OFF -> VM_STATE_RECONFIGURING)
Could not get canonical path for /vmfs/volumes/.../srv08/srv08.vmdk: No such file or directory
DISKLIB-LINK : "/vmfs/volumes/.../srv08/srv08.vmdk" : creation successful.
DISKLIB-VMFS : "/vmfs/volumes/.../srv08/srv08-rdmp.vmdk" : open successful (17) size = 312552194048, hd = 0. Type 10
DISKLIB-VMFS : "/vmfs/volumes/.../srv08/srv08-rdmp.vmdk" : closed.
DISKLIB-VMFS : "/vmfs/volumes/.../srv08/srv08-rdmp.vmdk" : failed to open (2490377): AIOMgr_Open failed. Type 10
DISKLIB-DSCPTR: Failed to open extents for descriptor file in normal mode
DISKLIB-LINK : "/vmfs/volumes/.../srv08/srv08.vmdk" : failed to open (Function not implemented).
DISKLIB-CHAIN : "/vmfs/volumes/.../srv08/srv08.vmdk" : failed to open (Function not implemented).
DISKLIB-LIB : Failed to open '/vmfs/volumes/...0/srv08/srv08.vmdk' with flags 0 (Function not implemented).
Foundry operation failed with system error: Function not implemented (38), translated to 1
Failed to get result state: CreateBacking: Error: Internal error
Event 39 : Failed to create virtual disk /vmfs/volumes/.../srv08/srv08.vmdk Reconfigure failed
And when i try to low level format the disk from the hosts QLogic BIOS i got an error too. But verify works.
Best regards
Stefan
-
Hi Stefan,
i have a similar configuration:
DSS on a box with some TBs and QLA234X Dualport in Targetmode
are you able to rescan the vmhba?
how much capacity?
-> /proc/vmware/scsi/vmhba#/T:L
-> VI-Client -> Configuration -> Storage Adapters -> T:L
-> VI-Client -> Configuration -> Storage -> Add Storage
4 days ago i had an issue reporting the lun capacity as none instead of for instance 500GB. My problem was a bad GBIC on host side in my fc switch. After replacing all was fine. I saw some errors on switch level and /var/log/vmkernel
I could also try to use the fdisk command for creating partitions and formating with vmfs3.
- esxcfg-vmhbadevs -> which /dev/sd# for a given vmhbaC:T:L
- fdisk /dev/sd#
n
p
1
ENTER
ENTER
t
fb
x
b
1
128
w
- vmkfstools -C vmfs3 -S DS-Name vmhbaC:T:L:1
come back with any questions regarding ESX3 and DSS on that place
Erich Popp
-
Hi Erich,
i just wrote my current problems with ESX here:
http://forum.open-e.com/showthread.php?p=2156#post2156
The problem is had before, i created the LUN's with a blocksize of 4096 bytes. It seems that ESX can only handle 512 bytes blocksize...
Regards
Stefan
-
Hi Stefan,
i can confirm that fc connect with my equipment isn't working with 4k blocks. After creating with 512B blocks fc worked for me.
regards Erich
