Limitations in JUNOS Release 10.2 for EX Series Switches

This section lists the limitations in JUNOS Release 10.2R1 for EX Series switches.

Access Control and Port Security

When you have configured more than 1024 supplicants on a single interface, 802.1X authentication might not work as expected and the 802.1X process (dot1xd) might fail.
The RADIUS request sent by an EX Series switch contains both Extensible Authentication Protocol (EAP) Identity Response and State attributes.
When an external RADIUS server goes offline and comes back online after some time, subsequent captive portal authentication requests might fail until the authd daemon is restarted. As a workaround, you can configure the revert interval—the time after which to revert to the primary server—and restart the authd daemon.

Bridging, VLANs, and Spanning Trees

On EX Series switches, configuring more than 64,000 MAC address clone routes in a single VLAN causes the Routing Engine to create core files and reboot.

Class of Service

On EX8200 switches, classification of packets using ingress firewall filter rules with forwarding-class and loss-priority configurations does not rewrite the DSCP or 802.1p bits. Rewriting of packets is determined by the forwarding-class and loss-priority values set in the DSCP classifier applied on the interface.
On EX4200 switches, the traffic is shaped at rates above 500 Kbps, even when the shaping rate configured is less than 500 Kbps. The minimum shaping rate is 500 Kbps.

Firewall Filters

On EX3200 and EX4200 switches, when interface ranges or VLAN ranges are used in configuring firewall filters, egress firewall filter rules take more than 5 minutes to install.
On EX3200 and EX4200 switches, IGMP packets are not matched by user-configured firewall filters.

Infrastructure

If you configure interface parameters on an EX3200 or EX4200 switch running JUNOS Release 9.2 or Release 9.3 for EX Series switches and then attempt to upgrade to a later release or a later version of Release 9.3 than the one that is currently installed, the switch might display the following error message: init: interface-control is thrashing , not restarted. As a workaround, on the interfaces you had previously configured, configure no-auto-negotiation and set the link mode to full-duplex, then commit the revised configuration.
On EX Series switches, an SNMP query fails when the SNMP index size of a table is greater than 128 bytes, because the Net SNMP tool does not support SNMP index sizes greater than 128 bytes.
On EX Series switches, the show snmp mib walk etherMIB does not display any output, even though the etherMIB is supported. This occurs because the values are not populated at the module level—they are populated at the table level only. You can issue show snmp mib walk dot3StatsTable, show snmp mib walk dot3PauseTable, and show snmp mib walk dot3ControlTable commands to display the output at the table level.
When you issue the request system power-off command, the switch halts instead of turning off power.
In the J-Web interface, the Ethernet Switching monitoring page might not display monitoring details if there are more than 13,000 MAC entries on the switch.
In the J-Web interface, changing the port role from Desktop, Desktop and Phone, or Layer 2 Uplink to another port role might not remove the configurations for enabling dynamic ARP inspection and DHCP snooping.
On EX8200 switches, if IS-IS is enabled on routed VLAN interfaces (RVIs), IS-IS adjacency states go down and come up after a graceful Routing Engine switchover (GRES).
Momentary loss of an inter-Routing Engine IPC message might trigger the alarm that displays the message Loss of communication with Backup RE. There is no functionality affected.

Interfaces

EX Series switches do not support queued packet counters. Therefore, the queued packet counter in the output of the show interfaces interface-name extensive command always displays a count of 0 and is never updated.

The following message might appear in the system log:

Resolve request came for an address matching on Wrong nh nh:355, type:Unicast...?

You can ignore this message.

On EX3200 and EX4200 switches, when port mirroring is configured on any interface, the mirrored packets leaving a tagged interface might contain an incorrect VLAN ID.
On EX8200 switches, port mirroring configuration on a Layer 3 interface with the output configured to a VLAN is not supported.
On EX8200 switches, when an egress VLAN that belongs to a routed VLAN interface (RVI) is configured as the input for a port mirroring analyzer, the analyzer incorrectly appends a dot1q (802.1Q) header to the mirrored packets or does not mirror any packets at all. As a workaround, configure a port mirroring analyzer with each port of the VLAN as egress input.
The following interface counters are not supported on routed VLAN interfaces (RVIs): local statistics, traffic statistics, and transit statistics.
EX Series switches do not support IPv6 interface statistics. Therefore, all values in the output of the show snmp mib walk ipv6IfStatsTable command always display a count of 0.
The show interfaces interface-name detail | extensive command might display double counting of packets or bytes for the transit statistics and traffic statistics counters. You can use the counter information displayed under the Physical interface section of the output.

Layer 2 and Layer 3 Protocols

On EX3200 and EX4200 switches, IPv6 ping is not supported for more than 64 virtual routing and forwarding (VRF) addresses.

Limitations in JUNOS Release 10.2 for EX Series Switches

Access Control and Port Security

Bridging, VLANs, and Spanning Trees

Class of Service

Firewall Filters

Infrastructure

Interfaces

Layer 2 and Layer 3 Protocols

Related Topics