Scribd Logo
Upload

Welcome to Scribd!

  • Networking LACP Vs Trunk

    Uploaded by

    tvarvara
    22 views1 page
    LACP uses the 802.3ad protocol to negotiate interfaces with the remote device and uses hashing algorithms to load balance traffic across the interfaces. It can adjust the number of interfaces without impacting the logical link and detects misconfigured interfaces to prevent packet loss. In contrast, a "trunk" simply combines interfaces without negotiation, requiring both sides to be configured identically for the link to work. LACP is preferred when possible as it is easy to implement and provides benefits like load balancing and interface adjustment without impact.

    Original Description:

    Original Title

    Networking LACP vs Trunk

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    LACP uses the 802.3ad protocol to negotiate interfaces with the remote device and uses hashing algorithms to load balance traffic across the interfaces. It can adjust the number of interfaces without impacting the logical link and detects misconfigured interfaces to prevent packet loss. In contrast, a "trunk" simply combines interfaces without negotiation, requiring both sides to be configured identically for the link to work. LACP is preferred when possible as it is easy to implement and provides benefits like load balancing and interface adjustment without impact.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as docx, pdf, or txt
    22 views1 page

    Networking LACP Vs Trunk

    Uploaded by

    tvarvara
    LACP uses the 802.3ad protocol to negotiate interfaces with the remote device and uses hashing algorithms to load balance traffic across the interfaces. It can adjust the number of interfaces without impacting the logical link and detects misconfigured interfaces to prevent packet loss. In contrast, a "trunk" simply combines interfaces without negotiation, requiring both sides to be configured identically for the link to work. LACP is preferred when possible as it is easy to implement and provides benefits like load balancing and interface adjustment without impact.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as docx, pdf, or txt
    of 1

    LACP vs Trunk

    It has nothing to do with VLANs.

    LACP uses the 802.3ad protocol to negotiate the interfaces with the remote device. It uses
    hash algorithms for load-balancing and can be increased or decreased in the number of
    interfaces without any impact to the logical link. It also detects if the other side of the
    interface is misconfigured and stops sending packets on misconfigured interfaces to prevent
    packet loss. You may know it from Cisco as an EtherChannel. 

    "trunk" just puts this interfaces together but does not negotiate anything with the other site. It
    is mandatory that the other site is also configured as a trunk for the link to be working.

    I usually go with LACP as often as possible, since it is really easy to implement and brings
    only positives.
    Some server (f.e. VMWware ESXi ) can not "speak" 802.3ad natively (or only with the
    biggest license), so I have to use static trunks or switch independent load-balancing.

    You might also like