What are the best practices for configuring port-channels on an Aruba controller?

Aruba Employee
Q:

We can bundle two or more ports in an aruba controller to form a port channel. What are the best practices for configuring the same?



A:

1. Use LACP for port channel rather than a static port channel. LACP will negotiate the configuration with the uplink device and will not use a port if there is any misconfiguration. We can see the port channel type by the command:

#show interface port-channel 1

Port-Channel 1 is administratively up
Hardware is Port-Channel, address is 00:0B:86:6E:D8:2C (bia 00:0B:86:6E:D8:2C)
Description: Link Aggregate (LACP)
Spanning Tree is Forwarding
Switchport priority: 0
Member port:
    GE 1/0, Admin is up, line protocol is up
    GE 1/1, Admin is up, line protocol is upMore Colors...
    GE 1/2, Admin is up, line protocol is up
Last clearing of "show interface" counters 1 day 2 hr 40 min 17 sec
link status last changed 0 day 0 hr 15 min 4 sec
    457803 packets input, 84881469 bytes
    Received 166488 broadcasts, 0 runts, 0 giants, 0 throttles
    3 input error bytes, 0 CRC, 0 frame
    59019 multicast, 291315 unicast
    55214 packets output, 13764067 bytes
    0 output errors bytes, 0 deferred
    0 collisions, 0 late collisions, 0 throttles
Port-Channel 1 is NOT TRUSTED

 

2. A port channel is untrusted by default. This will force all the traffic to enter the user table. This might result in APs doing down / coming up as inactive / dirty flag. Thus we must trust a port channel manually:

(Master) #configure t
Enter Configuration commands, one per line. End with CNTL/Z

(Master) (config) #interface port-channel 1
(Master) (config-channel)#trusted

(Master) (config-channel)#show interface port-channel 1

Port-Channel 1 is administratively up
Hardware is Port-Channel, address is 00:0B:86:6E:D8:2C (bia 00:0B:86:6E:D8:2C)
Description: Link Aggregate (LACP)
Spanning Tree is Forwarding
Switchport priority: 0
Member port:
    GE 1/0, Admin is up, line protocol is up
    GE 1/1, Admin is up, line protocol is up
    GE 1/2, Admin is up, line protocol is up
Last clearing of "show interface" counters 1 day 2 hr 43 min 51 sec
link status last changed 0 day 0 hr 18 min 38 sec
    460047 packets input, 85160136 bytes
    Received 167471 broadcasts, 0 runts, 0 giants, 0 throttles
    3 input error bytes, 0 CRC, 0 frame
    59775 multicast, 292576 unicast
    56529 packets output, 13862313 bytes
    0 output errors bytes, 0 deferred
    0 collisions, 0 late collisions, 0 throttles
Port-Channel 1 is TRUSTED

 

3. If possible, configure EVEN number of member of port channels. This will allow even hash distribution resulting in more equal bandwidth utilization across the links.

4. a member port inherits the configuration of the port channel. Thus the port level configuration (like spanning tree, trunk mode native vlan etc.) should only be configured on the port channel interface and not on the member ports:

(Master) (config-channel)#interface port-channel 1
(Master) (config-channel)#switchport mode trunk
 

5. At lease one device on a port channel member link should be in active mode for LACP. If bot participants are passive, the LACP port channel will not come up. 

Version history
Revision #:
2 of 2
Last update:
‎02-23-2017 01:46 PM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: