Wireless Access

last person joined: an hour ago 

Access network design for branch, remote, outdoor and campus locations with Aruba access points, and mobility controllers.
Expand all | Collapse all

Port Channel failing

This thread has been viewed 21 times
  • 1.  Port Channel failing

    Posted Jul 23, 2021 12:30 PM
    I am experiencing a problem creating a port channel in AOS 8.6 

    Interface 0/0/4 and 0/0/5 work okay as non LACP 10 G trunks. However, when in a LACP active trunk group they don't work. All looks to be okay with the config. I must be overlooking something simple. I've taken 0/0/4 out of the port channel group, and left the md working on 0/0/4. The only thing I haven't tried is to convert the interfaces to access before entering them into the port channel. Any pointer on the setup?

    Config for port channel 1, without 0/04 which is been put back into production:

    Port-Channel 1 is administratively up, Link is up, Line protocol is down
    Hardware is Port-Channel, address is 00:0B:86:B8:1D:C7 (bia 00:0B:86:B8:1D:C7)
    Description: Link Aggregate (LACP)
    Spanning Tree is Discarding
    Switchport priority: 0
    MTU: 1500 bytes
    Member port(s):
    GE 0/0/5, Admin is up, Link is up, Line protocol is down
    Speed :0 Mbps
    Interface index: 8194
    Last clearing of "show interface" counters 10 day 16 hr 18 min 46 sec
    link status last changed 4 day 3 hr 14 min 50 sec
    2794142 packets input, 1055694895 bytes
    Received 563756 broadcasts, 0 runts, 0 giants, 0 throttles
    0 input error bytes, 0 CRC, 0 frame
    451748 multicast, 2230386 unicast
    3399114 packets output, 1443483042 bytes
    0 output errors bytes, 0 deferred
    0 collisions, 0 late collisions, 0 throttles
    Port-Channel 1 is TRUSTED

    Statistics for member port: GE 0/0/5
    2794142 packets input, 1055694895 bytes
    Received 563756 broadcasts, 0 runts, 0 giants, 0 throttles
    0 input error bytes, 0 CRC, 0 frame
    451748 multicast, 2230386 unicast
    3399114 packets output, 1443483042 bytes
    0 output errors bytes, 0 deferred
    0 collisions, 0 late collisions, 0 throttles


    Name: Port-channel 1
    Switchport: Enabled
    Administrative mode: trunk
    Operational mode: trunk
    Administrative Trunking Encapsulation: dot1q
    Operational Trunking Encapsulation: dot1q
    Access Mode VLAN: 0 ((Inactive))
    Trunking Native Mode VLAN: 140 (mobility management)
    Trunking Vlans Enabled: < correct list of VLANS > 
    Trunking Vlans Active: < same as correct list of VLANs above >
    (nodename) [MDC] *#


    (nodename) [MDC] *# show interface port-channel 1 trusted-vlan

    Name: Port-Channel1
    Trusted Vlan(s)
    1-4094


    ------------------------------
    Racingyacht
    ------------------------------


  • 2.  RE: Port Channel failing

    Posted Jul 24, 2021 05:43 PM
    Take a look at the thread here for some ideas on the switch side of things:  https://community.arubanetworks.com/community-home/digestviewer/viewthread?MID=49433

    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
    ------------------------------



  • 3.  RE: Port Channel failing

    Posted Jul 25, 2021 10:25 AM
    Thanks for the link to the doc. I will change the individual interfaces to allow all vlans as per the document instead of only the vlans that I currently need. That is a much better approach as the port channel configuration will control vlans to allowed.
     
    I note that within AOS8.6 there are no longer options via the GUI or cli to configure the port channel priority, or the timeout period. Do these parameters now default, and therefore they are no longer required to be entered in the config?

    ------------------------------
    Racingyacht
    ------------------------------



  • 4.  RE: Port Channel failing

    Posted Jul 25, 2021 10:59 AM
    Unfortunately, I don't know.

    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
    ------------------------------