Specifications

OpenFlow

•

OpenFlow v1.0 running on an EX9200 switch does not respond reliably to interface up

or down events within a specified time interval. Per a fix implemented in Junos OS

Release 13.3R3.6, OpenFlow v1.0 running on an EX9200 switch responds reliably to

interface up or down events if the echo interval timeout is set to 11 seconds or more.

PR989308

Platform and Infrastructure

•

On an EX9200 switch working as a DHCP server, when you delete an IRB interface or

change the VLAN ID of a VLAN corresponding to an IRB interface, the DHCP process

(jdhcpd) might create a core file after commit because a stale interface entry in the

jdhcpd database has been accessed. PR979565

Routing Protocols

•

On EX9200 switches with IGMP snooping enabled on an IRB interface, some transit

TCP packets might be treated as IGMP packets, causing packets to be dropped.

PR979671

Software Installation and Upgrade

•

When you are upgrading Junos OS on an EX9200 switch, the following warning message

might be displayed: Could not open requirements file for jroute-ex:

/etc/db/pkg/jroute-ex/+REQUIRE. You can ignore this message. PR924106

Spanning-Tree Protocols

•

On EX9200 switches, the MSTI identifier range for MSTP is limited to 1 through 64

while it should be 1 through 4094. PR846878

Resolved Issues: Release 13.3R2

Bridging and Learning

•

On EX9200 switches, trunk configuration [edit interface interface-name unit 0 family

ethernet-switching interface-mode trunk] might not work as expected, causing traffic

loss. PR963175

Dynamic Host Configuration Protocol

•

On an EX9200 switch that is configured for DHCP relay, with the switch acting as the

DHCP relay agent, the switch might not be able to relay broadcast DHCP inform packets,

which are used by the client to get more information from the DHCP server. PR946038

•

On EX9200 switches with Dynamic Host Configuration Protocol (DHCP) relay

configured, permanent Address Resolution Protocol (ARP) entries for relay clients are

installed. When the client is reachable by means of a different preferred path (due to

STP topology changes or MC-LAG changes and so on), the forwarding state is not

refreshed. This might cause packets to be dropped until the relay binding is cleared.

PR961479

Resolved Issues