Skip to content

Failure when there are more than 10 interfaces #3

@dannywarner

Description

@dannywarner

When using this script to set up bonding on a server with 12 interfaces, I got the following traceback:

Scanning for bonding peers...
Enabling interfaces............
Sleeping 5 seconds for switch port negotiation...
Scanning....Traceback (most recent call last):
File "/home/rack/.adc/bonding/bonding.py", line 949, in
handleArgs()
File "/home/rack/.adc/bonding/bonding.py", line 934, in handleArgs
groups = peers(False)
File "/home/rack/.adc/bonding/bonding.py", line 286, in peers
data = s2.recv(60)
socket.error: [Errno 100] Network is down

Looking into this, it appears that the script enabled interfaces eth0-9, but did not enable eth10 or eth11 and then failed while scanning for peers.

The first 8 interfaces (eth0-7) are standard gigabit ethernet and eth8-11 are 10G fiber ethernet, but that does not seem to matter. The bonding script worked after I manually enabled the interfaces. Please let me know if you need any more info.

Thanks,
Danny

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions