Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Open Issues

For the most complete and latest information about known Junos OS Evolved defects, use the Juniper Networks online Junos Problem Report Search application.

General Routing

  • Below is the expected performance for this 21.4. Profile Freq (Hz) NoiseTransfer_0_00391_Results PASS PASS NoiseTransfer_0_00781_Results FAIL FAIL NoiseTransfer_0_01563_Results FAIL FAIL NoiseTransfer_0_03125_Results FAIL FAIL NoiseTransfer_0_06156_Results FAIL FAIL NoiseTransfer_0_12313_Results FAIL FAIL NoiseTransfer_0_24625_Results PASS PASS NoiseTransfer_0_4925_Results PASS PASS NoiseTransfer_0_985_Results PASS PASS NoiseTransfer_1_985_Results PASS PASS NoiseTransfer_3_985_Results PASS PASS NoiseTransfer_7_985_Results PASS PASS PR1624502

  • On PTX10000 platforms, fault state is latched on PSM although all input and output is OK with no chassis alarm. PR1669323

  • In high scaled (beyond 14000 s,g routes - 7000 ipv4 and 7000 ipv6 )NGMVPN SPMSI scenarios, core might be seen on PTX10003 platforms due to memory getting exhausted. PR1708454

  • On all Junos OS Evolved platforms, VMcores are seen when MACsec (Media Access Control Security) key-chains and BGP(Border Gateway Protocol) configurations are applied through Netconf. PR1732611

  • When class-of-service with shaping rate is configured on Aggregate Ethernet interfaces, and the firewall policer queries the aggregate Ethernet member and not the AE interface, the shaping rate or the policy configuration does not take effect as the shaping rate is not configured in AE member. PR1735087

  • The na-grpcd might crash if there are OCST, IPAFT, cliNoise, snmp polling going on in the background. It will restart automatically and should be running fine afterwards.PR1744033

  • On all Junos OS Evolved based PTX platforms with physical interface/LAG (Link Aggregation Group) interface in Layer 3 mode, the untagged control traffic on Layer 3 interface gets dropped if lport value of Layer 3 interface matches with lport value of Layer 2 aggregated ethernet (AE) interface in trunk mode. PR1745528

  • Both SIB PWR/STAT H/W LEDs become Unlit/OFF by Routing Engine switchover on PTX10004, PTX10008, and PTX10016 Junos OS Evolved platforms. PR1749781

  • This is a day-1 issue and currently in Junos OS Evolved on PTX10008 the fan FRU is not showing in the SNMP queries. In Junos OS Evolved only FT and FTC is shown - This is in comparison MX which also show as FAN also and its status in SNMP FRU. PR1754833

  • On all Junos OS Evolved PTX platforms, RIB (Routing Information Base) and FIB (Forwarding Information Base) tables are not synchronized properly, causing the P2MP (Point-to-Multipoint) LSP (label-switched-path) traffic outage when executing the CLI command clear rsvp session.PR1757635

  • On all Junos OS Evolved PTX10008, PTX10004, and PTX10016 platforms, when a Fan-tray is removed followed by an insertion, it will lead to fan-tray failures. PR1767111

  • With DHCP trace options enabled in their regression scripts, this core was seen. Issue is random not seen always. This was enabled in script for debugging in production network this will not be enabled by default hence the issue will not be seen. Its recommended to enable DHCP trace options only for debugging not otherwise.PR1771121

  • Transient parity erorr "pp_0_filter_action_0_intr_pmv_eq_zero" might seen, during filter modification with traffic running. PR1778622

  • This FIB limitation is roughly 4 million routes is related to PTX systems: PTX10001-36MR PTX10000-LC1201-36CD Note: For exact scale and other details please open JTAC ticket or engage Juniper account team. PR1772732

  • Low hold timer BGP sessions might flap post NSR switchover at 8000 BGP sessions scale in 23.4 release. PR1781414

  • On Junos OS Evolved platforms, when configuration of Decap filter action is on egress, commit error on both RE/PFE syslog messages is seen, however there is no service impact due to this issue. PR1793356

  • In case of primary-only inet6 address uses for re[01]:mgmt-0 interfaces, if there is inet6 address modification, the legacy inet6 address might still reside when do "ip -6 add show dev vmb0" under OS shell. The output of CLI command show interfaces re[01]:mgmt-0 shows the inet6 address correctly. PR1796934

  • On all Junos OS Evolved platforms, time-zone info changes to default UTC after upgrade is done with restart-upgrade. PR1803511

  • On all Junos OS Evolved platforms, while executing show log messages", error message sysctl kern.corefile not supported is seen which is introduced during daemon initialisation. PR1808481

  • On Junos OS Evolved platforms, when license gets expired, LICENSE_EXPIRED syslog is supposed to get generated which is missing. PR1808956

  • [evpn_vxlan] [evpn_instance] ptx10001-36mr :: JDI-RCT: Error message observed "RT : Mac Route install failed for rtt table index:452 Mac:0x5e000004 BD:170 ifl:4294967295 error:Generic failure" after performing disable ae member link on TOR device. PR1810348

  • On Junos OS Evolved PTX platform, the Border Gateway Protocol (BGP) session flap can be seen when inline Bidirectional Forwarding Detection (BFD) is configured under routing instance without loopback interface (lo0) leading to partial traffic drop. The issue is only seen when the interface is within the routing-instance. PR1811245

  • VRRP (Virtual Router Redundancy Protocol) will not work when VRRP group 0 is configured and specific Junos OS Evolved platforms PTX10001, PTX10003, PTX10004, PTX10008, and PTX10016 are working as primary.PR1816310

  • Segmentation fault on grpc timer thread (might be related to keepalive) #32085 grpc issue https://github.com/grpc/grpc/issues/32085 grpc stack needs to be upgraded to 1.53 or later. PR1722414

  • In Junos Evolved OS, during scaled configuration commit, Configd daemon in UI-infra is taking more time to process the commit. To optimise the processing time, most likely there will be design change required. There is no LKWR/pass instance. Also based on the configuration scale and the time taken for the commit to complete, it seems that this is a Day-1 issue.PR1701214

  • JNP10K-PWR-AC3: There is a mismatch of the physical LED and shown in the SNMP LED status in case of d2d failure. PR1831436

  • JNP10K-PWR-AC3: There is a mismatch of the physical LED and shown in the SNMP LED status in case of health check failure. PR1831444

Flow-based and Packet-based Processing

  • A router running sampling might see the msvcs-db daemon run at 99.9% for an extended period. PR1816542

Infrastructure

  • The request routing-engine login other-routing-engine command might fail.PR1712705

Interfaces and Chassis

  • On Junos OS Evolved PTX10000 platforms, the vmcore might be seen if any component is forcefully removed from the PCI (Peripheral Component Interconnect) bus. PR1739142

MPLS

  • On all Junos OS Evolved platforms, when MPLS (Multiprotocol Label Switching) statistics is configured without LSP (Label-Switched Path) configuration, the rpd process will crash and impact the routing protocols. This leads to traffic disruption due to the loss of routing information.PR1698889

  • On all Junos OS Evolved platforms, a memory leak is observed in the traffic engineering database (TED) when the inet table is not cleaned up after routing instance deactivation. PR1701800

Multicast

  • On vPTX platforms, the PFE (packet forwarding engine) receives an invalid token from RPD (Routing Engine daemon) for composites next-hops due to which the PFE will crash leading to traffic drop. PR1740390

Network Management and Monitoring

  • EVO:JDI_EVO_REGRESSION:PLATFORM[ephemeral]:mgd core @ db_oneliner_perhaps. PR1753241

  • On Junos OS Evolved platforms, SNMP cold start trap is observed on console log upon system reboot, but it is not sent out to external server. PR1788308

Routing Policy and Firewall Filters

  • On all Junos OS Evolved PTX platforms, the fwstatsd process will crash when openconfig-NI filter last term is only routing-instance action with no IPv4/IPv6 match. The process crash will impact show commands and openconfig state sensor support. PR1788695

Routing Protocols

  • ISIS TLV holds a maximum of 255 bytes of information per TLV. TLV contains data that has more than 255 bytes, current RFCs and drafts don't specify how to deal with multiple TLVs of same prefix. Hence it is advisable to associate bier subdomain to different lo0 TLV size exceed more than 255 bytes. It is not possible to define how many Bier subdomain will fit for given lo0 since it depend on other applicable subtlv associated with prefix. It is recommended to have advance planning/calculation before putting multiple bier subdomains under a single lo0 address. IS-IS TLV size exceeds 255 bytes, router behavior is undefine and may lead to multiple network issues. PR1776786

User Interface and Configuration

  • If its a scaled configuration with some configuration groups containing both wildcard and non-wildcard configuration, then the time it takes to commit the configuration is high. If upgrade is performed with this scaled configuration, then initial commit after upgrade might timeout and lead to a corrupt databases which could lead to mustd crash. To avoid this problem, move the wildcard configuration to another group.PR1804515

  • Netconf: File copy with password less authentication is failing with RPC request. PR1769911