I have an InfiniBand network working with SRP sharing.
On the target system, I am running targetcli (the -fb free branch
version) and OpenFabric's srptools.
On the initiator system, I am running OpenFabric's srptools.
After I've gotten srp on the initiator to link a SRP target as a local
Two up to date arch systems. Kernel 4.1.2 (Arch -2).
2 Mellanox MT25418 [ConnectX VPI PCIe 2.0 2.5GT/s - IB DDR / 10GigE]
(rev a0) running mlx4_core driver v2.2-1 (Feb, 2014.) Both on most
recent firmware for PSID MT_04A0110002, FW Version 2.9.1000. Systems
directly connected, no switches.
e "-n" flag, how can I find out what my
initiator is going to send as initiator_ext, so the target can be set
up to work with it?
Or, can I set my own initiator_ext, it looks by appending it to
/etc/srp_daemon.conf ?
Why doesn't ibsrpdm give the initiator_ext value?
On Wed, Jan 6,
e "-n" flag, how can I find out what my
initiator is going to send as initiator_ext, so the target can be set
up to work with it?
Or, can I set my own initiator_ext, it looks by appending it to
/etc/srp_daemon.conf ?
Why doesn't ibsrpdm give the initiator_ext value?
On Thu, Dec 31,
I'm at a loss on how to get the hex address to go underneath acls when
setting up srpt. If I use the fe80 prefix I see everywhere including
/sys, it gets rejected. If I use the prefix shown in the kernel
rejection method, which I can't find anywhere else, it works fine.
I am using targetcli,
I'm at a loss on how to get the hex address to go underneath acls when
setting up srpt. If I use the fe80 prefix I see everywhere including
/sys, it gets rejected. If I use the prefix shown in the kernel
rejection method, which I can't find anywhere else, it works fine.
targetcli configuration:
