Interarea summarization reduces the number of type 3 LSAs that an ABR

advertises into an area when it receives type 1 LSAs. The network

summarization
range is associated with a specific source area for type 1 LSAs.
When a type 1 LSA within the summarization range reaches the ABR from
the
source area, the ABR creates a type 3 LSA for the summarized network
range.
The ABR suppresses the more specific type 3 LSAs, thereby preventing the
generation of the subordinate route’s type 3 LSAs. Interarea summarization
does
not impact the type 1 LSAs in the source area.
Figure 9-19 shows five type 1 LSAs (172.16.1.0/24 through 172.16.15.0/24)
being summarized into one type 3 LSA (the 172.16.0.0/20 network).

The PIM forwarder concept applies to PIM-DM and PIM-SM. It is commonly

used by PIM-DM but rarely used by PIM-SM because the only time duplicate
packets can end up in a LAN is if there is some sort of routing inconsistency.
With the topology shown in Figure 13-20, PIM-SM would not send duplicate
flows into the LAN as PIM-DM would because of the way PIM-SM operates.
For example, assuming that R1 is the RP, when R4 sends a PIM join message
upstream toward it, it sends it to the all PIM routers address 224.0.0.13, and
R2
and R3 receive it. One of the fields of the PIM join message includes the IP
address of the upstream neighbor, also known as the RPF neighbor.
Assuming
that R3 is the RPF neighbor, R3 is the only one that will send a PIM join to
R1.
R2 will not because the PIM join was not meant for it. At this point, a shared
tree
exists between R1, R3, and R4, and no traffic duplication exists.
Figure 13-21 illustrates how duplicate flows could exist in a LAN using
PIMSM. On the topology on the left side, R2 and R4 are running Open
Shortest Path
First (OSPF) Protocol, and R3 and R4 are running Enhanced Interior
Gateway
Routing Protocol (EIGRP). R4 learns about the RP (R1) through R2, and R5
learns about the RP through R3. R4’s RPF neighbor is R2, and R5’s RPF
neighbor is R3. Assuming that Receiver A and Receiver B join the same
group,
R4 would send a PIM join to its upstream neighbor R2, which would in turn
send
a PIM join to R1. R5 would send a PIM join to its upstream neighbor R3,
which
would send a PIM join to R1. At this point, traffic starts flowing downstream
from R1 into R2 and R3, and duplicate packets are then sent out into the
LAN
and to the receivers. At this point, the PIM assert mechanism kicks in, R3 is
elected as the PIM forwarder, and R2’s OIF interface is pruned, as illustrated
in
the topology on the right side.