Resolved Issues in JUNOS Release 10.2 for EX Series Switches

The following are the issues that have been resolved since JUNOS Release 10.2R1 for EX Series switches. The identifier following the descriptions is the tracking number in our bug database.

Note: Other software issues that are common to both EX Series switches and M, MX, and T Series routers are listed in Issues in JUNOS Release 10.2 for M Series, MX Series, and T Series Routers.

Access Control and Port Security

On EX4200 switches, the LLDP-MED Location ID contains a Type, Length, and Value (TLV) whose length is incorrect. [PR/521658: This issue has been resolved.]
On EX Series switches, packets might be dropped under certain network conditions, even though the user is authenticated. As a workaround, restart the dot1x protocol. [PR/524675: This issue has been resolved.]
On EX Series switches, if static MAC address bypass is configured for a client on an interface configured for 802.1X authentication, the client becomes unreachable every time the MAC address expires. [PR/536316: This issue has been resolved.]
If you connect a computer to a phone that is connected to an interface supporting multiple supplicants on an EX2200 switch, the Telecommunications Industry Association (TIA) network policy in the LLDP-MED packets from the EX2200 switch reports an incorrect VLAN and the phone might lose connectivity. [PR/542810: This issue has been resolved.]
On EX Series switches, if you change the LLDP management address before configuring the logical (inet) interface, the SNMP MIB is not updated correctly on the remote switch (lldpRemManAddr). As a workaround, set the logical (inet) interface before setting the LLDP management address, or bounce the interface. [PR/534138: This issue has been resolved.]

Bridging, VLANs, and Spanning Trees

On EX Series switches, in a scaled environment with more than 4000 VLANs, MVRP advertisements might not be sent intermittently when the VLAN membership is modified. [PR/475701: This issue has been resolved.]

Firewall Filters

On EX3200 and EX4200 switches, firewall filters configured with the dscp match condition do not filter traffic on the egress interfaces. [PR/538403: This issue has been resolved.]
On EX4500 switches, if you activate or deactivate a firewall filter configuration, VSTP convergence might not occur properly. As a workaround, restart the Ethernet switching process (eswd). [PR/548446: This issue has been resolved.]

Hardware

An EX2200 switch might not be able to recognize an SFP transceiver’s EEPROM information. [PR/540609: This issue has been resolved.]

Infrastructure

On EX Series switches, the static Neighbor Discovery Protocol (NDP) entries for IPv6 addresses are cleared automatically after some time. [PR/453710: This issue has been resolved.]
On EX Series switches, the clear interface statistics all command takes a long time to execute. [PR/509303: This issue has been resolved.]
On EX4200 switches, the headers in ARP requests sent from a virtual IP address contain the virtual IP address as the source address instead of the virtual MAC address. [PR/512488: This issue has been resolved.]
On an EX8208 switch, the master Routing Engine might create a core file and reboot when there are more than 64,000 MAC clone routes in a single VLAN. [PR/513321: This issue has been resolved.]
On EX8200 switches, the output of an SNMP walk on jnxOperatingTemp and jnxFruTemp does not show the temperature for line cards. [PR/524112: This issue has been resolved.]
On EX4500 switches, the interface shutdown action for a storm control configuration does not have any effect. [PR/526077: This issue has been resolved.]
In a Q-in-Q tunneling configuration that includes aggregated Ethernet interfaces (LAGs), after a forwarding (pfem) process restart, the member interfaces in the VLAN might be incorrectly set. [PR/527117: This issue has been resolved.]
A memory leak might occur when the software forwarding process (sfid) attempts to reconnect to other JUNOS Software processes, eventually resulting in an sfid core file. [PR/534824: This issue has been resolved.]
On the EX3200 and EX4200 switches after a hardware reboot and initialization, when the switch is rebooting the following message might appear: "Firewall rows could not be redirected on device 0". This message is a false positive and is generated intermittently due to a timing issue. If you see this message during consecutive reboots, contact the Juniper Technical Assistance Center (JTAC). [PR/537400: This issue has been resolved.]
On EX2200 and EX4200 switches, if you have configured the system ports console log-out-on-disconnect statement, the switch does not log out when the console is disconnected. [PR/538263: This issue has been resolved.]
If you configure a large number of VLANs and aggregated Ethernet interfaces and commit the configuration, the forwarding process (pfem) utilization stays at 80 percent for more than 60 minutes. As a result, the aggregated Ethernet interfaces cannot be used until the pfem usage reduces to normal limits. [PR/544433: This issue has been resolved.
If no intraconnect module or Virtual Chassis module is installed in an EX4500 switch, the switch boots but is not fully functional. Traffic loss might occur during packet forwarding. [PR/544628: This issue has been resolved.]
A Packet Forwarding Engine (PFE) core file might be created if the unicast next hops are not present on the network. PR/546674: This issue has been resolved.]
After you reboot an EX Series switch, a kernel panic might occur on the backup Routing Engine. [PR/550880: This issue has been resolved.]
On EX2200 switches, the software forwarding process (sfid) displays the following message frequently:
```
TASK_OS_MEMHIGH: Using 55005 KB of memory, 109 percent of available
```
[PR/551157: This issue has been resolved.]
When the DNS server configured is not reachable, the name resolution for localhost takes a long time and the output of the show ntp association command takes a long time to appear. [PR/551739: This issue has been resolved.]
On EX8200 switches, after routing and traffic recover from a graceful Routing Engine switchover (GRES) operation, a core file might be created after the Ethernet switching process (eswd) is restarted or after a line card is taken offline. [PR/570645: This issue has been resolved.]
During the TFTP transfer portion of an automatic software download procedure, the software package might be truncated or corrupted. [PR/570901: This issue has been resolved.]
On EX4200 switches, autonegotiation bypass, which allows a link in a Gigabit Ethernet SFP uplink port to begin operation even if autonegotiation on the link partner is disabled, fails to bring up the link. [PR/571198: This issue has been resolved.]
The Ethernet switching process (eswd) might crash and then recover when the following change is made in the CLI (either in a single commit or in separate commits):
- First, you remove an interface from the interface range on which VoIP is configured.
- Then, you either delete the removed interface or change its address family to a family other than ethernet-switching.
[PR/571863: This issue has been resolved.]
On an EX4200 Virtual Chassis, a forwarding process (pfem) core file might be created if all 802.1X-enabled interfaces are in the held state or the connecting state. [PR/571865: This issue has been resolved.]
On EX Series switches on which the last term in a loopback firewall filter is either an implicit deny-all or explicit deny-all, received packets whose TTL is exceeded are dropped instead of being processed by the CPU. Thus, for example, traceroute packets received with a TTL of 0 are dropped, and ICMP unreachable packets are not sent back. [PR/573170: This issue has been resolved.]
On EX4200 switches, when the mode on an SFP+ uplink module is changed from 10g to 1g, or from 1g to 10g, the switch does not learn MAC addresses until it is rebooted. [PR/573857: This issue has been resolved.]
On a switch on which nonstop routing (NSR) is enabled and on which transit unicast and multicast traffic is flowing, after multiple graceful Routing Engine switchover (GRES) operations, the routing protocol process (rpd) can continue to utilize large amounts of memory. [PR/574442: This issue has been resolved.]
On EX2200 switches, the software forwarding process (sfid) might deadlock, with the result that traffic is blocked and MAC addresses cannot be learned. As a workaround, reboot the switch. [PR/579725: This issue has been resolved.]
A large number of MAC pause frames might stall a Virtual Chassis member's IPC connection, causing the member to lose its connection to the Virtual Chassis. [PR/581804: This issue has been resolved.]

Interfaces

On EX8200 switches, if you deactivate the chassis configuration and upgrade the Routing Engine software, the backup Routing Engine might go down and come back up and create a core file when you enable and commit the chassis configuration. This might also result in slower response in the CLI. To stop the backup Routing Engine restarting continuously, deactivate the chassis on the backup Routing Engine. [PR/489029: This issue has been resolved.]
In a Virtual Chassis setup, on consecutive reboots of the master switch, the peer device connected to the EX4200 switch over Link Aggregation Control Protocol (LACP) does not recognize the LACP messages sent by the EX4200 switch and the links become standalone links. [PR/505069: This issue has been resolved.]
On EX4500 switches, when traffic congestion occurs on the ingress side of a Gigabit Ethernet interface with flow control enabled, the interface might generate pause frames. As a workaround, disable flow control on the ingress interface. [PR/528326: This issue has been resolved.]
EX8200 switches might not detect the front-panel LCD display. [PR/553144: This issue has been resolved.]

J-Web Interface

In the J-Web interface, uploading a software package to the switch might not work properly if you are using Microsoft Internet Explorer version 7. [PR/424859: This issue has been resolved.]
In the J-Web interface, interfaces configured with no-flow-control might be displayed in the LACP (Link Aggregation Control Protocol) Configuration page (Configure > Interfaces > Link Aggregation). [PR/437410: This issue has been resolved.]
In the J-Web interface, in the OSPF Configuration page (Configuration > Routing > OSPF), the Traceoptions tab in the Edit Global Settings window does not display the available flags (tracing parameters). As a workaround, use the CLI to view the available flags. [PR/475313: This issue has been resolved.]
The J-Web interface for EX4200 switches in a Virtual Chassis setup might display the following message when you request support information: “The configuration on the Switch is too large for JWEB to handle. Please use the CLI to manipulate the configuration.” [PR/511185: This issue has been resolved.]
In the J-Web interface, if RIP, BGP, OSPF, and DHCP are not configured, you cannot click the links Commit, Help, and Logout in the monitoring pages for RIP, BGP, OSPF, and DHCP because the message “Not configured” that appears on these pages masks the Commit, Help, and Logout links in the J-Web interface. [PR/528346: This issue has been resolved.]
In the J-Web interface, the MAC Learning Log table in the Ethernet Switching Monitor page (Monitor > Switching > Ethernet Switching) does not display any entries even though the show ethernet-switching mac-learning-log command output displays correct log entries. [PR/535200: This issue has been resolved.]
In the J-Web interface, if you attempt to configure TACACS+ server authentication (Configure > System Properties > User Management), you cannot use the password prompt "password"--you must use the prompt "Password". The CLI allows use of either prompt. [PR/540217: This issue has been resolved.]
On EX4500 switches and on EX4200-24F switches, the total number of ports displayed in the dashboard (Dashboard > Capacity Utilization > Total number of ports) in the J-Web interface increases every 2 seconds, each time an automatic refresh occurs. [PR/543913: This issue has been resolved.]
When you configure port mirroring in the J-Web interface, the aggregated Ethernet (ae) interface is not included in the selection list. [PR/546740: This issue has been resolved.]
In the J-Web interface, when you use an HTTPS connection in the Microsoft Internet Explorer browser, you cannot upload (Maintain > Config Management > Upload) or download (Maintain > Config Management > History > Configuration History) a configuration file. As a workaround, use an HTTP connection. [PR/551200: This issue has been resolved.]
Committing configurations when an SSL certificate is added to the switch from the CLI editor (Configure > CLI tools > CLI Editor) fails if you are using the Microsoft Internet Explorer browser . As a workaround, use the Mozilla Firefox browser to commit configurations. [PR/552629: This issue has been resolved.]

Layer 2 and Layer 3 Protocols

When an EX Series switch configured to strip private AS numbers from the AS path receives an advertisement with private AS prefixes, the switch removes the private AS and advertises back to the BGP peer from which it received the advertisement, thus creating a loop. [PR/501286: This issue has been resolved.]
If an EX8200 switch receives an IGMP packet of unknown type, the switch might flood the packet on all interfaces, including the ingress interface from which the packet was received. [PR/502248: This issue has been resolved.]

Management and RMON

On EX4200 switches, the LACP process (lacpd) creates core files when an SNMP MIB lookup is performed. [PR/533226: This issue has been resolved.]

Multicast

When multicast packets are transmitted from interfaces on which PIM is not enabled, VRRP might flap. [PR/520194: This issue has been resolved.]
PIM register messages might be received and sent with incorrect checksums. [PR/532928: This issue has been resolved.]
PIM join messages sent from an EX8208 switch to a Cisco RP using Auto-RP show the upstream neighbor as being the EX8208 switch itself and not the Cisco RP. [PR/557130: This issue has been resolved.]
Some multicast groups stop forwarding packets after an unused 8-port 10-Gigabit Ethernet line card is taken offline and removed from an EX8208 switch. [PR/560463: This issue has been resolved.]

Virtual Chassis

On an EX4200 Virtual Chassis, a large number of awk processes and defunct processes might be running. [PR/576621: This issue has been resolved.]
EX4200 Virtual Chassis members might not reboot and might create a Virtual Chassis control process (vccpd) core file. [PR/588466: This issue has been resolved.]