Table of Contents
Advertisement
Limitations in Junos OS Release 10.4 for EX Series Switches
, the Bidirectional Forwarding Detection process (
) starts and
slot-number offline
bfd
stops repeatedly. The same
process behavior occurs on a line card that is connected
bfd
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.
If you install a large configuration (more than 5 MB)—for example, if you install more
than four 40-port SFP+ line cards—in an EX8200 switch, the error message
"Configuration on the Switch is too large for JWeb to handle. Please use the CLI to
manipulate the configuration" is displayed in the Support Information page (Maintain
> Customer Support > Support Information) in the J-Web interface.
If you perform a graceful Routing Engine switchover (GRES) on an EX Series switch
that has a large number (on the order of 1000 or more) of unresolved ARP entries, core
files are created on the backup Routing Engine.
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
. However, no
"Loss of communication with Backup RE"
functionality is affected.
If you perform graceful Routing Engine switchover (GRES) on an EX4200 or an 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
command.
clear ethernet-switching table
On EX4500 switches running IPv6, when you send a large number of pings to the switch
in quick succession, packet loss might occur because of low values configured for rate
limiting.
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.
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 is not supported on a Layer 3 interface
with the output configured to a VLAN.
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.
Copyright © 2011, Juniper Networks, Inc.
193
Advertisement
Table of Contents
