not able to configure sharing when using GNS3

[Nico_Lueck]

I Start using GNS3 (Version 22.1.1.5) and trying to set up a link aggregation.

When using the standard sharing command I'm getting the following error:

* EXOS-VM.3 # enable sharing 1 grouping 1-2 algorithm address-based lacpError: PC environment supports only round robin algorithm.
but Round Robin is not an option when doing the configuration:

* EXOS-VM.4 # enable sharing 1 grouping 1-2 algorithm ? address-based address based* EXOS-VM.4 # enable sharing 1 grouping 1-2 algorithm
Found out the rigth command for it and tried to configure:
* EXOS-VM.1 # enable sharing 1 grouping 1-2 algorithm roundRobin-based lacp ^%% Invalid input detected at '^' marker.anyone an idear how to fix that?

Thanks

[Stefan_K_]

“I have finally brought up the sharing port with LACP.“

I’m sorry, but you have not. 😄 You would see a “Y” under “Agg Mbr” if the LAG is up and running.

Do you see anything in “show log”?
What’s the output of “show lacp counters”

“Tag:   *1(FW),*8(FRA),!3(RR)g,*5(ISC)bg”
(b) means that it is blocked on the vlan, which could have different reasons. Wrong LACP config is one of them afaik.

Are you using spantree?

[Sven2]

I am trying to configure LACP within EXOS-VM running on eve-ng but cannot get any traffic through it. I have finally brought up the sharing port with LACP. The switch SW05 port 5 is connected to SW06 on port 5.

* SW05-LAB.15 # show sharing
Load Sharing Monitor
Config    Current Agg     Min    Ld Share        Ld Share  Agg Link  Link Up
Master    Master  Control Active Algorithm Flags Group     Mbr State Transitions
================================================================================

     5            LACP       1              A     5         -     A      75

* SW06-LAB.83 # show sharing
Load Sharing Monitor
Config    Current Agg     Min    Ld Share        Ld Share  Agg Link  Link Up
Master    Master  Control Active Algorithm Flags Group     Mbr State Transitions
================================================================================
     5            LACP       1              A     5         -     A      86

I saw many Link Up/down events, but after changing to LACP passive this seems to be way better. On the VLAN I can see;

* SW05-LAB.16 # sh vlan IGP
VLAN Interface with name IGP created by user
    Admin State:     Enabled     Tagging:    802.1Q Tag 18
    Description:     None
    Virtual router:     VR-Default
    IP Anycast:         Disabled
    IPv4 Forwarding:     Disabled
    IPv4 MC Forwarding:  Disabled
    Primary IP:         1.1.1.1/29
    IPv6 Forwarding:     Disabled
    IPv6 MC Forwarding:  Disabled
    IPv6:                None
    STPD:               None
    Protocol:            Match all unfiltered protocols
    Loopback:            Disabled
    NetLogin:            Disabled
    QosProfile:          None configured
    Egress Rate Limit Designated Port: None configured
    Flood Rate Limit QosProfile:       None configured
    Suppress ARP:        Disabled
    Suppress ND:         Disabled
    Proxy ARP:           Entry required
    Ports:   4.       (Number of active ports=3)
       Tag:   *1(FW),*8(FRA),!3(RR)g,*5(ISC)bg
    Flags:    (*) Active, (!) Disabled, (g) Load Sharing port
                  (b) Port blocked on the vlan, (m) Mac-Based port
                  (i) Port inactivated on the vlan due to VXLAN configuration
                  (a) Egress traffic allowed for NetLogin
                  (u) Egress traffic unallowed for NetLogin
                  (t) Translate VLAN tag for Private-VLAN
                  (s) Private-VLAN System Port, (L) Loopback port
                  (x) VMAN Tag Translated port
                  (A) Dynamically added by Auto-peering
                  (F) Dynamically added by Fabric Attach
                  (G) Multi-switch LAG Group port
                  (H) Dynamically added by MVRP
                  (I) Dynamically added by IDM
                  (N) Dynamically added by Netlogin
                  (U) Dynamically added uplink port
                  (V) Dynamically added by VM Tracking

Indeed I see no mac-addresses learned on the port when I check the fdb. Is this expected that LACP is not working? When I remove LACP I can ping just fine end-to-end. When connecting two Juniper devices with LACP, this works fine too. I have tried multiple EXOS versions (30.7.1.1 and 31.1.1.3 patch1-1) by the way, same behaviour unfortunately.

[Tripathy__Priya]

Thanks for letting us know to conclude this discussion now. Looking forward for more assistance in the future if you need any ......

[Nico_Lueck]

Happy new Year...Yes all open questions are answered. Many thanks!