Layer 2 And Layer 3 Protocols - Juniper JUNOS OS 10.4 - RELEASE NOTES REV 6 Release Note

Copyright © 2011, Juniper Networks, Inc.
On EX4500 switches, the J-Web interface might display the following as valid options
although these options are not supported on EX4500 switches:
DHCP snooping in the Edit Port Role window in the Ports Configuration page
Input filter association in the VLAN Configuration page
[PR/525671]
When you use an HTTPS connection in the Microsoft Internet Explorer browser to save
a report from the following pages in the J-Web interface, the error message "Internet
Explorer was not able to open the Internet site" is displayed:
Files page (Maintain > Files)
History page (Maintain > Config Management > History)
Port Troubleshooting page (Troubleshoot > Troubleshoot > Troubleshoot Port)
Static Routing page (Monitor > Routing > Route Information)
Support Information page (Maintain > Customer Support > Support Information)
View Events page (Monitor > Events and Alarms > View Events)
[PR/542887]
If you configure 802.1X on an EX Series switch, the J-Web interface performance slows
down. [PR/543298]
On EX4500 switches and on EX4200-24F switches, the total number of ports displayed
in the dashboard (Dashboard > Capacity Utilization > Total number of ports) in the
J-Web interface increases every 2 seconds, each time an automatic refresh occurs.
[PR/543913]
When you open a J-Web session using HTTPS, then enter a username and password
and click on the button, the J-Web interface takes 20 seconds longer to launch
Login
and load the Dashboard page than it does if you use HTTP. [PR/549934]
If you navigate to a new page before all the components of a page in the J-Web interface
are loaded, a pop-up window with the error message "Object Expected" is displayed.
[PR/567756]
In the J-Web interface, aggregated Ethernet interfaces are not populated in the Port
Association table. [PR/579555]

Layer 2 and Layer 3 Protocols

On EX8200 switches, if you take a line card offline when GRES and IGMP snooping are
enabled, existing multicast traffic might be affected because indexes are not updated
correctly. [PR/569637]
On an EX4200 Virtual Chassis, when you configure the RPM hardware timestamp with
the
hardware-timestamp
command displays the hardware timestamp status as "No hardware timestamps". As
a workaround, do not configure a source address for RPM probes. Packets are sent
Outstanding Issues in Junos OS Release 10.4 for EX Series Switches
configuration statement, the
show services rpm probe-results
205