Open Issues
Learn about open issues in this release for EX Series switches.
For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.
General Routing
-
runt, fragment and jabber counters are not incrementing on EX4300-MPsPR1492605
-
On EX4300-48MP platform, if POE is enabled, a master RE reconnect might be seen which could cause traffic impact. PR1499771
-
On EX2300, EX3400,:EX4300-48MP and EX4300 , Pause frames counters does not get incremented when pause frames are sent.PR1580560
-
On all EX platforms, whenever beacon LED functionality is enabled, there is a mismatch between the physical LED status and the output of the CLI command ?show chassis led? showing incorrect port LED status for interfaces as LED up instead of off.PR1697678
-
On EX4650, the SFP-LX interface will not be UP when different Small Form-factor Pluggable(SFP-10GBASE-T and SFP-LX) are plugged in within the same 4 port group. The presence of the 10GE-T SFP resets the speed of the quad back to 10G even if the quad port speed is set to 1G. Normally 10G interface by itself will be up when set to 1G if no other SFP is plugged in.PR1714833
-
On EX4400, a "BCM Error: API bcm_plp_mode_config_set" error msg may be seen in the syslog when converting a VCP to network port. There is no functionality impact.PR1738410
-
Disable the vme interfaces or have the default route added properly from the shell script for the connectivity with the ztp server to workPR1743222
-
EX-hardening: EX4400: set chassis config-button no-clear is not workingPR1758042
-
EX2300 VC: Dot1x authentication flapping in multiple supplicant mode with 100 user scalePR1767706
-
On EX2300/EX3400 series with SFP-SX/LX interface is not coming up due to auto-negotiation failure. PR1789617
Interfaces and Chassis
-
You can configure the routing platform to track IPv6-specific packets and bytes passing through the router. To enable IPv6 accounting, include the route-accounting statement at the [edit forwarding-options family inet6] hierarchy level: [edit forwarding-options family inet6] route-accounting; By default, IPv6 accounting is disabled. If IPv6 accounting is enabled, it remains enabled after a reboot of the router. To view IPv6 statistics, issue the show interface statistics operational mode command. Can be found here: http://www.juniper.net/techpubs/en_US/junos10.4/topics/usage-guidelines/pol icy-configuring-ipv6-accounting.html PR717316
Layer 2 Ethernet Services
-
If name-server information is changed via CLI after the DHCP subscribers are up, DNS obtained from DHCP server is overwritten by local config. This may result in DNS look up failures in some cases. PR1743611
Platform and Infrastructure
-
On Junos OS EX4300 and EX4300-VC platforms, if zeroize or interface configuration deletion performed, PFEX process crash will se seen when interface/device comes up and there will be traffic loss during the PFE restart.PR1714117
-
In a rare scenario, due to timing issues, the Packet Forwarding Engine (PFE) crash is observed on Junos EX4300 platforms. This causes traffic loss until the PFE comes up.PR1720219
-
On EX4300-VC, the Online Insertion and Removal (OIR) of Quad Small Form-factor Pluggable (QSFP) may result in a PFE crash under near-zero idle CPU conditions.PR1733339
-
On EX4300 VC setup, "qsfp_tk_read_mem_page: Rear QSFP+ PIC failed to select addr 127 err 1000" messages may be seen intermittently. There is no functionality impact for these error messagesPR1747126
-
On all EX4300 platforms, traffic is sent on an AE interface and sent to the removed child interface from AE (Aggregated Ethernet) where the traffic is lost.PR1749406
Virtual Chassis
-
On EX4600-VC, when "request system reboot all members" is executed, post-reboot one of the VC member/Flexible PIC Concentrator(FPC) might disconnect and join the VC back due to Packet Forwarding Engine (PFE) restart. Traffic loss is seen when FPC is disconnected.PR1700133