TechLibrary

Table of Contents

ContentIndex

[+] Expand All

[-] Collapse All

Download This Guide

This section lists the known issues in hardware and software in Junos OS Release 13.2R8 for the EX Series.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

On EX9200 switches, the system log message UI_OPEN_TIMEOUT: Timeout connecting to peer 'dhcp' might appear even though no DHCP features are configured. The operation of the switch is not affected, and you can ignore the message. PR895320

On EX9200 switches, after an upgrade using unified ISSU, multicast traffic might not exit from an MC-LAG interface even when snooping entries are present in the Routing Engine and the kernel. PR904987

On EX9200 switches, ARP messages might not get resolved for a host added to a port that has been configured for Q-in-Q tunneling. PR849728
On EX9200 switches, the routing process (rpd) might continuously generate core files while processing an (S,G) entry if that entry has been deleted. PR942561
On EX9200 switches, the show ethernet-switching table vlan-name vlan-name | display xml CLI command does not have the vlan-name attribute in the l2ng-l2ald-rtb-macdb XML tag. PR955910
On EX9200 switches, continuous fpc0 XMCHIP(0): MALLOC error messages might appear in the logs. If not seen in large numbers, these messages can be ignored. PR958661
On EX9200 switches, if a session is initiated with a peer that is not configured, and the peer AS is a member of a confederation, then an RPD core file is created. PR963565
On EX9200 switches, GENCFG: op 8 (COS BLOB) failed; err error messages might appear in the logs. These messages have no service impact. PR997946
On EX9200 switches, if the switch receives BFD control packets larger than the maximum supported packet size of 256 bytes, the BFD process (bfdd) might generate a core file. PR1004482
On EX9200 switches, recurring LMEM data errors might cause a chip wedge. PR1033660

On EX9200 switches, multicast traffic might stop forwarding for a few minutes after an MC-LAG peer comes up. As a workaround, configure another MC-AE interface under the same redundancy group without configuring init-delay-time. PR1003805
On EX9200 switches, after a LAG interface flap, flooding of known unicast traffic might occur. PR1020851

If you configure a large number of PIM source-specific multicast (SSM) groups on an EX9200 switch, the switch might experience periodic IPv6 traffic loss. As a workaround, configure the pim-join-prune-timeout value on the last-hop router (LHR) as 250 seconds. PR853586

On EX9200 switches, Layer 3 traffic over MC-LAG interfaces does not converge after the MC-LAG links flap because ARP entries do not point to the correct next hop. As a workaround, either allow the ARP entries to expire or issue the clear arp command to delete the ARP entries. Then the ARP entries will be relearned. PR901361

On EX9200 switches running the VLAN Spanning Tree Protocol (VSTP), incoming BPDUs might not be included in the output of the show spanning-tree statistics interface command. PR847405