PR Number |
Synopsis |
Category: JUNOS kernel/ukernel changes for ACX |
1481151 |
Memory utilization enhancement is needed.
Product-Group=junos |
RPD memory chunk size is optimized for ACX platform to reduce the memory foot print. |
PR Number |
Synopsis |
Category: Sflow on qfx10k/ptx series PRs for defect & enhancement req |
1521732 |
Output interface index in SFLOW packet is zero when transit traffic is observed on the IRB interface with VRRP enabled
Product-Group=junos |
When VRRP is enabled on IRB interface and SFLOW is enabled on QFX10000 Series platforms, output interface Index in SFLOW packet will be zero for the traffic destined to VRRP MAC address. |
PR Number |
Synopsis |
Category: Multicast for L3VPNs |
1546739 |
MVPN multicast route entry may not be properly updated with actual downstream interfaces list
Product-Group=junos |
In multicast VPN RPT-SPT mode with both locally and remotely connected receivers, the multicast forwarding entry related to the actual downstream interfaces may not be properly updated. The issue may happen when multicast forwarding entry is created by locally connected PIM receiver, followed by remote receiver and after local receiver decides to prune its membership in that multicast group. |
PR Number |
Synopsis |
Category: vMX Data Plane Issues |
1544856 |
The riot forwarding daemon crash might be observed on vMX based platforms configured with IRB interface
Product-Group=junos |
On vMX based platforms enabled with IRB interface, the riot forwarding daemon crash might be observed which could lead to traffic loss. |
PR Number |
Synopsis |
Category: Protocol Independant Multicast |
1501722 |
The rpd process might crash in a multicast scenario with BGP configured.
Product-Group=junos |
In multicast scenario with BGP configured, when a new BGP link is brought up (such as, after updating specific BGP policies), which changes the RPF neighbor information and this update causes the rpd core to happen. The issue is seen only while updating RPF neighbor information and not seen while building it for the first time. |
PR Number |
Synopsis |
Category: KRT Queue issues within RPD |
1493963 |
The rpd process generates a core dumps
Product-Group=junos |
On EVO platforms running BGP with knob 'route-record' or sampling, the rpd might crash if BGP paths exceed around 5600K. |
PR Number |
Synopsis |
Category: RPD route tables, resolver, routing instances, static routes |
1507638 |
On all Junos OS dual-Routing Engine GRES or NSR enabled routers, the rpd process might crash on a new master Routing Engine if the Routing Engine switchover occurs right after massive routing-instance deletion.
Product-Group=junos |
On all Junos platforms, if GRES and NSR are enabled at a dual-RE router and if RE switchover happens (either manually or due to some other reasons) right after deleting a big number of routing instances, then rpd at a new master RE could crash once. Once a new master RPD crashed, it will restart by itself. |
PR Number |
Synopsis |
Category: IPSEC functionality on M/MX/T ser |
1544794 |
CMVTS:mspmand cored at pconn_client_try_connect (clnt=0x10064ae00) at ../../../../../src/junos/lib/libconn/pconn_conn.c:2155
Product-Group=junos |
During activate/deactivate of interfaces multiple times, sometimes mspmand may core in pconn library because of NULL pointer access. The service pic will auto-recover after a reboot. |
PR Number |
Synopsis |
Category: Trio pfe bridging, learning, stp, oam, irb software |
1506861 |
The MEP session on the aggregated Ethernet interface might not come up if OAM runs with PPM mode by default.
Product-Group=junos |
On MX platform running with enhance IP mode or enhanced ethernet mode, also, Operation, Administration and Maintenance (OAM) is enabled with Periodic Packet Management (PPM) mode by default, maintenance association end point (MEP) session might be failed to create. In the end, network connection failure might not be efficiently monitored. This is functional impact. |
1542211 |
Trio-based FPC might crash when the underlying layer 2 interface for ARP over IRB interface is changed from physical interface to LSI interface
Product-Group=junos |
This issue applies to a Trio-based FPC using the integrated routing and bridging (IRB) interface with a VPLS instance using the label-switched interface (LSI) to provide VPLS functionality. The FPC may restart unexpectedly. The restart is triggered when the underlying layer-2 interface for ARP over IRB interface changes from the physical interface to the LSI interface. |
PR Number |
Synopsis |
Category: VSRX platform software |
1524243 |
The control link may be broken when there is excessive traffic load on the control link in vSRX cluster deployment
Product-Group=junosvae |
In the vSRX2.0 cluster running on KVM, when there is excessive traffic load on the control link (em0 link), the error message kernel: em0: watchdog timeout on queue 0 might be shown in the syslog. This interruption might cause the cluster control link to fail and dynamic routing protocols not to work properly. |