Service Side

The following platforms support EtherChannel and also offer load balancing for EtherChannel on the service side:

• Cisco 4000 Series Integrated Services Routers

  • Cisco 4451-X Integrated Services Router

  • Cisco 4461 Integrated Services Router

  • Cisco 4431 Integrated Services Router

  • Cisco 4331 Integrated Services Router

  • Cisco 4351 Integrated Services Router

• Cisco ASR 1000 Series Aggregation Services Routers

  • Cisco ASR 1001-X Router

  • Cisco ASR 1006-X Router

  • Cisco ASR 1001-HX Router

  • Cisco ASR 1002-HX Router

  • Cisco ASR 1002-X Router

• Cisco Catalyst 8000V Edge Software

• Cisco Catalyst 8200 Router

• Cisco Catalyst 8300 Router

• Cisco Catalyst 8500 Series Edge Router

Supported NIMs

The following NIMs are supported on Integrated Services Routers, for service side:

• NIM-1GE-CU-SFP

• NIM-2GE-CU-SFP

• SM-X-4x1G-1x10G

• SM-X-6X1G

• C-NIM-2T

• C-NIM-1X

• C-NIM-1M

Note	Network Interface Modules (NIMs) with L2 ports do not support EtherChannels on the service side.

Enable Flow Based Load Balancing on a Global Level

Note	The default hash algorithm for flow-based load balancing is src-dst-ip.

Port-channel load-balancing flow 

Enable Flow Based Load Balancing Per Port Channel

interface Port-channel channel-number 
load-balancing flow 

Enable Hash Algorithms for Flow based Load Balancing for Each Portchannel Interface

interface Port-channel 1
load-balance-hash-algo [src-dst-ip dst-ip | dst-mac | src-dst-ip | src-dst-mac | src-dst-mixed-ip-port | src-ip | src-mac ] 

Enable Hash Algorithms for Flow based Load Balancing on a Global level

port-channel load-balance-hash-algo {dst-ip | dst-mac | src-dst-ip | src-dst-mac | src-dst-mixed-ip-port | src-ip | src-mac} 
  

Note

From Cisco Catalyst SD-WAN Manager Release 20.15.1, you can use any other hash algorithims for load balancing on the service side. The Hash Algorithms For Flow-based Load Balancing feature is supported only on Cisco Aggregation Services Routers platforms, where the hardware load-balancing for Etherchannel is supported. This command is not supported on Cisco Integrated Services Routers and Cisco Catalyst Router platforms.

This example shows a configuration where flow-based load balancing is configured on port channel 2 while the VLAN manual method is configured globally:

!
port-channel load-balancing vlan-manual

.
.
.
interface Port-channel2
 ip address 10.0.0.1 255.255.255.0
 no negotiation auto
 load-balancing flow
!

interface GigabitEthernet2/1/0
 no ip address
 negotiation auto
 cdp enable
 channel-group 2
!
interface GigabitEthernet2/1/1
 no ip address
 negotiation auto
 cdp enable
 channel-group 2
!

This example shows a configuration for each port channel interface where port-channel1 uses sdwan hash algorithm for the transport side, Port-channel2 uses the src-dst-mixed-ip-port for the service side, and Port-channel3 uses the globally default src-dst-ip hash algorithm for the service side. :

device(config)# interface Port-channel 1
device(config-if)# load-balance-hash-algo sdwan
device(config-if)# exit

device(config)# interface Port-channel 2    
device(config-if)# load-balance-hash-algo src-dst-mixed-ip-port 
device(config-if)# exit

device(config)# interface Port-channel 3                    
device(config-if)# no shut 
device(config-if)# commit
device(config-if)# end

The following is a sample output to view the configuration for each interface port channel using show etherchannel load-balancing command.

device# show etherchannel load-balancing 
flow-based
LB Algo type: Source Destination IP

 Port-Channel:                       LB Method
    Port-channel1                   :  flow-based (SDWAN Inner packet LB)
    Port-channel2                   :  flow-based (Source Destination Port, IP addr)
    Port-channel3                   :  flow-based (Source Destination IP)

Manual Traffic Distribution Based on VLAN ID

port-channel load-balancing vlan-manual 

Note	This command is available for configuration in the global configuration mode, and applies to all the port-channel configured on the device.

This example shows how the load-balancing configuration can be globally applied to define policies for handling traffic by using the port-channel load-balancing command.

port-channel load-balancing vlan-manual

!
interface Port-channel1
!
interface Port-channel1.100
 encapsulation dot1Q 100 primary GigabitEthernet 1/1/1
 secondary GigabitEthernet 1/2/1
 ip address 10.16.2.100 255.255.255.0
!
interface Port-channel1.200
 encapsulation dot1Q 200 primary GigabitEthernet 1/2/1
 ip address 10.16.3.200 255.255.255.0
!
interface Port-channel1.300
 encapsulation dot1Q 300
 ip address 10.16.4.300 255.255.255.0
 !
interface GigabitEthernet 1/1/1
 no ip address
 channel-group 1!
interface GigabitEthernet 1/2/1
 no ip address
 channel-group 1

Enable VLAN Load Balancing Per Port Channel on the Service Side

interface Port-channel channel-number 
 load-balancing vlan 

This example shows configuration for VLAN load balancing on the service side, when the flow-based load balancing is set to default on the global level:

 interface Port-channel channel-number 
 interface GigabitEthernet slot/subslot/port 
  channel-group channel-group-number 
  interface GigabitEthernet slot/subslot/port 
  channel-group channel-group-number 
 interface Port-channel channel-number 
  load-balancing vlan  
 interface Port-channel channel-number 
  encapsulation dot1Q vlan_id primary interface1 secondaryinterface2 

Note	Interface 1 and interface 2 must be member ports of a port channel when encapsulation dot1q is configured.

From Cisco IOS XE Catalyst SD-WAN Release 17.13.1a, the following platforms support EtherChannels on the transport side. From Cisco IOS XE Catalyst SD-WAN Release 17.14.1a, the following platforms support load balancing:

• Cisco 4000 Series Integrated Services Routers

  • Cisco 4461 Integrated Services Router

• Cisco ASR 1000 Series Aggregation Services Routers

  • Cisco ASR 1001-HX Router

  • Cisco ASR 1002-HX Router

• Cisco Catalyst 8200 Series Edge Routers

• Cisco Catalyst 8300 Series Routers

• Cisco Catalyst 8500 Series Edge Routers

Note	Starting with Cisco IOS XE Catalyst SD-WAN Release 17.14.1a, the load balancing configuration command portchannel load-balance-hash-algo sdwan is supported only on the Cisco 4461 Integrated Services Router and Cisco Catalyst 8300 Series routers.

1. From the Cisco SD-WAN Manager menu, choose Configuration > Configuration Groups.

2. Under Transport and Management, click Add New to add a new service profile or select any existing service profiles, and click Edit.

3. Select +, and click on the Ethernet Interface to add a new interface. See Ethernet Interface for more details.

4. Select Add New from the Ethernet Interface drop-down menu.

5. Under Basic Configurations, enter the interface name and description.

6. Click Ether Channel, and assign the EtherChannel to a port channel or member interface from the drop down menu.

   Note	You can create multiple interfaces which can be either member or port channel interfaces.

7. Select Global from the Tunnel field, to enable a tunnel for the port channel interface.

   Note	To reassign the ethernet interface type, you must delete the existing ethernet interface feature and create a new one.

8. Click Save.

9. Click Configuration tab, and deploy the newly created port channels.

Enable Load Balancing on Individual Portchannel Interface

Minimum supported releases: Cisco IOS XE Catalyst SD-WAN Release 17.15.1a Cisco Catalyst SD-WAN Manager Release 20.15.1

Note	We recommend using this method to configure load balancing for EtherChannels on the transport side.

1. Enter the port channel interface configuration mode.

   interface Portchannel channel number

2. Enable load balancing on an individual port channel.

   load-balance-hash-algo sdwan

Enable Load Balancing Globally for EtherChannels on the Transport Side

Minimum supported releases: Cisco IOS XE Catalyst SD-WAN Release 17.14.1a and Cisco Catalyst SD-WAN Manager Release 20.14.1

For more information about using CLI templates, see CLI Add-On Feature Templates and CLI Templates.

port-channel load-balance-hash-algo sdwan 

Note	In this command, port-channel load-balance-hash-algo sdwan , the sdwan option was added in Cisco IOS XE Catalyst SD-WAN Release 17.14.1a.

Enable Hash Algorithms Globally for EtherChannels on the Transport Side

1. Configure the algorithm used for load balancing.

   To configure load balancing for IPv4 addresses, which is the default setting, use the following configuration:

    sdwan 
    ip load-sharing algorithm {src-dst-ip|ip-and-ports|src-ip-only} 

   To configure load balancing for IPv6 addresses, use the following configuration:

    sdwan 
    ipv6 load-sharing algorithm {src-dst-ip|ip-and-ports|src-ip-only} 

   • src-dst-ip : Balances traffic based on both source and destination IP addresses.

   • ip-and-ports : Balances traffic using a combination of IP addresses and port numbers.

   • src-ip-only : Balances traffic based solely on the source IP address.

   The ip load-sharing algorithm command is a global configuration that applies to all Cisco Catalyst SD-WAN tunnels. Changing the algorithm with options such as src-dst-ip or src-dst-mixed-ip-port affects the load-sharing mechanism for other Cisco Catalyst SD-WAN tunnel traffic as well.

   When you configure a port channel on both the service side and the transport side, using the port-channel load-balance-hash-algo sdwan command applies load balancing to the transport side. For the Service side, the port channel defaults to the src-dst-ip load balancing mode. For more information, see Configure Network Interfaces.

   To change the load-balancing algorithm for the Service side when a Transport-VPN port-channel is also configured, use the port-channel load-balance-hash-algo command. This command allow you to switch from the default sdwan mode to alternative modes such as dst-ip , dst-mac , src-dst-ip , src-dst-mac , src-dst-mixed-ip-port , src-ip , or src-mac . However, this change disables the SD-WAN-based load balancing for the transport side.

Here's the complete configuration for enabling load balancing and apply the desired hash algorithm for traffic distribution on the transport side of Cisco IOS XE Catalyst SD-WAN devices.

port-channel load-balance-hash-algo sdwan
sdwan
 ip load-sharing algorithm src-dst-ip

port-channel load-balance-hash-algo sdwan
sdwan
 ipv6 load-sharing algorithm src-dst-ip

This example shows configuration enabling load balancing for each port channel interface. When sdwan hash algorithm is configured on the transport side, you can enable different hash algorithm options on the service side.

device(config)# interface Port-channel 1
device(config-if)# load-balance-hash-algo sdwan
device(config-if)# exit

device(config)# interface Port-channel 2    
device(config-if)# load-balance-hash-algo src-dst-mixed-ip-port 
device(config-if)# exit

device(config)# interface Port-channel 3                    
device(config-if)# no shut 
device(config-if)# commit
device(config-if)# end

The following is a sample output to view the configuration for per-interface port channel using show etherchannel load-balancing command.

device# show etherchannel load-balancing 
flow-based
LB Algo type: Source Destination IP

 Port-Channel:                       LB Method
    Port-channel1                   :  flow-based (SDWAN Inner packet LB)
    Port-channel2                   :  flow-based (Source Destination Port, IP addr)
    Port-channel3                   :  flow-based (Source Destination IP)

In Cisco Catalyst SD-WAN Manager, you can configure aggregate EtherChannel QoS using the CLI templates. For more information about using CLI templates, see CLI Add-On Feature Templates and CLI Templates.

Note	By default, CLI templates execute commands in global config mode.

1. Create the aggregated port channel.

   
   platform qos port-channel-aggregate port-channel-number 
    interface Port-channel channel-number 
    no shutdown 
    ip address ip-address mask  

2. Assign member links to port channel.

   
    interface GigabitEthernet slot/subslot/port 
     no negotiation auto 
     channel-group channel-group-number mode {active passive} 
     exit 

3. Configure tunnels.

   
    interface Tunnel tunnel-number 
     no shutdown 
     ip unnumbered port-channel-interface 
     tunnel source port-channel-interface 
     tunnel mode sdwan 

   
    sdwan 
     interfacechannel-group-number 
      tunnel-interface 
       encapsulation ipsec 
       color public-internet 

4. Configure QoS.

   
    interface channel-group-number 
     service-policy output pre-defined qos policy-map 
     

Here's the complete configuration example for configuring aggregate EtherChannel QoS.

!
class-map match-any Best-Effort
 match qos-group 2
!
class-map match-any Bulk
 match qos-group 3
!
class-map match-any Business
 match qos-group 1
!
class-map match-any Critical
 match qos-group 0
!
policy-map qos_template
 class Critical
  police rate percent 15
  !
  priority level 1
 !
 class Business
  bandwidth remaining percent 55
 !
 class Best-Effort
  bandwidth remaining percent 10
 !
 class Bulk
  bandwidth remaining percent 20
 !
!
policy-map shape_Port-channel1
 class class-default
  service-policy qos_template
  shape average 100000000
 !
!
interface TenGigabitEthernet0/1/6
 no shutdown
 no negotiation auto
 channel-group 1 mode active
 lacp rate fast
exit
interface TenGigabitEthernet0/1/7
 no shutdown
 no negotiation auto
 channel-group 1 mode active
 lacp rate fast
exit
interface Port-channel1
 no shutdown
 ip address 10.1.15.15 255.255.255.0
 ipv6 nd ra suppress all
 service-policy output shape_Port-channel1
exit
interface Tunnel1
 no shutdown
 ip unnumbered Port-channel1
 tunnel source Port-channel1
 tunnel mode sdwan
exit
!
sdwan
 interface Port-channel1
  tunnel-interface
   encapsulation ipsec
   color lte
   no allow-service bgp
   allow-service dhcp
   allow-service dns
   allow-service icmp
   no allow-service sshd
   no allow-service netconf
   no allow-service ntp
   no allow-service ospf
   no allow-service stun
   allow-service https
   no allow-service snmp
   no allow-service bfd
  exit
 exit