Resolved Issues in JUNOS Release 10.1 for EX Series Switches

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

Access Control and Port Security

When both DHCP relay and DHCP snooping are configured on an EX2200 switch, the DHCP snooping database might not be built on the switch. [PR/480682: This issue has been resolved.]

Bridging, VLANs, and Spanning Trees

When Multiple VLAN Registration Protocol (MVRP) and MSTP are enabled together on EX Series switches, convergence does not occur between MVRP and MSTP. [PR/449248: This issue has been resolved.]
On EX4200 switches with the access interface through which traffic enters the switch configured as trusted (secure-access-port interface interface-name dhcp-trusted), VLAN Spanning Tree Protocol (VSTP) bridge protocol data units (BPDUs) are sent to the Routing Engine with the learning CPU code 37 instead of the reserved learning CPU code 306. [PR/468095: This issue has been resolved.]
On EX3200 and EX4200 switches with large VLAN configurations (more than 1024 VLANs), stale dynamic VLAN entries might be found in the Ethernet switching process (eswd) after you delete VLANs or deactivate the Multiple VLAN Registration Protocol (MVRP). [PR/471647: This issue has been resolved.]
On an EX2200 switch, when there is no spanning-tree protocol or redundant trunk group configured in the network and there is traffic looping, after the network loop is broken, sometimes MAC learning might not occur. As a workaround, restart the forwarding (pfem) process. [PR/473454: This issue has been resolved.]
When MVRP and VSTP are enabled together on EX Series switches, convergence does not occur between MVRP and VSTP. [PR/477019: This issue has been resolved.]
On EX3200 and EX4200 switches, when MVRP dynamic VLAN creation is disabled, deregistration of VLANs on trunk interfaces does not occur even after the tag associated with the VLAN has been modified. [PR/479636: This issue has been resolved.]
On EX3200 and EX4200 switches, stale MVRP VLAN membership entries might be found on blocked interfaces even after MVRP has been deactivated on the peer switch. [PR/482126: This issue has been resolved.]

Class of Service

On an EX2200 switch, when a queue is oversubscribed and you modify a scheduler with the buffer-size exact option on it such that it reduces the allocated buffers on the queue, the queue can stop dequeueing packets. As a workaround, stop traffic going out on the port, and deactivate and reactivate class of service (CoS). You can also reboot the switch. [PR/481401: This issue has been resolved.]

Firewall Filters

The accept action and the log and syslog action modifiers in the firewall filter configuration might not work as expected for packets destined for the switch. [PR/406714: This issue has been resolved.]
On EX3200 and EX4200 switches, if you configure an egress firewall filter with the match condition source-address or destination-address on a VLAN and its routed VLAN interface (RVI), the firewall filter might not work properly. [PR/476626: This issue has been resolved.]
On an EX2200 switch when you add a syslog action modifier to the firewall filter, the forwarding (pfem) process might create a core file when the filter binding is changed from an egress VLAN to an ingress VLAN. [PR/495572: This issue has been resolved.]

Hardware

On 48-port SFP line cards used in EX8200 switches, do not install a transceiver in the first or last port on the bottom row (ports 1 and 47). Transceivers installed in these ports are difficult to remove. As a workaround, you can remove the transceiver by using a small flathead screwdriver or other tool to lift the lock on the transceiver. [PR/423694: This issue has been resolved.]

Infrastructure

On an EX2200 switch, if the following message is displayed when the switch is booting, the installed package might be corrupted:
mount_check: SHA1 (/packages/jkernel-ex-10.1-20090925.0) = f45dd191b053b608dafecc0ef3ea329c9f85693b !=5fe72546eed0c0cb83e6addc6709720f56e8b6da
As a workaround, reinstall the image from the loader prompt with the -- format option set. [PR/433663: This issue has been resolved.]
Though the interface-range configuration statement is not supported under the [edit groups] hierarchy, an error message might not be displayed when you use the interface-range statement. [PR/453538: This issue has been resolved.]
The DHCP snooping database is not built after graceful Routing Engine switchover (GRES) is performed twice. Even though packets are coming from the DHCP server, they are not inserted in the DHCP relay. [PR/461318: This issue has been resolved.]
If an interface is assigned to a VLAN before the interface's stg state is set, loops might form in the network if a VLAN ID is assigned to the VLAN while the interface is active in a redundant topology. [PR/472617: This issue has been resolved.]
On EX8200 switches, after a graceful Routing Engine switchover (GRES), you can navigate through the Maintenance menu in the LCD even after the Maintenance menu in the LCD has been disabled using the set chassis lcd maintenance-menu disable command. As a workaround, delete the LCD Maintenance menu configuration using the CLI on the new master switch, and then disable the LCD Maintenance menu using the set chassis lcd maintenance-menu disable command. [PR/473597: This issue has been resolved.]
In some rare cases, switch bootup fails when the JUNOS Software is loading. The message Device not ready displays because the NAND flash is not responding. Workaround: Power cycle the switch. [PR/482026: This issue has been resolved.]
The name of the ethernet-switching-options authentication-whitelist statement will be changed. The new name is correct in the documentation but is shown in the CLI as ethernet-switching-options white-list. [PR/487167: This issue has been resolved.]
A memory leak might be present in the pfem SPF database. As a workaround, you can restart the forwarding (pfem) process. [PR/493197: This issue has been resolved.]

J-Web Interface

In the J-Web interface, the Edit MSTI window in the Spanning Tree Configuration page might not display details of an uncommitted interface configuration. [PR/433506: This issue has been resolved.]
In the J-Web interface, the menu on the left side of the J-Web pages and contents of the J-Web pages might disappear when you double-click the Troubleshoot tab. As a workaround, click the Dashboard tab or the Configure tab, and then click the Troubleshoot tab to display the menu and contents of the page. [PR/459936: This issue has been resolved]
In the J-Web interface, in the OSPF Configuration page, no flags are displayed for the Traceoptions tab in OSPF Global Settings. [PR/461558: This issue has been resolved.]
In the J-Web interface, in the BGP Configuration page (Configuration > Routing > BGP), if the values entered in the text boxes (for protocols, filename, and description) contain double quotation marks, the J-Web interface does not allow you to delete those values. If the value in the Group Name field contains double quotation marks, the J-Web interface allows you to delete the BGP group name, but the deleted value reappears when you refresh the BGP Configuration page. As a workaround, delete the values that contain double quotation marks using the CLI. [PR/464030: This issue has been resolved.]
When you access the J-Web interface using the Mozilla Firefox Web browser and move a J-Web window (for example, the Add Interface window) over the browser toolbars, the window appears behind the browser toolbars. After this problem occurs, the window cannot be moved, because the title bar of the window is not visible. If you cancel and reopen the window, the window continues to appear behind the browser toolbars. [PR/473238: This issue has been resolved.]
In the J-Web interface Static Routing Configuration page, you might not be able to delete a configured next-hop address because the Delete button is disabled. [PR/476572: This issue has been resolved.]
In the J-Web interface, the OSPF Monitoring page might display an error message if there are multiple interfaces or neighbors detected in an autonomous system. [PR/502132: This issue has been resolved.]

Resolved Issues in JUNOS Release 10.1 for EX Series Switches

Access Control and Port Security

Bridging, VLANs, and Spanning Trees

Class of Service

Firewall Filters

Hardware

Infrastructure

J-Web Interface

Related Topics