Configuration commit operation after policy change causes rpd crash

The rpd might crash during the policy configuration changes.

When activating security flow traceoptions, the unfiltered traffic is captured.

On all SRX Series platforms, when the flow traceoptions with the packet filter are enabled, the traces of other sessions that are not configured in the packet filter might be captured in the logs. However, when the packet filters are removed, the traces are got dumped into the log file for some time less than 30 seconds.

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.

The RA packets may be sent out without using the configured virtual gateway address

In an EVPN scenario, even if an IPv6 "virtual-gateway-address" is configured on "IRB" interface, the router advertisement (RA) packets may be sent out with the physical interface/link-local IPv6 address instead of configured virtual-gateway-address.

The rpd end up with krt queue stuck may be seen in vrf scenario

In rare cases, if using vrf configurations along with a static default route to em0 or fxp0, the interface flaps may result in rpd end up with krt queue stuck.

In rare cases rpd might crash after RE switchover when BGP multipath and L3VPN vrf-table-label are configured

When BGP multipath and L3VPN vrf-table-label are configured, after RE switchover, in rare cases, rpd might crash due to a vrf-table-label reallocation issue. During the crash, the routing table and neighborship will become unstable and traffic will be dropped, it will be restored automatically.

The process rpd crash may be observed with EVPN type-3 route churn

In an EVPN scenario, rpd may crash with EVPN type-3 route churn due to a race condition (Incorrect sequence of allocating and freeing memory for processing the updates between BGP and EVPN).

The service PIC might crash while changing CGNAT mode

On the MX platform, if changing CGNAT mode from deterministic to PBA (secured-port-block-allocation), the service PIC might crash.

The na-grpcd log file is not rotated and keeps growing until RE is out of disk space

In JET/Telemetry scenario, the Telemetry log file is not rotated and keep growing until Routing Engine (RE) is out of disk space, this might cause unexpected impact of RE, and eventually lead to RE crash. The fix has now been provided to set max allowable size to 50M and once the file reaches its max size, it will get rotated and compressed.

The port at FPC(e.g. JNP10K-LC1101) might fail to come up

On rare occasions, the port at FPC(e.g. JNP10K-LC1101) might fail to come up due to the retimer initialization failure upon the FPC reboot/OIR and a QSFP OIR.

The vlan tag is wrongly inserted on the access interface if the packet is sent from an IRB interface

With access interface configured on MPC7E/MPC8E/MPC9E/MX10k-LC2101/MX10003/MX204, the vlan tag is wrongly inserted on the access interface if the packet is sent from an IRB interface.

The IRB interface might flap after committing configuration change on any interface

When configuring an IRB interface with iff (interface address family) MTU higher than ifd (physical interface) MTU and that particular IRB interface is part of a bridge-domain or VLANs, if the above two configurations are committed at the same time, the IRB interface might flap on the subsequent committing which invokes interface configuration daemon (e.g. any interface configuration, bridge-domain or routing-instance configuration, etc.).

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.

Traffic might be dropped due to LDP label corruption after RE switchover

The LDP transit egress route for a BGP route has an indirect nexthop. In NSR and GRES scenario, after RE switchover, in some cases, LDP might fail to receive route flash for a BGP route from inet.0 and would not update the inet.3 route for the BGP route. As a result, the nexthop for LDP transit egress route will become unusable and the LDP transit egress route will get deleted. It could cause BGP sessions to go down and cause traffic drop.

4x10G interfaces on PTX3000/PTX5000 FPC type 3 might not come up after frequently flap for a large amount of time

On PTX3000/PTX5000 platforms with FPC3, if remote-connected interface continuously flaps for a large amount of time, the 4x10G interfaces on FPC3 might get down and never come up. The probability of occurrence increases with the number of continuous flaps.

Traffic is dropped after FPC reboot with AE member links deactivated by remote device

On JUNOS routers and switches with Link Aggregation Control Protocol (LACP) enabled, deactivating a remote Aggregate Ethernet (AE) member link will make the local member link move to LACP Detached state. The Detached link will be invalidated from the PFE AE-Forwarding table as expected. However, if the device is rebooted with this state, all the member links will be enabled in PFE AE-Forwarding table irrespective of LACP states and result in traffic drop.

The system does not reboot or halt as configuration when encountering the disk error

Even though "disk-failure-action reboot" or "disk-failure-action halt"is configured, the system does not reboot or halt as expected when it encounters the disk error.

Specific interface on P3-15-U-QSFP28 PIC card remains down until another interface comes up

On 15x100GE/15x40GE/60x10GE QSFP28 (P3-15-U-QSFP28) PIC card which is used on PTX5000 platform, the interface status is swapped between port 12 channel 2 and port 12 channel 3, hence the interface is not able to come up until another one comes up.

PTX10K/LC1101: when an interface is configured with jumbo frames support (e.g. MTU = 9216), the effective MTU size for locally sourced traffic is 24 bytes less than the expected value

PTX10K/LC1101: when an interface is configured with jumbo frames support (e.g. MTU = 9216), the effective MTU size for locally sourced egress traffic is 24 bytes less than the expected value. This issue is confined to locally originated traffic only and does not affect transit traffic.

"SIB Link Error" detected on a specific PFE may cause complete service impact

On QFX10002-60C/PTX10002-60C platforms, if there is a "SIB Link Error" detected on specific PFE, all the PFEs may not forward traffic between each other. The error may be caused by hardware condition such as any bad optics connected.

i40e NVM upgrade support for EX platform

Added support for i40e NVM upgrade in EX9208 in 19.3R1