Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation  Back up to About Overview 

Resolved Issues in Junos OS Release 12.3X50 for the QFX Series

The following issues have been resolved in Junos OS Release 12.3X50 specified maintenance releases listed in this topic.

For the latest, most complete information about outstanding and resolved issues with the Junos OS software, see the Juniper Networks online software defect search application at http://www.juniper.net/prsearch .

Note: Some issues that apply to EX Series switches may apply to the QFX Series as well. If you are looking for a resolved issue but cannot locate it in this section, see the “Resolved Issues in Junos OS Release 12.3 for the EX Series” section in the Junos OS 12.3 Release Notes PDF Document.

Issues Resolved in Release 12.3X50-D45

The following issues have been resolved since Junos OS Release 12.3X50-D40. The identifier following each description is the tracking number in our bug database.

Interfaces

  • On QFX Series switches systems running Junos OS releases 12.3X50-D20 and later, when a DAC cable is connected to a 10-Gigabit Ethernet interface, this interface might transition down and up continuously. [PR/896037: This issue has been resolved.]
  • On a QFX Series switch, if a routed VLAN interface is configured with family ISO, the ISO maximum transmission unit (MTU) of the interface is reduced from 1500 (default) to 1497 bytes. Any transit ISO traffic larger than 1497 bytes might be sent to the CPU and cause latency issues. [PR/955710: This issue has been resolved.]
  • On a QFX Series switch running MSTP, a non-edge interface might be incorrectly marked as a boundary interface. [PR/996108: This issue has been resolved.]
  • On a QFX Series switch with a multichassis link aggregation group MC-LAG) and the init-delay-time statement configured, traffic might be dropped if you reboot the switch while a peer MC-LAG link is in down state. [PR/999855: This issue has been resolved.]

Layer 3 Protocols

  • If a QFX Series switch with per-packet load balancing enabled has multiple Equal Cost Multiple Paths (ECMP) next hops and these also have multiple ECMP next hops, ECMP entries might be installed twice if they have overlapping members. The duplicate entries result in those links carrying twice the traffic of the other links in the ECMP group. [PR/936707: This issue has been resolved.]
  • A BGP update containing a specifically crafted set of transitive attributes can cause corruption of memory and lead to an RPD routing process crash and restart. This issue affects only routers supporting 4-byte AS numbers connected to a BGP peer that does not support 4-byte AS numbers. [PR/953037: This issue has been resolved.]
  • DHCP unicast packets with a destination MAC address that is a VRRP MAC on a QFX Series switch might get dropped if the switch is acting as VRRP master. [PR/1022543: This issue has been resolved.]

Multicast Protocols

  • On a QFX3500 switch, when there are multiple sources and Layer 2 receivers in the source VLAN of a multicast group and there are no Layer 3 receivers for the group, if a Layer 2 receiver in the source VLAN sends an IGMP leave for that group, then the forwarding process might fail. [PR/999511: This issue has been resolved.]

Routing Protocols

  • On a QFX Series switch, the rpd scheduler might slip because of a memory allocation issue. This might occur when routing entries are updated. [PR/998911: This issue has been resolved.]

Security

  • During initialization on a QFX Series switch, the software programs dynamic filters for protocols such as BGP, LDP, and so on. The dynamic software-defined filters are required for sending special types of packets to the CPU or to change the CPU traffic queue, and the system-defined dynamic filters have a higher priority than the user-defined filters. Because user-defined filters have a lower priority, in some cases action in the dynamic system-defined filters is applied to that traffic instead of the action in the user-defined filters. (The traffic hits the dynamic system-defined filters before it hits the user-defined filters.) [PR/974616: This issue has been resolved.]
  • On a QFX Series switch with firewall filters configured, if a filter is configured with the match condition destination-port-range-optimize, traffic matching the term may be dropped even if the action is accept. [PR/1008624: This issue has been resolved.]

Software Installation and Upgrade

  • On a QFX Series switch, if the Uboot or jloader process fails, the switch might reboot and generate a misc hardware reason error message. To fix this issue and provide more details, new hardware failure codes have been added to assist customers and JTAC in diagnosing software reset and BIOS auto recovery conditions more precisely. [PR/978542: This issue has been resolved.]

Storage and Fibre Channel

  • On a QFX3500 switch, you can configure native Fibre Channel (FC) interfaces to add to an FC fabric (fc-fabric) using the interface-range opt ion. Previously, configuring a range of FC interfaces with the interface-range option resulted in a rejected configuration. The interface-range option provides the flexibility to add a member range of native FC interfaces to an fc-fabric configuration on the switch, instead of having to configure the FC interfaces individually. [PR/1012524: This issue has been resolved.]

Issues Resolved in Release 12.3X50-D40

The following issues have been resolved since Junos OS Release 12.3X50-D35. The identifier following each description is the tracking number in our bug database.

Interfaces

  • If you insert an SFP module in a management interface on a QFX switch while it is running a previous build of Junos OS 12.3X50—that is, if you hot swap the SFP module—the management interface might not work properly. [PR/888245: This issue has been resolved.]
  • If you configure family iso on a routed VLAN interface (RVI) of a QFX3500 or QFX3600 switch, the maximum transmission unit of the RVI might be reduced from the default 1500 bytes to 1497 bytes. If the RVI then receives packets larger than 1497 bytes, the traffic might be forwarded to the CPU, which can cause significant latency. [PR/955710: This issue has been resolved.]

Layer 3 Features

  • If you issue a show route resolution command on a QFX3500 or QFX3600 switch running a previous build of Junos OS 12.3X50 and the resulting output is very extensive, the routing protocol daemon (RPD) process might crash. [PR/861574: This issue has been resolved.]
  • If the Virtual Router Redundancy Protocol (VRRP) is enabled on an interface on a QFX switch running a previous build of Junos OS 12.3X50 and you deactivate and reactivate the interface, the IP address associated with the interface might disappear. If the interface also belongs to a routing instance, deactivating and reactivating the routing instance can also cause the IP address to disappear. [PR/912295: This issue has been resolved.]
  • If you create a large scale BGP configuration (for example, 50 BGP sessions with each session advertising more than 1000 routes) on a QFX Series switch running a previous build of Junos OS 12.3X50, the RPD scheduler might slip if you issue a show route command. [PR/928835: This issue has been resolved.]

Services

  • If you use DHCP or BOOTP relay on a QFX switch running a previous build of Junos OS 12.3X50 and you reload the configuration or add VLANs and commit a new configuration, DHCP or BOOTP relay might stop working. [PR/945574: This issue has been resolved.]

Issues Resolved in Release 12.3X50-D35

The following issues have been resolved since Junos OS Release 12.3X50-D30. The identifier following each description is the tracking number in our bug database.

Junos OS Basics

  • With the previous build of Junos OS 12.3 for the QFX3500 and QFX3600 switches (Junos OS 12.3X50-D30.2), the Zero Touch Provisioning feature can fail to properly commit configuration information on a platform. [PR/916531: This issue has been resolved.]
  • On a QFX3500 or QFX3600 switch running a previous build of Junos OS 12.3, a commit confirmed operation might fail. When this happens, the new configuration is committed even if you do not confirm it within the specified time limit—that is, a rollback does not occur even though it should. You might also see the error message commit confirmed failed during copy of rollback data. [PR/925512: This issue has been resolved.]

Layer 3 Features

  • On a QFX3500 or QFX3600 switch running a previous build of Junos OS 12.3, BGP multipath may use more ECMP groups than necessary if the import policy uses the policy action next-hop peer-address to set the route's protocol next hop. To work around this issue, use the policy action next-hop IP-address instead of the action next-hop peer-address. [PR/921938: This is is resolved.]
  • On a QFX3500 or QFX3600 switch running a previous build of Junos OS 12.3, a syslog message is not generated if the maximum number of ECMP table entries is reached. With Junos OS 12.3X50-D35, a syslog message is created if the maximum number of ECMP table entries is reached. [PR/922083: This issue has been resolved.]
  • On a QFX3500 or QFX3600 switch running a previous build of Junos OS 12.3, a problem can occur if a BGP route is resolved using a next hop that is learned from BGP and BGP ECMP is also used. In this circumstance, the route might be incorrectly programmed. [PR/922389: This issue has been resolved.]

Issue Resolved in Release 12.3X50-30

The following issue has been resolved since Junos OS Release 12.3X50-D20. The identifier following the description is the tracking number in our bug database.

Layer 3 Features

  • If a QFX3500 or QFX3600 switch running a previous release of Junos OS 12.3X50 has a multichassis link aggregation interface configured and is operating as a BGP transit switch, some BGP packets might be inappropriately dropped. This occurs because an implicit BGP filter that filters BGP packets intended for the CPU also discards packets that should be forwarded. [PR/863819: This issue has been resolved.]

Issues Resolved in Release 12.3X50-D20

The following issues have been resolved since Junos OS Release 12.3X50-D10. The identifier following each description is the tracking number in our bug database.

Interfaces and Chassis

  • On a QFX3500 switch, if you change an interface family from inet to ethernet-switching, DHCP discover messages received from DHCP clients connected to that interface are not forwarded. To work around this problem, delete the interface and re-create it with ethernet-switching as its family. [PR/809696: This issue has been resolved.]

Layer 2 Features

  • On a QFX3500 switch, if VLAN translation is enabled on an xle-0/2/x interface configured as a VLAN trunk, VLAN translation does not work correctly with egress VLAN traffic, and the traffic exits with incorrect VLAN tags. [PR/848313: This issue has been resolved.]

Network Management and Monitoring

  • On a QFX3500 switch, if you configure remote port mirroring with an IP address as the output, the mirrored packets might have the source MAC address 0x00deadbeef, and the source IP address might be the network address of the network that the egress interface is a member of. The correct addresses should be the MAC address and IP address of the interface that the GRE encapsulated mirrored packets exit from. [PR/828546: This issue has been resolved.]
  • On a QFX3500 switch, if you configure remote port mirroring with an IP address as the output, the identification field in the IP header is always set to 0 and the "do not fragment" bit in the flags field is not set. This means that fragmentation is allowed, and if the packet is fragmented, it cannot be reassembled properly. You should ensure that the path MTU of each network segment between the QFX3500 switch and the analyzer device is large enough so that fragmentation does not occur. [PR/829722: This issue has been resolved.]

Security

  • On QFX3500 and QFX3600 switches, policers applied to a loopback interface (to protect the Routing Engine) do not work properly. [PR/839453: This issue has been resolved.]
  • To apply a firewall filter to IGMP reports on a QFX3500 switch, you must configure this explicitly by including protocol igmp in a from term. [PR/844665: This issue has been resolved.]

System Administration

  • On a QFX3500 switch or QFX3600 switch, if both Dynamic Host Control Protocol (DHCP) and automatic software upgrade (Zero Touch Provisioning) are enabled, the QFX3500 switch or QFX3600 switch broadcasts a DHCP discover packet every  6 minutes. If a DHCP server on the network responds with a DHCP ACK packet with DHCP vendor options set with the necessary values to initiate an automatic software upgrade, then the automatic software upgrade proceeds.

    To disable broadcasting the DHCP discover packet every 6 minutes without performing an automatic software upgrade, manually delete the auto-image-upgrade statement located at the [edit chassis] hierarchy level. If an automatic software upgrade finishes without errors, the auto-image-upgrade statement is automatically deleted.

    You can monitor the status of an automatic software upgrade in progress by looking at the following log files:

    • /var/log/dhcp_logfile
    • /var/log/image_load_log

    [PR/834103: This issue has been resolved.]

Related Documentation

Modified: 2015-04-10

Previous Page Next Page