Configuring Point-To-Multipoint Lsps; Flooding Unknown Traffic Using Point-To-Multipoint Lsps In Vpls; Figure 6: Flooding Unknown Vpls Traffic Using Ingress Replication; Figure 7: Flooding Unknown Vpls Traffic Using A Point-To-Multipoint Lsp - Juniper EX9200 Features Manual

Vpls feature guide ex series
Hide thumbs Also See for EX9200:
Table of Contents

Advertisement

CHAPTER 8

Configuring Point-to-Multipoint LSPs

Flooding Unknown Traffic Using Point-to-Multipoint LSPs in VPLS

Copyright © 2016, Juniper Networks, Inc.
Flooding Unknown Traffic Using Point-to-Multipoint LSPs in VPLS on page 71
Mapping VPLS Traffic to Specific LSPs on page 75
For a VPLS routing instance, you can flood unknown unicast, broadcast, and multicast
traffic using point-to-multipoint (also called P2MP) LSPs. By default, VPLS relies upon
ingress replication to flood unknown traffic to the members of a VPLS routing instance.
This can cause replication of data at routing nodes shared by multiple VPLS members,
as shown in
Figure 6 on page
provider router P1 and doubled between provider routers P1 and P2. By configuring
point-to-multipoint LSPs to handle flood traffic, the VPLS routing instance can avoid
this type of traffic replication in the network, as shown in

Figure 6: Flooding Unknown VPLS Traffic Using Ingress Replication

Figure 7: Flooding Unknown VPLS Traffic Using a Point-to-Multipoint LSP

71. The flood data is tripled between PE router PE1 and
Figure 7 on page
71.
71

Advertisement

Table of Contents
loading

Table of Contents