NOTE: When identical site IDs are used without configuring multihoming, a
collision log message is generated at each signaling:
RPD_L2VPN_SITE_COLLISION: Same site ID 2 configured on remote PE (RD
8.8.8.1:1013:) and local PE in VPN 1013 (non-multihomed site 2). This is expected
behavior.
VPLS Single-Homed Site Configuration
All VPLS single-homed sites are connected to the same default VE device. All interfaces
in a VPLS routing instance that are not configured as part of a multihomed site are
assumed to be single-homed to the default VE device.
Related
Documentation
VPLS Multihoming Overview on page 1237•
• Example: VPLS Multihoming, Improved Convergence Time
• active-interface
• multi-homing
Configuring Firewall Filters and Policers for VPLS in ACX Series
You can configure both firewall filters and policers for VPLS. Firewall filters allow you to
filter packets based on their components and to perform an action on packets that match
the filter. Policers allow you to limit the amount of traffic that passes into or out of an
interface.
VPLS filters and policers act on a Layer 2 frame that includes the media access control
(MAC) header (after any VLAN rewrite or other rules are applied), but does not include
the cyclical redundancy check (CRC) field.
You can apply VPLS filters and policers on the PE router to customer-facing interfaces
only.
The following sections explain how to configure filters and policers for VPLS:
•
Configuring a VPLS Filter on page 1271
•
Configuring a VPLS Policer on page 1273
Configuring a VPLS Filter
To configure a filter for VPLS, include the filter statement at the [edit firewall family vpls]
hierarchy level:
[edit firewall family vpls]
filter filter-name {
interface-specific;
term term-name {
from {
match-conditions;
1271Copyright © 2017, Juniper Networks, Inc.
Chapter 35: Configuring Virtual Private LAN Service
To Next Page
Loading...
Need help?
General
