DOM MIB jnxDomCurrentTable for 1G SFP interface not working

The Digital Optical Monitoring (DOM) MIB jnxDomCurrentTable for 1G SFP interfaces does not return any value.

Rpd memory leak is observed in a next generation MVPN environment

Rpd memory leak is seen when NG-MVPN type 6 and type 7 route adds/deletes/changes. The leak is 36 byte block size on Junos versions prior to 15.1, and 44 byte block size on Junos versions 15.1 or higher.

The rpd might crash after deleting some vrf instances if "vrf-table-label" is configured.

In scaled number of vrf instances scenario with "vrf-table-label" configured, the rpd might crash after deleting some vrf instances.

The rpd might crash when the MPLS LSP path change occurs.

In scaling MPLS Label Switched Paths (LSP) scenario with Junos OS Release 16.1 and later releases, if the LSP path change occurs frequently, rpd crashes and generates a core file.

If MPLS LSP self-ping is enabled (self-ping is enabled by default), the kernel might panic with an error message Fatal trap 12: page fault while in kernel mode.

This issue occurs when using MPLS LSPs and RSVP-TE self-ping. When rpd sends out a self-ping packet and an RSVP packet at the same time, these packets might overwrite the kernel's packet buffers causing memory corruption and the kernel to panic.

Customers running 32-bit Junos OS might generate rpd core file when traceoptions are enabled.

Junos system running 32-bit might cause rpd process crash when traceoptions are enabled.

The rpd might crash when the link flaps on an adjacent router

The rpd (Routing Protocol Process) might crash during heavy next hops churn.

Traffic might be dropped on third-generation FPCs on PTX.

On PTX with third-generation FPCs, if optics not certified by Juniper Networks (NON-JNPR) are used and there is specific traffic pattern with congestion, traffic might be dropped.

OpenSSL Security Advisories [16 Apr 2018] and [12 June 2018]

The ?OpenSSL project has published security advisories for vulnerabilities resolved in the OpenSSL library on April 16, 2018, and June 12, 2018. See https://kb.juniper.net/JSA10919 [juniper.net] for details.

Downstream interface is not removed from multicast route after getting PIM prune.

In NG-MVPN scenario where source and receivers are on the same PE but different routing-instances, if PIM prune (*, g) is received on a downstream interface, Type 7 route might not get updated accordingly, resulting in the interface remaining in multicast route. Thus unwanted multicast traffic keeps being forwarded to that interface.