Resolved Issues
Learn about the issues fixed in this release for vSRX.
For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.
- Chassis Clustering
- Flow-Based and Packet-Based Processing
- General Routing
- J-Web
- Platform and Infrastructure
Chassis Clustering
-
Traffic loss after RG1 failover. PR1726753
Flow-Based and Packet-Based Processing
-
High latency and packet drops will be observed with the "transmit-rate exact" knob enabled for one or more schedulers of an IFL/IFD. PR1692559
-
Packet loss is observed for IPSec sessions when PMI is enabled. PR1692885
-
On SRX platforms, tunnel fails to come up when tunnel destination routing instance is configured. PR1693767
-
Packets are dropped because flow sessions will not be created for the MPLS routed traffic. PR1703678
-
The inet6 packet mode drops traffic significantly. PR1733819
-
Virtual Routing Instance configured on ingress interface will drop the icmp traffic. PR1742739
General Routing
-
Log streaming Hosts configured as FQDN may fail when DNS re-query is performed. PR1708116
-
Security log missing space between timestamp and hostname. PR1716776
-
The flowd process crash is observed when the web proxy packet reinjection fails. PR1719703
-
The DNS cache gets wiped out due to the flowd crash on all SRX platforms after the upgrade. PR1732028
-
Traffic drop caused by PFE memory leak on SRX platforms. PR1738656
J-Web
Platform and Infrastructure
-
When deploying a new vSRX on Azure, if "Accelerated" is selected for the initial interface selected by default, the vSRX will duplicate the fxp0 interface MAC address to ge-0/0/0 and make that interface unusable. As a workaround, de-select “Accelerated” from the interface at the initial deployment. PR1726091