Resolved Issues in JUNOS Release 10.2 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

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: This issue has been resolved.]
On EX4200 switches, sometimes the DHCP server process (dhcpd) causes high CPU utilization. [PR/507241: This issue has been resolved.]

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.]
EX Series switches with 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.]

Firewall Filters

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.]
If you configure an ingress firewall filter with an interface interface-name match condition for a LAG interface, delete this firewall filter configuration, and add or delete a member interface from the LAG referred to in the firewall filter match condition, the forwarding (pfem) process might create a core file. When the pfem process is restarted, it works as expected. [PR/504273: This issue has been resolved.]

Infrastructure

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 issues has been resolved.]
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: This issue has been resolved.]
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.]
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: 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, when static hostname mapping is configured for IPv6 (system static-host-mapping ipv6-address), ping and traceroute commands with the source option do not work—the hostname does not resolve. [PR/505143: This issue has been resolved.]

J-Web Interface

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]
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.]
On EX3200 and EX4200 switches, JUNOS Software on the switch cannot be upgraded from JUNOS Releases 9.0 through 10.1 to JUNOS Release 10.2 using the J-Web interface, because the size of the JUNOS Release 10.2 software package exceeds the space allocated to /var/jail/tmp directory. As a workaround, use the CLI to upgrade to JUNOS Release 10.2. [PR/509073: This issue has been resolved.]

Interfaces

On EX8200 switches, when the chassis configuration is activated after the software has been upgraded to JUNOS Release 9.6R1 or 9.6R2, the backup Routing Engine might go down and come back up and create a core file. [PR/489029: 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, resulting in a loop. [PR/501286: This issue has been resolved.]

Resolved Issues in JUNOS Release 10.2 for EX Series Switches

Access Control and Port Security

Bridging, VLANs, and Spanning Trees

Firewall Filters

Infrastructure

J-Web Interface

Interfaces

Layer 2 and Layer 3 Protocols

Related Topics