PR Number |
Synopsis |
Category: Ardbeg Hardware related issues. |
1532088 |
PTX10001-36MR - Continuous CRC errors seen during repetitive reboot tests after 22 iterations of system reboot
Product-Group=evo |
When a PTX10001-36MR is repeatedly rebooted then in 1 out of 25 iterations, one of the fabric links may start showing continuous CCL errors. |
PR Number |
Synopsis |
Category: Express BT PFE L3 Features |
1536681 |
20.2R2 MultiD: Latency for traffic from 100G to 10G port is 4 time more compared to latency for traffic from 400G to 100G port; all within single router
Product-Group=evo |
Traffic from a 100G interface to 10G interface in PTX1001-36MR shows 4 times more latency compared to traffic from a 400G interface to 100G interface. |
PR Number |
Synopsis |
Category: EVO ARP related PRs |
1520016 |
PTX10001 Memory leak seen with 48 hours passive stability
Product-Group=evo |
In PTX10001-36MR with multiple protocols and services configured with scale, the user may see available free memory reducing over time even without doing any changes in the configuration. |
PR Number |
Synopsis |
Category: EVO build infrastructure related issues. |
1508626 |
Add Python 3.x for EVO - module list
Product-Group=evo |
There are Python 3.x modules that are missing from the Junos Evolved library. The equivalent of these modules is already installed under Python 2.7 module library. |
PR Number |
Synopsis |
Category: software upgrade infra issues |
1554107 |
Software upgrade rollback may fail on Junos OS EVO platforms
Product-Group=evo |
On all Junos EVO platforms, during software rollback, if certain db and configuration files are not copied to chroot environment then mgd may fail to perform the configuration validation. |
PR Number |
Synopsis |
Category: Configd, ffp issues |
1534858 |
The firewall filter for both IPv4 and IPv6 may not work when it is applied through apply-groups
Product-Group=evo |
On Junos OS Evolved PTX devices, the firewall filter for both IPv4 and IPv6 does not work when it is applied through apply-groups on the subinterface |
PR Number |
Synopsis |
Category: Express PFE CoS Features |
1478811 |
[cos] [scheduler] PTX10008:scheduler with all queues oversubscribed, maximum latency is different on different queues - 21ms ~ 29ms.
Product-Group=evo |
In PTX10001-36MR when all CoS queues are over-subscribed, then maximum latency may vary from 21ms to 29ms for different queues. |
1519345 |
[cos] [scheduler] with all queues oversubscribed, latency time varies from 5ms ~ 27 ms for queue#0~#7 (l3_cos_jitter.robot)
Product-Group=evo |
with all queues oversubscribed, latency time varies from 5ms ~ 27 ms for queue#0~#7 (l3_cos_jitter.robot) |
1535523 |
Ardbeg: 20.2R2 MultiD: Interface queue counter shows incorrect large value (18446743936270598160) on applying apply-group on IFD for scheduler
Product-Group=evo |
In rare cases, when interface statistics of an individual interface is cleared, then the queue counter for that interface might show large number of incorrect 20-digit counter values. |
PR Number |
Synopsis |
Category: ISIS routing protocol |
1540400 |
PTX10008 : traffic loss seen after Graceful switchover with LSR Core MPLS_DSCP profile configuration
Product-Group=evo |
PTX10008 : traffic loss seen after Graceful switchover with LSR Core MPLS_DSCP profile configuration |
PR Number |
Synopsis |
Category: PRs for Lazurite Platform and Interface |
1538514 |
After config "global system name-server" config commit should fail but commit is succeeds.
Product-Group=evo |
After config "global system name-server" config commit should fail but commit is succeeds. |
PR Number |
Synopsis |
Category: Multiprotocol Label Switching |
1532365 |
Junos EVO - Deactivating mpls protocols commit is allowed when spring is enabled which is not expected
Product-Group=evo |
On a Junos Evolved platform, with the "Source Packet Routing In Networking" (SPRING) feature - the system, erroneously, allows you to deactivate the "protocols mpls" configuration stanza. |
PR Number |
Synopsis |
Category: Microkernel for neo mpc |
1538131 |
JDI-RCT:M/Mx: NPC crashed @ cmtfpc_mic_neo_state_check (mic_env=< optimized out>, mic_slot=< optimized out>) at ../../../../src/pfe/common/applications/cmt/jam/cmtfpc_pic_npc_jam.c:4808
Product-Group=evo |
This issue is due to Thread hogging for 2.5s after ISR registration during ISSU done phase causing a core at FPC. FPC will get rebooted with ISR registration again during normal init. This issue is specific to "3D 20x 1GE(LAN)-E,SFP" and "3D 20x 1GE(LAN)-EH,SFP" MIC types. |
PR Number |
Synopsis |
Category: vMX Data Plane Issues |
1534568 |
[CORE-PR][vZT]: Inconsistent core.python2.7.mpc0 core is seen with stacktrace @ea_wi_precl,@ea_macsec_receive
Product-Group=evo |
Inconsistent core.python2.7.mpc0 core is seen with stacktrace @ea_wi_precl,@ea_macsec_receive() |
PR Number |
Synopsis |
Category: KRT Queue issues within RPD |
1511539 |
Traffic loss might be seen after GRES
Product-Group=evo |
On all platforms with GRES enabled packet loss around 1% was seen after GRES check pass and then GRES. |