Aniruddha Bohra wrote:
Hello,
I tried connecting 2 endpoints using the new uDAPL library.
The connection fails with an invalid route option.
Attached is the log with DAT_DBG_TYPE=0xffff and DAPL_DBG_TYPE=0xffff.
I traced the call to ib_at_route_by_ip(),
It seems like all the arguments (dst_ip, src_ip, r_qual..) are 0x00.
I have also attached my dat.conf, lsmod, /etc/ibhosts, and /etc/hosts.
Could you please direct me where to look?
Looks like your configuration is ok.
The debug message prints the dest GID on return which is a little
misleading since the route information is not updated until the async
callback fires. I will change this to print the src and dst ip addresses.
What address are you using for dap_ep_connect? The src_ip address will
be set to 10.10.10.12 which was retrieved from the hca_open and the
dst_ip address is taken from your (struct sockaddr_in *)
remote_ia_address provided with your dat_ep_connect call. Did you
ifconfig the IPoIB devices on both sides? Can you ping using the IPoIB
addresses?
Thanks,
-arlin
Thanks
Aniruddha
dapl_ep_connect (0x8057218, {4294967280.4294967295.4294967295.4294967295},
4A275800, 0, -1, (nil), 0, 0)
connect: r_SID 1244092416, pdata (nil), plen 0
connect: at_route ret=-1,Invalid argument req_id 0 GID 0000000000000000
0000000000000000
ib_at_route_by_ip Invalid argument
destroy_cm_id: conn 0x80832c8 id 134755424
dapl_ep_connect () returns 0x50000
_______________________________________________
openib-general mailing list
[email protected]
http://openib.org/mailman/listinfo/openib-general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
