Configure Dynamic LAG

About this task

Perform this procedure to configure a dynamic LAG.

Procedure

  1. Enter the interface configuration mode and configure the ingress group with the required ingress ports. 
    device(config)# interface ethernet 1/1
device(config-if)# ingress-group ingress-group-name
device(config-ingress-group-name)#
  2. Enter the global configuration mode and configure a LAG or port-channel with single or multiple interfaces. 
    device# configure terminal 
device(config)# interface port-channel 1
  3. Configure LACP. 
    device(config)# protocol lacp
  4. Enter the interface configuration mode and add LAG interfaces or port-channels to ingress (LAG1) and egress (LAG2) groups, as required. 
    device(config)# interface ethernet 1/1 
device(config-if)# channel-group LAG1 mode on
device(config-if)# channel-group LAG2 mode on
  5. Verify if LACP is able to bring other ports up when the active port is down.
  6. Configure the required options for L2 (MAC) or L3 (IPv4/IPv6) ACL in the access list:
    • L2 (MAC) ACL: 
      device# match mac access-list name
    • L3 (IP) ACL:
      device# match ip access-list name
    • L3 (IPv6) ACL:
      device# match ipv6 access-list name
  7. Enter the route-map configuration mode and configure L2 or L3 ACL in the route-map.
    • Deny: Traffic flows or packets that match this criteria are dropped.
    • Permit: Traffic flows or packets that match this criteria are forwarded to egress group or egress port.
    device# config-route-map
device(config-route-map)# forward-action [ permit | deny ]
    The traffic flows or packets are dropped or forwarded based on the configured criteria in the route-map.
  8. Apply route-map policy to the ingress group. 
    device(config-ingress-group-name) # route-map name
  9. Send the traffic flows to the device under test.
  10. Verify that the traffic flows received from multiple interfaces of LAG1 are aggregated.
  11. Verify that the forwarded traffic received at LAG2 is symmetric load balanced across multiple egress ports.
  12. Verify the gNMI or CLI LAG/port-channel statistics to determine the number of flows aggregated and/or load balanced.
  13. Verify the gNMI or CLI ingress and/or egress group statistics to determine the number of packets or flows dropped.
  14. Verify the statistics by enabling the logs of forwarding agents.
9038134-00 Rev AA