wiki:centos_bonding_interfaces
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
wiki:centos_bonding_interfaces [2017/06/26 11:40] – [Management Interface Bonding] walkeradmin | wiki:centos_bonding_interfaces [2023/03/09 22:35] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 3: | Line 3: | ||
\\ | \\ | ||
\\ | \\ | ||
- | |||
- | ---- | ||
===== Introduction ===== | ===== Introduction ===== | ||
For network redundancy, we can bond interface pairs on the G6/G7 servers. For this example I am using CentOS 6.x, so luckily still have the ethx naming convention. | For network redundancy, we can bond interface pairs on the G6/G7 servers. For this example I am using CentOS 6.x, so luckily still have the ethx naming convention. | ||
Line 61: | Line 59: | ||
</ | </ | ||
\\ | \\ | ||
+ | So <color # | ||
\\ | \\ | ||
- | So ifcfg-eth0 and ifcfg-eth1 don't contain any address information, | ||
\\ | \\ | ||
- | \\ | + | <color #22b14c>ifcfg-bond0</ |
- | ifcfg-bond0 contains all of the addressing information for the two interfaces that are bonded (ifcfg-eth0 and ifcfg-eth1) | + | |
\\ | \\ | ||
\\ | \\ | ||
Reboot the server, and you should be able to ping the management address (192.168.27.100 in this case) and if you only unplug one interface at a time, the pings should continue (you might miss one or two pings during transition). | Reboot the server, and you should be able to ping the management address (192.168.27.100 in this case) and if you only unplug one interface at a time, the pings should continue (you might miss one or two pings during transition). | ||
+ | \\ | ||
+ | \\ | ||
+ | <color # | ||
+ | \\ | ||
+ | \\ | ||
+ | |||
+ | ---- | ||
+ | ===== Ingress/ | ||
+ | \\ | ||
+ | For bonding the ingress/ | ||
+ | < | ||
+ | ifcfg-eth2 | ||
+ | ifcfg-eth3 | ||
+ | ifcfg-bond1 | ||
+ | route-bond1 | ||
+ | </ | ||
+ | So <color # | ||
+ | \\ | ||
+ | ==== ifcfg-eth2 ==== | ||
+ | < | ||
+ | DEVICE=eth2 | ||
+ | HWADDR=00: | ||
+ | TYPE=Ethernet | ||
+ | UUID=6530a0c3-592d-44d0-8418-b6795818cf55 | ||
+ | ONBOOT=yes | ||
+ | MASTER=bond1 | ||
+ | SLAVE=yes | ||
+ | </ | ||
+ | ==== ifcfg-eth3 ==== | ||
+ | < | ||
+ | DEVICE=eth3 | ||
+ | HWADDR=00: | ||
+ | TYPE=Ethernet | ||
+ | UUID=13c99bfe-03f9-44c8-8a91-277dbd2c192b | ||
+ | ONBOOT=yes | ||
+ | MASTER=bond1 | ||
+ | SLAVE=yes | ||
+ | </ | ||
+ | \\ | ||
+ | Now we have the bond file (<color # | ||
+ | \\ | ||
+ | ==== ifcfg-bond1 ==== | ||
+ | < | ||
+ | DEVICE=bond1 | ||
+ | ONBOOT=yes | ||
+ | BOOTPROTO=static | ||
+ | USERCTL=no | ||
+ | BONDING_OPTS=" | ||
+ | IPADDR=11.0.100.1 | ||
+ | NETMASK=255.0.0.0 | ||
+ | </ | ||
+ | \\ | ||
+ | Finally we have a routing file (<color # | ||
+ | \\ | ||
+ | ==== route-bond1 ==== | ||
+ | < | ||
+ | ADDRESS0=239.0.0.0 | ||
+ | NETMASK0=255.0.0.0 | ||
+ | GATEWAY0=11.0.100.1 | ||
+ | </ | ||
+ | \\ | ||
+ | \\ | ||
+ | <color # | ||
+ | \\ | ||
+ | \\ | ||
+ | |||
+ | ---- | ||
+ | ==== Route ==== | ||
+ | Below we can see the route information with the bondx entries in the right hand column. | ||
+ | \\ | ||
+ | < | ||
+ | Destination | ||
+ | 192.168.27.0 | ||
+ | link-local | ||
+ | link-local | ||
+ | link-local | ||
+ | link-local | ||
+ | link-local | ||
+ | link-local | ||
+ | 239.0.0.0 | ||
+ | 10.0.0.0 | ||
+ | 11.0.0.0 | ||
+ | default | ||
+ | </ | ||
\\ | \\ | ||
\\ | \\ |
wiki/centos_bonding_interfaces.1498473612.txt.gz · Last modified: 2023/03/09 22:35 (external edit)