[ewg] ib_acme fails for requests with IPv4 addresses (ofed 3.5)

[Hefty, Sean]

Note that you can test each node separately by making the source/destination addresses the same.  This may show that your first system, rc002, is working, but rc003 is not.

> On the second node, the ib_acme command fails only for IPs, too. But it returns
> with a different message ('Cannot assign requested address'):
> ===============================================================================
> ==
> rc003 ~/tmp/ibacm-1.0.7 $ ib_acme -f i -s 10.0.0.52 -d 10.0.0.51 -v -P -V
> Service: localhost
> Destination: 10.0.0.51
> Source: 10.0.0.52
> ib_acm_resolve_ip failed: Cannot assign requested address
> SA verification: failed Cannot assign requested address
> 
> Error Count,Resolve Count,No Data,Addr Query Count,Addr Cache Count,Route Query
> Count,Route Cache Count
> localhost,1,2,0,0,0,0,0
> return status 0x0
> 
> rc003 ~/ $ cat /var/log/ibacm.log
> ...
> 1363872021.460: acm_svr_accept:
> 1363872021.460: acm_svr_accept: assigned client 0
> 1363872021.460: acm_server: receiving from client 0
> 1363872021.460: acm_svr_receive: client 0
> 1363872021.460: acm_svr_resolve_dest: client 0
> 1363872021.460: acm_svr_resolve_dest: src  10.0.0.52
> 1363872021.460: acm_get_ep: 10.0.0.52
> 1363872021.460: acm_get_ep: notice - could not find 10.0.0.52

It doesn't appear that the ibacm address information is correct.  Having the complete log file may help.  The assigned address configuration would end up being near the top of the log file.

ibacm uses an address file, ibacm_addr.cfg, to assign address information to ports.  If this file is not present, it will be created.  It's a text file, and the format is hopefully straightforward to follow.  As a couple of places to look , the file may be in:

/etc/rdma/ibacm_addr.cfg
/usr/local/etc/rdma/ibacm_addr.cfg

If you find the file, the simplest thing to do may be to just remove it.  You can look at the existing file to see that the correct IP address has been assigned to the right port.

- Sean