Alert Type
SRN - Software Release Notification
Risk
Risk Description
Low/Notification
Software Release Notification
Impact
Impact Description
Low/Notification
Software Release Notification
Product Affected
ACX PTX QFX running Junos Evolved Software
Alert Description
Junos Software Service Release version 21.4R3-S4-EVO is now available for download from the Junos software download site
Download Junos Software Service Release:
Go to
Junos Platforms - Download Software page
Input your product in the "Find a Product" search box
From the Type/OS drop-down menu, select
Junos SR
From the Version drop-down menu, select your version
Click the Software tab
Select the Install Package as need and follow the prompts
Solution
Junos Software service Release version 21.4R3-S4-EVO is now available.
21.4R3-S4-EVO - List of Fixed issues
PR Number
Synopsis
Category: EX4300 Layer 2 implementation
1684072
The l2cpd process crash may be observed when disabling RSTP on an interface
Product-Group=evo
On all Junos and Junos Evolved platforms, the l2cpd process may crash and generates the core when disabling RSTP (Rapid Spanning Tree Protocol) on an interface.
PR Number
Synopsis
Category: EX2300/3400 PFE
1695771
Traffic loss is seen when a MAC moves from dot1x port to non-dot1x port
Product-Group=evo
On all Junos and Junos OS Evolved platforms is having dot1x enabled interface. When two or more MAC addresses are learnt on a dot1x port, and if one of them is shifted to a non-dot1x port, the MAC address that was moved is still seen as a MAC-based VLAN entry on the Layer2 Address Learning Manager (l2alm). This could lead to network traffic being lost.
PR Number
Synopsis
Category: EX2300/3400 platform
1695057
The l2cpd telemetry crash would be observed when the LLDP Netconf notification from external controllers along with Netconf services configuration is present on the device
Product-Group=evo
On all Junos and Junos Evolved platforms, configuring Link Layer Discovery Protocol (LLDP) with "system services netconf notification" enabled will trigger the l2cpd crash. This crash causes the CPU to spike.
PR Number
Synopsis
Category: AFT l2lam
1721704
Sending GARP reply packet on a VTEP interface causes flooding in network on QFX5130 and QFX5700 platforms
Product-Group=evo
On Junos OS Evolved QFX5130 and QFX5700 platforms, Gratuitous Address Resolution Protocol (GARP) flooding occurs in the network when it receives a GARP reply packet on a Virtual Tunnel End Point (VTEP) interface.
PR Number
Synopsis
Category: EVO interface software
1716518
Interface on PTX1001-36MR router remains down with QSFP-100GBASE-SR4 optics
Product-Group=evo
On Junos Evolved PTX10001-36MR platform, when the third party QSFP-100GBASE-SR4 is being used, rewriting the value of rx-out-amplitude (receiver side signal integrity parameter) with default value(0X3), causes the link to remain down.
PR Number
Synopsis
Category: Bi Directional Forwarding Detection (BFD)
1673624
[MNHA_PDT] After interface MTU config change, unexpected behavior of BFD connection.
Product-Group=evo
Bfd session remains in Up state at one end down state in another side. This can be caused when the session flapped and doesn't age out at one end.
1725971
Multiple flaps of the interface will cause the BFD session to be down
Product-Group=evo
On all Junos and Junos Evolved platforms, the IPv4 static route BFD (Bidirectional Forwarding Detection) session may stay down if the corresponding interface flaps multiple times.
PR Number
Synopsis
Category: Border Gateway Protocol
1687887
More than expected traffic loss is seen with ECMP FRR enabled during link down scenario
Product-Group=evo
On all Junos and Junos Evolved platforms, in a link down/BFD (Bidirectional Forwarding Detection) down event traffic loss is seen to occur more than the expected with ECMP (Equal-Cost Multipath) FRR (Fast Reroute) or BGP PIC (Prefix-Independent Convergence) configured.
1695062
Traffic null routes are observed when it takes a long time to remove the BGP routes from RIB
Product-Group=evo
On Junos platforms, if a BGP peer goes down and stays down, the system might take an extremely long time to finish removing the BGP routes. This issue is observed when a BGP peer sends many routes, the system only selects only a small number of routes are as the active routes in the routing information base (RIB), and the BGP delete job gets only a small portion of the CPU time because other work in the routing process is utilizing the CPU.
1739919
An Improper Input Validation vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS).
Product-Group=evo
An Improper Input Validation vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS). Please see https://kb.juniper.net/
JSA71542
[juniper.net]
for more details.
PR Number
Synopsis
Category: EVO VXLAN PFE for BCM XGS Platforms
1720399
The ECMP routing table does not get updated when underlay L3 interface link flaps in EVPN-VXLAN scenario
Product-Group=evo
On all Junos Evolved QFX5130/QFX5700 switches, in an EVPN-VXLAN (Ethernet Virtual Private LAN - Virtual Extensible LAN) deployment, Type-2 Overlay ECMP (Equal Cost Multi Path) routing does not happen when the underlay Layer 3 interface is flapped.
1722109
The VRF route leaking will not happen for the routes learned on the AE interface in the EVPN-VXLAN MAC-VRF routing-instance
Product-Group=evo
On QFX5130 and QFX5700 Junos OS Evolved platforms, configured with Ethernet Virtual Private Network Virtual Extensible LAN (EVPN-VXLAN) with routing-instance MAC-VRF and Aggregate Ethernet (AE) interface is a member of it, the routes learned on the AE interface will not leak to other routing instances even if configured to do so. Thus, the layer 3 traffic across the VRF will be impacted for the routes that are learned on the AE interface.
PR Number
Synopsis
Category: EVO Services Sflow PRs for defect & enhancement requests
1680040
The Sflow output is not as expected in 'show route forwarding-table destination <>'
Product-Group=evo
The destination mask reported in Sflow exported packet could display compressed mask length instead of the un-compressed value reported in the 'show route forwarding-table destination <>' command. Hence the exported value of destination mask length could be lesser compared to what is displayed in the mentioned CLI command.
PR Number
Synopsis
Category: Express BT PFE L3 Features
1660701
Traffic loss due to long MPLS reroute local convergence time on AE flap
Product-Group=evo
On PTX10003, PTX10003-160C, PTX10003-80C, PTX10008, PTX10016 Evolved platforms, MPLS (Multiprotocol Label Switching) FRR (Fast Reroute) convergence takes longer time when an AE (Aggregate Ethernet) interface is disabled.
1723808
Unstable interface statistic (ingress) going up and down
Product-Group=evo
The PPS reported for the interface may fluctuate for a few seconds and show either higher or lower value. The chance of this happening is very rare
PR Number
Synopsis
Category: L2NG RTG feature
1715518
Traffic loss is seen on RTG bound interface
Product-Group=evo
On all Junos and Junos OS Evolved platforms, configuring mac-move with action shutdown can disable the RTG (Redundant Trunk Groups) interface leading to traffic loss bound to that interface.
PR Number
Synopsis
Category: Gnats category for dynamic rendering infrastructure
1681777
Invalid XML output can be seen for RPC get response
Product-Group=evo
If the configured data has special characters in it, then rpc get output will not escape these special characters and display the data as it is. For example, if we have configured qos class as , then ---- > the response should have default as response value .
PR Number
Synopsis
Category: EVO ARP related PRs
1691524
Inconsistent clear ARP behavior leads to traffic loss to host(s)
Product-Group=evo
On all Junos OS Evolved platforms, when executing "clear arp hostname " command, host IP in all the routing instances get cleared (if they exist), as against the expectation that it should be cleared only in default routing instance. If traffic is ongoing, and ARP entry for the host IP gets wrongly cleared due to this action, some traffic drops will be seen till ARP re-learning happens. It is advised to use "clear arp hostname vpn " command only to obtain expected results.
PR Number
Synopsis
Category: EVO cfmd RE related PRs
1695518
[Error] CTRL:CFM:: PpmCtrlProtoCfm:: getSessionKey: Unknown Cfm transmit session type params0x0 ( ) can be seen when router is rebooted with CFM config
Product-Group=evo
When CFM configurations are present on the router, and the router is rebooted, below error logs may be seen. [Error] CTRL:CFM:: PpmCtrlProtoCfm:: getSessionKey: Unknown Cfm transmit session type params0x0 ( ) There is no feature impact when this error log is seen. CFM sessions will be unaffected. The error log is not emitted consistently, and may be seen only sometimes.
PR Number
Synopsis
Category: EVO Netstack FIB Service Daemon
1685545
The command "show route forwarding-table destination " will be slow in scaled scenario
Product-Group=evo
On EVO platforms, issuing "show route forwarding-table destination " command takes long time in a scaled system for non-/32 prefixes.
1698611
The route leaking does not work between different routing instances by using rib-groups on all Junos OS Evolved platforms
Product-Group=evo
On all Junos OS Evolved platforms, if the rib-groups is used to import/export routes into the default routing instance from another routing instance, then connectivity fails between those routing instances.
PR Number
Synopsis
Category: Firewall related development
1674893
Error messages are observed while configuring the firewall filter with family inet6 with next-header and no payload-protocol and committing them
Product-Group=evo
On all Junos evolved PTX platforms, when firewall filter with family inet6 is configured with source-port/destination-port and has next-header and no payload-protocol, error messages are observed causing the filter fail to install.
1699138
The SCU/DCU firewall filter match will not work as expected
Product-Group=evo
On all Junos Evolved PTX platforms, when the source class usage (SCU)/destination class usage (DCU) firewall filter is configured without payload protocol or TCP/UDP protocol it will not work properly and will give errors whenever the filters are added or re-activated. When the error is encountered, the installation of other filters would also be impacted.
1703169
CCL:NGPR: filter with payload-protocol cannot be attached to the lo0 egress interface
Product-Group=evo
The commit check 'filter with payload-protocol cannot be attached to the lo0 egress interface' was added to the 22.3 and onward releases as this feature was not supported by the Kernel. The same commit check was not added to 21.4 releases as adding this commit check was high risk. This commit check was introduced in the RLI 53437.
1720389
Commit error will not be seen after deactivating routing-instance applied under firewall filter
Product-Group=evo
On Junos OS Evolved platforms with enabled firewall filter, deactivating routing-instance which is already applied under the firewall filter, will not show any commit error after commit is issued. This can be seen occasionally and might impact control plane traffic.
PR Number
Synopsis
Category: Interface PRs defect & enhancement requests
1722201
PTX10004/8/16 EVO "show interfaces media|extensive|brief|detail" CLI show "Down" state when CFMD brings IFD down
Product-Group=evo
On PTX10K EVO platforms, all show interfaces "terse|media|extensive|brief|detail" CLI show "Down" state when CFMD brings IFD down. The correct behavior is that 'terse' level shows the CFM control plane status which is 'down', and that the other "media|extensive|brief|detail" levels should show 'down' only when IFD is down at physical layer. The Up/down state of show interfaces "media|extensive|brief|detail" is determined based on the status of the physical link. So the 'media|extensive|detail|brief' output must show "Up" state when CFMD brings IFD down because there is no fault at the L1 level and the physical link is UP.
1724286
PTX10004/8/16 EVO "Device flags" in "show interfaces" CLI is "Present Running Down" when CFMD brings IFD down
Product-Group=evo
On PTX10004/8/16 EVO platforms, "Device flags" in "show interfaces" CLI is "Present Running Down" when CFMD brings IFD down. "Present Running" is expected in this case.
PR Number
Synopsis
Category: EVO RPD agent PRs
1665362
Few protocol sessions remain down after quick arpd process disable and enable
Product-Group=evo
Few protocol sessions remain down causing traffic loss in certain prefixes after quick arpd process disable and enable. The system can be recovered from erroneous state by executing "restart routing gracefully" in CLI.
1732786
The rpd process will crash if too many trace options are initialised
Product-Group=evo
On all Junos OS Evolved platforms, rpd crash will be seen when debug tracing is enabled, routing services will be impacted during rpd crash recovery.
PR Number
Synopsis
Category: EVO Socket replication
1732611
vmcores might be seen when macsec (key-chain) and bgp configs are applied through netconf
Product-Group=evo
vmcores might be seen when macsec and bgp configs are applied through netconf.
PR Number
Synopsis
Category: SNMP, mib2d issues
1683517
snmp-subagent cored when FPCs are down/restarted
Product-Group=evo
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 may core.
PR Number
Synopsis
Category: Category for software tracing Infra issues
1637992
The babeltrace crash may be triggered in a rare condition
Product-Group=evo
On Junos OS Evolved platforms, the babeltrace crash may be triggered in a rare condition when the trace file is being truncated. The babeltrace is a tool that provides trace reading and writing.
PR Number
Synopsis
Category: EVPN control plane issues
1638776
The rpd core might be seen when the VLAN-id of a bridge domain in an EVPN instance is changed
Product-Group=evo
The rpd core might be seen when the VLAN-id of a bridge domain in an EVPN instance is changed.
1723832
The rpd core is seen in the long-running devices with EVPN enabled
Product-Group=evo
On Junos and Junos Evolved platforms, BGP (Border Gateway Protocol) community object reference count is not handled properly during the process of remote BGP peer routes update event. The community reference count is increasing during the increment function. However, decrement functions are not called in one of the places after processing the routes update. This will lead to a disturbance of the continuity reference count, which will cause an rpd crash.
PR Number
Synopsis
Category: EVPN Layer-2 Forwarding
1712259
The Anycast Gateway stretched across 2 DCs over the seamless MPLS stitching DCI does not have Anycast Gateway MAC information coming from the remote DC when VLAN and VNI ids are different
Product-Group=evo
On all Junos and Junos OS Evolved platforms, the AnyCast Gateway stretched across 2 Data Centres (DC) over the Data Centre Interconnect (DCI) using seamless Multiprotocol Label Switching (MPLS) stitching through Interconnect knob and having different VLAN and Virtual Network Identifier (VNI) ids (e.g., VLAN ID 101 <-- -> VNI 1101), then upon deactivating the Integrated Routing and Bridging (IRB) interface on all the gateways within DC, the AnyCast Gateway MAC information coming from Interconnect-Ethernet Segment Identifier (I-ESI) will not be available in the bridge mac-table and thus, the Inter VLAN/VNI routing will be impacted.
PR Number
Synopsis
Category: Express PFE FW Features
1719581
Some outgoing control traffic gets dropped by BGP flowspec or L3VPN filter on certain Junos OS Evolved platforms
Product-Group=evo
BGP FlowSpec or a L3VPN (Layer3 Virtual Private Network) filter drops a L3-injected packet which is an outgoing control packets on certain Junos OS Evolved platforms (PTX10001-36MR/PTX10004/PTX10008/PTX10016 with LC1201/LC1202) because it hits the condition with DISCARD/REJECT action. The filter should be skipped for a L3-injected packet based on L3-injected service type.
1720865
Ingress port didn't work with flow spec traffic
Product-Group=evo
On Junos Evolved platforms, the traffic ingress port became unavailable after forwarding the traffic to different routing-instances by a scale configuration of flow spec routes.
PR Number
Synopsis
Category: ISIS routing protocol
1699076
The rpd process might crash when SPF is recalculated
Product-Group=evo
On all Junos and Junos Evolved platforms, the rpd (Routing Protocol Daemon) process can crash due to periodic SPF (Shortest Path first) recalculation when ISIS (Intermediate System to Intermediate System) connected or direct routes get deleted.
1718734
Unexpected behavior of bandwidth based metric for IS-IS protocol
Product-Group=evo
On all Junos and Junos OS Evolved platforms unexpected behavior of bandwidth based metric in IS-IS is seen since actual bandwidth is falling back to 0 bps when one of the member interface of AE (Aggregated Ethernet) bundle (interface-group) goes down.
1725686
Unnecessary SPF calculation is causing high CPU utilization
Product-Group=evo
On all Junos and Junos Evolved platforms, very frequent SPF (Shortest Path First) calculation, being caused by leaking multiple prefixes across the IS-IS areas, is causing high CPU utilization.
PR Number
Synopsis
Category: jdhcpd daemon
1689005
DHCP packets might not be sent to the clients when 'forward-only' is reconfigured under the routing instance
Product-Group=evo
On all Junos platforms, reconfiguring 'forward-only' in any routing instance is leading to deactivate of [default:default] jdhcpd filter. Dynamic Host Configuration Protocol (DHCP) packets might not be sent to the clients.
1714260
The DHCPv4 relay will send two option-82 to the server and the DHCP session will not be established
Product-Group=evo
On all Junos and Junos OS Evolved platforms, when Dynamic Host Configuration Protocol (DHCPv4) Relay is configured with forward-only mode along with "trust-option-82", DHCP-relay should not add another option 82 to the packet sent to the DHCP server. The DHCP server upon receiving the packet with two option-82 will respond only with 1st header of option-82 which might get dropped by the relay, thus the packet is not forwarded to the DHCP client and the DHCP session won't get established.
PR Number
Synopsis
Category: Layer 2 Circuit issues
1691295
Post FPC restart CCC status is getting wrongly updated on the local interface
Product-Group=evo
On all Junos and Junos Evolved platforms in the L2VPN (Layer 2 Virtual Private Network) scenario, the CCC (Circuit Cross-Connect) link status will remain up after the FPC (Flexible PIC Concentrators) restart, when the CCC status is down between the local PE-CE link.
PR Number
Synopsis
Category: Layer 2 Control Module
1717267
Traffic loop is seen due to incorrect root bridge ID
Product-Group=evo
On all Junos and Junos Evolved platforms, in VSTP (Virtual Spanning-Tree Protocol) topology, whenever a new vlan is added in between previously configured vlan group followed by configuring the system-identifier, the bridge priority will change for existing vlans which might give incorrect system ID or bridge ID creating a traffic loop.
PR Number
Synopsis
Category: Layer2 forwarding on EX/NTF/PTX/QFX
1707878
Mac entry not ageout in RTG in EX4600-VC after VCP port reconnect
Product-Group=evo
EX4600 with Redundant Trunk Group (RTG) configured, after VCP port between members of EX4600 disconnect and connect again. Mac address entry created in RTG cannot ageout.
1716270
mac-move-limit : MMAS flag not getting reset after interface recovers due to l2-learning restart
Product-Group=evo
MMAS Flag will not be displayed for interface after it recovers due to l2-learning process restart
1727954
On all Junos and Junos Evolved platforms the l2ald process memory usage is seen to increase over time
Product-Group=evo
On all Junos and Junos Evolved platforms service impact is seen due to a consistent increase in l2ald (Layer 2 Address Learning Daemon) memory usage.
PR Number
Synopsis
Category: lacp protocol
1609618
LACP Member interfaces might get stuck in out of sync state.
Product-Group=evo
When sync-reset feature is enabled on the device then few member interfaces might stay in out of sync state even when number of available child interfaces is greater than minimum-links configured for the Lag interface. This will affect the overall capacity of the lag interface .
PR Number
Synopsis
Category: Multicast for L3VPNs
1682573
Core observed with multiple daemons restart
Product-Group=evo
On all Junos and Junos Evolved platforms supporting dual-RE (Routing Engine) and NSR (Nonstop Active Routing), a core is observed with multiple daemons restart. There is no functional impact and the system recovers after the restart.
1710323
MVPN tunnel is not synced to backup router
Product-Group=evo
On all Junos and Junos Evolved platforms, when OSPF inter-area is configured with segmented provider-tunnel and master undergoes MBB(make-before-break), the multicast route entry on backup router will not have the tunnel name synced with master.
PR Number
Synopsis
Category: QFX5K EVO Platform Optic
1725300
Link failure is seen on 10G SFP+ ports of QFX platforms
Product-Group=evo
On QFX Junos Evolved platforms, the 10G SFP+ ports on specific QFX platforms (QFX5130-32CD, QFX5220-32CD and QFX5220-128C) does not come up even on the normal scenario.
PR Number
Synopsis
Category: Indirect nexthop routing infrastructure
1692776
The rpd crash will be observed when there is a temporary recursion loop and routes are flapping
Product-Group=evo
On all Junos and Junos Evolved platforms, the rpd process crashes when a temporary recursive loop forms. This happens when a BGP route flaps and while the options 'multipath-resolve' and 'preserve-nexthop-hierarchy' are configured.
PR Number
Synopsis
Category: Issue related to mcnh routing infrastructure within RPD
1718510
RPD cores when routing churn happens, if RE restart was missed after configuring FMBB knob
Product-Group=evo
On PTX EVO platforms, rpd cores when routing churn happens, if RE restart was missed after configuring FMBB knob.
PR Number
Synopsis
Category: RPD Next-hop issues including indirect, CNH, and MCNH
1655052
Momentary traffic drop observed for 2 to 3sec while RE switchover
Product-Group=evo
RE switchover may result in a momentary traffic drop for about 2 to 3 sec, In EVPN-VXLAN setup with EVPN type 5 traffic and NSR configuration.
PR Number
Synopsis
Category: RPD policy options
1662909
When changing static route's next-hop using OpenConfig, the next-hops may not display correctly
Product-Group=evo
When changing static route's next-hop using OpenConfig, the next-hop still shows under static route, discrepancy between OC stanza and Junos-yang
PR Number
Synopsis
Category: RPD route tables, resolver, routing instances, static routes
1716153
Multipath route is not getting compute and skip the multipath eligibility check
Product-Group=evo
On all Junos platforms, multipath route will not be formed correctly when a BGP route is received from RR (Route Reflector) and preference decided based on cluster list length.
PR Number
Synopsis
Category: Resource Reservation Protocol
1681403
In the RSVP-TE scenario, with Entropy label capability is enabled during MBB issues handling Resv Messages
Product-Group=evo
On all platforms with entropy-label configured, the issue shows up during Make-Before-Break (MBB) at a transit Juniper node when non-Juniper Egress constructs and sends a Resv message with multiple flow-descriptors (includes descriptors for both old and new instances). Juniper transit device has an issue handling such Resv Messages, the RRO object that is part of the flow-descriptor was getting dropped when the LSP_ATTRIBUTES object was also present within the flow-descriptor.
1690110
Traffic is not load-balanced when one of the next-hop LSP is down
Product-Group=evo
On all Junos and Junos Evolved platforms, in the multi-LSP next-hop load-balance scenario, in case any one of the label-switched path (LSP) is down, the traffic will not be load-balanced to the rest of the LSPs, due to the weight of LSP next hops not being set correctly.
1703424
Pathtear message is not forwarded by PLR to merge point which is causing data plane blackholing
Product-Group=evo
On all Junos and Junos OS Evolved platforms, the PLR (point of local repair) is not sending the pathtear message when the merge point supports the enhanced FRR while the route reaching the neighbor is using a shortcut route under MVPN (Multicast Virtual Private Network) configured scenario.
1713392
PathErr with RoutingProblem error code generated unexpectedly during dual failure local repair
Product-Group=evo
When an LSR acts as a Point of Local Repair (PLR) as well as a Merge Point (MP) for an LSP during a double failure scenario, the LSR incorrectly originates one or two PathErr messages with RoutingProblem (code=24/2) instead of originating PathErr with NotifyError (code/subcode=25/3). This will not cause any service impact if the ingress LER would not react adversely to RoutingProblem error (code=24/2).
PR Number
Synopsis
Category: RPD API infrastructure
1693567
PDT: ONDATRA: context deadline exceeded observed on while adding NH , IPv4
Product-Group=evo
Few times, the execution of gribi Modify RPC can fail due to deadline exceeded error. There are two scenarios when this can happen: 1. When the response from Junos device takes longer than a minute to arrive: Some requests which require FIBACK can get timed out because fib acks may be delayed. 2. When the response never arrives from Junos device - This is a rare scenario. In this scenario, it has been noticed that the proxy gateway on Junos doesnt propagate the subsequent requests on existing RPC to the endpoint daemons, hence those requests are notserved properly.
PR Number
Synopsis
Category: PTX10K platform specific fabric PRs
1693697
The fabspoked-pfe process crashes when a FATAL ERROR occurs in the PFE
Product-Group=evo
On PTX10004, PTX10008 and PTX10016 platforms running Junos OS Evolved with PTX10K-LC1201 or PTX10K-LC1202 line cards, the fabspoked-pfe process will crash on occurrence of FATAL ERROR in the Packet Forwarding Engine (PFE). As a result, the line card will restart and traffic will be impacted till it recovers.
PR Number
Synopsis
Category: PTX10K specific platform PRs
1682659
The FPC can go to a fault state on certain Junos Evolved PTX platforms after system reboot
Product-Group=evo
On certain Junos Evolved PTX platforms FPC (Flexible PIC concentrator) goes to a fault state after a system reboots with a Major alarm - Power Failure. This issue is a rare issue and the FPC in a fault state will impact the data traffic. To recover from this issue the impacted FPCs need to be rebooted.
1716276
PTX10004/8/16 EVO "LINE CARDS" LED on Status Panel is Lit ON in Green right after FPC is inserted although FPC is Present state
Product-Group=evo
On PTX10K running Junos Evolved software platforms, the "LINE CARDS" LED on Status Panel is Lit ON in Green right after FPC is inserted although FPC is Present state.
1720276
Application failure would occur on Routing Engine switchover
Product-Group=evo
On Junos OS Evolved platforms, application failure would be observed if it exits without cleaning up the zookeeper contents. This is a rare issue, however can have potential impact depending on the application which fails.
1724151
PTX10004/8/16 EVO hwdre core is generated when FTC (fan tray controller) is inserted
Product-Group=evo
On PTX10004/8/16 EVO, hwdre core is generated when FTC(fan tray controller) is inserted.
PR Number
Synopsis
Category: PTX10K Timing/Sync-E issues tracking
1725260
PTX EVO - esmc transmit interfaces may not be listed in "show synchronous-ethernet esmc transmit" CLI with generating clksyncd core by replacing "interface name" with "replace pattern" CLI
Product-Group=evo
On PTX Junos Evolved platforms, esmc transmit interfaces may not be listed in "show synchronous-ethernet esmc transmit" CLI with generating clksyncd core by replacing "interface name".
PR Number
Synopsis
Category: Virtual Router Redundancy Protocol
1683871
If VRRP authentication key is more than 16 characters it is ignoring remaining characters
Product-Group=evo
VRRP returns error if the authentication key exceeds 8 characters for simple and 16 for md5.
1714831
VRRP master does not respond to Neighbor Solicitation on Junos Evolved platforms
Product-Group=evo
On Junos Evolved platforms there can be no response received for NS (Neighbour Solicitation)message sent to virtual-link-local-address. This happens in the IPv6 (Internet Protocol Version6) VRRP (Virtual Router Redundancy Protocol) scenario due to the VMAC (Virtual Media Access Control) for virtual-link-local-address being attached to a different route. There will be a traffic impact as the ARP for the Virtual IP is not resolved.
PR Number
Synopsis
Category: EVO Services Sflow PRs for defect & enhancement requests
1710919
[sflow] [EVO-Brackla] sflow reports incorrect extended switch data for different untagged/vlan-tagged and vlan-tagged/untagged ingress/egress interface combinations
Product-Group=evo
Sflow reports incorrect extended switch data for different untagged/vlan-tagged and vlan-tagged/untagged ingress/egress interface combinations. In Ingress ECMP scenarios, where the egress ifl is tagged and ingress ifl is untagged, the extended switch data is missing in the sflow records.
PR Number
Synopsis
Category: Express ZX PFE L3 Features
1720264
Unnecessary "resiliencyd" messages appear for trap codes
Product-Group=evo
Unnecessary "resiliencyd" messages appear for trap codes. We do have "cda trapstats" which count these.
21.4R3-S4-EVO - List of Known issues
PR Number
Synopsis
Category: Border Gateway Protocol
1673160
The routes with an independent resolution can trigger an rpd crash when the last BGP peer is down
Product-Group=evo
On all Junos and Junos Evolved platforms, Independent resolution routes imported from another table (i.e. VRFs with color routes that need resolution) can trigger an rpd crash when the last BGP peer is down.
Resolved In:
evo:21.2R3-S4-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R1-EVO evo:23.1R1-EVO junos:21.2R3-S4 junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:23.1R1
1712406
IPv4 routes learnt over a link-local BGP session not advertised ahead to other BGP peers
Product-Group=evo
When rib (Routing Information Base) contains IPv4 routes with IPv6 next-hops, these routes do not get re-advertised by IPv4 EBGP sessions unless export policy is configured to change it to IPv4 next-hop.
Resolved In:
evo:22.2R3-EVO evo:22.3R3-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:22.1R3-S2 junos:22.2R3 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.1R2 junos:23.2R1
PR Number
Synopsis
Category: PTX10003 Platform related issues
1706688
Router will undergo silent reboot due to disk related failures
Product-Group=evo
On all Junos OS Evolved platforms, if a disk related failure or error is detected, a software reboot will be triggered even if the error is a transient or temporary one. A resiliency fix to check the SSD freeze for multiple times before triggering the reboot is added.
Resolved In:
evo:22.2R2-S2-EVO evo:22.3R3-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.1R2-EVO evo:23.2R1-EVO
PR Number
Synopsis
Category: PFE COS features on BT based platforms
1732461
Traffic drop under strict-priority queue before low priority queue
Product-Group=evo
On Junos OS Evolved PTX10001-36MR, PTX10004, PTX10008, and PTX10016 platforms, when a strict-high priority queue without transmit-rate is configured on a 10Gig port, it will experience a packet drop before the low priority queue.
Resolved In:
evo:22.3R3-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO
PR Number
Synopsis
Category: software upgrade infra issues
1699699
The commit changes will not take effect post software upgrade once the system is rebooted on Junos OS Evolved platforms
Product-Group=evo
On Junos OS Evolved Platforms, any UI (user interface) set (configuration, script, license) changes done post software addition were being lost after the subsequent reboot.
Resolved In:
evo:23.3R1-EVO junos:23.2R1 junos:23.3R1
PR Number
Synopsis
Category: mgd, ddl, odl infra issues
1665008
The system will ask for password while saving configuration files on single RE platforms
Product-Group=evo
The system may ask for your password when you are thing to save configuration file.
Resolved In:
evo:23.1R1-EVO junos:23.1R1
PR Number
Synopsis
Category: Express PFE FW Features
1709204
Lo0 filter change might trigger parity error, when filter is changed from ISF to Non ISF or vice versa
Product-Group=evo
Lo0 filter change might trigger parity error, when filter is changed from ISF to Non ISF or vice versa
Resolved In:
PR Number
Synopsis
Category: All Guardian (ACX7509) Platform related issues
1640585
Continuous syslog flooding of "picd: PICD_XCVR_LANE_ALARM: xcvr-x/x/x chan 0 RX LOS alarm set"
Product-Group=evo
Syslog of "picd: PICD_XCVR_LANE_ALARM: xcvr-x/x/x chan 0 RX LOS alarm set" is continuously flooded on EVO platforms.
Resolved In:
evo:22.1R2-EVO evo:22.2R1-EVO
PR Number
Synopsis
Category: ISIS routing protocol
1713008
Stale entries present in the lsdist table after ISO address change
Product-Group=evo
On all Junos and Junos OS Evolved platforms configured with IS-IS and MPLS traffic engineering database (TED), if there is an ISO address change on another Intermediate System (IS), there will be stale entries being present in the link-state distribution (lsdist) table even though they might have been deleted in IS-IS and TED. This has an impact on the routes, and thus the services, related to the stale entries present in the lsdist.
Resolved In:
evo:23.2R1-EVO evo:23.3R1-EVO junos:20.3X75-D36 junos:23.2R1 junos:23.3R1
PR Number
Synopsis
Category: MX10K platform
1674322
SNMP traps "Power Supply failed" and "Power Supply OK" are not generated
Product-Group=evo
On all Junos MX10k and PTX10k platforms, when a PSU with no feeds connected, but the DIP switch at the back of the PSU is set in a position where it expects the feeds to be connected, then POWER FAILED TRAPs might not get generated as expected.
Resolved In:
evo:22.1R3-EVO evo:22.2R2-EVO evo:22.3R2-EVO evo:22.4R1-EVO junos:20.3X75-D36 junos:20.4R3-S5 junos:22.1R3 junos:22.2R2 junos:22.3R2 junos:22.4R1 junos:23.1R1
PR Number
Synopsis
Category: Periodic Packet Management Daemon
1723199
Around 60 BFD sessions went down and did not come up post NSR switchover.
Product-Group=evo
When bfdd restarts on master RE and then on backup, it clears all the replication sessions. Due to software changes, some of the sessions may not come up correctly.
Resolved In:
evo:23.3R1-EVO junos:23.3R1
PR Number
Synopsis
Category: Issues related to NETCONF
1709056
Unable to upgrade Junos using NetConf or Junos script
Product-Group=evo
On all Junos and Junos OS Evolved platforms, if RPC get-configuration is invoked before RPC request-package-add in the same session of the NETCONF or Junos script, RPC request-package-add will not work.
Resolved In:
evo:22.2R2-S2-J2-EVO evo:22.3R2-S1-EVO evo:22.3R3-EVO evo:22.3X50-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:21.4R3-S4 junos:22.1R3-S3 junos:22.2R3-S1 junos:22.3R2-S1 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R1-S1 junos:23.1R2 junos:23.2R1 junos:23.3R1
PR Number
Synopsis
Category: Issues related to YANG Data Models
1725934
ODL controller is throwing unavailable capabilities error for few of the Openconfig Yang modules
Product-Group=evo
ODL controller is throwing unavailable capabilities error for few of the Openconfig Yang modules
Resolved In:
evo:22.4R3-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:22.4R2-S1 junos:22.4R3
Modification History
First publication 2023-06-23
21.4R3-S4-EVO: Software Release Notification