Outstanding Issues in JUNOS Release 10.2 for EX Series Switches

The following are outstanding issues in JUNOS Release 10.2R1 for EX Series switches. The identifier following the description is the tracking number in our bug database.

Access Control and Port Security

On EX Series switches, when you enable and disable IPv6 on the management interface (me0), the management information is not displayed in the show lldp local-information command output. [PR/503955]
On EX4200 switches, the LLDP-MED Location ID contains incorrect Type, Length, and Value (TLV). [PR/521658]
On EX2200, EX3200, and EX4200 switches, deleting a static MAC address entry from the Ethernet switching table does not change the authentication status for the interface in the 802.1X table with MAC RADIUS, and the interface remains authenticated. [PR/523919]
On EX3200 and EX4200 switches with static MAC bypass of authentication configured, MAC address learning takes a few minutes after the MAC address table is cleared. [PR/524044]
On EX Series switches, you might experience traffic drops under certain network conditions, even though the user is authenticated. As a workaround, you may restart the dot1x-protocol. [PR/524675, 528691

Bridging, VLANs, and Spanning Trees

There might be traffic loss on VLANs learned through MVRP during GRES. After the GRES, there will not be any traffic loss. [PR/458303]
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]

Class of Service

On EX3200 and EX4200 switches, the show interface queue command output displays the count of transmitted packets and queued packets together under the field Queued instead of displaying the values under Queued and Transmitted fields. [PR/259525]
If you are configuring an interface as part of an aggregated Ethernet interface and also configuring CoS on that interface, do not commit both configurations using a single commit operation. Use separate commit operations to commit the two configurations. [PR/490542]

Hardware

On EX4500 switches, all interfaces might go down if you hot-remove an uplink module and hot-insert it in less than 10 seconds. As a workaround, after hot-removing the uplink module, wait for a minimum of 10 seconds before hot-inserting it. [PR/495351]
On EX4500 switches, when you hot-remove an SFP+ transceiver and hot-insert an SFP-T transciever in the same port, the following messages are logged in the system log at 30-second intervals:
```
link 1 SFP receive power low  warning set
link 1 SFP receive power low  warning cleared
```
These messages are harmless.
[PR/506962]

Infrastructure

On EX Series switches, MAC addresses not present in the forwarding database (FDB) because of hash collision are not removed from the Ethernet switching process (eswd). These MAC addresses do not age out of the Ethernet switching table even if traffic is stopped completely and are never relearned when traffic is sent to these MAC addresses, even when there is no hash collision. As a workaround, clear those MAC addresses from the Ethernet switching table. [PR/451431]
On EX Series switches, the static neighbor discovery protocol (NDP) entries for IPv6 addresses are cleared automatically after some time. [PR/453710]
On EX8200 switches, when IGMP snooping is enabled on an interface, the IPv6 multicast Layer 2 control frame is not forwarded to other interfaces in the same VLAN. [PR/456700]
On EX4200 switches with GRES enabled, when a backup member switch has a route to a destination whose egress member is on the backup member itself, packets generated on the backup member egress out of the switch. [PR/506119]
On EX Series switches, the clear interface statistics all command takes a long time to execute. [PR/509303]
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]
On EX8200 switches with a 10-gigabit uplink port, when the Routing Engine is switched over, the 10-Gigabit uplink port stops forwarding traffic in the egress direction. [PR/515011]
On EX4500 switches, the following message appears in the system log whenever the uplink modules are taken offline:
```
fpc0 539:Port-STG-Set failed(Invalid Params:-2)
```
[PR/521077]
On EX8200 switches, the output of an SNMP walk on jnxOperatingTemp and jnxFruTemp does not show the temperature for line cards. [PR/524112]
On EX4500 switches, the interface shutdown action for storm control configuration does not have any effect. [PR/526077]

Interfaces

On EX8200 switches, aggregated Ethernet interfaces might go down and come back up for a few minutes while the switch is updating many routes. [PR/416976]
On EX8200 switches, after enabling GRES. you might not be able to connect to the management interface on the backup Routing Engine using Telnet, and an existing Telnet session with the management interface on the backup Routing Engine might become inactive. [PR/520966]
On EX4500 switches, the show chassis lcd and show chassis led command outputs do not display the details of the uplink module ports and show all network ports as ge- interfaces even though some ports are 10-Gigabit Ethernet interfaces. [PR/521124]
On EX8200 switches, the following message is logged frequently in the /var/log/mastership file:
```
mcontrol_refresh_mastership: time 6
```
These messages are harmless.
[PR/522513]
On EX4500 switches, when traffic congestion occurs on the ingress side of a 1-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]

J-Web Interface

In the J-Web interface, you cannot commit some configuration changes in the Ports Configuration page and the VLAN Configuration page because of the following limitations for port mirroring ports and port mirroring VLANs:
- A port configured as the output port for an analyzer cannot be a member of any VLAN other than the default VLAN.
- A VLAN configured to receive analyzer output can be associated with only one port.
[PR/400814]
In the J-Web interface, uploading a software package to the switch might not work properly if you are using Internet Explorer version 7. [PR/424859]
If an SRE module, RE module, SF module, line card, or Virtual Chassis member is in offline mode, the J-Web interface might not update the dashboard image accordingly. [PR/431441]
In the J-Web interface, in the Port Security Configuration page, you are required to configure action when you configure MAC limit even though configuring an action value is not mandatory in the CLI. [PR/434836]
In the J-Web interface, interfaces configured with no-flow-control might be displayed in the Link Aggregation Configuration page. [PR/437410]
In the J-Web interface, in the OSPF Global Settings table in the OSPF Configuration page, the Global Information table in the BGP Configuration page, or the Add Interface window in the LACP Configuration page, if you try to change the position of columns using the drag-and-drop method, only the column header moves to the new position instead of the entire column. [PR/465030]
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]
When you have a large number of static routes configured and if you have navigated to pages other than page 1 in the Route Information table in the J-Web interface (Monitor > Routing > Route Information), changing the Route Table to query other routes refreshes the page but does not return to page 1. For example, if you run the query from page 3 and the new query returns very few results, the Results table continues to display page 3 and shows no results. To view the results, navigate to page 1 manually. [PR/476338]
In the J-Web interface, the dashboard does not display the uplink ports or uplink module ports when transceivers are not plugged into the ports. [PR/477549]
An IPv4 static route that has been configured using the CLI might not be displayed when you select the Configure > Routing > Static Routing option in the J-Web interface. [PR/483885]
On EX8200 switches, when a firewall filter is applied on the loopback (lo0) interface, the switch stops generating local ARP requests for transit traffic. As a workaround, you can do the following:
- Create firewall filters to block known unwanted traffic to the Routing Engine, and then accept all other traffic.
- Create firewall filters for specific hosts and all local subnets, and then discard all other traffic.
[PR/486443]
In the J-Web interface, when you use the point-and-click configuration editor to change configuration and if you have made configuration changes simultaneously using the CLI, committing the configuration from J-Web might fail. [PR/514771]
In the J-Web interface, no warnings are displayed when you have configuration changes that are not committed and when you upload and install software packages or reboot the switch. [PR/514853]
In the J-Web interface for EX4500 switches, port configuration pages, port security configuration pages, and firewall filter configuration pages display features that are not supported on EX4500 switches. [PR/525671]
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]

Layer 2 and Layer 3 Protocols

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]
On EX4200 switches, if you have configured MTU on a logical interface and the route information for an inactive route on the interface changes, traffic loss might occur for a few seconds. [PR/520448]

Virtual Chassis

On EX4200 switches, factory default configuration does not set the configuration required for pre-provisioning, causing the set system commit factory-settings reset-virtual-chassis-configuration command to be not available after the switch is reset to the factory default configuration. As a workaround, delete the junos.conf* files from the config directory and reset the switch to factory default configuration. [PR/506855]

Outstanding Issues in JUNOS Release 10.2 for EX Series Switches

Access Control and Port Security

Bridging, VLANs, and Spanning Trees

Class of Service

Hardware

Infrastructure

Interfaces

J-Web Interface

Layer 2 and Layer 3 Protocols

Virtual Chassis

Related Topics