8. (Optional) The VCF forwards broadcast, unknown unicast, and multicast (BUM) traffic among the
members of the VCF using multicast distribution trees (MDTs). By default, the VCF creates MDTs for
every member of the VCF with that member as the root node of an MDT. If this default MDT creation
method is not optimal for your installation, you can control which members become MDT root nodes.
The set virtual-chassis member member-id fabric-tree-root configuration statement preempts the
default method of creating MDTs, and specifies whether a member in a VCF can be an MDT root node.
If this statement is configured for one or more members, MDTs are created only with the specified
members as root nodes. See Understanding Traffic Flow Through a Virtual Chassis Fabric and fabric-tree-root
for more on why you might want to choose this MDT creation method instead of the default method.
Note that if you decide to use this option, we recommend that you specify all the spine members (and
only spine members) as MDT root nodes.
If desired, configure the spine devices in the VCF to be fabric MDT root nodes. For example, if you are
preprovisioning a VCF with members 0 through 3 as spine devices (independent of the role):
[edit virtual-chassis]
user@device# set member 0 fabric-tree-root
user@device# set member 1 fabric-tree-root
user@device# set member 2 fabric-tree-root
user@device# set member 3 fabric-tree-root
NOTE: This option can also be configured anytime later during VCF operation if you observe
internal VCF multicast traffic flow issues with default MDTs.
9. Commit the configuration:
user@device# commit
10. (EX4300 switches in a mixed QFX5100 VCF using 40-Gbps QSFP+ interfaces as VCPs only) Perform
one of the following tasks to convert the 40-Gbps QSFP+ interfaces into VCPs:
377