Welcome to TP-LINK Tech Support Forum
+ Reply to Thread
Results 1 to 1 of 1
  1. #1

    TL-SG2008 802.1AX/802.3AD - No 802.3ad response from Switch

    Region : Germany
    Model : TL-SG2008
    Hardware Version : V1
    Firmware Version : 1.0.0 Build 20150624 Rel.57993

    Hello TP-Link Team,

    i bought the TL-SG2008 a few days ago from Amazon and today finally had time to set it up.
    The device was already running the latest firmware.

    Now to my problem. I have setup my Ubuntu Server 16.04 LTS (latest LTS updates and kernel) and enabled bonding.
    I activated LACP on the switch for port 7 and 8.

    I receive following kernel message from my Ubuntu Server:
    Code:
    bond0: Warning: No 802.3ad response from the link partner for any adapters in the bond
    so i checked for details:
    Code:
    cat /proc/net/bonding/bond0
    Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
    
    Bonding Mode: IEEE 802.3ad Dynamic link aggregation
    Transmit Hash Policy: layer2 (0)
    MII Status: up
    MII Polling Interval (ms): 100
    Up Delay (ms): 0
    Down Delay (ms): 0
    
    802.3ad info
    LACP rate: slow
    Min links: 0
    Aggregator selection policy (ad_select): stable
    
    Slave Interface: enp2s0
    MII Status: up
    Speed: 1000 Mbps
    Duplex: full
    Link Failure Count: 0
    Permanent HW addr: 00:25:90:34:2d:82
    Slave queue ID: 0
    Aggregator ID: 2
    Actor Churn State: none
    Partner Churn State: none
    Actor Churned Count: 0
    Partner Churned Count: 0
    
    Slave Interface: enp3s0
    MII Status: up
    Speed: 1000 Mbps
    Duplex: full
    Link Failure Count: 0
    Permanent HW addr: 00:25:90:34:2d:83
    Slave queue ID: 0
    Aggregator ID: 2
    Actor Churn State: none
    Partner Churn State: none
    Actor Churned Count: 0
    Partner Churned Count: 0
    there is no LACPDU's exchange at all.
    if LACPDU's exchange would happen than it would list information like this:

    taken from the same setup but with a cisco switch!
    you can see the Server and Switch exchange LACPDU's and therefore the bond works and the Server receives information such as this:
    Code:
    Active Aggregator Info:
        Aggregator ID: 1
        Number of ports: 2
        Actor Key: 33
        Partner Key: 2
        Partner Mac Address: cc:e1:7f:2b:82:80
    I have following output in the switch for the switch itself:

    Code:
    TL-SG2008#show lacp internal
    Flags:  S - Device is requesting Slow LACPDUs
            F - Device is requesting Fast LACPDUs
            A - Device is in active mode       P - Device is in passive mode
    
    Channel group 1
                                LACP port     Admin     Oper    Port        Port
    Port      Flags   State     Priority      Key       Key     Number      State
    Gi1/0/7   SA      Up        32768         0x1       0x5e1   0x7         0x3d
    Gi1/0/8   SA      Up        32768         0x1       0x5e1   0x8         0x3d
    my bonding configuration:
    Code:
    # The loopback network interface
    auto lo
    iface lo inet loopback
    
    # The primary network interface
    auto enp2s0
    #iface enp2s0 inet dhcp
    iface enp2s0 inet manual
        bond-master bond0
    
    # The secondary network interface
    auto enp3s0
    iface enp3s0 inet manual
        bond-master bond0
    
    auto bond0
    iface bond0 inet static
        address x.x.x.x
        netmask x.x.x.x
        network x.x.x.x
        broadcast x.x.x.x
        gateway x.x.x.x
        dns-nameservers x.x.x.x
        dns-nameservers x.x.x.x
        dns-nameservers x.x.x.x
        bond-miimon 100
        bond-mode 4
        bond-slaves enp2s0 enp3s0
        bond-lacp-rate slow
    notice bond-mode 4 => 802.3ad which is supported by the TL-SG2008
    notice bond-lacp-rate slow => which the switch requires (see show lacp internal)

    so i checked if the switch see's the network cards. which are intel e1000 NIC's
    Code:
    TL-SG2008#show lacp neighbor
    Flags:  S - Device is requesting Slow LACPDUs
            F - Device is requesting Fast LACPDUs
            A - Device is in active mode       P - Device is in passive mode
    
    Channel group 1
                      LACP port                  Admin  Oper   Port    Port
    Port      Flags   Priority   Dev ID          Key    Key    Number  State
    Gi1/0/7   SA      255        0025.9034.2d82  0      0x9    0x1     0x3d
    Gi1/0/8   SA      255        0025.9034.2d82  0      0x9    0x2     0x3d
    let's check the MAC adress table and see what the switch see's on those ports which are setup for bonding:
    Code:
    TL-SG2008#show mac address-table interface gigabitEthernet 1/0/7
    
    MAC                vlan-id port     type    aging
    ---                ------- ----     ----    -----
    Code:
    TL-SG2008#show mac address-table interface gigabitEthernet 1/0/8
    
    MAC                vlan-id port     type    aging
    ---                ------- ----     ----    -----
    there is nothing.


    This switch is advertised and sold with the "IEEE 802.3ad" feature.
    See here: http://www.tp-link.com/us/products/d...specifications
    But it is not the case: " bond0: Warning: No 802.3ad response from the link partner for any adapters in the bond"
    It is definitly not an Linux kernel issue but an issue on the switches end!

    Apparently it is failing at transmitting and exchanging the LACDPU's.
    Last edited by Celoxocis; 10-17-2017 at 14:35.


 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Copyright 1996-2017 TP-LINK Technologies Co., Ltd. All rights reserved.