Fing+LACP=Up/Down detection problems? [SOLVED]

[pdx501]

I'm using a command like

Code: Select all

fing -n 192.168.0.0/24 -o table,html,hosts.html

to generate an HTML page. When run from a particular host on the LAN (a 10.5.8 Xserve with LACP bonded Ethernet ports) the results indicate almost all hosts are "down" as soon as the page is rendered. I added a -o log,text argument and watched - it seems the hosts are initially detected as up (obviously, otherwise how are they detected). Then a few seconds after the scan completes and the "...Next round starting..." line appears they are detected as down.

Also, the same command run on the LACP machine frequently finds far less hosts than the same scan on other systems.

Fing-ing the same network from another non-aggragated host works fine. Are the bonded ports to blame?

[pdx501]

Update: The answer is yes. I destroyed the bonded interface, ran the scan over a normally configured port and everything acted much more as expected.

[overlook.support]

We love when users solve their issues themselves!
However, we don't want to force you to change your tools and the way you work. Can you tell us what steps you performed to create the LACP interface, so that we can try to replicate the issue and verify what went wrong?

Thanks,

[pdx501]

Can you tell us what steps you performed to create the LACP interface, so that we can try to replicate the issue and verify what went wrong?

On a 10.5/10.6 Mac with dual ethernet (Xserve and Server OS, in my case, but a Mac Pro running client or even a notebook with USB ethernet adapters should work) you:

1. Go to System Preferences -> Network
2. From the gear menu select Manage Virtual Interfaces...
3. Click the + (plus) and select New Link Aggregate...
4. Select your two ethernet interfaces, name the bond, etc. Configure the interface as you normally would if it were only a single link (Manual IP, in my case).

Make sure the original interface is deactivated. 10.6 does this properly, 10.5 may not.