Topic: [Solved] Enabling NIC bonding

[toothandnail]

I am in the process of setting up an IBM (well, Lenovo, now) System x3630 M4 server with the 64-bit version of SME 9. Its in server only mode, since its mainly intended as an file server for a busy drafting office.

In older versions of SME, I've been offered NIC bonding as an option during install. In this instance, I wasn't offered it at all. Since I've very limited experience with SME 9 and none at all with server hardware quite as powerful as the x3630, I'm wondering what has caused this? Is it a feature change in SMe 9, or is there something in the hardware that is preventing the bonding option being offered?

So, my first question is should SME 9 be offering to set up bonding during install when there are multiple NICs and the server is set for server only use?

Also, is there a limit to the number of NICs used in bonding? The x3630 has 4 gigabit ethernet ports, but only two are enabled unless a licence is bought for the others.

Paul.

[guest22]

So, my first question is should SME 9 be offering to set up bonding during install when there are multiple NICs and the server is set for server only use?

Yes, it should.

Also, is there a limit to the number of NICs used in bonding? The x3630 has 4 gigabit ethernet ports, but only two are enabled unless a licence is bought for the others.

The current maximum NICs for bonding is 2.

guest

[toothandnail]

Yes, it should.

Thanks. Sounds as though there is a bug of some sort, though where it is, I don't know. I've made a couple of changes to the firmware and will try a fresh install. If I'm still not given the option of setting up bonding, I'll open a bug for it. The x3630 system is certified for Redhat 6 and 7, so I would hope the hardware is fully supported.

The current maximum NICs for bonding is 2.

Useful to know, thanks. No point in purchasing the licence to enable the other two ports then.

One other question. Can someone give me a sample of /etc/modprobe.d/bonding.conf so I can try setting it up manually with a template fragment?

Thanks.

Paul.

[guest22]

Useful to know, thanks. No point in purchasing the licence to enable the other two ports then.

Please note that the bonding option is only presented when the number of detected NICs is _exactly_ 2 (in the pick list of NICs). So if the other unlicensed (and maybe unfucntional) NICs are detected (so in total 4), the bonding option will not be presented.

If that is the case, you may have to disable that hardware in the bios.

guest

[toothandnail]

Please note that the bonding option is only presented when the number of detected NICs is _exactly_ 2 (in the pick list of NICs). So if the other unlicensed (and maybe unfucntional) NICs are detected (so in total 4), the bonding option will not be presented.

If that is the case, you may have to disable that hardware in the bios.

guest

Thanks! That was the clue. I had already disabled the 2 non enabled gigabit ports but the pick list was showing a third device:

Code: [Select]

cdc_ether 42:f2:e9:fd:26:07 "USB0"
After hunting through the firmware, I found a setting for ethernet over USB. Disabling that reduced the pick list to the two Intel gigabit ports and bonding is now working.

Paul.

[Stefano]

Please note that the bonding option is only presented when the number of detected NICs is _exactly_ 2 (in the pick list of NICs). So if the other unlicensed (and maybe unfucntional) NICs are detected (so in total 4), the bonding option will not be presented.

nice hit HF.. is that wikied?

good job, indeed