ipdiscover and hosts with bonded interfaces

Bug #1276834 reported by Daniel Rich
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OCS Inventory: Server
Invalid
Undecided
Unassigned

Bug Description

(this was originally reported in the forums: http://forums.ocsinventory-ng.org/viewtopic.php?id=13196)

The OCS Inventory ipdiscover code seems to have issues with hosts that have bonded interfaces. For almost all of my servers with bonds, I'm seeing them both in the inventory *and* in ipdiscover, with the same MAC address in both. For example, one of my LDAP servers has the following in the interface inventory:

Description Type Speed MAC address Status IP address Netmask Gateway Network number DHCP IP
bond0 Ethernet F4:CE:46:B9:3B:F4 Up 10.110.10.203 255.255.255.0 10.110.10.1 10.110.10.0
eth0 Ethernet F4:CE:46:B9:3B:F4 Up 10.110.10.1 0.0.0.0 10.110.10.149
eth1 Ethernet F4:CE:46:B9:3B:F4 Up 10.110.10.1 0.0.0.0

yet also shows up in ipdiscover for the 10.110.10 subnet with a duplicated entry (with the hostname replaced):

IP address MAC address Netmask Date DNS name Delete Register
10.110.10.203 f4:ce:46:b9:3b:f4 (Hewlett Packard) 255.255.255.0 2013-08-14 14:03:27 hostname.example.com
10.110.10.203 f4:ce:46:b9:3b:f4 (Hewlett Packard) 255.255.255.0 2013-08-14 14:03:27 hostname.example.com

Since I see this on most of my hosts with bonds, I'm assuming it's happening because it finds the same MAC on multiple interfaces and doesn't know how to handle it.

Here is the ipconfig output from this host:

bond0 Link encap:Ethernet HWaddr F4:CE:46:B9:3B:F4
          inet addr:10.110.10.203 Bcast:10.110.10.255 Mask:255.255.255.0
          inet6 addr: fe80::f6ce:46ff:feb9:3bf4/64 Scope:Link
          UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
          RX packets:3929803787 errors:1 dropped:0 overruns:0 frame:1
          TX packets:4294474859 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2259212304130 (2.0 TiB) TX bytes:3370758106988 (3.0 TiB)

eth0 Link encap:Ethernet HWaddr F4:CE:46:B9:3B:F4
          UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
          RX packets:2355909712 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4293162724 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1403107466117 (1.2 TiB) TX bytes:3370593081217 (3.0 TiB)
          Interrupt:138 Memory:f8000000-f8012800

eth1 Link encap:Ethernet HWaddr F4:CE:46:B9:3B:F4
          UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
          RX packets:1573894075 errors:1 dropped:0 overruns:0 frame:1
          TX packets:1312135 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:856104838013 (797.3 GiB) TX bytes:165025771 (157.3 MiB)
          Interrupt:146 Memory:f6000000-f6012800

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:1185733083 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1185733083 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:243836178349 (227.0 GiB) TX bytes:243836178349 (227.0 GiB)

sit0 Link encap:IPv6-in-IPv4
          NOARP MTU:1480 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Any ideas what might be happening and/or how to fix it? I was seeing this on 2.0.5 and I'm still seeing it in 2.1RC1. The host is still running the 2.0.5 agent as I haven't had a chance to upgrade all of my agents yet.

Tags: ipdiscover
Revision history for this message
Daniel Rich (drich-u) wrote :

Duplicate of 1216940, I didn't see that one when I searched (and I don't see a way for me to close it as a duplicate)

Changed in ocsinventory-server:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.