2013-12-09 01:06 PM
2013-12-15 01:49 AM
This is very easy to setup and we're currently using NIC Bonding as well on our servers. You need to ensure that LACP is setup on the Switch and both ports eth0 and eth1 are going to the SAME switch -- LACP has this limitation that it cannot span multiple physical switches. Here's how you configure Security Analytics server for boding:
/etc/modprobe.d/bonding.conf should be:
alias bond0 bonding
options bonding miimon=1000 mode=4 lacp_rate=1
/etc/sysconfig/network-scripts/ifcfg-bond0 should be:
DEVICE=bond0
IPADDR=YOUR_IP
NETMASK=YOUR_NETMASK
GATEWAY=YOUR_GATEWAY
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
/etc/sysconfig/network-scripts/ifcfg-em1 should be:
DEVICE=em1
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
MASTER=bond0
SLAVE=yes
/etc/sysconfig/network-scripts/ifcfg-em2 should be:
DEVICE=em2
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
MASTER=bond0
SLAVE=yes
You can then run this to verify your configuration AFTER you run service network restart.
cat /proc/net/bonding/bond0
2013-12-15 01:49 AM
This is very easy to setup and we're currently using NIC Bonding as well on our servers. You need to ensure that LACP is setup on the Switch and both ports eth0 and eth1 are going to the SAME switch -- LACP has this limitation that it cannot span multiple physical switches. Here's how you configure Security Analytics server for boding:
/etc/modprobe.d/bonding.conf should be:
alias bond0 bonding
options bonding miimon=1000 mode=4 lacp_rate=1
/etc/sysconfig/network-scripts/ifcfg-bond0 should be:
DEVICE=bond0
IPADDR=YOUR_IP
NETMASK=YOUR_NETMASK
GATEWAY=YOUR_GATEWAY
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
/etc/sysconfig/network-scripts/ifcfg-em1 should be:
DEVICE=em1
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
MASTER=bond0
SLAVE=yes
/etc/sysconfig/network-scripts/ifcfg-em2 should be:
DEVICE=em2
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
MASTER=bond0
SLAVE=yes
You can then run this to verify your configuration AFTER you run service network restart.
cat /proc/net/bonding/bond0