Navigation  Back up to About Overview 
[+] Expand All
[-] Collapse All

No index entries found.

Outstanding Issues in Junos OS Release 12.3 for EX Series Switches

The following are outstanding issues in Junos OS Release 12.3R12 for EX Series switches. The identifier following the description is the tracking number in our bug database.

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

Note: Other software issues that are common to both EX Series switches and M, MX, and T Series routers are listed in Outstanding Issues in Junos OS Release 12.3 for M Series, MX Series, and T Series Routers.

Access Control and Port Security

  • On EX9200 switches, the LLDP database is not updated when you change the interface description or system name. [PR/848320]
  • On EX Series switches, if multiple source MAC addresses are flooded into a port on which MAC authentication is enabled, a dot1xd process core file might be created. [PR/1140634]

High Availability

  • On EX Series switches, there is no RPC equivalent for the CLI command show chassis nonstop-upgrade. [PR/872587]


  • On EX9200 switches, if you configure multichassis link aggregation (MC-LAG) in active-active mode and then one of the provider edge (PE) routers is rebooted, Layer 3 traffic might be lost for more than 10 seconds. This loss occurs because, by default, whenever a peer PE router is rebooted, the Link Aggregation Control Protocol (LACP) system ID on the other peer router changes.

    As a workaround, designate one of the PE routers to be status-control active using the following command on the PE router: set interfaces aex aggregated-ether-options mc-ae events iccp-peer-down prefer-status-control-active. As a result of issuing this command on the PE router, when a peer PE router goes down, the LACP system ID does not change.

    Note: To configure the prefer-status-control-active statement, you must configure the status-control active statement. Do not configure status-control as standby.


  • On EX Series switches, the wildcard range set interfaces interface-name unit logical-unit-number vlan-id-list [vlan-id, vlan-id-vlan-id] CLI command does not work. An error message is displayed on the console if you issue that command. As a workaround, configure the VLAN list by using expanded configuration commands. [PR/1030369]
  • On EX9200 switches, recurring LMEM data errors might cause a chip wedge. [PR/1033660]
  • On EX Series switches, fpc0 dfw_counter_get_by_name failed inst 0 policer index 0 status 7 error messages might appear in the log files when show firewall counter or snmp mib get jnxFirewallCounterTable is executed. [PR/1035113]
  • On EX Series switches, if you issue the show ethernet-switching table | display xml CLI command, the < l2ng-mac-entry> tag does not appear in the output. [PR/1097532]
  • On EX4550 Virtual Chassis, traffic might drop on a VCP even when the traffic rate is within the allocated bandwidth. [PR/1146961]


  • If you configure a VLAN range on an access interface of an EX9200 switch, the Layer 2 address learning process (l2ald) might fail. As a workaround, do not configure VLAN ranges on EX9200 switch access interfaces. [PR/837608]
  • If an EX4550-32F switch in a Virtual Chassis reboots and comes online, LACP interfaces on any member of the Virtual Chassis might go down and not come up. [PR/1035280]

J-Web Interface

  • In the J-Web interface on EX4200 switches, if you try to change the position of columns using the drag-and-drop method, only the column header moves to the new position instead of the entire column in the OSPF Global Settings table in the OSPF Configuration page, the Global Information table in the BGP Configuration page, or the Add Interface window in the LACP Configuration page. [PR/465030]
  • If you configure an IPv6 address for a VLAN in the J-Web interface, you cannot then edit the VLAN configuration. [PR/466633]
  • When a large number of static routes are configured and you have navigated to pages other than page 1 in the Route Information table in the Static Routing monitoring page in the J-Web interface (Monitor > Routing > Route Information), changing the Route Table to query other routes refreshes the page but does not return to page 1. For example, if you run a query from page 3 and the new query returns very few results, the Results table continues to display page 3 and shows no results. To view the results, navigate to page 1 manually. [PR/476338]
  • If you access the J-Web interface by using the Microsoft Internet Web browser version 7, on the BGP Configuration page (Configure > Routing > BGP), all flags might be shown in the Configured Flags list (in the Edit Global Settings window, on the Trace Options tab) even though the flags are not configured. As a workaround, use the Mozilla Firefox Web browser. [PR/603669]
  • On the process details page of the J-Web interface (Monitor > System View > Process Details), there are multiple entries listed for a few processes that do not impact any functionality. [PR/661704]
  • In the J-Web interface, the Next Hop column in the Static Routing page (Monitor > Routing > Route Information) displays only the interface address; the corresponding IP address is missing. The title of the first column displays Static Route Address instead of Destination Address. As a workaround, use the CLI to execute the show route detail command to fetch the corresponding next-hop interface IP address. [PR/684552]
  • In the J-Web interface, HTTPS access might work with an invalid certificate. As a workaround, after you change the certificate, issue the restart web-management command to restart the J-Web interface. [PR/700135]
  • On EX2200-C switches, if you have changed the media type and committed the change, the Ports configuration page (Configure > Interfaces > Ports) might not list the uplink port. [PR/742847]
  • On EX8200 Virtual Chassis, if you are using the Virtual Chassis Wizard in the J-Web interface in the Mozilla Firefox version 3.x browser, if you have selected more than six port pairs from the same member for conversion, the wizard might display the incorrect port conversion status. Also, if you double-click Next after deleting an active member in the Members page, the J-Web interface might stop working. [PR/796584]

Multicast Protocols

  • On EX9200 switches, the mcsnoopd process creates multiple core files at rt_nexthops_free during graceful Routing Engine switchover (GRES) with Layer 3 multicast traffic. [PR/848732]
  • On EX9200 switches, Layer 3 multicast traffic loss might occur for about 20 seconds on the switch when the switch is acting as the last-hop router (LHR) and the software performs a graceful Routing Engine switchover (GRES). [PR/848861]
  • 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) to 250 seconds. [PR/853586]

Network Management and Monitoring

  • EX Series switches do not notify users that a system log event has occurred. [PR/897200]

Routing Policy and Firewall Filters

  • On EX Series switches, if the switch receives BFD control packets larger than the maximum supported size of 256 bytes, the BFD process (bfdd) might generate a core file. [PR/1004482]

Software Upgrade and Installation

  • On EX8200 Virtual Chassis, when an NSSU is initiated to upgrade to Junos OS Release 12.3R5, multiple pfem core files might be created on some member switches. [PR/917863]

Virtual Chassis

  • On an EX9200 Virtual Chassis, with the Virtual Chassis member switches having multiple aggregated Ethernet (ae) interfaces configured for load balancing, if you reconfigure a Virtual Chassis port (VCP) as a network-traffic Ethernet port, you might see permanent traffic losses for Layer 3 traffic that transits the aggregated Ethernet interfaces. [PR/895058]

Related Documentation

Modified: 2016-06-09