Specifications

Services Applications
•
SIP call forwarding might fail when NAT is used between parties even though the SIP
ALG is in use. PR839629
•
Junos OS Release 11.4 introduced the IKEv2 support and a stricter check on IKE/IPsec
SAs proposal parameters. PR843893
•
DNS multiple queries A and AAAA might cause the Service-PIC to restart. PR943425
•
During a rare scenario, switchover on another sp interface can crash a service PIC when
running traffic in hairpinning scenario. PR945114
•
Jl2tpd process experiences high CPU condition if the process is restarted or if GRES is
executed. The jl2tpd process does recover. The length of the high CPU condition is
directly proportional to the number of tunnels on average, it is 1 second per tunnel.
PR955378
Subscriber Access Management
•
LNS-Service accounting updates not sent. PR944807
•
Radius attribute ignore logical-system-routing-instance not ignoring VSA26-1. PR953802
•
Configuration change of the IPv4 address range in address-assignment pool does not
always take effect. PR954793
User Interface and Configuration
•
If a configuration file that contains groups related configuration is loaded by command
"load replace", a "commit confirmed" operation might fail. When this issue occurs, the
new configuration is committed even if you do not confirm it within the specified time
limit. PR925512
VPNs
•
The issue happens when the virtual routing forwarding (vrf) is configured
"no-vrf-propagate-ttl" and the vrf import policy changes the local preference of the
vrf route. With "no-vrf-propagate-ttl", BGP will resolve the primary l3vpn route and
the vrf secondary route separately. The root cause is overwriting the route parameters
of the second vrf route with the route parameters of the primary route. So changes to
the local preference of the vrf route might not work. PR935574
•
NG MVPN receiver PE does not generate TYPE 4 route after receiving TYPE 3. PR953449
•
With these high amount of streams, we have a higher number of data-mdt-tlvs to
process which is becoming a bottleneck. PR957280
•
Before Release 13.3R2, if no loopback interface inside vrf was configured, then Rosen
V6 might not be able to use default main loopback as source for PE_PE pim
communications., As a result, Rosen v6 neighbor will not be formed toward remote
PEs. PR966825
Related
Documentation
New and Changed Features on page 21•
Copyright © 2015, Juniper Networks, Inc.134
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series