Alert Type

SRN - Software Release Notification
Low/NotificationSoftware Release Notification
Low/NotificationSoftware Release Notification

Product Affected

ACX, EX, MX, PTX, QFX, NFX, SRX, VRR, and VMX

Alert Description

Junos Software Service Release version 18.4R3-S2 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

Warning: With VPLS/Bridge-Domain environment, an MX/EX9200 Series router with Trio-based MPCs running software version 18.4R3-S2. The MPCs may experience NH memory leak in the PFEs when using integrated routing and bridging (IRB) interface participating in the VPLS/Bridge-domain instance.
 

Junos Software service Release version 18.4R3-S2 is now available.

18.4R3-S2 - List of Fixed issues

PR NumberSynopsisCategory: EX4300 PFE
1491348The traffic destined to VRRP VIP might be dropped after the IRB interface is disabled on the initial VRRP primary
Product-Group=junos		On the EX4300 virtual-chassis scenario, the traffic destined to the VRRP Virtual IP Address (VIP) might be dropped on the Virtual-Chassis if the VRRP IRB interface is disabled on the initial VRRP primary. For details, please refer to the following topology and problem description.
PR NumberSynopsisCategory: EX2300/3400 platform
1467707FPCs might get disconnected from EX3400 VC briefly after reboot/upgrade
Product-Group=junos		On EX3400 Virtual Chassis, during reboot or upgrade, because of a high CPU load in slow path of fxpc, TCP keep alive message is not sent. Hence, it is observed that sometimes a few Virtual Chassis members might get disconnected from the Virtual Chassis briefly and join back in 3-6 minutes.
PR NumberSynopsisCategory: NFX LTE Software
1493711LTE - Package related files are getting missed after image upgrade from D497.1 to 18.4R3.3 porter-2 image
Product-Group=junosvae		In 18.4R3.3, LTE module is not contained on platform NFX250-ATT-LS1.
PR NumberSynopsisCategory: QFX Multichassis Link Aggregrate
1488681MClag consistency check for multiple irb's configured with same vrrp-group
Product-Group=junos		The MClag consistency check fails if the same vrrp-group is used for multiple irb configurations on Local and Remote REs of the MCLAG topology. This change corrects the defect and makes the MClag consistency check to pass.
PR NumberSynopsisCategory: QFX PFE L2
1481031Connectivity is broken through LAG due to members configured with hold-time and force-up
Product-Group=junos		Connectivity through link aggregation group bundle could break after there is a flap event on the physical ports when one physical member interface is configured with hold-time and the other member interface is having LACP force-up feature configured.
PR NumberSynopsisCategory: QFX L3 data-plane/forwarding
1485612QFX 5100 VC/VCF : fpc are going to NotPrsnt state after upgrading the QFX 5100 VC/VCF
Product-Group=junos		On QFX5100-24Q, there are three PICs: PIC0, PIC1, and PIC2. Ports on PIC0 uses the integrated PHY capability (called PHYLESS) on the Broadcom ASIC. PIC1 and PIC2 have an external PHY capability (called PHY). If PIC1 or PIC2 ports (PHY ports) interfaces used for VCP creation then after upgrade FPC may go to NotPrsnt state due to link not coming up.
1487707All interfaces stop transmitting traffic on multi-link simultaneously
Product-Group=junos		On QFX5000 platforms (QFX5100/QFX5110/QFX5120/QFX5200/QFX5210) with point-to-point multi-link scenario, when the switch ingress buffer saturation happens, all interfaces on multi-link stop sending traffic at the same time.
PR NumberSynopsisCategory: Accounting Profile
1458143A problem with statistics on some interfaces of a router may be observed after FPC or PIC reboot
Product-Group=junos		In some rare scenarios upon FPC or PIC reboot, the pfed (packet forwarding engine daemon) database may not get updated with the correct location_id for some physical interfaces (IFDs), then a problem with statistics on some interfaces of a router may be observed. If this issue happens in the subscriber management environment, and depending on the radius server configuration, it may cause the subscribers to get disconnected by the radius server because of the radius server can not receive the proper statistics update for the subscribers from the pfed.
PR NumberSynopsisCategory: ACX PFE
1479733Link does not come up when 100-Gigabit Ethernet is channelized to 4x25-Gigabit Ethernet interfaces.
Product-Group=junos		Link does not come up when 100-Gigabit Ethernet is channelized to 4x25-Gigabit Ethernet interfaces.
PR NumberSynopsisCategory: Junos Fusion Infrastructure
1366106PoE over LLDP negotiation is not supported on Junos Fusion Enterprise setup
Product-Group=junosvae		PoE (Power over Ethernet) over LLDP (Link Layer Discovery Protocol) negotiation is not supported in Junos Fusion Enterprise (JFE) setup. The issue results in powering up failure when a device makes PoE over LLDP negotiation with the JFE.
1454335SDPD core found @ vfpc_all_eports_deletion_complete vfpc_dampen_fpc_timer_expiry
Product-Group=junos		SDPD core found @ vfpc_all_eports_deletion_complete vfpc_dampen_fpc_timer_expiry
PR NumberSynopsisCategory: Bi Directional Forwarding Detection (BFD)
1432440In BFD and GR enabled scenario, BFD DOWN packets are not being sent immediately after BFD failure
Product-Group=junos		In both GR helper and GR restarter scenarios, BFD down packets are not immediately sent. It might cause an issue where BGP session down is notified before BFD DOWN.
PR NumberSynopsisCategory: Border Gateway Protocol
1437837The rpd process crash might be observed if leaking multi-pathed BGP routes from routing-instance to another routing table
Product-Group=junos		This issue applies to Junos platforms with BGP multipath configured under a routing-instance and a RIB group is deployed to leak routes from that routing-instance to another routing table. "rpd" may restarts unexpectedly when performing multipath calculation operations for the secondary routes - (such as, removing the rib-groups/bouncing BGP neighbor under routing-instance.) The secondary routes refer to the second RIB in a RIB (Routing Information Base) group.
1487893The process rpd may generate soft cores after "always-compare-med" is configured for BGP path-selection
Product-Group=junos		If a manually configured rib-group or automatically generated rib-group (via "family inet labeled-unicast resolve-vpn") is used to copy inet.0 (IP routing table) routes to inet.3 (MPLS routing table), the process rpd may continuously generate soft cores after "protocols bgp path-selection always-compare-med" is configured.
PR NumberSynopsisCategory: BBE Remote Access Server
1479486Verify deleting services via CoA when the specified family-type has been deactivated failed since incorrect number of service sessions are active
Product-Group=junos		While Verifying deleting services via CoA, when the specified family-type has been deactivated (failed) since incorrect number of service sessions are active. Hence Customer will notice some services are still active even though the family is deleted.
PR NumberSynopsisCategory: PTX Chassis Manager
1462987PIC may restart if the temperature of QSFP optics is overheated on PTX3K/5K
Product-Group=junos		On PTX3K/5K platform with P3-24-U-QSFP28/P3-15-U-QSFP28/P3-10-U-QSFP28 PIC used, if the temperature of QSFP optics is overheated, the PIC might restart.
PR NumberSynopsisCategory: Device Configuration Daemon
1475634Commit error is not thrown when member link is added to multiple aggregation group with different interface specific options
Product-Group=junos		Commit error is not thrown when member link was added to multiple aggregation group with different interface specific options. When member interface added to bundle with both ether and gig-ether interface specific options, gig-ether option takes precedence over ether options.
PR NumberSynopsisCategory: DNX platform MPLS FRR features
1485444ACX5448 L2VPN with interface ethernet-ccc input-vlan-map/output-vlan-map can cause traffic blackhole
Product-Group=junos		On the ACX5448 platform, l2vpn application with ethernet-ccc input-vlan-map/output-vlan-map can experience traffic blackhole while the control plane is still up. This issue is a software defect introduced by changes made via PR1456624 in the ethernet-ccc ingress interface. This software defect adds an internal vlan tag to all packets. As a result, customers' desired vlan-tag was not added in ccc->mpls direction. Causing the remote PE -- expecting vlan-tagged traffic -- to drop these packets due to vlan mismatch.
PR NumberSynopsisCategory: Covers Application classification workflows apart from custo
1479684Recent changes to JDPI's classification mechanism caused a considerable performance regression
Product-Group=junos		Recent changes to JDPI's (Juniper Deep Packet Inspection) classification mechanism caused a considerable performance regression (more than 30 percent).
PR NumberSynopsisCategory: EVPN control plane issues
1490953The rpd core might be seen when doing RE switchover after disabling BGP protocol globally
Product-Group=junos		On EVPN scenario with BGP and routing-instance configured, if BGP protocol is disabled globally and then doing RE switchover, multiple rpd core might be seen. And the rpd does not run on new primary RE. Hence it would affect the traffic and service.
PR NumberSynopsisCategory: EVPN Layer-2 Forwarding
1484296Dead next-hops might flood in a rare scenario after remote PEs are bounced
Product-Group=junos		On all Junos platforms with EVPN-MPLS scenario, due to a timing condition, dead next-hops might flood after remote PEs are bounced. This will affect BUM traffic flooding to remote EVPN PEs.
1495098[evpn_vxlan] [evpn_type5] vtep interface are not installed under the vxlan bridge domain after restart chassisd on mx10003
Product-Group=junos		On chassis control restart, vtep ifd is taking lot of time to get created. There is a tracking bug 1495394 for that. Even before vtep ifd is up, other media ifds are up and bgp neighborship is established, and triggers vtep ifl creations requests to l2ald. l2ald ignores as there Is no vtep ifd. subsequently after vtep ibid is created, tunnels are created but no MC routes are received from rpd, so vteps are not added to the bd. To recover, restart l2ald after ifd his up.
PR NumberSynopsisCategory: Issues related to EX MACsec
1469663Traffic loss might be seen with framing errors or runts if MACsec is configured on EX4600/QFX5100 platforms
Product-Group=junos		On EX4600/QFX5100 platforms with Media Access Control Security (MACsec) configured, if there is traffic flowing through the MACsec enabled link, increasing framing errors or runts statistics might be seen in the output of "show interfaces extensive <>" for the affected interface. Traffic loss might also happen due to this issue.
PR NumberSynopsisCategory: Express PFE FW Features
1491575BFD sessions start to flap when the firewall filter in the loopback0 is changed
Product-Group=junos		On all Junos based PTX/QFX10000 series platforms with large filter configuration (e.g. one filter has more than 500 terms or one term has more than 500 filters) scenario, during the change operation of loopback0 filter, the bfd sessions start to flap.
PR NumberSynopsisCategory: Integrated Routing & Bridging (IRB) module
1484964VLAN creation failure might be seen on QFX-series platforms with scaled VLAN and L3 configuration
Product-Group=junos		On QFX platforms with scaled VLAN and L3-interface configuration setup, when the VLANs are deleted and added back quickly, the newer VLANs might not get created successfully.
PR NumberSynopsisCategory: jdhcpd daemon
1488771For MX204 platform, the Vendor-ID is set as MX10001 in Factory default config and DHCP client messages
Product-Group=junos		MX204 platform presents itself as MX10001 in Factory default config and DHCP client messages.
PR NumberSynopsisCategory: Adresses ALG issues found in JSF
1483834FTPS traffic might get dropped on SRX/MX platforms if FTP ALG is used
Product-Group=junos		On SRX/MX platforms with FTP ALG enabled, if there are more than one FTPS connection between a pair of FTP client and server, the closure of one connection might cause other connections between that pair of FTP client and server to be affected, hence there might be traffic impact. It is a rare timing issue.
PR NumberSynopsisCategory: Flow Module
1489494Sometimes multiple flowd core files are generated on both nodes of chassis cluster at the same time when changing media MTU.
Product-Group=junos		On SRX5000 series with SPC3 card, SRX4000 series and vSRX platforms, if the traffic is kept running, when some configuration changes (e.g. changing media MTU configuration) are made to the egress interface, the interface might get into the invalidated status in a race condition, and then the flowd process might crash due to this issue.
PR NumberSynopsisCategory: Firewall Policy
1492436TCP-Proxy was mistakenly engaged in Unified-Policies when Web-Filtering was configured in a potential match policies.
Product-Group=junos		TCP-Proxy was mistakenly engaged in Unified-Policies when Web-Filtering was configured in any of the potential policy candidates. For customers who are only utilizing dynamic-applications and EWF in their policy, large performance improvements are seen with this fix.
PR NumberSynopsisCategory: Layer 2 Circuit issues
1498040l2circuit Stuck in RD state at one end
Product-Group=junos		L2circuit running on MC-LAG environment with backup neighbor might stuck in RD state at one end post the core link flap. Neighbor: 10.0.0.1 Interface Type St Time last up # Up trans ae1.2004(vc 20042004) rmt Up Mar 24 03:06:41 2020 2 Remote PE: 10.0.0.1, Negotiated control-word: No Incoming label: 307024, Outgoing label: 320784 Negotiated PW status TLV: Yes local PW status code: 0x00000010, Neighbor PW status code: 0x00000000 Local interface: ae1.2004, Status: Up, Encapsulation: VLAN Flow Label Transmit: No, Flow Label Receive: No Neighbor: 10.8.0.1 Interface Type St Time last up # Up trans ge-1/0/0.2004(vc 20042004) rmt RD Mar 24 04:06:42 2020 1 Remote PE: 10.8.0.1, Negotiated control-word: No Incoming label: 320784, Outgoing label: 307024 Negotiated PW status TLV: Yes local PW status code: 0x00000000, Neighbor PW status code: 0x00000010 Local interface: ge-1/0/0.2004, Status: Up, Encapsulation: VLAN Flow Label Transmit: No, Flow Label Receive: No
PR NumberSynopsisCategory: Layer 2 Control Module
1473610ERP might not come up properly when MSTP and ERP are enabled on the same interface
Product-Group=junos		When both MSTP and ERP are enabled on the same interface, then ERP will not come up properly.
PR NumberSynopsisCategory: Layer2 forwarding on EX/NTF/PTX/QFX
1484468Packet loss might be observed after device rebooted or l2ald restarted in EVPN-MPLS scenario
Product-Group=junos		In EVPN-MPLS scenario, if the core-facing interface (mpls interface) and the CE-facing interface are on different PEs, and the traffic from core is not continuous and DMAC (Dynamic MAC) ages out, due to an incorrect flood next-hop programming across different PFEs, packet loss might be observed after device rebooted or l2ald restarted.
PR NumberSynopsisCategory: MPC11 ULC platform software related issues.
1467725Hotswap between MPC11e and MPC9/8/6 is not supported
Product-Group=junos		On MX2020/MX2010 platforms, hotswap MPC11e with MPC9/8/6 or vice versa will result in training failures. It is recommended to power-off the chassis before swapping the cards.
PR NumberSynopsisCategory: Multiprotocol Label Switching
1497641The rpd might crash when SNMP polling is done using OID "jnxMplsTeP2mpTunnelDestTable"
Product-Group=junos		In a very rare P2MP with SNMP scenario, if the OID "jnxMplsTeP2mpTunnelDestTable" is polled by SNMP, the rpd (Routing Protocol Daemon) might crash since the relevant value is empty on the device and SNMP can not walk it at that time.
PR NumberSynopsisCategory: OS IPv4/ARP/ICMPv4
1496429RE crash might be seen when a large number of nexthops are quickly deleted and re-added in large ARP/ND scale scenario
Product-Group=junos		On all Junos platforms with large ARP/ND scale scenario, if a large number of nexthops are deleted and re-added very quickly (such as a result of link flap), the memory corruption might occur and eventually cause RE crash.
PR NumberSynopsisCategory: "ifstate" infrastructure
1486161Kernel core might be seen if deleting an ifstate
Product-Group=junos		On all Junos platforms, some operations such as configuration change may cause state information to change and eventually cause the ifstate to be deleted. In a very rare case, deleting an ifstate (kernel state) might cause kernel core and RE (Routing Engine) restart. There is no specific trigger, this issue is reported by the configuration change.
PR NumberSynopsisCategory: Kernel MPLS / Tag / P2MP Infrastructure
1493053Backup RE might crash unexpectedly due to a rare timing issue
Product-Group=junos		The backup Routing Engine might crash unexpectedly due to a rare timing issue during a route churn in the network.
1493431BGP session might keep flapping between two directly connected BGP peers because of the wrong TCP-MSS in use
Product-Group=junos		In case the two directly connected BGP peers are established over a one-hop LSP, if the IP layer's MTU is smaller than the MPLS layer's MTU, plus the BGP packets from the host have the DF bit set, the BGP session might keep flapping because of the wrong TCP-MSS in use.
PR NumberSynopsisCategory: JUNOS Network App Infrastructure (for ping, traceroute, etc)
1484689Show system buffer command display's all zero in the MX104 chassis and it looks like cosmetic issue as there is no service impact reported
Product-Group=junos		Corrected the odl tags and buffer data handling while xmlizing the output.
PR NumberSynopsisCategory: Layer 3 issues for VMX
1485706Interface input error counters are not increasing on MX150
Product-Group=junos		The input errors on MX150 may be zero under show interfaces extensive output when there are CRC/Align errors on the interface.
PR NumberSynopsisCategory: Protocol Independant Multicast
1443056PIM RPF selection for the specific multicast group might get incorrectly applied to other multicast groups
Product-Group=junos		On MX platforms, changing an RPF interface for a particular multicast group using PIM rpf-selection configuration, might cause other multicast groups to take, a newly changed RPF interface.
PR NumberSynopsisCategory: Issues related to PKI daemon
1489249Has the risk of service interruption on all SRX platforms with a dual-stacked CA server
Product-Group=junos		On all SRX products with Online Certificate Status Protocol (OCSP) or Certificate Revocation List (CRL) configured which belongs to a dual-stacked (IPv4/IPv6) Certificate Authority (CA) server, and if one of the IP addresses gets failure, all the services that rely on it might be interrupted, as Junos only selects the first IP from the DNS response message as the IP of the OCSP or CRL.
PR NumberSynopsisCategory: QFX platform optics related issues
1402127QSFP-100GBASE-SR4/LR4 might take a long time to come up after disabling interface or reboot
Product-Group=junos		On QFX5110 platform with QSFP-100GBASE-SR4/LR4 port used, after disabling an 100G port and then enable the port again, or reboot the device, there is a long time delay (5-15 minutes) before the ports come up.
1457266QFX5110 QSFP-100GBASE-SR4 made by Avago cannot linkup
Product-Group=junos		On QFX5110, interface on QSFP-100GBASE-SR4 whose Xcvr vendor is Avago on the QFX side cannot linkup, FEC errors might be seen on the other side. Note : Do not use 19.3R2-S2, 18.2R3-S3 and 18.2R3-S4 for this fix. The fix causes that FPC will go down when 100G link comes up and this leads FPC up and down every 90 seconds. The fix will work on 19.3R2-S3 and 18.2R3-S5 properly.
PR NumberSynopsisCategory: QFX L2 PFE
1385954"CMQFX: Error requesting SET BOOLEAN, illegal setting 66" is generated at booting up.
Product-Group=junos		The following log may be generated at booting up. >> Feb 10 02:15:26 jtac-qfx5100-48s-6q-r2373 : %PFE-3: fpc0 CMQFX: Error requesting SET BOOLEAN, illegal setting 66. This is a cosmetic log and you can ignore the log safely.
1454095Changing the VLAN name associated with access ports may cause that MAC addresses can not be learned under EVPN-VXLAN scenario
Product-Group=junos		On the QFX5k platform with EVPN-VXLAN configured, if the VLAN name associated with access ports is changed, then the virtual bridge domain may not be created. Due to this, the MAC addresses will not be learned. This issue will cause traffic loss.
PR NumberSynopsisCategory: Routing Information Protocol
1485009The rpd crashes if the same neighbor is set in different RIP groups
Product-Group=junos		If the same neighbor is configured under different RIP groups, the commit check fails to capture this invalid configuration and commit can be done successfully. However the rpd will crash.
PR NumberSynopsisCategory: RPD Next-hop issues including indirect, CNH, and MCNH
1458595The rpd crash might be seen if BGP route is resolved over same prefix protocol next-hop in inet.3 table which has both RSVP and LDP routes
Product-Group=junos		In race condition, if BGP route is resolved over same prefix protocol next-hop in inet.3 table which has both RSVP and LDP routes, when the RSVP and LDP routes are flapping (firstly these routes are down and then up), the BGP route will be re-resolved, and then the rpd crash might be seen.
PR NumberSynopsisCategory: Resource Reservation Protocol
1469567Fast reroute detour next-hop down event might cause primary LSP down in particular scenario
Product-Group=junos		In detour protection scenario (Fast-reroute enabled in LSP) in which the incoming detour LSPs that arrives on the primary next-hop merge with the locally originated detour LSP, sometimes after detour LSP next-hop down event the node incorrectly chooses the primary nhop (next hop) as the detour nhop, as a result it could cause brief traffic loss (a few seconds).
PR NumberSynopsisCategory: jflow/monitoring services
1439630Sampling might return incorrect ASN for BGP traffic
Product-Group=junos		In a BGP scenario with sampling enabled, incorrect ASN (autonomous system number) might be returned for the traffic originated from an internal prefix. This is because some AS paths and routes don't hold the latest information in the message buffers that srrd (sampling route-record daemon) uses to send to the clients.
PR NumberSynopsisCategory: SW PRs for SCBE3 fabric
1491968FPCs might stay down or restart when swapping MPC7/8/9 with MPC10/11 or vice versa in the same slot
Product-Group=junos		In MX240/MX480/MX960 routers with SCB3E or MX2010/2020 with SFB3 scenario, if MPC7E/8E/9E is swapped with MPC10E/11E each other or vice versa in the same slot, the different encoding mode between two MPCs might cause SCB3E/SFB3 to not change the mode gracefully according to the new MPC type inserted. This causes fabric destination errors which can trigger fabric healing mechanisms and cause system-wide impact due to fabric planes and FPCs getting reset.
PR NumberSynopsisCategory: MS-MPC Logging on MX
1478972TCP-log sessions might be in Established state but no logs get sent out to the syslog server
Product-Group=junos		When TCP-based syslog is configured under the service-set, the Services PICs will establish the TCP sessions with syslog server. When the networks between the syslog server and the MX/SRX are not stable, TCP retransmit may not work properly and cause the TCP sessions to hang. When issuing "show services tcp-log connections", the TCP sessions are still shown in "Established" state, however, no syslog messages are sent to the syslog server.
PR NumberSynopsisCategory: security-intelligence feature on SRX
148294719.2R2:VSRX3.0:SRX-RIAD:ipfd core found at 0x08601e14 in ipid_msg_process (svr=< optimized out>, client_id=< optimized out>, msg=< optimized out>, len=< optimized out>) at ../../../../../../src/pfe-shared/include/jnx/usp/ipid_shared.h:622
Product-Group=junos		If ipfd core happens with similar stack trace, it is likely that PR1482947 applies, it is self-heal, does not need special action, and does not impact production traffic
PR NumberSynopsisCategory: platform related PRs on SRX branch platforms
1488348All interfaces remain in the down status after the SRX3xx devices power-up/reboot
Product-Group=junos		The SRX3xx device may encounter a condition where revenue ports remain in the down status after the device reboot/power-up.
PR NumberSynopsisCategory: SRX-1RU HA SW defects
1487951If a cluster-id of 16 or multiples of 16 is used the cluster might not come up
Product-Group=junos		When using the SRX4600 firewall in a cluster, if a cluster-id of 16 or multiples of 16 is being used, the cluster might not come up.
PR NumberSynopsisCategory: SRX-1RU platfom datapath SW defects
1477627The flowd/srxpfe process might crash when deleting UserFW local authentication table entry
Product-Group=junos		When deleting UserFW (User Firewall) local auth table entry on an SRX4600 or SRX5000 Series device with SRX-SPC3 installed, the flowd/srxpfe process might crash if that entry has associated session and that session has installed NP cache on NP/IOC.
PR NumberSynopsisCategory: Trio pfe bridging, learning, stp, oam, irb software
1466470VXLAN packet may be discarded with flow caching enabled on MX150 and vMX
Product-Group=junos		On MX150 and vMX platform, VXLAN(Virtual Extensible LANs) packet may be discarded because flow caching doesn't support VXLAN when flow caching enabled.
1491091MAC malformation might happen in a rare scenario under MX-VC setup
Product-Group=junos		On MX-VC setup, if traffic is going through a VCP (virtual chassis port) port and forwarding to an egress port to the destination, while the traffic is handled entirely by the same PFE, MAC malformation might happen.
PR NumberSynopsisCategory: Trio pfe multicast software
1478981The convergence time for MVPN fast upstream failover might be more than 50ms
Product-Group=junos		On MX platforms which act as Next Generation Mulicast Virtual Private Network (NG-MVPN) Provider Edge (PE) routers, if the hot-root-standby and sender-based-rpf features are configured to enable MVPN fast upstream failover, once the primary multicast flow rate falls below the configured "mvpn hot-root-standby min-rate rate" threshold, the egress PE router is supposed to take switchover action from the primary flows to the backup ones, and the covergence time should be within 50 milliseconds. Due to this issue, the covergence time might be more than 50ms and reach up to several seconds (e.g. 2~3s) in a highly scaled scenario (e.g. the number of the multicast groups undergoing the switchover simultaneously is greater than 250 groups). This will result in more traffic loss than expected.
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1480348TFTP installation from loader prompt may not succeed on the EX series devices
Product-Group=junos		On the EX series platforms with 17.1R1 onwards, software installation from loader prompt may not succeed by using TFTP.
PR NumberSynopsisCategory: V44 Satellite Device Infra
1466324Temperature sensor alarm is seen on EX4300 in Junos Fusion scenario
Product-Group=junosvae		In Junos Fusion scenario with EX4300 acting as SD, the temperature sensor alarms and logs might be seen due to the wrongly reading about 2-3 degrees lower than the expected. There's no CLI command to clear the alarm and logs.
PR NumberSynopsisCategory: PTX/QFX10002/8/16 specific software components
1450090"Power supplies" LED on the status panel stays green while one or more PEMs have FAULT LED turned on
Product-Group=junosvae		"Power supplies" LED on the status panel stays green while one or more PEMs have FAULT LED turned on due to expected feed missing
PR NumberSynopsisCategory: Virtual Router Redundancy Protocol
1489425The "vrrp-inherit-from" change operation leads to packets loss when traffic is forwarding to the VIP gateway
Product-Group=junos		On all Junos platforms with VRRP scenario, if "vrrp-inherit-from" is configured and changing parameters under "vrrp-inherit-from" to another VRRP group, packets loss could happen when traffic forwarding toward to the VIP gateway.
PR NumberSynopsisCategory: ZT pfe l3 forwarding issues
1474160An MPC11 crash might occur on MX2K platform using multi-dimensional advanced scale configuration having Inline Keep Alive Sessions
Product-Group=junos		On an MX2k platform, in a rare scenario, after loading a complex multiple dimensional configuration with scaled Inline KA sessions, an MPC11 crash might occur due to transient condition of change and add of Inline Keep alive sessions.
 

Modification History

2022-03-23: non-technical changes; corrected formatting issue

2020-09-18: Update to include a warning about PFE memory leaks when using IRB with VPLS/Bridge-domain

2020-04-26: First publication 

01/04/2022: Non-technical changes; formatting modified