similar to: Regd: Ethernet Channel Bonding Clarification is Needed

Dear All, I have configured Cluster Suite with 2 servers Server 1 : 192.168.13.110 IP Address and hostname is primary Server 2 : 192.168.13.179 IP Address and hostname is secondary Floating : 192.168.13.83 IP Address (Assumed by currently active server) I have configured Ethernet Channel Bonding in Each Cluster Nodes and Channel Bonding Configuration Details are 1) Created bonding devices in

Dear All, I have configured Cluster Suite with 2 servers Server 1 : 192.168.13.110 IP Address and hostname is primary Server 2 : 192.168.13.179 IP Address and hostname is secondary Floating : 192.168.13.83 IP Address (Assumed by currently active server) I have configured Ethernet Channel Bonding in Each Cluster Nodes and Channel Bonding Configuration Details are 1) Created bonding devices in

Dear All, I have configured RHEL Cluster Suite with 2 servers Server 1 : 192.168.13.110 IP Address and hostname is primary Server 2 : 192.168.13.179 IP Address and hostname is secondary Floating : 192.168.13.83 IP Address (Assumed by currently active server) In am followed the RHEL Cluster Suite Configuration document "rh-cs-en-4.pdf" and I have configured Ethernet Channel Bonding in

Hi, I'm trying to configure a network bridge over a bonding without any success. Here is my configuration: ifcfg-eth0: DEVICE=eth0 HWADDR=00:1E:C9:E8:3F:E5 ONBOOT=yes USERCTL=no MASTER=bond0 SLAVE=yes ifcfg-eth1: DEVICE=eth1 HWADDR=00:1E:C9:E8:3F:E7 ONBOOT=yes USERCTL=no MASTER=bond0 SLAVE=yes ifcfg-bond0: DEVICE=bond0 ONBOOT=yes BRIDGE=br0 USERCTL=no ifcfg-bridge0: DEVICE=br0

Hi all, Read many posts on the subject. Using 802.3ad. Few problems; Cannot ping some hosts on the network, they are all up. Cannot resolve via DNS which is one of the hosts that I cannot ping, internal nor external DNS hosts. Unplugging the NICS and plugging them back in will then not allow pining if the default d=gateway. When cold booting it somewhat works, some hosts are pingable while

took a couple months off due to road blocks, hoping a fresh look would allow me to use my server as desired. I have three ports, eth0-2 over two nics. I want to bond them, and then use a bridge to connect to virtual machines on the virtual host computer. Never having done this, I am confused on some parts. Here is where I am at now and any pointers helpful. Single server, centos 6.x My issue

Hi all, I've setup a ethernet bond on my centos 5.6 server , when i do a reboot the bond does come up but cleared all the slaves and i've to manually re-add them with ifenslave. does anyone know a solution to this? am i missing something? offcourse i can add it to my rc.local but there must be a more elegant way. please see my configs below Thanks, Wessel ifcfg-bond0: DEVICE=bond0

Hi all, I just noticed that my two nics that are bonded via mode 0 are showing the same mac addy in ifconfig. Is this normal? In syslog I keep getting; kernel: pbond0: received packet with own address as source address Some guidance is appreciated before I dive in and troubleshoot. If I don't list the mac addy in my ifcfg-th# files, only one of the 2 nic comes up during boot.

Hi all, we are testing CentOS 7 in order to migrate from Scientific Linux 6 / CentOS 6 and we are facing an issue with the network. Trying to configure network with teaming in activebackup mode or also with bonding in mode=1 (active backup as well) we see many RX dropped packets in the bond0 interface (around 10% of the total), 100% RX drops in the backup interface and 0% in the active interface.

I'm running into a situation where a bogus bonded interface named "bond0" is being created, in addition to the desired "bond2" interface. Can anyone confirm this? Anyone know why it's happening or what I do to get rid of it? I wanted to start my numbering scheme at 2 instead of 0, which I didn't think would be a problem. As you can see, I have no reference

Hi, last weekend I've updated samba and ctdb on my 2-node cluster. Samba is now on 3.5.6 (from 3.3.4), ctdb on 1.0.114 (from 1.0.84). Both installed from repo via yum and ctdb-packages. After restarting both nodes everything was fine, we could access files on the cluster. On monday I noticed that the nodes didn't had their initial adresses: Node 1: hostname dscln01, public IP

Guys, good afternoon I'm using in my bond interfaces as active backup, in theory, should assume an interface (or work) only when another interface is down. But I'm just lost packets on the interface that is not being used and is generating packet loss on bond. What can that be? Follow my settings bond [root at xxxxx ~]# ifconfig bond0 ; ifconfig eth0 ; ifconfig eth1 bond0

Dear All, I have configured Cluster Suite with 2 servers Server 1 : 192.168.13.110 IP Address Server 2 : 192.168.13.179 IP Address Floating : 192.168.13.83 IP Address (Assumed by currently active server) I want all snmp packets going out through the active server to be stamped with floating IP So i have added a iptables rules as "iptables -t nat -A POSTROUTING -p udp -s

I have a machine I just deployed w/ tg3 interfaces, I have setup bonding on this same line of server (HP DL380 G4) a million times. I saw there were changes recently to how you configure a bond and have my setup configured according to: http://kbase.redhat.com/faq/docs/DOC-7431 The HP switch has a LACP trunk defined on the two ports. Problem is, when rebooting, I need to issue a `service network

Hi *, I'm running into a problem configuring bonding on an HP DL 360 G4p, running 4.3 + tg3 driver version 3.43f. I'm connecting eth0 and eth1 to a Cisco 2948 (CatOS 8.1(3)) and receiving flapping notices. The ethernet address is that of the primary interface. I have tried several different modes, including balance-rr (0), active-backup (1), and balance-alb (6). All have the

I am able to bring up a bonded NIC in Centos4 without requiring to bring up the bond0 with an ip address, but with CentOS-3 I must assign the NIC an address or eth0 and eth1 will not slave. I need to bring bond0 up without an ip address becuase I will be using tagged VLANs. ie. <snip /etc/sysconfig/network-scripts/ifcfg-bond0> DEVICE=bond0 BOOTPROTO=none ONBOOT=yes IPADDR=169.254.0.1

*Hi all, I''m not quiet sure the most reasonable way to dealing with bonding on xenserver. My configuration is as follow. It was ok if i do nothing, but When I tried to ''service network restart'', the bond is break. Then, /proc/net/bonding/pbond: Slave Interface: eth0 eth1 was down bonding MII status: down My questions are: how to deal with this situation? how to avoid

I was given the challenge recently of creating a LAN-LAN bridge between two buildings several hundred metres from each other, using only existing Cat 3 wiring and without having to resort to an expensive and finicky 5 Ghz wireless link. I was able to create a 90 megabit link for about $3,000 Cdn with new PC's, CentOS 4.1, and the newly avaliable Black Box VDSL Ethernet Extender, which

Dear All, My Requirement is 1. I am taking backup from client to server and i configured floating IP Address at the client 2. From primary or secondary server rsync command will be triggerd via floating IP Address to the client PC I am using the following rules in firewall scripts /sbin/iptables -F INPUT /sbin/iptables -F OUTPUT /sbin/iptables -F FORWARD

I have two servers with identical hardware ... TYAN i3210w system boards with dual intel gigabit interfaces, and a PCI intel gigabit nic. I'm running Centos 5.4, x86_64, 2.6.18-164.6.1.el5 Every other time I reboot, the nics initialize in a different order. anaconda had setup /etc/modprobe.conf with alias lines for the cards: alias eth0 e1000 alias eth1 e1000e alias eth2 e1000e However,