Resolved Issues in Junos OS Release 10.3 for EX Series Switches

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

Bridging, VLANs, and Spanning Trees

On EX Series switches, when the VLAN with the lowest-numbered VLAN ID is down, the show ntp associations command output displays the following message:
```
/usr/bin/ntpq: write to localhost failed: No route to host
```
[PR/466595: This issue has been resolved.]
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.]
On EX Series switches, having a large number of VSTP instances and RSTP instances might cause continuous changes in the topology. As a workaround, reduce the number of VSTP instances to fewer than 190. [PR/504719: This issue has been resolved.]

Infrastructure

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: This issue has been resolved.]
On EX8200 switches, the system log messages from the line cards display the timestamp in UTC, instead of the time zone specified in the CLI configuration. [PR/494892: This issue has been resolved.]
On EX Series switches, the /var directory appears full after some files in the /var/log directory are deleted. To avoid this problem, use the clear log filename command to clear the log files, instead of deleting them manually. [PR/496298: This issue has been resolved.]
On EX8200 switches, the show pfe statistics traffic multicast fpc fpc-slot dev-number command takes a long time to display output, and the output shows incorrect values. [PR/506031: This issue has been resolved.]

J-Web Interface

In the J-Web interface, the procedure of 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 Link Aggregation Configuration page. [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.]
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.]
On EX3200 and EX4200 switches, you might not be able to upgrade the switch to Junos OS Release 10.3 using the J-Web interface from a release prior to Junos OS Release 10.2. As a workaround, you can upgrade the switch using the CLI. [PR/509073: This issue has been resolved.]
The Configure PoE and Monitor PoE might not display on Microsoft Internet Explorer version 7. [PR/516048: This issue has been resolved.]
When are assigning interfaces to a VLAN using the inband management option, J-Web ezsetup might display only interfaces in which transceivers have been inserted. [PR/521632: This issue has been resolved.]
If RIP, BGP, OSPF, and DHCP are not configured on a switch, the “feature not configured” validation message masks the Commit, Help, and Logout menu options if you are using Mozilla Firefox. As a workaround, refresh the J-Web interface. [PR/528346: This issue has been resolved.]

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: This issue has been resolved.]

Resolved Issues in Junos OS Release 10.3 for EX Series Switches

Bridging, VLANs, and Spanning Trees

Infrastructure

J-Web Interface

Layer 2 and Layer 3 Protocols

Related Topics