DPDK usage discussions
 help / color / mirror / Atom feed
* [dpdk-users] Does BONDING_MODE_8023AD is works in 17.11?
@ 2017-11-17 22:24 Алексей Телятников
  2018-01-18 14:14 ` Thomas Monjalon
  0 siblings, 1 reply; 2+ messages in thread
From: Алексей Телятников @ 2017-11-17 22:24 UTC (permalink / raw)
  To: users

Greetings. I have issue with link-aggregation in DPDK. My HP A5820X 
switch does not recive LACP from DPDK application.

Has anyone worked with BONDING_MODE_8023AD?

I have: DPDK 17.11 HEAD & 11.1-RELEASE-p4 FreeBSD

Also I build examples/bond with little changes:

--- a/examples/bond/main.c
+++ b/examples/bond/main.c
@@ -226,7 +226,7 @@ bond_port_init(struct rte_mempool *mbuf_pool)
         uint16_t nb_rxd = RTE_RX_DESC_DEFAULT;
         uint16_t nb_txd = RTE_TX_DESC_DEFAULT;

-       retval = rte_eth_bond_create("bond0", BONDING_MODE_ALB,
+       retval = rte_eth_bond_create("net_bonding0", BONDING_MODE_8023AD,
                         0 /*SOCKET_ID_ANY*/);
         if (retval < 0)
                 rte_exit(EXIT_FAILURE,

Run it:

$ sudo build/bond_app
EAL: Sysctl reports 16 cpus
EAL: Detected 16 lcore(s)
EAL: Contigmem driver has 1 buffers, each of size 32GB
EAL: Mapped memory segment 1 @ 0x8023ff000: physaddr:0x800000000, len 
34359738368
EAL: PCI device 0000:03:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1521 net_e1000_igb
EAL:   0000:03:00.0 not managed by UIO driver, skipping
EAL: PCI device 0000:03:00.3 on NUMA socket 0
EAL:   probe driver: 8086:1521 net_e1000_igb
EAL:   0000:03:00.3 not managed by UIO driver, skipping
EAL: PCI device 0000:05:00.0 on NUMA socket 0
EAL:   probe driver: 8086:10fb net_ixgbe
EAL: PCI device 0000:05:00.1 on NUMA socket 0
EAL:   probe driver: 8086:10fb net_ixgbe
User device list:
PMD: ixgbe_dev_link_status_print():  Port 0: Link Down
Port 0 MAC: 90:e2:ba:d0:a3:c4
PMD: ixgbe_dev_link_status_print():  Port 1: Link Down
Port 1 MAC: 90:e2:ba:d0:a3:c5
EAL: Initializing pmd_bond for net_bonding0
PMD: Using mode 4, it is necessary to do TX burst and RX burst at least 
every 100ms.
EAL: Create bonded device net_bonding0 on port 2 in mode 4 on socket 0.
PMD: ixgbe_dev_link_status_print():  Port 0: Link Down
PMD: ixgbe_dev_link_status_print():  Port 1: Link Down
Port 2 MAC: 90:e2:ba:d0:a3:c4
Starting lcore_main on core 1:0 Our IP:7.0.0.10
bond6>show
90:e2:ba:d0:a3:c4
90:e2:ba:d0:a3:c5
Active_slaves:0 packets received:Tot:0 Arp:0 IPv4:0

Active slaves always 0. I tried configure bond in testpmd. Same problem.

On the switch all ports is in up state but:

Received LACP Packets: 0 packet(s)

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [dpdk-users] Does BONDING_MODE_8023AD is works in 17.11?
  2017-11-17 22:24 [dpdk-users] Does BONDING_MODE_8023AD is works in 17.11? Алексей Телятников
@ 2018-01-18 14:14 ` Thomas Monjalon
  0 siblings, 0 replies; 2+ messages in thread
From: Thomas Monjalon @ 2018-01-18 14:14 UTC (permalink / raw)
  To: users
  Cc: Алексей
	Телятников,
	declan.doherty

No reply after 2 months, adding maintainer Cc.

17/11/2017 23:24, Алексей Телятников:
> Greetings. I have issue with link-aggregation in DPDK. My HP A5820X 
> switch does not recive LACP from DPDK application.
> 
> Has anyone worked with BONDING_MODE_8023AD?
> 
> I have: DPDK 17.11 HEAD & 11.1-RELEASE-p4 FreeBSD
> 
> Also I build examples/bond with little changes:
> 
> --- a/examples/bond/main.c
> +++ b/examples/bond/main.c
> @@ -226,7 +226,7 @@ bond_port_init(struct rte_mempool *mbuf_pool)
>          uint16_t nb_rxd = RTE_RX_DESC_DEFAULT;
>          uint16_t nb_txd = RTE_TX_DESC_DEFAULT;
> 
> -       retval = rte_eth_bond_create("bond0", BONDING_MODE_ALB,
> +       retval = rte_eth_bond_create("net_bonding0", BONDING_MODE_8023AD,
>                          0 /*SOCKET_ID_ANY*/);
>          if (retval < 0)
>                  rte_exit(EXIT_FAILURE,
> 
> Run it:
> 
> $ sudo build/bond_app
> EAL: Sysctl reports 16 cpus
> EAL: Detected 16 lcore(s)
> EAL: Contigmem driver has 1 buffers, each of size 32GB
> EAL: Mapped memory segment 1 @ 0x8023ff000: physaddr:0x800000000, len 
> 34359738368
> EAL: PCI device 0000:03:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:1521 net_e1000_igb
> EAL:   0000:03:00.0 not managed by UIO driver, skipping
> EAL: PCI device 0000:03:00.3 on NUMA socket 0
> EAL:   probe driver: 8086:1521 net_e1000_igb
> EAL:   0000:03:00.3 not managed by UIO driver, skipping
> EAL: PCI device 0000:05:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:10fb net_ixgbe
> EAL: PCI device 0000:05:00.1 on NUMA socket 0
> EAL:   probe driver: 8086:10fb net_ixgbe
> User device list:
> PMD: ixgbe_dev_link_status_print():  Port 0: Link Down
> Port 0 MAC: 90:e2:ba:d0:a3:c4
> PMD: ixgbe_dev_link_status_print():  Port 1: Link Down
> Port 1 MAC: 90:e2:ba:d0:a3:c5
> EAL: Initializing pmd_bond for net_bonding0
> PMD: Using mode 4, it is necessary to do TX burst and RX burst at least 
> every 100ms.
> EAL: Create bonded device net_bonding0 on port 2 in mode 4 on socket 0.
> PMD: ixgbe_dev_link_status_print():  Port 0: Link Down
> PMD: ixgbe_dev_link_status_print():  Port 1: Link Down
> Port 2 MAC: 90:e2:ba:d0:a3:c4
> Starting lcore_main on core 1:0 Our IP:7.0.0.10
> bond6>show
> 90:e2:ba:d0:a3:c4
> 90:e2:ba:d0:a3:c5
> Active_slaves:0 packets received:Tot:0 Arp:0 IPv4:0
> 
> Active slaves always 0. I tried configure bond in testpmd. Same problem.
> 
> On the switch all ports is in up state but:
> 
> Received LACP Packets: 0 packet(s)
> 
> 

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2018-01-18 14:15 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-11-17 22:24 [dpdk-users] Does BONDING_MODE_8023AD is works in 17.11? Алексей Телятников
2018-01-18 14:14 ` Thomas Monjalon

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).