Switching

Expand all | Collapse all

EX3300 LAG (LACP) strange behavior

Jump to Best Answer
  • 1.  EX3300 LAG (LACP) strange behavior

    Posted 01-21-2018 05:33

    Hello guys.

    I have a 2 x XE port LACP going from an EX300 virtual chassis (lets call it EX-VC) to en EX3300 standalone (lets call it EX).

    I have configured the EX-VC as such:

    # show interfaces xe-0/1/1
    ether-options {
        802.3ad ae0;
    }
    # show interfaces xe-1/1/1
    ether-options {
        802.3ad ae0;
    }
    show interfaces ae0
    aggregated-ether-options {
        lacp {
            active;
        }
    }

    I have configured the EX as such:

    # show interfaces xe-0/1/0
    ether-options {
        802.3ad ae0;
    }
    # show interfaces xe-0/1/1
    ether-options {
        802.3ad ae0;
    }
    # show interfaces ae0
    aggregated-ether-options {
        lacp {
            active;
        }
    }
    unit 0 {
        family ethernet-switching;
    }

    Now, let's look at the aggregated interfaces.
    Here is the EX-VC, and we can see something odd here already:

    # run show lacp interfaces ae0
    Aggregated interface: ae0
        LACP state:       Role   Exp   Def  Dist  Col  Syn  Aggr  Timeout  Activity
          xe-1/1/1       Actor    No    No   Yes  Yes  Yes   Yes     Fast    Active
          xe-1/1/1     Partner    No    No   Yes  Yes  Yes   Yes     Fast    Active
        LACP protocol:        Receive State  Transmit State          Mux State
          xe-1/1/1                  Current   Fast periodic Collecting distributing
    

    So let's look at the EX side:

    # run show lacp interfaces ae0
    Aggregated interface: ae0
        LACP state:       Role   Exp   Def  Dist  Col  Syn  Aggr  Timeout  Activity
          xe-0/1/1       Actor    No    No   Yes  Yes  Yes   Yes     Fast    Active
          xe-0/1/1     Partner    No    No   Yes  Yes  Yes   Yes     Fast    Active
          xe-0/1/0       Actor    No   Yes    No   No   No   Yes     Fast    Active
          xe-0/1/0     Partner    No   Yes    No   No   No   Yes     Fast   Passive
        LACP protocol:        Receive State  Transmit State          Mux State
          xe-0/1/1                  Current   Fast periodic Collecting distributing
          xe-0/1/0                Defaulted   Fast periodic           Detached

    The EX side looks fine!

    But what's going on with the LACP on the EX-VC side? Let's look at the interfaces, and try to find out why it's only showing xe-1/1/1, when we have configured xe-0/1/1 to be a part of the LACP as well.

     run show interfaces xe-0/1/1
    error: device xe-0/1/1 not found

    Hmmm.. What interfaces can I select?

    Possible completions:
      <interface-name>     Name of physical or logical interface
      xe-0/1/0
      xe-0/1/0.0
      xe-0/1/3
      xe-1/1/0
      xe-1/1/0.0
      xe-1/1/1
      xe-1/1/1.0

    There is no xe-0/1/1, how ever theres an xe-0/1/3, but what the heck is that? It's not configured on the EX-VC, it's not a part ae0!
    I dont know how to move on from here. 😞



  • 2.  RE: EX3300 LAG (LACP) strange behavior

    Posted 01-21-2018 06:16

    HI Iodcdk

     

    Can you please paste me the output of show chassis hardware detail on EX-VC ?

    Is the transeiver plugged-in properly ?

    What code you are running ?

    The partner in EX-VC should be xe-0/1/0

     



  • 3.  RE: EX3300 LAG (LACP) strange behavior

    Posted 01-21-2018 06:23
    Hardware inventory:
    Item             Version  Part number  Serial number     Description
    Chassis                                GD0216520103      Virtual Chassis
    Routing Engine 0 REV 02   650-063365   GD0216520103      EX3300 24-Port
    Routing Engine 1 REV 14   750-034299   GD0213405768      EX3300 24-Port
    FPC 0            REV 02   650-063365   GD0216520103      EX3300 24-Port
      CPU                     BUILTIN      BUILTIN           FPC CPU
      PIC 0                   BUILTIN      BUILTIN           24x 10/100/1000 Base-T
      PIC 1          REV 02   650-063365   GD0216520103      4x GE/XE SFP+
        Xcvr 0       NL-B2    NON-JNPR     ADF20928050001    SFP+-10G-LR
        Xcvr 1                NON-JNPR     AHS0PTV           SFP+-10G-SR
        Xcvr 2                NON-JNPR     AN214M0           SFP+-10G-SR
        Xcvr 3                NON-JNPR     ANS1P5L           SFP+-10G-SR
      Power Supply 0                                         PS 100W AC
      Fan Tray                                               Fan Tray
    FPC 1            REV 14   750-034299   GD0213405768      EX3300 24-Port
      CPU                     BUILTIN      BUILTIN           FPC CPU
      PIC 0                   BUILTIN      BUILTIN           24x 10/100/1000 Base-T
      PIC 1          REV 14   750-034299   GD0213405768      4x GE/XE SFP+
        Xcvr 0       NL-B2    NON-JNPR     ADF209280de0008   SFP+-10G-LR
        Xcvr 1                NON-JNPR     AP50S5L           SFP+-10G-SR
        Xcvr 2                NON-JNPR     AKJ0N60           SFP+-10G-SR
        Xcvr 3                NON-JNPR     ALJ03UM           SFP+-10G-SR
      Power Supply 0                                         PS 100W AC
      Fan Tray                                               Fan Tray
    

    And yes, all SFP+ modules are plugged ind, and working.
    We see the links up.

    The question here, is mostly why xe-0/1/1 doesnt exist when it's configured to be a part of the LACP.

     

    the FPC setup is as follows on the EX-VC:
    xe-0/1/0 ISP

    xe-0/1/1 LACP ae0

    xe-0/1/2 VC

    xe-0/1/3 VC

     

    xe-1/1/0 ISP

    xe-1/1/1 LACP ae0

    xe-1/1/2 VC

    xe-1/1/3 VC

     

    I am not sure what you mean by what code I am running.

    The partner in the EX-VC "should'nt" be anything but what I tell it to be 🙂
    In this case xe-0/1/0 and 1/1/0 is the ISP uplinks, while xe-0/1/1 and xe-1/1/1 is used for the LACP



  • 4.  RE: EX3300 LAG (LACP) strange behavior
    Best Answer

    Posted 01-21-2018 07:02

    could it be that xe-0/1/1 by error is configured as a vc-port? That would explain why xe-0/1/1 is reported as non-existing.

    Please check with 'show virtual-chassis vc-port' and if I'm correct, remove it from via 'request virtual-chassis vc-port delete fpc-slot 0 pic-slot 1 port 1' (please validate fpc/pic numbering before executing command!).

     



  • 5.  RE: EX3300 LAG (LACP) strange behavior

    Posted 01-21-2018 10:58
     run show virtual-chassis vc-port
    fpc0:
    --------------------------------------------------------------------------
    Interface   Type              Trunk  Status       Speed        Neighbor
    or                             ID                 (mbps)       ID  Interface
    PIC / Port
    1/1         Configured         -1    Up           10000
    1/2         Configured         -1    Up           10000        1   vcp-255/1/2
    
    fpc1:
    --------------------------------------------------------------------------
    Interface   Type              Trunk  Status       Speed        Neighbor
    or                             ID                 (mbps)       ID  Interface
    PIC / Port
    1/2         Configured         -1    Up           10000        0   vcp-255/1/2
    1/3         Configured         -1    Up           10000

    From the looks of it, 0/1/1 incorrectly as being VC port. It should have been 0/1/3!!
    Why didnt I think of this...