Re: [OMPI users] Different Interfaces on Different Nodes .. OpenMPI 1.2.3, 1.2.4 ..
Hi Graham, Have you tried running without the btl_tcp_if_include line in the .conf file? Open MPI is usually smart enough to auto detect and choose the correct interfaces. Hope this helps, Tim Graham Jenkins wrote: We're moving from using a single (eth0) interface on our execute nodes to using a bond interface (bond0) for resilience. And what we're seeing on those nodes which have been upgraded is: -- [0,1,1][btl_tcp_component.c:349:mca_btl_tcp_component_create_instances] invalid interface "eth0" -- This of course, is because all nodes share a common copy of openmpi-mca-params.conf .. in which its says: -- btl_tcp_if_include=eth0 -- So .. does anybody have a suggestion for a way around this during our migration/upgrade period? If we place "bond0" in there as well, then we get error messages about whichever one is absent on the node where execution is happening. Regards ..
[OMPI users] Different Interfaces on Different Nodes .. OpenMPI 1.2.3, 1.2.4 ..
We're moving from using a single (eth0) interface on our execute nodes to using a bond interface (bond0) for resilience. And what we're seeing on those nodes which have been upgraded is: -- [0,1,1][btl_tcp_component.c:349:mca_btl_tcp_component_create_instances] invalid interface "eth0" -- This of course, is because all nodes share a common copy of openmpi-mca-params.conf .. in which its says: -- btl_tcp_if_include=eth0 -- So .. does anybody have a suggestion for a way around this during our migration/upgrade period? If we place "bond0" in there as well, then we get error messages about whichever one is absent on the node where execution is happening. Regards .. -- Graham Jenkins Senior Software Specialist, eResearch Monash University (Clayton Campus, Bldg 11, Rm S503) Email: graham.jenk...@its.monash.edu.au Tel: +613 9905-5942 (office) +614 4850-2491 (mobile)
