21.03.2013 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Figure 9: Multicast Topology with Source Connected via MC-Link<br />

ge-0/0/0.0<br />

Up and Down Event Handling<br />

Copyright © 2012, <strong>Juniper</strong> <strong>Networks</strong>, Inc.<br />

ae1.0 ae1.0<br />

MCL2<br />

N1<br />

ICCP<br />

ICL<br />

N2<br />

Active Active<br />

ae0.0 ae0.0<br />

MCL1<br />

ge-1/0/0.0<br />

In Figure 9 on page 97, MCL1 and MCL2 are on different devices and the multicast source<br />

or IGMP querier is connected via MCL2. The data forwarding behavior seen is similar to<br />

that explained for multicast topology with source connected via Layer 3.<br />

NOTE: IGMP snooping should not be configured in proxy mode. There should<br />

be no IGMP hosts or IGMP/PIM routers sitting on the ICL interface.<br />

The following conditions apply to up and down event handling:<br />

1. If the interchassis control protocol (ICCP) connection is UP but the ICL interface<br />

becomes DOWN, the router configured as standby will bring down all the multichassis<br />

aggregated <strong>Ethernet</strong> interfaces shared with the peer which is connected to ICL. This<br />

will make sure that there are no loops in the network. Otherwise, both PEs will becomes<br />

PIM designated routers and, hence, forward multiple copies of the same packet to<br />

the customer edge.<br />

Chapter 4: Configuring Aggregated <strong>Ethernet</strong> <strong>Interfaces</strong><br />

2. If the ICCP connection is UP and the ICL comes UP, the router configured as standby<br />

will bring up the multichassis aggregated <strong>Ethernet</strong> interfaces shared with the peer.<br />

3. If both the ICCP connection and the ICL are DOWN, the router configured as standby<br />

will bring up the multichassis aggregated <strong>Ethernet</strong> interfaces shared with the peer.<br />

4. The layer 2 address learn daemon (l2ald) does not store the information about a MAC<br />

address learned from a peer in the kernel. If l2ald restarts, and if the MAC address was<br />

not learned from the local multichassis aggregated <strong>Ethernet</strong> interface, l2ald will clear<br />

the MAC addresses and this will cause the router to flood the packets destined to this<br />

MAC address. This behavior is similar to that in a Routing Engine switchover. (Please<br />

note that currently l2ald runs on a Routing Engine only when it is a master). Also,<br />

during the time l2ald is DOWN, ARP packets received from an ICCP peer will be<br />

g017544<br />

97

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!