Open Issues

Platform dependency-state error is seen on cosd. PR1649388

The issue is 400G-ZR/400G-ZR-M optic transceiver firmware upgrade failure. It is a generic issue faced across all single RU platforms supporting QDD-400G-ZR/QDD-400G-ZR-M. PR1638284

The system ID that is exported should be different for UDP and GRPC/GNMI. In the case of UDP, the system name should be appended with the local IP address. PR1640442

On all Junos OS Evolved platforms, the license might get out of sync between primary and backup Routing Engine after the addition or deletion of licenses. PR1658869

GNOI API SetPackage through remote download is not supported.PR1665185

There is no support for leaf level paths for Packet Forwarding Engine sensors in Junos OS Evolved. PR1671424

Fragmented packets have an additional NH (frag) that causes the FLT to not match on ICMPv6 headers for lo0 filters. Workaround is to change the loopback MTU size. PR1675820

G.8273.2 SyncE to PTP and SyncE to 1PPS transient response test fails. PR1681527

Class B performance as per G.8273.2 fails for SyncE to PTP and SyncE to 1pps noise transfer for lower frequencies. PR1681884

The sync_response does not work correctly. PR1683552

Class B performance as per G.8273.2 shall be supported only when FEC is enabled on both the primary and secondary ports of the T-BC(default option). PR1683579

When a scaled number of interfaces (1000 and more logical interface) are been deleted and then re added with a configuration change. A fibd core might be encountered due a corner case condition. FIB will then restart and will function as normal. Since FIB will restart and recover by itself, no other recovery will be necessary. PR1685995

Trigger: Applying Layer 2 configuration with the interface in sp mode + Bd configuration and CFM configuration together in a single commit will result in ifbd creation failures. Impact: IFBD creations fails so the Layer 2 functionalities will not work on the configured interface. Traffic drops will be seen. Layer 2 configuration reference. set interfaces et-0/0/1 flexible-vlan-tagging set interfaces et-0/0/1 encapsulation flexible-ethernet-services set interfaces et-0/0/1 unit 1 encapsulation vlan-bridge set interfaces et-0/0/1 unit 1 vlan-id 1 set vlan v1 vlan-id 1 set vlans v1 interface et-0/0/1.1. PR1690635

With sharding enabled, BGP flags like the following are not displayed on Active route in show route extensive output: Accepted Multipath MultipathContrib MultiNexthop per shard view, using show route extensive <prefix> rib-sharding <shard-name> will show these flags.PR1693207

On PTX10008 Junos OS Evolved platforms, FTC (Fan Tray Controller) FPGA minimum supported firmware version mismatch alarm gets generated upon re-seating FTC because the current firmware version becomes null value after re-insertion. PR1698209

This issue is seen during CLI triggered onlining of the Packet Forwarding Engine, that is when request chassis fpc slot <slot-id> pfe <pfe-id> restart is executed. Please use the workaround provided. PR1699323

Changing decapsulation of only the tunnel destination address configuration after tunnel is up might not work and end up using the previously configured tunnel destination address for the decapsulation. After the system enters this state, any further configuration changes to tunnel configuration cannot be handled. PR1575724

Sometimes BGP and RSVP sessions remain down after quickly disabling and enabling arpd process. Whenever customer encounters such scenarios, the system can be recovered from erroneous state by executing restart routing gracefully in CLI.PR1665362

On a PTX Junos OS Evolved platform running EVPN-MPLS and 22.4 software, if a configuration statement likeprotocols evpn normailization is enabled (which is catastrophic to L2 and RPD daemons and involves deleting and adding the Rt instance tables) followed by Routing Engine switchover, RPD could encounter a core due to indirect-next-hop id being zero. The show krt indirect-next-hop | grep Index could be zero for one or more NHs, this is a timing issue that seems to affect some routing-instances. PR1694773

You must perform joji over the interface using test picd optics fpc_slot <fpc slot> pic_slot <pic slot> port <port num> cmd oir_enable test picd optics fpc_slot <fpc slot> pic_slot <pic slot> port <port num> cmd remove test picd optics fpc_slot <fpc slot> pic_slot <pic slot> port <port num> cmd insert test picd optics fpc_slot <fpc slot> pic_slot <pic slot> port <port num> cmd oir_disable command. PR1646915

Traceroute in MPLS OAM on SR over IPv6 might fail in ECMP incase PTX box is in topology. This occurs because of Linux kernel in the Junos OS Evolved puts an autoflowlabel on every IPv6 packet. This flow label is transparent to daemon process, which uses a null value for it and calculates the next hop details. Packet Forwarding Engine however takes the flow label into account and calculates the next hop details. This difference in calculation of next hop details leads to a mismatch in the path the packet takes to the destination and can cause traceroute to fail. PR1618406

When you configure the maximum-password-length command and tries to configure password whose length exceeds the configured maximum-password-length, error messgae gets generated along with error '(ok/)' tag gets emitted. Ideally 'ok/>' tag should not be emitted in an error scenario and the configuration does not get committed..PR1585855

When jnxCos mib is polled at a very high rate and if response from FPCs (evo-aftmand) is delayed (takes around 1 minute) then snmpd-subagent might generate a core file. PR1683517

Interface physical IP address is assigned to SNMP trap source address after chassis restart although source-address lo0 is configured under trap-options. PR1690850

This scenario happens when we enable IS-IS authentication key-chain having multiple keys between routers. The IS-IS adjacency is up since both routers have the same key active. When we manually change the system time in such a way that routers have different keys active in the key chain, the IS-IS adjacency must go down. However, that does not happen. PR1572441

When l2cpd (in the context of xSTP) clears the entries that it has programmed on ppmd, that is, when you delete xSTP configurations from the box, there can be a possibility of ppmd core file. If ppmd is in distributed mode then there will be no service impact, else there can be service impact as packet transmission for various protocols will happen through if ppmd is in centralized mode.PR1660299

The following IS-IS leaves will not be supported: /network-instances/network-instance/protocols/protocol/isis/global/config/n et /network-instances/network-instance/protocols/protocol/isis/interfaces/inte rface/levels/level/hello-authentication/ /network-instances/network-instance/protocols/protocol/isis/interfaces/inte rface/config/hello-padding. PR1678300

The system might ask for your password when you are thing to save configuration file. PR1665008

Configd-streamer cores during commit of wild-carded groups related configuration. The core is only seen with the wild-carded configuration which is used in the reported fusion test case. PR1674890