Specifications

Interfaces and Chassis
•
On EX9200 switches, in an MC-LAG scenario , a MAC address might incorrectly point
to an inter-chassis control link (ICL) after a MAC move from a single-home LAG to the
MC-LAG. PR1034347
Resolved Issues: Release 13.3R4
Dynamic Host Configuration Protocol (DHCP)
•
On an EX9200 switch acting as a DHCP relay agent, DHCP_ACK messages sent from
a DHCP server might not be forwarded to the client if the server identifier in the DHCP
packet is different from that in the DHCP relay agent’s binding table. PR994735
Multicast
•
On EX9200 switches that are configured in a multicast scenario with PIM enabled, an
(S,G) discard route might stop programming if the switch receives resolve requests
from an incorrect reverse-path-forwarding (RPF) interface. After this issue occurs, the
(S,G) state might not be updated when the switch receives multicast traffic from the
correct RPF interfaces, and multicast traffic might be dropped. PR1011098
Platform and Infrastructure
•
On EX9200 switches, the interface alias feature might not work as expected and
interfaces might go up and down after commit. PR981249
•
On an EX9200 switch, if the underlying Layer 2 interface of an IRB interface is changed
from access mode to trunk mode and bi-directional traffic is sent from an interface on
the same switch that has been changed from IRB over Layer 2 to Layer 3 mode, the
Layer 3 traffic toward the IRB interface might be dropped and PPE thread timeout
errors might be displayed. PR995845
15Copyright © 2015, Juniper Networks, Inc.
Resolved Issues