Junos® OS Ethernet Interfaces Configuration ... - Juniper Networks

Junos ®
OS 12.3 Ethernet Interfaces Configuration Guide
Data Forwarding with Qualified Learning
Since there are no multichassis links in learning domain ld3, for the IGMP speakers (hosts
and routers) in learning domain ld3, P-A and S-A will not appear to be one switch.
This discussion assumes interchassis link ICL1 corresponds to learning domain ld1 and
interchassis link ICL2 corresponds to learning domain ld2.
Control packet flow is supported, with the exception of passing information to IRB.
This discussion assumes one learning domain (LD), ld1, and further assumes interface I1
on router P-A is connected to the PIM-DR in the learning domain and pulls the traffic
from sources in the core.
For delivering traffic to hosts connected to router S-A (which is the non-DR) on the
single-homed link like I2, I4 (belonging to ld1), we rely on ICL1. The traffic that hits router
P-A on interface I1 is sent over interchassis link ICL1 to router S-A to be delivered to the
links that have reported interests in s,g or the links that are router facing in learning domain
ld1.
Static Groups on Single Homed Interfaces
When the interface ae0 leg in router P-A goes down, the hosts connected to the
multichassis link receive traffic from interface I1 via the interchassis link ICL1. In router
S-A, traffic received on interchassis link ICL1 is sent to multichassis links in the outgoing
interface list for which the aggregated Ethernet counterpart in router P-A is down.
It is further assumed that interface I9 in router S-A belongs to the learning domain ld3
with interests in s,g, and that interface I10 in learning domain ld3 in router P-A receives
traffic for s,g. Interface I9 does not receive data in this topology because there are no
multichassis links (in a-a mode) and hence no interchassis link in learning domain ld3.
For multichassis links, the static group configuration should exist on both legs and
synchronization with the other chassis is not required.
Synchronization of the static groups on single homed interfaces between the chassis is
not supported, however the addition of logical interfaces to the default outgoing interface
list supports traffic delivery to the interface within a static configuration.
Router Facing Interfaces as Multichassis Links
108
IGMP queries could arrive on either leg of the multichassis links but in both peers, the
multichassis link should be considered as router facing.
Reports should exit only once from the multichassis link, that is from only one leg.
The following MC-LAG support for IGMP snooping in IRB is provided:
• Non-proxy snooping
• Logical interfaces must be outgoing interfaces for all routes including the default route
• IGMP snooping in a pure Layer 2 switch
Copyright © 2012, Juniper Networks, Inc.