Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Configuring Multicast Load Balancing for Use with Aggregated 10-Gigabit Ethernet Links on EX8200 Switches (CLI Procedure)

    EX8200 switches support multicast load balancing on link aggregation groups (LAGs). Multicast load balancing evenly distributes Layer 3 multicast routed traffic over the aggregated links. You can aggregate up to twelve 10-gigabit Ethernet links to form a virtual link or a LAG. The MAC client can treat this virtual link as if it were a single link to increase bandwidth, provide graceful degradation if a failure occurs, and increase availability. On EX8200 switches, multicast load balancing is enabled by default. However, if it is explicitly disabled, you can reeable it.

    Note: An interface with an already configured IP address cannot form part of the LAG.

    To configure a LAG and ensure that multicast load balancing is enabled:

    1. Specify the number of aggregated Ethernet interfaces to be created:
      [edit chassis]
      user@switch# set aggregated-devices ethernet device-count number
    2. Specify the minimum number of links for the aggregated Ethernet interface (aex)—that is, the defined LAG—to be labeled up:

      Note: By default, only one link needs to be up for the LAG to be labeled up.

      [edit interfaces]
      user@switch# set aex aggregated-ether-options minimum-links number
    3. Specify each member to be included in the LAG:
      [edit interfaces]
      user@switch# set interface-name ether-options 802.3ad aex
    4. To reenable multicast load balancing:
      [edit chassis]
      user@switch# set multicast-loadbalance

      Note: You can disable multicast load balancing on an EX8200 switch by using the set chassis multicast-loadbalance disable command.

      Note: If the EX8200 switch is already handling multicast streams, then you reenable multicast load balancing, the existing steams might not be distributed evenly. In this case, we recommend clearing data related to these streams by using the clear pim join all and clear igmp-snooping membership commands.

    The default multicast load-balancing hashing algorithm, crc-sgip, involves the cyclic redundancy check of source and group IP addresses. You can optionally change the value of the hash-mode option in the multicast-loadbalance statement to try different algorithms until you find the one that best distributes your Layer 3 routed multicast traffic.

    If you change the hashing algorithm when multicast load balancing is disabled, the new algorithm takes effect after you reenable multicast load balancing.

    Note: You do not need to set link speed, which is automatically determined by the size of the LAG that uses multicast load balancing. For example, the link speed of a 40-gigabit LAG would be 40 gigabits per second.

    Modified: 2017-09-13