[openib-general] [openfabrics-ewg] Problems with OFED IPoIB HA on SLES10
Vladimir Sokolovsky
vlad at mellanox.co.il
Tue Oct 3 23:38:08 PDT 2006
Hi Scott,
You have an old version of ipoibtools package (ipoib_ha.pl).
All issues you are talking about were fixed in the new version which
will be available in OFED-1.1-rc7.
You can also download it from SVN:
https://openib.org/svn/gen2/branches/1.1/src/userspace/ipoibtools
Thanks,
Regards,
Vladimir
On Tue, 2006-10-03 at 14:53 -0700, Scott Weitzenkamp (sweitzen) wrote:
> Vlad, thaks for the fast response. I have some followup questions
> about configuring IPoIB HA, see below.
>
>
> 3) I got IPoIB HA working on SLES 10, but the
> documentation is a little lacking. Looks like I have to put the same
> IP address in ifcfg-ib0 and ifcfg-ib1, is this correct?
>
>
> Yes, IP address should be the same. Actually the configuration
> of the secondary interface does not matter.
> The High Availability daemon reads the configuration of the
> primary interface and migrates it between the interfaces in case of
> failure.
>
>
> If I don't have an ifcfg-ib1 file, then ipoib_ha.pl won't start.
>
> If I don't have an ifcfg-ib1, then ipoib_ha.pl won't start. I would
> prefer to not configure ifcfg-ib1 since I don't plan to use it.
>
> # ipoib_ha.pl --with-arping --with-multicast -v
> Can't open conf /etc/sysconfig/network/ifcfg-ib1: No such file or
> directory
> Can't open conf /etc/sysconfig/network/ifcfg-ib1: No such file or
> directory
> Can't open conf /etc/sysconfig/network/ifcfg-ib1: No such file or
> directory
> Can't open conf /etc/sysconfig/network/ifcfg-ib1: No such file or
> directory
> Can't open conf /etc/sysconfig/network/ifcfg-ib1: No such file or
> directory
> ...
>
> If I put different IP addresses in ifcfg-ib0 and ifcfg-ib1, then the
> ifcfg-ib1 IP address is used for both ib0 and ib1!
>
> # pwd
> /etc/sysconfig/network
> # cat ifcfg-ib0
> DEVICE=ib0
> BOOTPROTO=static
> IPADDR=192.168.2.46
> NETMASK=255.255.255.0
> ONBOOT=yes
> # cat ifcfg-ib1
> DEVICE=ib1
> BOOTPROTO=static
> IPADDR=192.168.6.46
> NETMASK=255.255.255.0
> ONBOOT=yes
> # /etc/init.d/openibd start
> Loading HCA driver and Access Layer: [ OK ]
> Setting up InfiniBand network interfaces:
> ib0 device: Mellanox Technologies MT25208 InfiniHost III Ex
> (Tavor com
> patibility mode) (rev 20)
> ib0 configuration: ib1
> Bringing up interface ib0: [ OK ]
> ib1 device: Mellanox Technologies MT25208 InfiniHost III Ex
> (Tavor com
> patibility mode) (rev 20)
> Bringing up interface ib1: [ OK ]
> Setting up service network . . . [ done ]
> # ifconfig ib0
> ib0 Link encap:UNSPEC HWaddr
> 00-00-04-04-FE-80-00-00-00-00-00-00-00-00-00
> -00
> inet addr:192.168.6.46 Bcast:192.168.6.255
> Mask:255.255.255.0
> inet6 addr: fe80::202:c902:21:700d/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:2044 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:128
> RX bytes:0 (0.0 b) TX bytes:224 (224.0 b)
>
> # ifconfig ib1
> ib1 Link encap:UNSPEC HWaddr
> 00-00-04-05-FE-80-00-00-00-00-00-00-00-00-00
> -00
> inet addr:192.168.6.46 Bcast:192.168.6.255
> Mask:255.255.255.0
> inet6 addr: fe80::202:c902:21:700e/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:2044 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:128
> RX bytes:0 (0.0 b) TX bytes:304 (304.0 b)
>
> Notice how both ib0 and ib1 have the IP address from ifcfg-ib1. This
> contradicts this info from ipoib_release_notes.txt:
>
>
> b. The ib1 interface uses the configuration script of
> ib0.
>
>
>
>
> Scott
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/general/attachments/20061004/b527f331/attachment.html>
More information about the general
mailing list