Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failure when there are more than 10 interfaces #3

Open
dannywarner opened this issue Apr 5, 2013 · 0 comments
Open

Failure when there are more than 10 interfaces #3

dannywarner opened this issue Apr 5, 2013 · 0 comments

Comments

@dannywarner
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant