Ethernet Switching; Firewall Filters; Infrastructure - Juniper JUNOS OS 10.4 - RELEASE NOTES Release Note

Copyright © 2010, Juniper Networks, Inc.

Ethernet Switching

If you perform graceful Routing Engine switchover (GRES) on an EX4200 or EX8200
switch, the Ethernet switching table might not refresh because the Packet Forwarding
Engine retains the forwarding database (FDB) entries. The result is that traffic is flooded
to the affected MAC addresses. As a workaround, refresh the Ethernet switching table
by issuing the clear ethernet-switching table

Firewall Filters

On EX4200 switches, if you configure a firewall filter with the match condition
, the error message "not supported" is displayed. There is no known
tcp-established
workaround. [PR/543316]
When you enable the
filter-id
of the required 802.1X authentication rules is not inserted in the IPv6 database. IPv6
traffic on the authenticated interface is not filtered; only IPv4 traffic is filtered on that
interface. [PR/560381]
On EX8200 switches and the XRE200 External Routing Engine, if you apply different
firewall filters to different VLANs, only the filter applied to the first VLAN is applied
correctly. For example, if you issue commands to apply filter f1 to VLAN1, filter f2 to
VLAN2, and filter f3 to VLAN3, filter f1 applies correctly, but filters f2 and f3 are not
applied to any VLANs. As a workaround, merge all the VLAN filters into one single filter
and apply that filter to all the VLANs. You can use the
firewall filter terms to differentiate the rules for each of the VLANs. [PR/568721]

Infrastructure

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.
The result is that IPv6 and VRRP for IPv6 neighbor solicitation fails. [PR/456700]
On EX3200 and EX4200 switches that are configured with the factory default
configuration, if you use the command
the date but display the following error message: "date: connect: Can't assign requested
address". [PR/499641]
On EX8200 switches, a temporary traffic loop occurs in the network after a graceful
Routing Engine switchover (GRES) or after a restart of the Ethernet switching process
( ). [PR/516611]
eswd
On EX8200 switches, if a
action in a firewall filter configuration, logging does not work. [PR/540097]
On EX8200 switches, the LACP process (
traffic to the Routing Engine is heavy. There is no known workaround. [PR/542897]
On EX8208 switches, when a line card that has no interface configurations and is not
connected to any device is taken offline using the command
, the Bidirectional Forwarding Detection process (
slot-number offline
stops repeatedly. The same
to a Layer 3 domain when another line card that is on the same switch and is connected
to a Layer 2 domain is taken offline. [PR/548225]
Outstanding Issues in Junos OS Release 10.4 for EX Series Switches
command.[PR/541311]
attribute on the RADIUS server for a particular client, one
to change the date, the switches accept
set date
or a action is configured along with an
log syslog
) might start and stop repeatedly when
lacpd
process behavior occurs on a line card that is connected
bfd
vlan match condition in the
interface
request chassis fpc-slot
) starts and
bfd
185