Resolved Issues

This section lists the issues fixed in the Junos OS main release and the maintenance releases.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

Resolved Issues: 17.2R2

On QFX5100, EX4300, or EX4600, traffic might be dropped when there is more than one forwarding class under the [forwarding-class-sets] hierarchy. PR1255077

Clients not getting IP addresses or ports are programmed under an incorrect VLAN. PR1230073
The FPC might encounter errors and stop forwarding traffic. PR1249375
EX9200: EVPN active/active ARP is not resolving on hosts. PR1267769
After MACsec link flaps, traffic stops forwarding across the MACsec link. PR1269229
The l2ald memory might leak for every IPv6 ND message it receives from peer the MC-LAG, and it does not free the memory allocated. PR1277203
An l2ald crash occurs with no apparent trigger. PR1302344

On an EX4300 egress VLAN-based firewall filter on a Q-in-Q interface, after a switch reboot, firewall counters might not increment as expected. PR1165450
The EX4300 aggregated interface goes down when the interface member VLAN is PVLAN and LACP is enabled. PR1264268

An interface explicitly disabled under RSTP is blocked under some conditions. PR1266035

EX4300 running Junos OS Release 17.1R1 cannot be converted on satellite mode. PR1267767
With show ethernet-switching table a few entries are stuck in DLR state after l2-learning restart. PR1268619
VRRP split brain in dual access device Junos Fusion. PR1293030
An access device without a cascade port cannot reach hosts over ICL link if they are authenticated by dot1x in a different VLAN than the default (manually assigned) VLAN. PR1298880

Layer 3 protocol packets are not being sent out from the switch. PR1226976
Preboot Execution Environment (PXE) unicast ACK packet isdropped on EX4300. PR1230096
Traffic is not forwarded through GRE tunnel on EX4300 in some cases. PR1254638
Unexpected Packet Forwarding Enginer manager (pfex) restart is seen on RE switchover. PR1258863
The mismatch of vlan-id between an interface IFL and VLAN config might result in traffic blackhole. PR1259310
On the EX4300 Virtual Chassis, the FPC might crash and a pfex core file might be generated. PR1261852
IPv6 neighbor solicitation messages are dropped when MLD snooping is enabled on EX4300. PR1263535
The l2ald process might crash when many dot1x clients are being re-authenticated. PR1269945
On EX4300, CPU usage related to pfex_junos increases because of DHCP relay traffic. PR1276995

The BGP session might flap during ISSU, resulting in 40-50 seconds of dropped traffic. PR1247937

When you add an EX4300 switch to the VCF, the following error message is seen: ?ch_opus_map_alarm_id alarm ignored: object 0x7e reason?. PR1234780

VLAN association is not being updated in the Ethernet switching table when the device is configured in single supplicant mode. PR1283880

MPC might crash during ISSU from Junos OS Release 15.1R1 to a later release when QSFP/CXP/CFP2 optics are present. PR1216924

After the rebooting of the Virtual Chassis, authentication of SNMPv3 users fails due to the change of the local engine ID. PR1256166

The egress PE device (EX4300) sends out LLDP frames toward the CE device with the destination MAC address of 01:00:0c:cd:cd:d0, which is a duplicated frame and rewritten by the ingress (PE) device. PR1251391

On EX4600 switches and Virtual Chassis, MACsec connections are deleted randomly after a switch reboot, optics removal, deactivation or activation of a MACsec configuration, or fxpc process restart. PR1234447

The BGP session might flap during ISSU, resulting in 40-50 seconds of dropped traffic. PR1247937