Example 2: Traffic flow from b1/ b2 to c1/ c2
Traffic from b1/ b2 to c1/ c2 is always sent by switch B through its MultiLink trunk to the core.
No matter at which switch (E or F) arrives at, it is sent directly to C through the local link.
Example 3: Traffic flow from a to d
Traffic from a to d (and d to a) is forwarded across the interswitch trunk because it is the shortest
path. This is treated as a standard link; SMLT and interswitch trunk parameters are not
considered.
Example 4: Traffic flow from f to c1/ c2
Traffic from f to c1/ c2 is sent out directly from F. Return traffic from c1/ c2 allows you to have
one active VRRP Master for each IP subnet. It is passed across the interswitch trunk if switch
C sends it to E.
SMLT and IST traffic flow example
In an SMLT environment, the two aggregation switches share the same forwarding database
by exchanging forwarding entries using the IST. In
info fdb-e 10
C). The entry for 00:E0:7B:B3:04:00 is shown on node C as being learned on MLT-1, but
because SMLT REMOTE is true, this entry was actually learned from node B. On B, that same
entry is shown as being directly learned through MLT-1 because SMLT REMOTE is false.
Figure 6: Network topology for traffic flow example
Configuration — Link Aggregation, MLT, and SMLT
on page 31, the forwarding databases are shown for a pair of IST nodes (B and
Figure 7: Output of the command show vlan
on page 30shows the network topology.
Split MultiLink Trunking
January 2012
29