On Tue, Aug 11, 2020 at 10:13:41PM +0200, Remi Locherer wrote:
> On Tue, Aug 11, 2020 at 02:07:32PM -0400, Winfred Harrelson wrote:
> > I know others are using the new aggr(4) interface but I am having a
> > problem with trying to use it on some new servers I have recently
> > gotten.  Hoping I could get some help from someone here since my
> > searches have not been very fruitful.
> > 
> > First off this is on a Supermicro X11DPi-N(T) and it is running a 6.7
> > snapshot from today because the 6.7 release hangs on trying to install.
> > 
> > I have two Intel duel port XXV710 cards with SPF28 and trying to
> > create an LACP bond.  Works fine using the trunk(4) interface but
> > not the aggr(4) interface.  This is what I get:
> > 
> > styx# ifconfig ixl0
> > ixl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> >         lladdr fe:e1:ba:d0:cc:aa
> >         index 1 priority 0 llprio 3
> >         trunk: trunkdev aggr1
>                           ^^^^^
> ixl0 is already member of aggr1
> 
> >         media: Ethernet autoselect (25GbaseSR full-duplex)
> >         status: active
> > styx# ifconfig ixl2 
> > ixl2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> >         lladdr fe:e1:ba:d0:cc:aa
> >         index 3 priority 0 llprio 3
> >         trunk: trunkdev aggr1
>                           ^^^^^
> same here

Thanks for the quick reply.

Unfortunately this is not the issue.  I had tried several attempts
before sending the email and had forgotten to clean up first before
sending the examples.  If the interface is already part of another
trunk group you will get an error attempting to add a different one.

I did a sysupgrade this morning in case something had changed and
also updated the XXV710 cards to the newest firmware but with no luck.



wharrels@styx2:/home/wharrels# dmesg | grep ^ixl
ixl0 at pci5 dev 0 function 0 "Intel XXV710 SFP28" rev 0x02: port 0, FW 
8.0.61820 API 1.11, msix, 8 queues, address 3c:fd:fe:ed:b7:28
ixl1 at pci5 dev 0 function 1 "Intel XXV710 SFP28" rev 0x02: port 1, FW 
8.0.61820 API 1.11, msix, 8 queues, address 3c:fd:fe:ed:b7:29
ixl2 at pci8 dev 0 function 0 "Intel XXV710 SFP28" rev 0x02: port 0, FW 
8.0.61820 API 1.11, msix, 8 queues, address 3c:fd:fe:eb:19:b0
ixl3 at pci8 dev 0 function 1 "Intel XXV710 SFP28" rev 0x02: port 1, FW 
8.0.61820 API 1.11, msix, 8 queues, address 3c:fd:fe:eb:19:b1
ixl4 at pci12 dev 0 function 0 "Intel X722 10GBASE-T" rev 0x09: port 0, FW 
3.1.57069 API 1.5, msix, 8 queues, address 3c:ec:ef:1a:df:f2
ixl5 at pci12 dev 0 function 1 "Intel X722 10GBASE-T" rev 0x09: port 1, FW 
3.1.57069 API 1.5, msix, 8 queues, address 3c:ec:ef:1a:df:f3

Yup, latest firmware.


wharrels@styx2:/etc# ifconfig ixl0
ixl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        lladdr 3c:fd:fe:ed:b7:28
        index 1 priority 0 llprio 3
        media: Ethernet autoselect (25GbaseSR full-duplex)
        status: active
wharrels@styx2:/etc# ifconfig ixl2 
ixl2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        lladdr 3c:fd:fe:eb:19:b0
        index 3 priority 0 llprio 3
        media: Ethernet autoselect (25GbaseSR full-duplex)
        status: active
wharrels@styx2:/etc# ifconfig aggr1 create
wharrels@styx2:/etc# ifconfig aggr1 trunkport ixl0
wharrels@styx2:/etc# ifconfig aggr1 trunkport ixl2
wharrels@styx2:/etc# ifconfig aggr1 up
wharrels@styx2:/etc# ifconfig aggr1
aggr1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        lladdr fe:e1:ba:d0:7c:e9
        index 11 priority 0 llprio 7
        trunk: trunkproto lacp
        trunk id: [(8000,fe:e1:ba:d0:7c:e9,000B,0000,0000),
                 (0000,00:00:00:00:00:00,0000,0000,0000)]
                ixl0 lacp actor system pri 0x8000 mac fe:e1:ba:d0:7c:e9, key 
0xb, port pri 0x8000 number 0x1
                ixl0 lacp actor state activity,aggregation,defaulted
                ixl0 lacp partner system pri 0x0 mac 00:00:00:00:00:00, key 
0x0, port pri 0x0 number 0x0
                ixl0 lacp partner state activity,aggregation,sync
                ixl0 port 
                ixl2 lacp actor system pri 0x8000 mac fe:e1:ba:d0:7c:e9, key 
0xb, port pri 0x8000 number 0x3
                ixl2 lacp actor state activity,aggregation,defaulted
                ixl2 lacp partner system pri 0x0 mac 00:00:00:00:00:00, key 
0x0, port pri 0x0 number 0x0
                ixl2 lacp partner state activity,aggregation,sync
                ixl2 port 
        groups: aggr
        media: Ethernet autoselect
        status: no carrier


Same issue.  Anything else to try?

This does work fine using trunk(4).

Winfred

Reply via email to