■ 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]
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 jnxFirewallMIB 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]
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.
194 ■ Outstanding Issues in JUNOS Release 10.1 for EX Series Switches
JUNOS 10.1 Software Release Notes
To Next Page
Loading...
Need help?
General
