Yep, that’s the problem – it keeps coming up with 3 ports instead of 4 and eth0 is always has a different Aggregator ID.

No idea why it does that – the other server is setup the same and it’s bonding works perfectly.

The only thing I can think of is some of the Xen virtual interfaces and bridges as disrupting it.

 

--Russell

 

 

From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Cameron Kerr
Sent: Thursday, 17 February 2011 6:18 a.m.
To: CentOS mailing list
Subject: Re: [CentOS] NIC bonding - missing eth0?

 

 

On 16/02/2011, at 3:12 PM, Smithies, Russell wrote:

 

802.3ad info

LACP rate: slow

Active Aggregator Info:

        Aggregator ID: 19

        Number of ports: 3 <<<<<<<<

        Actor Key: 17

        Partner Key: 5

        Partner Mac Address: 00:1b:90:3d:90:c0

 

Slave Interface: eth0

MII Status: up

Link Failure Count: 0

Permanent HW addr: 1c:c1:de:74:97:5c

Aggregator ID: 18                                    <<<<<<<<<

 

This is different.



 

Slave Interface: eth1

MII Status: up

Link Failure Count: 0

Permanent HW addr: 1c:c1:de:74:97:5d

Aggregator ID: 19

 

Slave Interface: eth2

MII Status: up

Link Failure Count: 0

Permanent HW addr: 1c:c1:de:74:97:5e

Aggregator ID: 19

 

Slave Interface: eth3

MII Status: up

Link Failure Count: 0

Permanent HW addr: 1c:c1:de:74:97:5f

Aggregator ID: 19

 

 

Attention: The information contained in this message and/or attachments from AgResearch Limited is intended only for the persons or entities to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipients is prohibited by AgResearch Limited. If you have received this message in error, please notify the sender immediately.