7/27/2019 Linux interface bonding

1/3

Step 1 enter the / etc / sysconfig / network directory.

# Cd / etc / sysconfig / networkStep 2 of using the ls command to view existing documents.If there is to be operating the card corresponding to the corresponding i fcfg ethX file (such as eth1 corresponds to the ifcfg eth1, eth1, [, h1] correspondingto the ifcfg eth2,) , then delete the h2] .Step 3 create and edit the ifcfg eth id MAC file.The MAC for the hardware address of the card to operate through ifconfig ethX command to view.

If the site in accordance with the other documents to complete the bond operation you available the cat / proc / net / the bonding / the bond0 command to view the two NIC's MAC address.To eth1, eth2, for example:1. Use the vi command for eth1 to create the ifcfg eth id 00: 18:82:1 e: f3: c4,file .2. Enter the following two lines:BOOTPROTO = 'static'STARTMODE = 'off'3. The same way, eth2 create the ifcfg eth, id 00: 18:82:1 e: f3: c5 files content and the ifcfg eth id 00: 18:82:1 e: f3: c4, the same.Step 4 h3] [lwm4] create and edit the ifcfg the bond0 file.The # vi the ifcfg the bond0

Step 5 enter the following content and save and exit.BOOTPROTO = staticThe IPADDR = ' 10.10.10 .1'The NETMASK = ' 255.255.255.0'STARTMODE = onbootBONDING_MASTER = yesBONDING_MODULE_OPTS = mode = active backup miimon = 100 use_carrier = 1BONDING_SLAVE0 = bus pci 0000: 06:00.0BONDING_SLAVE1 = bus pci 0000: 06:00.1Related fields have the following meanings:L IPADDRThe IP address of the logic card, according to the practical situation.L NETMASK

Logical subnet mask of the network card, according to the practical situation.L BONDING_SLAVE0 = bus pci 0000: 06:00.0Said the main card in the Bond object corresponding to the PCI BUS number,iphone4 4s cases, which can be the ethtool i eth1, command, query results in the figures behind the bus info is the network card PCI BUS No.An example is as follows.host131: ~ # ethtool i eth1driver: e1000version: 7.3.15 k3 of NAPIfirmware version: 2.1 7bus info: 0000:06:00.0L BONDING_SLAVE1 = bus pci 0000: 06:00.1 < / U the> , Said another card in the Bond object corresponding to the PCI BUS number, whic

h can be the ethtool i eth2, command query.

SuSE 10 operating system, BONDING_SLAVE0, BONDING_SLAVE1 configuration values ??must be PCI BUS No.

Each single board implementation of Fabric Dual LAN bind operation, you can copya ifcfg bond0 file, then change which the IPADDR = line fill in the IP address ofthe site planning, and the ethtool i eth, < with I> X command (X is the network

7/27/2019 Linux interface bonding

2/3

card number) to view the card PCI BUS number, to ensure that the BONDING_SLAVE0, BONDING_SLAVE1 configuration values ??and the actual consistent.Steps 6 the execution rcnetwork the restart command so that configuration to take effect.Steps 7 view the work status of the logic card.# The cat the / proc / net / the bonding / the bond0Interface display similar to the following information:The Ethernet the Channel Bonding Driver: v3.0.1 (January 9, 2006)

Bonding Mode: fault tolerance. (Active backup)The Primary the Slave: NoneCurrently the Active Slave: eth1,The MII the Status: upMII Polling the Interval (ms): 100Up Delay (ms): 0Down Delay (ms): 0

Slave the Interface: eth1,The MII the Status: upLink Failure Count: 0Permanent HW addr: 00:18:82:1 e: f3: c4

Slave the Interface: eth2,The MII the Status: up

Link Failure Count: 0Permanent HW addr: 00:18:82:1 e: f3: c5If the MII Status line show Down is execute the following command to start the card.# The ifconfig the bond0 upStep 8 the check the configuration results.Bond operation card will use the primary NIC (eth1) for the MAC address and thebond operation to form the logic card.For example, assume that eth1 MAC address: 00:18:82:1 E: F3: C4, and the bond operation was successful, the Executive the ifconfig a | grep HWaddr command, thesystem displays the following:Bond0 Link encap: Ethernet HWaddr 00:18:82:1 E: F3: C4eth0 Link encap: Ethernet HWaddr 00:18:82:1 E: F3: D4

eth1 Link encap: Ethernet HWaddr 00:18:82:1 E: F3: C4eth2 Link encap: Ethernet HWaddr 00:18:82:1 E: F3: C4eth3 Link encap: Ethernet HWaddr 00:18:82:1 E: F3: CEeth4 Link encap: Ethernet HWaddr 00:18:82:1 E: F3: CF

[H1] should be Eth2

[H2]: If you do not remove, the need to back up. Do not backed up to the currentpath, such as: backup to the current path the name of the ifcfg eth2bak cause bond0 operation failed, reason: was to match the ifcfg eth2, the results match tothe ifcfg eth2bak document. Previous do mdsp parts NIC teaming operation like t

his ^ _ ^

Suggested that other directory path or their own hand to create a bak directorymv the files go to the backup operation in case it is deleted, the error duringoperation is not recoverable ^ _ ^Or delete the file error during operation, the need to restore the re configuration can also go through the yast tool.

[H3] In addition, if the step does not perform the two machine software vcs notstart. Has already been verified.

7/27/2019 Linux interface bonding

3/3