Alert Type

PSN - Product Support Notification
Low/NotificationSoftware Release Notification
Low/NotificationSoftware Release Notification

Product Affected

ACX PTX QFX running Junos Evolved Software

Alert Description

Junos Software Service Release version 21.2R3-S1-EVO is now available for download from the Junos software download site

Download Junos Software Service Release:

  1. Go to Junos Platforms - Download Software page
  2. Input your product in the "Find a Product" search box
  3. From the Type/OS drop-down menu, select Junos SR
  4. From the Version drop-down menu, select your version
  5. Click the Software tab
  6. Select the Install Package as need and follow the prompts

Solution

Junos Software service Release version 21.2R3-S1-EVO is now available.

21.2R3-S1-EVO - List of Fixed issues

PR NumberSynopsisCategory: Border Gateway Protocol
1643178On all junos platforms, when a route is received with broadcast address as next-hop, the platform may not consider it as an invalid route and drop the traffic intended for the destination
Product-Group=evo
On all Junos platforms, in an eBGP scenario, if a route is received with a broadcast address next hop, it successfully programs it into the RIB (Routing Information Base), and eventually the route gets programmed into the FIB (Forwarding Information Base) as well. The treating of an invalid next hop as a valid one makes the platform try and fail when traffic for that route is received.
1651211Delay in BGP session establishment due to longer time for the listening task to be ready on all platforms running rpd
Product-Group=evo
On all platforms running rpd, the longer time for the listening task to be ready might have the longest time for the active task to be created, resulting in BGP session delay establishment.
1655228An RPD process crash may be observed, when the received prefix count exceeds configured "prefix-limit"
Product-Group=evo
In all Junos and Junos Evolved platforms, when the BGP neighbor is brought down due to the received prefix count exceeding configured "prefix-limit" and if BGP disable and enable operation performed to bring the BGP session up then the "rpd" process crash might be observed.
PR NumberSynopsisCategory: PTX10003 Platform related issues
1654762[PTX10003] SSD DGM28-B56D81BCBQ || RE 0 SSD Primary minimum supported firmware version mismatch
Product-Group=evo
PTX10003 may show alarm "RE # SSD Primary minimum supported firmware version mismatch" if the routing-engine is installed with Innodisk SSD.
PR NumberSynopsisCategory: Express BT PFE L3 Features
1651932An error might be seen when the member link on an AE bundle is deleted
Product-Group=evo
On all EVO PTX platforms, gRPC connection between the "evo-aftmand" process and the "cda" process maybe disconnect with the messages "[Error] CDA: exprGrpcAsyncApi: failed cq read", and "GOAWAY with error code ENHANCE_YOUR_CALM". When the disconnection happens, the Junos Evolved system can no longer retrieve status or programs forwarding ASICs. This is a catastrophic failure.
PR NumberSynopsisCategory: Firewall Filter
1625309Packet loss might be reported after hitting the firewall filter on Junos platform
Product-Group=evo
On Junos platform, on the egress or ingress PFE instance, after hitting a firewall, it might lead to packet loss and impact service.
PR NumberSynopsisCategory: Lacp related problems and issues.
1647145The lacpd may not come up on one of the links in the AE bundle
Product-Group=evo
On EVO platforms during lacpd process restart, child IFD indexes from the port options IFD based data which gets stored in kernel by lacpd, might not get reused due to old indexes weren't freed. When this occurs, new indexes may be generated repeatedly which could cause the port numbers exhaustion problem in AE (Aggregated Ethernet interface) bundle.
PR NumberSynopsisCategory: QFX5200/5110/5120/5210 Interface
1654459LACP sent IN SYNC to server facing interface when core-isolation is in effect
Product-Group=evo
In all Junos and Junos Evolved platforms, in the case of "core-isolation" is in effect, and if AE (AE with LACP) links between leaf and CE device flaps then, these flaps may enable LACP links during "core-isolation". This may cause CE to forward traffic to the node where the core is down.
PR NumberSynopsisCategory: Category for QFX5K EVO Platform Software PRs related to Chas
1665229EVO white space in optics serial number in "show chassis hardware display xml or json"
Product-Group=evo
There is unnecessary white space in optics serial number in the output by "show chassis hardware display | [xml or json]".
PR NumberSynopsisCategory: RPD Interfaces related issues
1659102The rpd memory leak might be seen while processing vlan-ccc configuration
Product-Group=evo
On all Junos and Junos Evolved platforms, when deleting/adding the whole interface unit of family vlan-ccc, the rpd will observe a memory leak.
PR NumberSynopsisCategory: Resource Reservation Protocol
1593959ISIS BFD sessions may take a long time to recover when the interface flaps
Product-Group=evo
When RSVP link-protection bypass LSPs active after the primary link goes down and comes back up. The BFD session over the interface stays down until all LSPs using the bypass LSPs come back up. This happens because RSVP installs a /32 route pointing to the bypass tunnel which is required to signal backup LSPs. This route is removed when all LSPs stop using bypass after the link comes back up. This is day 1 RSVP behavior.
PR NumberSynopsisCategory: Virtual Router Redundancy Protocol
1658966VRRP operations may flap when configuration changes are committed under unrelated VRRP groups present on the same physical interface
Product-Group=evo
On all Junos and Evolved platforms, the addition or removal of VRRP group might cause other VRRP groups under the same physical interface to flap. The issue causes the already existing configuration of all VRRP groups under the same physical interfaces(along with the ones where no configuration change is being committed) to be treated as a new configuration and eventually deletes it before re-adding. This causes all VRRP sessions to flap and virtual-router uptime to be reset.
 
 

21.2R3-S1-EVO - List of Known issues

PR NumberSynopsisCategory: "agentd" software daemon
1611498Alfaromeo: show ldp traffic-statistics interface p2mp is not displaying any traffic stats
Product-Group=evo
Re cli "show ldp traffic-statistics interface p2mp" does not display traffic stats. This issue is applicable to AFT based trio line cards on MX routers.
PR NumberSynopsisCategory: EVO L3 routing for BCM XGS Platforms
1652873EVO QFX "EvoPfemand-main" process memory leak
Product-Group=evo
EVO QFX switch platforms may experience a memory leak in the "EvoPfemand-main" process because mac deleting is not properly handled in software while the mac is properly deleted from hardware table and leads the memory leak. This could be detected by cli "show system processes extensive no-forwarding". The memory will increase depending on a number of learning mac address and internal debugging resources and this is expected but if it exceeds 5G and still keep increasing, the memory leak may be happening. root@QFX-EVO> show system processes extensive no-forwarding ... snip... PID USER TID PRI NI SIZE RSS S TIME %MEM %CPU COMMAND 14373 root 14373 19 0 64408 148296 R 11:05:58 0.5 99.9 snmpd{snmpd} 15627 root 18310 19 0 1182936 1373308 S 1-07:53:43 4.2 30.0 EvoPfemand-main{IfStatsMgr} <<<<<< The column "RSS" of EvoPfemand-main may keep increasing. The memory leak happens when the following log is generated so that if there are lots of the entries, the memory may be increasing over time. root@QFX-EVO> show trace application evo-pfemand 1135664 2022-03-14T11:15:38.890 - 2022-03-13 02:33:23.049052933 re0:evo-pfemand:15627:TRACE_ERR BrcmPfe_TP_Msg_Error compName = "L2", tpName = "BrcmPlusL2Fdb", msg = " func = deleteMac Entry, Entry not present for MAC: = 52:54:00:9f:7b:3a, VLAN = 21
PR NumberSynopsisCategory: PFE COS features on BT based platforms
1656837wrong transmit HW priority for CLI "priority medium-low"
Product-Group=evo
In EVO PTX10001-36MR, LC1201 and LC1202 (FPCs using BTchip), for a normal-mode scheduler (without strict-priority-scheduler in TCP), "priority medium-low" should map to hardware priority Medium (same as "priority medium-high").
PR NumberSynopsisCategory: Alias for DHCP issue on DNX based platform.
1610229Restarting the DHCP process on ACX5000s platforms may take longer than expected
Product-Group=evo
A restart of DHCP takes more time because of internal issues with the SIGTERM event.
PR NumberSynopsisCategory: ZT/YT pfe infra issues
1633286When ZPL ISSU is performed, PPMAN crash may be seen and MPC cards will be struck in the ISSU state
Product-Group=evo
During ZPL ISSU, if LACP and LFM configurations are present, PPMAN core may be seen and MPC10 and MPC11 cards will be stuck in the ISSU state. There will be traffic impact due to crash and the wrong card state.
PR NumberSynopsisCategory: ZT/YTpfe bridging, learning, stp, oam, irb software
1648059Interoperability issue between TRIO line cards and MPC10E and MPC11E AFT cards cause incorrect egress load balancing over Aggregated Ethernet links
Product-Group=evo
On MX platforms, due to a software defect seen in interoperability scenarios on newer AFT-based MX cards (MPC10E and MPC11E), packets entering through legacy(non-AFT) card interfaces and exiting through AE interfaces via IRB may get incorrectly load balanced.

Modification History

First publication 2022-06-14