ExtremeSwitching (EXOS)

Expand all | Collapse all

not able to configure sharing when using GNS3

  • 1.  not able to configure sharing when using GNS3

    Posted 12-23-2016 10:51
    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 lacp[/code]Error: PC environment supports only round robin algorithm.[/code]
    but Round Robin is not an option when doing the configuration:

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

    Thanks



  • 2.  RE: not able to configure sharing when using GNS3

    Posted 12-23-2016 11:00
    There are lots of limitaion on virtual EXOS switches and I remember LAG is one if them. Actually round robin is NOT a kind of algorithm for real switches. Just try "enable sharing 1 group 1-2" and it will work.


  • 3.  RE: not able to configure sharing when using GNS3

    Posted 12-23-2016 12:01
    Thank you!


  • 4.  RE: not able to configure sharing when using GNS3

    Posted 12-24-2016 16:33
    You still can add lacp on EXOS VM: "enable sharing 1 grouping 1,2 lacp"



  • 5.  RE: not able to configure sharing when using GNS3

    Posted 12-26-2016 01:04
    The following example defines a static load-sharing group that contains ports 9 through 12, and uses the first port in the group as the master logical port 9:

    enable sharing 9 grouping 9-12

    In this example, logical port 9 represents physical ports 9 through 12.
    When using load sharing, you should always reference the master logical port of the load-sharing group.

    Coming to the algorithm used in LACP for extreme switches we may use either standard or custom algorithm. For more information you may refer to page 219 of EXOS user guide 21.1 PDF.



  • 6.  RE: not able to configure sharing when using GNS3

    Posted 12-30-2016 01:22
    Nico we feel your concern is fixed after having followed up the above posted conversation.
    Do let us know if you have any further concern. Else we can close this Hub conversation here.

    Wish you in advance happy new year 2017 ............


  • 7.  RE: not able to configure sharing when using GNS3

    Posted 01-02-2017 06:18
    Happy new Year...Yes all open questions are answered. Many thanks!


  • 8.  RE: not able to configure sharing when using GNS3

    Posted 01-03-2017 01:30
    Thanks for letting us know to conclude this discussion now. Looking forward for more assistance in the future if you need any ......



  • 9.  RE: not able to configure sharing when using GNS3

    Posted 08-31-2021 13:15

    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.



  • 10.  RE: not able to configure sharing when using GNS3

    Posted 09-02-2021 08:17

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

    I’m sorry, but you have not. :D 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?