HP XC System Software Administration Guide Version 4.0

You can implement Ethernet NIC bonding on any node, but not on the head node.
Ethernet NIC bonding is implemented through node imaging; this allows its subsequent persistent
automatic configuration when the node is reimaged. For more information on node imaging,
see Chapter 11 (page 141).
The /opt/hptc/config/nicbond/nicbond.staticdb file enables you to specify the key
data to implement Ethernet NIC bonding. Example 9-1 (page 134) is an example of this file edited
to bond two Ethernet NICs (eth2 and eth3) on node n4.
Example 9-1 The Annotated nicbond.staticdb File
$VAR1 = {
'nodes' => {
'n4' => {
1
'bonds' => {
'bond0' => {
'ipaddr' => '192.0.2.10',
2
'netmask' => '255.255.254.0',
3
'gateway' => '192.0.2.100',
4
'params' => {
'mode' => '1',
'primary' => 'eth1',
5
},
'eth1' => {
6
'hwaddr' => '00:00:00:00:0e:01',
7
},
'eth2' => {
8
'hwaddr' => '00:00:00:00:0e:02'
9
},
},
},
},
},
};
1
The name of the node identified for Ethernet NIC bonding.
2
The network IP address.
3
The netmask value.
4
The network gateway address.
5
The Ethernet device that will serve as the primary device for the logical master device,
bond0. If the throughput of the Ethernet NICs differ, use the device with the fastest
throughput.
6
The name of a physical Ethernet device to be bonded to the logical device, bond0.
7
The MAC address of the Ethernet device.
8
The name of another physical Ethernet device to be bonded to the logical device, bond0.
9
The MAC address of the Ethernet device.
Use the following procedure to bond two Ethernet NICs together:
NOTE: In the example used in this procedure, two Ethernet NICs are bonded together for only
one node, named n4.
1. Log in as superuser (root) on the head node.
2. Gather the information you will need to provide in the /opt/hptc/config/nicbond/
nicbond.staticdb file:
134 Network Administration