Configuring Static Point-To-Multipoint Flooding Lsps; Configuring Dynamic Point-To-Multipoint Flooding Lsps; Configuring Dynamic Point-To-Multipoint Flooding Lsps With The Default; Template - Juniper EX9200 Features Manual

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

Advertisement

Configuring Static Point-to-Multipoint Flooding LSPs

Configuring Dynamic Point-to-Multipoint Flooding LSPs

Copyright © 2016, Juniper Networks, Inc.
The following sections describe how to configure static and dynamic point-to-multipoint
LSPs for flooding unknown traffic in a VPLS routing instance:
Configuring Static Point-to-Multipoint Flooding LSPs on page 73
Configuring Dynamic Point-to-Multipoint Flooding LSPs on page 73
The
option creates a static flooding point-to-multipoint LSP that includes all
static-lsp
of the neighbors in the VPLS routing instance. Flood traffic is sent to all of the VPLS
neighbors using the generated point-to-multipoint LSP. VPLS neighbors added to the
routing instance later are not automatically added to the point-to-multipoint LSP. You
will need to manually add the new VPLS neighbors to the static point-to-multipoint
flooding LSP. By configuring static point-to-multipoint LSPs for flooding, you have more
control over which path each sub-LSP follows.
To configure a static flooding point-to-multipoint LSP, specify the name of the static
flooding point-to-multipoint LSP by including the
static-lsp lsp-name;
You can include this statement at the following hierarchy levels:
[edit routing-instances routing-instance-name provider-tunnel rsvp-te]
[edit logical-systems logical-system-name routing-instances routing-instance-name
provider-tunnel rsvp-te]
To configure a dynamic point-to-multipoint flooding LSP, include the
label-switched-path-template
routing-instance-name provider-tunnel rsvp-te]
[edit routing-instances routing-instance-name provider-tunnel rsvp-te]
label-switched-path-template (Multicast)
(default-template | lsp-template-name);
}
You can automatically generate the point-to-multipoint LSP to be used for flooding
unknown traffic or you can manually configure the point-to-multipoint LSP:

Configuring Dynamic Point-to-Multipoint Flooding LSPs with the Default

Template on page 73
Configuring Dynamic Point-to-Multipoint Flooding LSPs with a Preconfigured
Template on page 74
Configuring Dynamic Point-to-Multipoint Flooding LSPs with the Default Template
The
option, specified at the
default-template
provider-tunnel rsvp-te label-switched-path-template]
point-to-multipoint LSPs to be created with default parameters. The default parameters
are for a minimally configured point-to-multipoint LSP. The name of this
Chapter 8: Configuring Point-to-Multipoint LSPs
static-lsp
statement option at the
[edit routing-instances
hierarchy level:
{
[edit routing-instances routing-instance-name
hierarchy level, causes the
statement:
73

Advertisement

Table of Contents
loading

Table of Contents