Unsolved
This post is more than 5 years old
2 Posts
0
30816
Unable to provide VLAN id to access iSCSI lun in my blade servers M620 via Qlogic QME8262-k HBAs
QLogic FastUtil! utility doesn't have option to provide VLAN id in order to access the iSCSI target lun. Please advice.
Gowri
Anonymous
274.2K Posts
0
April 21st, 2015 11:00
Hello Gowri,
Are you trying to use DCB or just VLAN tagging? Without DCB configured, the EQL array won't support VLAN tags. DCB requires switches that properly support iSCSI DCB (vs. just FCoE) and are properly configured.
Have you checked with Qlogic support?
Regards,
Don
gshanmugam
2 Posts
0
April 21st, 2015 13:00
Firstly, we don't have EQL storage array or DCB in our environment.
Here's a small recap of our current environment.
Our M1000e Chassis has the following I/O Fabric Interfaces configured
Fabric A with 10 GbE KR BRCM 10GbE 2P 57810s bNDC
Fabric B with 10 GbE (KR Only) QLogic 10GbE 2P QME8262-k Mezz
We've configured VLANs for all network communications (public and SAN related) in both Fabric A and B switches and we have multiple SAN's(Nimble and Netapp) each in their own subnet. I don't have any problem in accessing a target iscsi lun using fabric A & broadcom nics. But when I try to do the same using fabric b and qlogic nics, for some reason, I don't get the link and iscsi login is failing during booting of machine. We are using iSCSI protocol for accessing SAN luns. During the system boot, my qlogic nics are listed as iBFT and they attempt to login into iscsi target lun and failing. I need your help in resolving this issue.
Thanks,
Gowri
Anonymous
274.2K Posts
0
April 21st, 2015 15:00
Hello Gowri,
You've posted your question in the Equallogic forum, which is why I assumed you were using Dell / EQL storage.
I would suggest you open a support case.
Regards,
SysAdminTX
13 Posts
0
April 22nd, 2015 07:00
What kind of switches do you have in fabric B on the M1000e chassis? Or do you use passthrough modules?
If they are switches, you could consider assigning an IP to each VLAN you want to use and verify you can then ping them from the host. If you can, then you want to test pinging the next device (LAN switch VLAN, or maybe directly to the Nimble or NetApp SAN?).
This wouldn't be a solution, but may help you identify where your communication stops so you know what part to troubleshoot.