-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fibre Channel is not discoverable on demo mode #179
Comments
ATTRIBUTE CONFIG GROUPcache_dynamic_acls=1 |
Hello, I don't have the hardware to test it personally but I asked a colleague of mine to help, I will post an update as soon as I have some news |
thanks, |
Hello I will look into this option, test it and get back to you. Regards |
I tested this on Fedora33 My target looks like this. [root@jammerfed34 ~]# targetcli ls Now take two new initiators [root@ml150 ~]# cat /sys/class/fc_host/host*/port_name Add the attribute to generate_node_acls=1 each of the naa.xxx for the target Try connect from the new initiators and it does not work. I will investigate but I suspect this has never been used for qla2xxx F/C tcm_qla2xxx, and really only has been used on ISCSI. Regards |
Hello OK, I looked at the source here Maurizio can comment further, we should probably fix the bug in the manpage then [loberman@jammerfed34 targetcli-fb-2.1.53]$ grep generate_node_acls targetcli/ui_target.py
Thanks |
so what should we do if we want to use FC in demo mode(share globally)? and everyone that connects to that port can see and use share? |
I think you are right, I looked at the kernel code and despite the fact that |
is this problem solved at 2.1.54 release? or not? |
I compiled and installed the latest targetcli 2.1.53 and rtslib and configshell on centos 8.3 to activate qla2xxx target driver shell and rtslib
also, I used a new 5.10 elrepo kernel that includes tcm_qla2xxx and other target drivers for targetcli
when I configure qla2xxx on the target side it configures correctly and shows everything well
but on the initiator side, I cannot discover targets unless I enter initiator ACL on targetcli
so the gen-acl function does not work and I can not share globally without setting ACL's one by one by enabling generate_node_acls=1 like iSCSI on attributes?
my target card is QLogic qle2672 and my initiator card is Emulex (Broadcom) lpe16002B and they connected back-to-back correctly and work fine if I set ACL's on targetcli
what should I do? is it a bug? or something else?
The text was updated successfully, but these errors were encountered: