[
System Basics
]
VPNs
■
Mirroring IRB packets as Layer 2 packets (MX Series router)
—If you associate
an IRB with the bridge domain (or VPLS routing instance), and also configure
within the bridge domain (or VPLS routing instance) a forwarding table filter with
the
port-mirror
or
port-mirror-instance
action, then the IRB packet is mirrored as
a Layer 2 packet. You can disable this behavior by configuring the
no-irb-layer-2-copy
statement in the bridge domain (or VPLS routing instance).
[
MX Series Layer 2 Configuration
]
■
Layer 2 circuits, call admission control (CAC), and bypass LSPs
—You can now
configure CAC on Layer 2 circuit-based LSPs with bandwidth constraints and
also enable link and node protection. However, if the primary LSP fails, CAC
might not be applied to the bypass LSP, meaning that the bypass LSP might not
meet the bandwidth constraint for the Layer 2 circuit. To minimize the risk of
losing traffic, the Layer 2 circuit continues to use the non-CAC bypass LSP while
an attempt is made to establish a new Layer 2 circuit route over an LSP that does
support CAC. Previously, the Layer 2 circuit route was deleted if the bypass LSP
did not have sufficient bandwidth.
[
VPNs
]
■
Service VLANs and the use of
vlan-id all
statement in a VPLS routing
instance
—If you configure the
vlan-id all
statement in a VPLS routing instance,
we recommend using the
input-vlan-map pop
and
output-vlan-map push
statements
on the logical interface to pop the service VLAN ID on input and push the service
VLAN ID on output and in this way limit the impact of doubly-tagged frames on
scaling.
[
MX Series Layer 2 Configuration
]
■
Layer 2.5 VPNs support ISO family and MPLS family over TCC (MX Series
routers)
—JUNOS Release 8.3 introduced support for M320 and T Series routers.
JUNOS Release 10.1 extends support to MX Series routers.
Interfaces supporting TCC (Ethernet, extended VLANs, PPP, HDLC, ATM, and
Frame Relay) support ISO traffic and MPLS traffic on Layer 2.5 VPNs. Previously,
Layer 2.5 VPNs configured on MX Series routers supported only inet traffic. For
a protocol to be supported on a Layer 2.5 VPN, you must configure both ends
of the VPN with the protocol configuration. IPv6 is not supported.
To enable ISO or MPLS traffic over TCC, include the
mpls
or
iso
statement at the
[edit interfaces
interface-name
unit
logical-unit-number
family tcc protocol]
hierarchy
level. To display which protocol is supported for an interface, issue the
show
interfaces interface-name extensive
operational mode command. The protocol is
displayed in the Flags field.
To enable ISO over TCC in cases in which the Ethernet interface is on a
customer-edge (CE) router, include the
point-to-point
statement at the
[edit
protocols isis interface
interface-name
]
hierarchy level on the CE router. When
you include this statement, the IS-IS protocol treats the Ethernet interface as
point to point, even though the actual interface is a LAN interface.
52
■
Changes in Default Behavior and Syntax in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
JUNOS 10.1 Software Release Notes
