Specifications

•
Support for ATM virtual connection multiplexing and LLC encapsulation (MX
Series)—Starting in Junos OS Release 13.3, ATM virtual connection (VC) multiplexing
and logical link control (LLC) encapsulation are supported on the Channelized
OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP. ATM virtual connection
multiplexing and LLC are the two methods for identifying the protocol carried in ATM
Adaptation Layer 5 (AAL5) frames. The methods are defined in RFC 2684, Multiprotocol
Encapsulation over ATM Adaptation Layer 5.
In the ATM virtual connection multiplexing method, each ATM virtual connection carries
protocol data units (PDUs) of exactly one protocol type. When multiple protocols need
to be transported, there is a separate virtual connection for each protocol.
The LLC encapsulation method enables multiplexing of multiple protocols over a single
ATM virtual connection. The protocol type of each PDU is identified by a prefixed IEEE
802.2 LLC header.
[See ATM Support on Circuit Emulation PICs Overview.]
•
Support for MPLS-signaled LSPs to use GRE tunnels (MX Series)—Starting in Junos
OS Release 13.3, MPLS label-switched paths (LSPs) can use generic routing
encapsulation (GRE) tunnels to traverse routing areas, autonomous systems, and ISPs.
Bridging MPLS LSPs over an intervening IP domain is possible without disrupting the
outlying MPLS domain. This feature is supported on the Channelized OC3/STM1
(Multi-Rate) Circuit Emulation MIC with SFP and is defined in the RFC 4023,
Encapsulating MPLS in IP or Generic Routing Encapsulation (GRE).
[See Configuring MPLS-Signaled LSPs to Use GRE Tunnels.]
•
Support for SCBE2 (MX240, MX480, and MX960)—Starting in Junos OS Release
13.3, the Enhanced SCB—SCBE2 supports the following features:
•
Increased fabric bandwidth per slot
•
Improved external clock redundancy
•
Dynamic multicast replication only
•
GRES
The following scenarios are to be noted when you are using an MX Series router with
an SCBE2:
•
You must configure the set chassis network-services (enhanced-ip |
enhanced-ethernet) configuration command and reboot the router to bring up the
FPCs on the router. However, after the router reboots, the MS DPC, the MX FPC, and
the ADPC are powered off.
•
All the FPCs and DPCs in the router are powered off when you reboot the router
without configuring either the enhanced-ip option or the enhanced-ethernet option
at the [edit chassis network-services] hierarchy level.
•
You must reboot the router when you configure or delete the enhanced-ip option or
the enhanced-ethernet option at the [edit chassis network-services] hierarchy level.
[See Centralized Clocking Overview and Network Services Mode Overview.]
Copyright © 2015, Juniper Networks, Inc.36
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series