Wired Intelligent Edge

 View Only
last person joined: yesterday 

Bring performance and reliability to your network with the HPE Aruba Networking Core, Aggregation, and Access layer switches. Discuss the latest features and functionality of your switching devices, and find ways to improve security across your network to bring together a mobile-first solution
Expand all | Collapse all

Smart Rate and Link Aggregation

This thread has been viewed 7 times
  • 1.  Smart Rate and Link Aggregation

    Posted Apr 29, 2020 01:00 PM

    Ive been search all over but cannot find this inforamtion,

    is it posible to create a Link Aggregation using a Smart Rate and non Smart Rate port?

    for instance between a 510 Series AP and a 2930M Switch. i have a future project and im looking to create a redundent links betwen a 3x 2930M stack and around 10 AP and was wonding if the Smart rate ports would work at the higher Multi-gig speeds is a lag.

     



  • 2.  RE: Smart Rate and Link Aggregation

    MVP GURU
    Posted Apr 29, 2020 02:02 PM

    Hi! Port Trunking (Link Aggregation) requires that all involved links (port trunk member interfaces) must be:

     

    1. point-to-point connections between a switch and another switch (there are exceptions: connections can be "not co-terminus" only when you're dealing with a virtual switch made of two ore more physical switches like with: DT-Trunking, VSF, VSX, IRF or Backplane Stacked Switches deployments), router, server, or workstation configured for port trunking.
    2. Not interrupted by intervening, non-trunking devices in between.
    3. referenced to physical ports - on both ends - that are working using the same mode (speed and duplex) and same flow control settings.

    Given this if the E0/E1 of the Aruba 510 Access Point are set with that in mind you can aggregate E0 and E1 together by using LACP as your preferred link aggregation control protocol.

     

    IMHO forget the case of aggregating the Aruba 510 E0 interface - working at a negotiated Smart Rate speed of 2.5 Gbps - with the Aruba 510 E1 interface working instead at normal Gigabit Ethernet of 1 Gbps. This would violate one of the essential requirements listed above (speed mismatch between Port Trunk member ports).