Question & Answer
Question
Why does a new network bond in NPS display an incorrect mode?
Answer
After adding a bond to your network setup and specifying a bond mode, you find that the bond does not uphold the specified mode.
The Red Hat knowledgebase (kbase.redhat.com) recommends the following procedure for adding bonds to your system:
To ensure that the module is loaded when the channel bonding interface is brought up, add the following line to /etc/modprobe.conf:
alias bond<N> bonding
options bond<N> miimon=100 mode=1
However, if you have several bonds on the NPS system, a bug occurs in which all bonds are listed in the mode of the first bond. The syntax above causes the "mode=x" switch to be ignored in subsequent bonds.
IBM recommends that you specify bonds in the following way:
install bond0 /sbin/modprobe bonding -o bond0 miimon=200 mode=2
install bond1 /sbin/modprobe bonding -o bond1 miimon=500 mode=6
This method will respect the bond mode for each bond defined.
If you would like to learn more about bond modes, refer to "Red Hat Supported Bonding Modes".
Related Information
[{"Product":{"code":"SSULQD","label":"IBM PureData System"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":null,"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.0.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Historical Number
NZ492889
Was this topic helpful?
Document Information
Modified date:
17 October 2019
UID
swg21570667