On Nov 22, 2013, at 1:19 PM, Paul Kapinos <kapi...@rz.rwth-aachen.de> wrote:
> Well, I've tried this path on actual 1.7.3 (where the code is moved some 12 > lines - beginning with 2700). > !! - no output "skipping device"! Also when starting main processes and > -bind-to-socket used. What I see is > >[cluster.rz.RWTH-Aachen.DE:43670] btl:usnic: found: device mlx4_1, port 1 > >[cluster.rz.RWTH-Aachen.DE:43670] btl:usnic: this is not a usnic-capable > >device > >[cluster.rz.RWTH-Aachen.DE:43670] btl:usnic: found: device mlx4_0, port 1 > >[cluster.rz.RWTH-Aachen.DE:43670] btl:usnic: this is not a usnic-capable > >device That's actually ok -- that's from the usnic BTL, not the openib BTL. The usnic BTL is the Cisco UD verbs component, and it only works with Cisco UCS servers and VICs; it will not work with generic IB cards. Hence, these messages are telling you that the usnic BTL is disqualifying itself because the ibv devices it found are not Cisco UCS VICs. Look for the openib messages, not the usnic messages. -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
