[dpdk-users] bonding - slave mac address is not updated

[dpdk-users] bonding - slave mac address is not updated

[Eugene Iskra]

Hello,

I am using DPDK 18.11.2 with bonding in BONDING_MODE_ACTIVE_BACKUP mode.
When both slaves are connected to the switch, the primary slave receives 
/ sends traffic
and everything work well.
When the primary port is disconnected, and the secondary slave becomes 
primary,
no packets are received, except for broadcast packets.

Looking at bond_ethdev_lsc_event_callback in rte_eth_bond_pmd.c, I see that
mac_address_slaves_update is called only when slave link is brought up, 
but if slave
goes down, mac addresses are not updated.

Also the mac_address_slaves_update function itself doesn't seem to 
update mac address
correctly for the new primary port, since it updates 
internals->primary_port instead
of internals->current_primary_port.

Is this an actual bug or am I misunderstanding something / something is 
not configured
right?


Regards,
Eugene

Re: [dpdk-users] bonding - slave mac address is not updated

[Eugene Iskra]

I see there's an open bug on this issue.
https://bugs.dpdk.org/show_bug.cgi?id=256

On 10/7/19 21:17, Eugene Iskra wrote:
> Hello,
>
> I am using DPDK 18.11.2 with bonding in BONDING_MODE_ACTIVE_BACKUP mode.
> When both slaves are connected to the switch, the primary slave 
> receives / sends traffic
> and everything work well.
> When the primary port is disconnected, and the secondary slave becomes 
> primary,
> no packets are received, except for broadcast packets.
>
> Looking at bond_ethdev_lsc_event_callback in rte_eth_bond_pmd.c, I see 
> that
> mac_address_slaves_update is called only when slave link is brought 
> up, but if slave
> goes down, mac addresses are not updated.
>
> Also the mac_address_slaves_update function itself doesn't seem to 
> update mac address
> correctly for the new primary port, since it updates 
> internals->primary_port instead
> of internals->current_primary_port.
>
> Is this an actual bug or am I misunderstanding something / something 
> is not configured
> right?
>
>
> Regards,
> Eugene