I hope I've got this question in the best spot on the forums.

 

I use a bonded network connection set to Load Balancing (round-robin).  

 

Should i worry about dropped or over-run packets?  I've never looked at those numbers but did just poking around tonight.  

The over-run packets (not totally sure what that means) are connected to one of the two NIC's.  However, the dropped packets seem to only be recorded with the bonded pair and neither of the individual nic's.  Not sure how that would occur

 

See attached screen clip.  Is this anything to worry about?  What does "over-run" refer too?

 

 

Thanks as always 

 

Still need some help with this if anyone can offer insight or information.

Not sure if this will help; but this is what mine looks like

I posted this question on Toms Hardware and this is the response I got back:  This is broken in 3 segments. His first response.  My reply.   His second response.

 

Quote

 

Humm, in a bonded network, you've got redundancy. So if the packet is received, validated, isn't the second packed immediately dropped?

The packets are dropped only overall, not at all at the NIC level.

I'd say it works well. As long as you don't see any errors, or drops on the actual ports, it's all good.

 

 

 

Quote

This is the description I have for mode 0:
balance-rr or 0 
Round-robin policy: Transmit packets in sequential order from the first available slave through the last. This mode provides load balancing and fault tolerance.
I think it's balancing the two NIC's giving you more throughput capability, and the fault protection is that if one NIC goes down, you still have a 2nd in place. So I don't think its actually receiving two of everything and dropping half.
If I"m misunderstanding this, please let me know. 

 

 

Quote

It's doing both. RR duplicates all packet flow, if it can. It will prioritize FIFO and spread work, but if one NIC is done all it's work, it will try to do the work of the other, and whichever completes first will drop the other reception.
It's quite sophisticated stuff, but since it tries to minimize latency and provide redundancy, it behaves like that.
It doesn't do nothing when it's not saturated, it still tries to "preempt" a NIC fault, and if the NIC does fail, you don't lose the packet, because it was always duplicated.
RR is the best solution for similar packet-sized transmissions to minimize latency and maximize fault-tolerance.
Again, your hardware is not misbehaving.

 

I thought it was worth sharing here.

I never did get any explanation of "over-runs" if anyone knows, I do appreciate it.