The RE-PFE out-of-sync errors might be seen in syslog

When a configuration that moves the Packet Forwarding Engine offline and another configuration that brings the Packet Forwarding Engine back online are committed in quick succession, out-of-synchronization syslog errors might occur. Most of the time these are benign errors, but sometimes these errors might result in Packet Forwarding Engine crash.

Error drops in XM/MQSS fabric streams(q-node stats) are not accounted in class-of-service fabric stats

The output of the cli command "show class-of-service fabric statistics" now includes traffic that was dropped because of internal errors in the drop counts

The VRF static route might not be exported when route-distinguisher-id is used on RR in BGP L3VPN scenario

In Border Gateway Protocol (BGP) Layer 3 Virtual Private Network (L3VPN) scenario, on the Route Reflector (RR) with Virtual Routing and Forwarding (VRF) instance deployed, if Auto-RD (Automatic Route Distinguishers) feature is used, the VRF static route might not be exported to bgp.l3vpn.0 table correctly under race condition. Hence the static route could not be advertised to remote device.

Traffic loss might be seen on new primary after the interface flaps followed by RE switchover in VRRP scenario

VRRP MAC filter will not be seen in PFE if interfaces flap followed by GRES, before VRRP state settles down after flap. During this time VRRP state is backup in primary-RE and VRRP state is idle in Backup-RE.

Control traffic loss may be seen on SRX4600 platform.

On SRX4600 platform, FPC major error may be observed after system initializes like system reboot/power on, which will cause the device to potentially discard control traffic.

MX10003 Alarm LED reflects the stale entry on backup RE, post GRES switchover.

MX10003 Alarm LED reflects the stale entry on backup RE. The Alarm LED in backup RE remains in yellow state forever.

The EVPN implementation does not follow RFC-7432

The EVPN implementation does not follow RFC-7432 when encoding/decoding 20-bit MPLS labels into ESI Label field in ESI Label Extended Community.

SPC3: ike sa detail output is not showing proper traffic statistics

The output of "show security ike sa detail" does not show proper traffic statistics. Following fields display statistics as 0 when there should be a non-zero value. 1. Input bytes 2. Input fragmentated packets 3. Input fragmentated packets

In EVPN A-A scenario with MX or EX acting as PE device,flood NHs to handle BUM traffic may not get created or miss certain branches when the configuration is performed in a particular sequence

In EVPN A-A scenario with MX or EX acting as PE device,flood NHs to handle BUM traffic may not get created or miss certain branches when the configuration is performed in a particular sequence

The snmp trap sends wrong info with "Manual failover"

When RG1+ failover because of IF, SNMP may send the wrong info with "Manual failover".

FPC Errors might be seen in subscriber scenario

In subscriber scenario, if the"service-accounting-deferred" is configured on dynamic-profile, and there is multicast to a large number of destinations on the same physical port, the FPC Errors might be seen.

The pfe_disable action does not disable the logical tunnel interfaces belonging to the affected PFE

When pfe_disable action is triggered (for example by a major error on the PFE), all the physical interfaces for that PFE will be disabled. This PR is meant to ensure that logical tunnel interfaces (e.g. lt-*) are also disable to prevent attracting traffic to the failed PFE.

Changing the value of mac-table-size to default may lead all FPC to reboot

If the value of mac-table-size of a given VLAN which is carrying traffic is changed to default, then the layer 2 forward table ( IFL-List ) needs to be re-associated with Flush-List which keeps the newest MAC list pushed by the Route Engine ( RE ), then the IFL-List must be deleted for this re-association. However, when the MAC entries are deleted, their flags might still remain in the IFL-List, that causes the MAC deletion failure, also the update of the Flush-List might get stuck. Consequently, all FPC might reboot.

The rpd might crash when traceoptions are enabled

When traceoptions are enabled with a lot of trace flags or 'flag all', the rpd might crash due to buffer overflow issue. This is a timing issue.

On SRX5400, SRX5600, SRX5800 devices with SPC3, "show security ike security-association detail" command does not display ?local IKE-ID? field correctly.

On SRX5400, SRX5600, SRX5800 devices with SPC3, "show security ike security-association detail" command does not display "local IKE-ID" field correctly.

Traffic destined to VRRP VIP gets dropped as filter is not updated to related ifl

On MX platform with enhanced-ip and VRRP configured, if remove/add a child link from AE bundles, traffic destined to VRRP VIP might be dropped.

SNMPD crashed and caused core dump.

Issue: snmpd daemon leaks memory in snmpv3 query path and crashes. Cause: The issue is caused by a memory leak when the request PDU is dropped by snmp when config - "snmp filter-duplicates" is enabled. Each request PDU has a structure pointer for the SNMPv3 security details. This is allocated when the pdu is created/cloned. But while dropping the duplicate requests the corresponding free for this struct is not done, which causes the memory leak. Fix: The fix adds the security state reference cleanup callback during PDU free.

A few minutes of traffic loss might be observed during recovery from link failure

On EVPN-VXLAN Multi-homing environment, when interface state is changed, a few minutes traffic loss might be observed during recovery from link failure. It happens in this configuration scenario where large (such as, a few hundreds) sub-interface style configurations and ESI are configured in one IFD (Pysical interface), then any change in the IFL (Logical interface) might result in programming all IFLs which share the same ESI, and then multiple updates would be sent to the kernel. At last the l2ald (Layer 2 Address Learning Daemon) would be very busy and it causes a few minutes delay programming of flooding for VTEP interface, and during this period the traffic would be dropped.

The chassisd might crash and restart after the AGENTX session timeout between primary(snmpd) and sub-agent

On all platforms, after the AGENTX session timeout between primary(snmpd) and sub-agent, the chassisd might crash and restart.

SRX4600 40G interface flaps multiple time by MAC Local Fault

On SRX4600 device, 40G interface might flap multiple times by MAC local fault.

The BUM traffic might not be flooded in EVPN-MPLS scenario

In EVPN-MPLS (Ethernet VPN - Multiprotocol Label Switching) scenario with bridge-domains used, any configuration change which causes a BD (Bridge Domain) reincarnation (e.g. change of vlan-id-list under bridge-domains) might break the flooding of BUM (Broadcast, Unknown-unicast, Multicast) traffic. The issue leads to BUM traffic loss. All services that relying on BUM traffic might be impacted.

IPv6 link-local address for virtual-gateway address is marked as duplicate in EVPN

In EVPN A-A mode, if the same link-local IPv6 address is configured on both IRB interfaces on the two PEs, DAD will mark one of the IRB interfaces as the duplicate.

MPLSoUDP/MPLSoGRE tunnel may not come up on interface route

In MPLS over UDP or MPLS over GRE scenario, if the nexthop type of the MPLSoUDP/MPLSoGRE tunnel is interface route, the tunnel may not come up.

All FPC cards might restart after L3VPN routes churn

In L3VPN network with large-scale prefixes, if the peer PE is other vendor's router (e.g. Cisco) configured with "per-prefix label", all FPC cards might restart after L3VPN routes churn multiple times.

The rpd might crash when LDP route with indirect next-hop is deleted

If Label Distribution Protocol (LDP) route with indirect next-hop exists (e.g. LDP egress-policy is used to advertise BGP route into LDP), the rpd might crash when the LDP route is deleted.

Junos OS: BGP packets can trigger rpd crash when BGP tracing is enabled. (CVE-2019-0019)

Junos OS: BGP packets can trigger rpd crash when BGP tracing is enabled. (CVE-2019-0019); Refer to https://kb.juniper.net/JSA10931 [juniper.net] for more information.

VPN does not recover on the high-end standalone SRX Series device when CLI operation restart ipsec-key-management is done.

VPN does not recover on the high-end standalone SRX when CLI operation "restart ipsec-key-management" is done.

RPD core upon RE switchover with scaled EVPN configuration.

on MX or QFX10k with dual RE/NSR enabled and a scaled EVPN configuration, RPD could core upon RE switchover due to a bug that corrupts the EVPN instance tree. Not seen with limited or few EVPN instances.

Traffic loss seen in IGMP subscribers after GRES.

There is a chance that some subscribers may not have IPTV post GRES. This condition will be seen if subscribers are logged in before the system has initialized fully or if dynamic profiles are changed with subscriber activity.

MPLS LSP traffic loss might be seen under rare conditions if CSPF is enabled

When make-before-break (MBB) new instance signaling experiences error and before retry is finished, other triggers such as auto bandwidth adjustment timer expiration have to be blocked until MBB finishes. Once the MBB finishes instance switching, blocked trigger needs to be scheduled, but should only be triggered after optimize-adaptive-teardown timer expires. In the affected releases, the blocked trigger is scheduled immediately after instance switching without taking optimize-adaptive-teardown timer into account, it causes old instance to be torn down before whole system finishes changing routes using the new instance, this leads to traffic loss.

The cosd process might crash during committing configuration change via netconf

If excess-priority is configured, the cosd process might crash during committing configuration change which includes assigning CoS profile on any logical interface via netconf.

The rpd crash due to memory corruption in EVPN

In Ethernet VPN (EVPN) active/active multi-homing scenario with MPLS encapsulation, toggling of multi-homed interface might cause memory corruption leading to rpd crash.

repd continue core on VC-Bm when there are too many IPv6 address on one session (hit PR1384889).

When the box hit PR 1384889, There will be multi IPv6 address on one session, On this scenario, It is possible to have repd continuous core when replicate SDB from VC-Mm to VC-Bm. When this issue happens below log can be observed: Dec 26 05:27:54.404 mxvc-r019-r026 repd[20605]: %DAEMON-3: sdb_db_store_sts_in_lts Flush STS->LTS Failed return -2 Dec 26 05:27:54.803 mxvc-r019-r026 repd[20605]: %DAEMON-3: sdb_db_store_sts_in_lts Flush STS->LTS Failed return -2 Dec 26 05:27:56.254 mxvc-r019-r026 repd[20605]: %DAEMON-3: sdb_db_store_sts_in_lts Flush STS->LTS Failed return -2 Dec 26 05:27:56.304 mxvc-r019-r026 repd[20605]: %DAEMON-3: sdb_db_store_sts_in_lts Flush STS->LTS Failed return -2

Scaled MPLS labels might cause slow labels allocation and high CPU utilization

On Junos platforms with scaled MPLS labels used, when the system is already running with high load, inefficient labels allocation might cause even higher CPU utilization at 100% for hours. The issue might affect traffic.

DHCP Not working for some clients in dual AD fusion setup on EP ports.

DHCP Not working for some clients in dual AD fusion setup on EP ports. When the SD is not reachable to the peer AD sdpd sends color 0 for color type MCAE and kernel is sending 0 to AD PFE. kernel has to convert this color to 0xFF before sending it to AD PFE.

The rpd might crash on a leaf node when handling the withdrawal of remote or local MAC address in an EVPN-VXLAN scenario

On all Junos OS platforms that are running Ethernet VPN (EVPN) with Virtual Extensible LAN (VXLAN) on the device, when handling the withdrawal of remote or local MAC address, it may cause stack corruption and may subsequently result in rpd crash on the leaf node.

Some files are missing during log archiving

When there are any scripts running on the router cscript.log will be created. It is found that the permission are set wrongly hence when any non-root user tries to archive the /var/log along with cscript, some other files in /var/log go missing in the archived file. So when we untar the file, less files are found. This issue is not seen when root user does the archive. With the fix of the PR non-root user would be able to archive the files.

IPv6 traffic might be dropped between VXLAN bridge-domain and IP/MPLS network

On Trio-based platforms, when an IPv6 host located in VXLAN bridge-domain tries to communicate with another IPv6 host located in IP/MPLS network via irb gateway, the IPv6 traffic might be dropped.

"show configuration" and "rollback compare" commands causing high CPU

CPU usage hits 100% for a few seconds if running "show configuration" or "show system rollback compare " commands.

Group VPN (GVPN): ToS/DSCP byte is not copied into the outer IPSec header during IP header preservation

With this fix, the following IP header fields of an unencrypted datagram are copied into the transport header: ToS/DSCP, TTL.

Traffic drop occurs when deleting MPLS family or disabling interface which has non-default EXP rewrite-rules

The non-VPN packets might be dropped when deleting family MPLS or disabling interface which has non-default EXP rewrite-rules. This is due to a cos-rewrite mask programming issue in Packet Forwarding Engine (PFE).

VLAN tag is added on access interface when configured on MPC7 interface

With access interface on MPC7, VLAN tag is being added on the packets send along this access interface and hence it might be rejected by the other side.

Family inet of the unnumbered interface might be getting deleted when deleting one of the IPs of the binding interface

When an unnumbered interface is binding to an interface which has more than one IP address and one of the IPs is deleted, the family inet of the unnumbered interface might be getting deleted. The issue results in traffic loss for all the services that rely on the family inet of the unnumbered interface. Configure preferred-source-address on the unnumbered interface will prevent deletion of the IP hence avoiding the deletion of the family inet of the unnumbered interface.

RPD may core while committing configuration changes when IPv4 labeled-unicast egress protection is running

On a Junos device configured with IPv4 labeled-unicast egress protection, RPD may core when a configuration change is committed (even an unrelated change having no relationship to egress protection itself). The behavior is nondeterministic and dependent on internal system timing so a core will not always be produced even if egress protection is configured. Specific confirmation that an RPD core is caused by this issue requires examination of the core file contents.

PEM 0 or PEM 1 I2C Failure major alarm might be set and cleared for multiple times

On SRX4600 device, the "Major alarm set" and "Major alarm cleared" for PEM 0/1 with I2C Failure might be seen for multiple times when SRX4600 fails to read the PEM register via I2C within two consecutive times.

Dynamic routing protocol flapped with vmhost RE switchover on NG-RE

In NG-RE dual RE platform, some commands for RE switchover might lend process rpd to down/up, due to a delay that made the process chassisd failed to update its status of mastership promptly. As the mastership status the chassisd governed determines which action the process rpd need to take the next, so if RE is rebooted and the chassisd mastership state is RE-Master then, in that case, rpd clears all the kernel states; and if chassisd mastership state for that RE is RE-Backup, then rpd just quits silently and restarts again in backup mode without any kernel states being cleaned. So that rpd cleanup kernel states caused this issue.

input and output bytes or bps statistic values might not identical for a same size of packet

On SRX4600 device, input and output bytes or bps statistic values might not identical for a same size of packet

AT&T IPAG : LSI interface is not getting associated to ipv6 neighbor after link failure

Upon LSI interface going down, nd6 entries in JUNOS will not have l2 interface resolved some times.

Complete device outage might be seen when SPU VM core happens

On SRX high-end platforms, when SPU (Services Processing Unit) VM core happens on one node, this triggers bad kernel state on this node and complete device outage could be seen, which means all IGP and BGP adjacencies would be affected. The reason is that the SPU VM core causes primary PE to dump live VM core, which blocks jsrpd from committing RG (Redundancy Group) state updates to kernel to set PFE to primary state. And if no PFE is in the primary state traffic would be lost because the original primary SPU is reset in the process of booting up. It is a very rare timing issue.

there is no SNMP Trap message generated for jnxHardDiskMissing/jnxHardDiskFailed on Summit MX

There is no Trap message generated in case of SSD missing or Disk failed on Summit platform (MX10003 and PTX10002 .etc.), with the fix of the PR, JUNOS will generate OID as below accordingly. OID: 1.3.6.1.4.1.2636.4.1.15 jnxHardDiskMissing OID: 1.3.6.1.4.1.2636.4.1.14 jnxHardDiskFailed

PPPoE session might be disconnected when LI attributes are received in access-accept with invalid data

In subscriber scenario, when LI attributes are received in access-accept with invalid data, attributes parsing might fail and login is denied with 'MALFORMED DATA' error, which leads to the result that PPPoE session will be disconnected.

A memory leak in rpd might be seen if source packet routing is enabled for IS-IS protocol

If source packet routing or segment routing is enabled for IS-IS protocol, a memory leak might happen in the routing protocol process (rpd). The rpd will crash and restart once the rpd runs out of memory.

Change the nd6 nexthops to reject NH once l2 interfaces gets disassociated with ipv6 entries

When IPv6 neighbors are learnt on IRB + L2 interface, upon L2 interface is link down, the ND6 neighbor nexthop state will change to reject instead of earlier behavior of remaining in UNICAST state leading to not resolving L2 interface again successfully.

rpd crash on backup routing-engine after enable nonstop-routing with EVPN

upon activating nonstop-routing backup routing-engine routing protocol daemon asserting when processing EVPN ESI changed with dynamic-list-next-hop.