Outstanding Issues in JUNOS Release 10.1 for EX Series Switches

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

Note: PRs 300576, 403842, 409934, 415569, 415748, 429589, 440611, 455670, and 488318, which were included in the earlier release notes as outstanding issues, have been removed, because these issues are not applicable to JUNOS Release 10.1R2 for EX Series switches.

Access Control and Port Security

If you configure the RADIUS server revert-interval interval option, the switch does not attempt to reconnect to the unreachable server after the revert interval has elapsed. [PR/304637]

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 EX2200 switches, CoS port-shaping can yield different shaping results on uplink ports than on normal network ports when the same shaping rate is used. [PR/453660]
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]

Firewall Filters

If an ingress firewall has been configured with a LAG interface match condition and you delete this firewall configuration, the forwarding (pfem) process might create a core file. When the pfem process is restarted, it works as expected. [PR/504273]

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 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]

The jnxFirewall MIB might not be populated in a firewall filter configuration. As a workaround, set up the following configuration to skip the firewall MIB:

user@switch# show snmp
view firewall_exclude {
    oid .1.3.6.1.4.1.2636.3.5 exclude;
    oid .1;
}
community public {
    view firewall_exclude;
    authorization read-only;
}

[PR/464061]

On EX2200 switches, the MIB OID ipv6Forwarding indicates that IPv6 is supported even though IPv6 is not supported. The value of the ipv6Forwarding.0 MIB object is 1. [PR/473128]
If you attempt to set the time zone to Europe/Berlin on a switch with dual Routing Engines, the commit command might fail. [PR/483273]

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]

J-Web Interface

In the J-Web interface, you cannot commit some configuration changes in the Ports Configuration page and 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, 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 when transceivers are not plugged into the ports. [PR/477549]
An IPv4 static route configured using the CLI might not be displayed when you select Configure -> Routing-> Static Routing in the J-Web interface. [PR/487597]