PreviousNext

Juniper Networks, Inc.

JunosE 15.1.0 Release Notes


Release Highlights

Release 15.1.0 includes the features described in this section.

Category
Feature
QoS

Hardware

l Customer edge side MPLS L2VPNs over LAG
l Ethernet raw mode encapsulation for packets entering and leaving pseudowires
l S-VLAN subinterface with an untagged C-VLAN ID

The impact caused by the removal of forwarding controller-specific functionalities are:

l In a MPLS L2VPN over LAG, load balancing of egress traffic among LAG member-links is not supported. All egress traffic flow through the primary link that is operationally UP.
l Removal and addition of S-VLAN tag for packets entering and leaving pseudowires is not supported. Hence, traffic is not supported when customer edge device is S-VLAN aware or unaware and provider edge device (that is, MPLS cloud) is unaware of S-VLAN.
l Transportation of both customer-tagged and customer-VLAN-untagged frames in a predefined stacked-tag over a pseudowire is not supported.

Change in existing Behavior: New feature added as described here.

L2TP

OSPF

Policy Management

QoS

SDX Software and SRC Software

The COPS-PR Policy Information Base (PIB) is modified with a new class junoseIpv6DhcpAddressClasses and two new objects such as JunoseIpv6AddressRequestEntry and JunoseIpv6DhcpDecisionEntry for the following:

System

l Line module slot number
l Line module type
l Packet drop sub-reason and respective drop count
l Direction of the dropped packet
l Threshold value configured for the sub-reason

Informational Note: The feature does not monitor control path drops. You can use the feature to monitor only 25 sub-reasons in a E series router. You cannot change the polling interval. The feature does not account drops occurring before the first polling interval. The feature does not support any recovery mechanism to rectify the monitored drops. The feature is applicable only for ES2 4G LM, ES2 10G LM, ES2 10G ADV LM, ES2 10G UPLINK LM, and GE/FE line module.

The packet-drop-monitoring threshold command is enhanced to support the configuration of threshold value based on the line module type, packet direction, and sub-reason.

The existing show packet-drop-monitoring-threshold command is obsolete and a new show packet-drop-monitoring command is introduced to monitor the configurations set by using the enhanced packet-drop-monitoring command.

The packet drop monitoring configuration is applied for all existing line modules and also for any new line modules inserted in the chassis, based on the line module for which the configuration is done. The configuration persists across unified ISSU and SRP resets. The configuration is not removed even after issuing the slot erase command.

Change in existing Behavior: Existing feature extended as described here. In lower-numbered releases, the detector logic is used to monitor all forwarding path packet drops irrespective of the sub-reason, packet direction, and line module type.


Copyright © 2014, Juniper Networks, Inc.
Report An Error
PreviousNext