packet loss at ip ping

Latest response

Hi ,

configured bonding successfully but getting packet loss while ip ping , can have any expert solutions

thanks and regards,
Dina

Responses

Hello Dina. There are a number of things to consider. (what kind of bond mode, how many interfaces in the bond, etc..) Assuming you created bond0, can you provide the output from the following:

cd /etc/sysconfig/network-scripts
cat ifcfg-bond0
egrep 'MASTER|SLAVE' ifcfg-*
cat /proc/net/bonding/bond0
service NetworkManager status

Also - plesae review:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s2-networkscripts-interfaces-chan.html

Potential issues:
one of the interfaces in your bond is not in the correct VLAN
there can be a delay when the bond first comes up
there are no slaves in your bond

You can attempt to monitor traffic on both physical interfaces (individually) using tcpdump to confirm you are seeing traffic on the VLAN you would expect

tcpdump -i em1

Hi Dina,

in addition to James' questions, please could you confirm;

  • the underlying hardware of the machine (vendor, model and NICs)
  • check for the string "non-zero address" in /var/log/messages

Many thanks,
Mark

Thanks Mark.

Dina - For the NIC information, you can run

for DEV in `lspci | grep -i 'ethernet' | awk '{ print $1 }'`; do lspci -v -s $DEV | egrep 'Ethernet|Subsystem|Kernel driver'; done

Hi ,

I think problem on delay when the bond first comes up

cat /proc/net/bonding/bond0

Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)

Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth0
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

Slave Interface: eth0
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: e4:1f:13:79:f0:78
Slave queue ID: 0

Slave Interface: eth1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: e4:1f:13:79:f0:7a
Slave queue ID: 0

service network restart

Shutting down interface bond0: [ OK ]
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface bond0: Determining if ip address x.x.x.x is already in use for device bond0...

for DEV in lspci | grep -i 'ethernet' | awk '{ print $1 }'; do lspci -v -s $DEV | egrep 'Ethernet|Subsystem|Kernel driver'; done
10:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709S Gigabit Ethernet (rev 20)
Subsystem: IBM Device 0370
Kernel driver in use: bnx2
10:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709S Gigabit Ethernet (rev 20)
Subsystem: IBM Device 0370
Kernel driver in use: bnx2

Unfortunately a delay in starting a bond is fairly typical (but not usually something that is not acceptable). I generally attach my bond to a bridge.

        br0
        / \
         |
       bond0
        /  \ 
     em1   p3p1

Be sure to review the bonding options:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/sec-Using_Channel_Bonding.html