L3 etherchannel Problem

[elmoutaallikbillahtaha]

Hi everyone

so I'm testing the L3 etherchannel gigaethernet interfaces

and the L3 etherchannel refuse to come up

here is my config

--------------
switch 1
--------------

interface GigabitEthernet0/2
 no switchport
 no ip address
 no negotiation auto
 channel-protocol lacp
 channel-group 24 mode active
!         
interface GigabitEthernet0/3
 no switchport
 no ip address
 no negotiation auto
 channel-protocol lacp
 channel-group 24 mode active

!

interface Port-channel24
no switchport
ip address 155.1.108.2 255.255.255.0

the result of my port-channel :

Flags:  D - down        P - bundled in port-channel
        I - stand-alone s - suspended
        H - Hot-standby (LACP only)
        R - Layer3      S - Layer2
        U - in use      N - not in use, no aggregation
        f - failed to allocate aggregator

        M - not in use, minimum links not met
        m - not in use, port not aggregated due to minimum links not met
        u - unsuitable for bundling
        w - waiting to be aggregated
        d - default port

        A - formed by Auto LAG


Number of channel-groups in use: 1
Number of aggregators:           1

Group  Port-channel  Protocol    Ports
------+-------------+-----------+-----------------------------------------------
24     Po24(RD)        LACP      Gi0/2(s)    Gi0/3(s)

-------------

Switch -2-
-------------

interface GigabitEthernet0/2
 no switchport
 no ip address
 no negotiation auto
 channel-protocol lacp
 channel-group 24 mode active
!         
interface GigabitEthernet0/3
 no switchport
 no ip address
 no negotiation auto
 channel-protocol lacp
 channel-group 24 mode active

!

interface Port-channel24
no switchport
ip address 155.1.108.4 255.255.255.0

--> the result of my port-channel : 

Flags:  D - down        P - bundled in port-channel
        I - stand-alone s - suspended
        H - Hot-standby (LACP only)
        R - Layer3      S - Layer2
        U - in use      N - not in use, no aggregation
        f - failed to allocate aggregator

        M - not in use, minimum links not met
        m - not in use, port not aggregated due to minimum links not met
        u - unsuitable for bundling
        w - waiting to be aggregated
        d - default port

        A - formed by Auto LAG


Number of channel-groups in use: 1
Number of aggregators:           1

Group  Port-channel  Protocol    Ports
------+-------------+-----------+-----------------------------------------------
24     Po24(RD)        LACP      Gi0/2(s)    Gi0/3(s) 

Please what I'm missing, it doesn't want to work.

[cofee]

It appears to be fine. Not sure about no negotiation auto command, did you try to bring up ether channel without it? try debugging it should tell you what's wrong "debug lacp all"

[elmoutaallikbillahtaha]

no negotiation auto it is just about negotiating the duplex and the speed.

the error message that I've got, is that the neghbor is not using LACP.

[Kin Loo]

you can try flapping all gig interfaces, if it does not help, try remove and reconfigure the etherchannels. are you using PT or real switch device, also what switch and ios are you using?

[elmoutaallikbillahtaha]

The problem is that Cisco VIRL as cofee@0400 mentienned before. I tried to make it on PT and it's working fine.

Thanks.

[Evanjrosado]

This is frustrating for me. When will this be fixed? Has anyone heard anything from VIRL. I'm experiencing the same bugs and its holding me back on both my studies and also with planning for network changes at my job. :(

[elmoutaallikbillahtaha]

hey don't wait for the fixe

it's working fine on packet tracer, and if you are using the same config as mine, it's correct, I've tried the same config on real devices and it's working.

[cofee]

So you debugged lacp on both switches and both switches are complaining that the neighbor is not running LACP?

[cofee · Accepted solution]

I hope you are not trying this on cisco virl, because it appears virl is having issues or layer 3 etherchannel is not supported when using LACP. But it works fine with static or pagp. I spent quite some time on Cisco virl and no matter what I did layer 3 etherchannel won't come up when using LACP and I was getting the same debug messages that you mentioned. As I mentioned static and pagp worked fine in virl. I didn't try this on a physical equipment, but shouldn't be an issue there.

[elmoutaallikbillahtaha]

Yes that is. I'm using Virl; and I tried the same config on PT and its working fine.

Thanks a lot.

[Collin Clark]

Did you create the port-channel interface or did you let the channel-group command create it?

[elmoutaallikbillahtaha]

Hi,

I let the channel-group command create it.

it may cause a problem?

[Kin Loo]

Hey dude, I am quite puzzled why would you even see the commands:

 channel-protocol lacp
 channel-group 24 mode active

within the show run output.

top of my head, there is no such command called channel-protocol. it should give an error.
channel-group 24 mode active is the command to use on both side of the links.

Unless you are using a model of switch that i have no idea of.

If you look at the picture I had uploaded, I had tried configuring on PT.

All i did was to interface range both GI interfaces, no switchport it and then channel-group 24 mode active.

At that stage, show eth sum was already showing P for in port-channel.

Next, I entered interface po24 and add the IP address you specified.

[MartinKajan]

Channel-protocol is a completely valid command at least on higher-end devices, though I'm pretty sure I've used it on the 2xxx and 3xxx switches.

LACP should simply be a default option when creating an etherchannel.
Lastly, there is absolutely no reason for the commands not to appear in running config.