wrong packet stats reported in ifHCInUcastPkts OID

The total number of packets is less than the sum of unicast, multicast and broadcast packets due to lag in read depending on packet rate. Now the total packets is set to the sum

Momentary dip in traffic when a GRES is performed

On GRES the implicit filters set by DFWD are cleared by DCD. Hence we are seeing a momentary dip in traffic.

mpls-ipv4 templates doesnot have correct src AS and dst AS as 4294967295 src Mask and DstMask as 0 after adding mpls-flow table size on the fly

mpls-ipv4 templates doesnot have correct src AS and dst AS as 4294967295 src Mask and DstMask as 0 after adding mpls-flow table size along with existing ipv4 and ipv6 templates

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.

The inline-jflow sampling configuration might cause FPC crash On MX platforms

On MX-series platforms, if the inline-jflow "nexthop-learning" knob is configured, when the sampling removes one next-hop, the FPC might crash. It is not easily reproducible and it is a rare issue.

VPLS with vlan-id-list not working properly in some releases when PE-CE is ae-interface with single member link and child ifd flap

On a VPLS scenario, on which the CE-PE facing interface is an aggregate (ae) interface with a single child link, and VPLS VLAN-ID-list is configured: If the child link flaps, then the VLAN-ID-List does not get properly programmed in Hardware and the VPLS does not work properly.

FPC high CPU utilization or crash during hot-banking condition

Trio-based line card might reach high CPU utilization or crash due to a defect in memory hot-banking condition handling.

Inline BFD keep flapping when inline samping was configured

Inline BFD keep flapping when inline sampling was configured

Packets might be dropped on data plane in the inline Jflow scenario

On MX series with MPC, in the inline Jflow scenario, due to a software defect, the data structure associated with inline Jflow feature may not be initialized correctly. This leads to not being able to forward traffic correctly on the affected MPC.

After multiple link flap events, l2circuit stops forwarding with core interface flap

After multiple link flap events, l2circuit stops forwarding with core interface flap

Constant memory leak might lead to FPC memory exhaustion

On MX/EX9200 platforms, constant memory leak might occur on a Flexible PIC Concentrator (FPC), and such condition might finally lead to memory exhaustion and the FPC would core.

PFT MX10008 Expected "inline-ipv4-export-packet-failures" is not listing in show services accounting error

Expected "inline-ipv4-export-packet-failures" is not listing in show services accounting errors command

BFD sessions bounced on none offlined FPC

Split Cmerror list and maintain one list per PFE for cases where errors are registered per PFE. The remaining errors which are registered without the is_pfe_support flag will be maintained under the PFE0 list.

If using SRX cluster and configuring 4 100G interfaces on PIC 0, all the 4 interfaces might be down

On SRX4600 platform, in chassis cluster scenario, if configuring 4 100G interfaces on PIC 0, after reboot for the changed configuration to take effect, all the 4 interfaces might be in the 'down' state.

CPSM daemon memory leak in VMHOST

CPSM (Control plane switch management) daemon memory leak in VMHOST, it may also cause logrotate doesn't work, and cause large cpsm log size.

Incorrect value for flow packets/octets fields might be seen in inline-jflow scenario

On MX platform with LU-chip based MPC, the value for flow packets/octets fields might be incorrect if ipv6-extended-attrib is enabled in inline-jflow scenario.

The rpd process may restart if non-BGP protocol route with an AS_PATH is used

An RPD process may restart with core files when processing a non-BGP route with AS PATH information with the following signature in its core file: "rt_notbest_sanity: Path selection failure on , 0x98aed50 recovering..."

Packet loss might occur on unrelated traffic when AppQoS rate-limiter is applied on SRX4600 and SRX5K platform using SPC3

On SRX4600 and SRX5K platform using SPC3, once AppQoS rate-limiter is applied to specific traffic, packet loss occurs on unrelated traffic continuously until reboot.

Per "physical-port-based" filter in the egress firewall'

This model of egress vpls filter with "physical-interface-specific" semantic is only to be used to cater to use-cases where there is a need to install "physical-port-based" (common across all IFLs & all families in the port) filter is needed. Only 1 such filter is required on per-port level.

Support for explicit map operaion swap-push/pop-swap on vpls-ifl

Introduced explicit swap-push map operations on vpls-ifl in ACX5K. This is already supported as part of implicit map operations / routing-instance level configurations.

Fabric packet forwarding performance might be degraded on MX2K platforms installed with SFB2 and MPC9E

On MX2K platforms installed with the switch fabric board SFB2 and the linecard MPC9E, the fabric packet forwarding performance might be degraded around 25% in Junos 18.2 release.