Download Administrator Manual - Support

4.5 Configuring Bonded Interfaces
• The bonded interface may be made up of two member interfaces,
and a third interface outside of the bond could be the boot interface.
(The boot interface is the node interface used to PXE boot the node
before the kernel loads (section 6.1)).
• The boot interface could itself be a member of the bonded interface.
If the boot interface is a member of a bonded interface, then this is
the first bonded interface when interfaces are listed as in the example on page 105.
• The bonded interface could be set up as the provisioning interface.
However, the provisioning interface cannot itself be a member of
a bonded interface. (The provisioning interface is the node’s interface that picks up the image for the node after the initial ramdisk is
running. Chapter 6 covers this in more detail).
• A bonded interface can be set up as the provisioning interface, while
having a member interface which is used for PXE booting.
4.5.3 Multiple Bonded Interface On A Regular Node
A node can also have multiple bonded interfaces configured. Possibilities
and restrictions are illustrated by the following:
• Any one of the configured bonded interfaces can be configured as
the provisioning interface. However, as already mentioned in the
case of single bond interfaces (section 4.5.2), a particular member of
a bonded interface cannot be made the provisioning interface.
• When a bonded interface is set as the provisioning interface, then
during the node-installer phase of boot, the node-installer brings up
the necessary bonded interface along with all its member interfaces
so that node provisioning is done over the bonded interface.
4.5.4 Bonded Interfaces On Head Nodes And HA Head Nodes
It is also possible to configure bonded interfaces on head nodes.
For a single head node setup, this is analogous to setting up bonding
on regular nodes.
For a high availability (HA) setup (chapter 14), bonding is possible for
internalnet as well as for externalnet, but it needs the following
extra changes:
• For the bonded interface on internalnet, the shared internal IP
alias interface name (the value of networkdevicename, for example, eth0:0 in figure 14.1) for that IP address should be renamed
to the bonded alias interface name on internalnet (for example,
bond0:0).
• For the bonded interface on externalnet, the shared external IP
alias interface name (the value of networkdevicename, for example, eth1:0 in figure 14.1) for that IP address should be renamed
to the bonded alias interface name on externalnet (for example,
bond1:0).
© Bright Computing, Inc.
107