Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 

Limitations in Junos OS Release 12.3X50 for the QFX Series

This section lists the limitations in Junos OS Release 12.3 for the QFX Series.

Interfaces and Chassis

  • After you insert a QSFP+ transceiver in a QFX3500 device, the status LED does not light green for up to 15 seconds. There is no workaround.
  • On a QFX3500 switch, when both of the multichassis LAG (MC-LAG) links on both connected peers are down, the MAC addresses learned on the MC-LAG links should be removed from the MAC address table. However, if you issue the show ethernet-switching table operational command after all of the MC-LAG links go down, the MAC addresses learned on the MC-LAG still appear in the table and must age out before they are removed.
  • On a QFX3500 switch, multichassis LAG (MC-LAG) interfaces are not supported for the default VLAN. Interfaces that are members of the default VLAN cannot be included in an MC-LAG interface.

Network Management and Monitoring

  • If a QFX3500 switch drops traffic because of an ingress firewall filter, the switch does not generate an sFlow monitoring technology flow sample packet that contains this dropped traffic.

Security

  • On a QFX3500 switch, if you enable multicast VLAN registration (MVR) and also apply a firewall filter to a VLAN (in either the input or output direction), the filter does not take effect.

Storage and Fibre Channel

  • Each Fibre Channel fabric on an FCoE-FC gateway supports a maximum of four Fibre Channel over Ethernet (FCoE) VLAN interfaces.
  • The maximum number of logins for each FCoE node (ENode) is a range of 32 to 2500. (Each ENode can log in to a particular fabric up to the maximum number of configured times. The maximum number of logins is per fabric, so an ENode can log in to more than one fabric and have its configured maximum number of logins on each fabric.)
  • The maximum number of FCoE sessions for the switch, which equals the total number of fabric login (FLOGI) sessions plus the total number of fabric discovery (FDISC) sessions, is 2500.
  • The maximum number of FIP snooping sessions per QFX3500 switch is 2500.
  • When you configure FIP snooping filters, if the filters consume more space than is available in the ternary content-addressable memory (TCAM), the configuration commit operation succeeds even though the filters are not actually implemented in the configuration. Because the commit operation checks syntax but does not check available resources, it appears as if the FIP snooping filters are configured, but they are not. The only indication of this issue is that the switch generates a system log message that the TCAM is full. You must check the system log to find out if a TCAM full message has been logged if you suspect that the filters have not been implemented.
  • You cannot use a fixed classifier to map FCoE traffic to an Ethernet interface. The FCoE application type, length, and value (TLV) carries the FCoE priority-based flow control (PFC) information when you use an explicit IEEE 802.1p classifier to map FCoE traffic to an Ethernet interface. You cannot use a fixed classifier to map FCoE traffic to an Ethernet interface because untagged traffic is classified in the FCoE forwarding class, but FCoE traffic must have a priority tag (FCoE traffic cannot be untagged).

    For example, the following behavior aggregate classifier configuration is supported:

    [edit class-of-service]
    user@switch# set congestion notification profile fcoe-cnp input ieee-802.1 code-point 011 pfc
    user@switch# set interfaces xe-0/0/24 unit 0 classifiers ieee-802.1 fcoe

    For example, the following fixed classifier configuration is not supported:

    [edit class-of-service]
    user@switch# set interfaces xe-0/0/24 unit 0 forwarding-class fcoe

  • On a QFX Series device, a DCBX interoperability issue between 10-Gigabit Ethernet interfaces on QFX Series devices and 10-Gigabit Ethernet interfaces on another vendor’s devices can prevent the two interfaces from performing DCBX negotiation successfully in the following scenario:
    1. On a QFX Series 10-Gigabit Ethernet interface, LLDP is running, but DCBX is disabled.
    2. On another vendor’s device 10-Gigabit Ethernet interface, both LLDP and DCBX are running, but the interface is administratively down.
    3. When you bring another vendor’s 10-Gigabit Ethernet interface up by issuing the no shutdown command, the device sends DCBX 1.01 (CEE) TLVs, but receives no acknowledge (ACK) message from the QFX Series device, because DCBX is not enabled on the QFX Series device. After a few tries, another vendor’s device sends DCBX 1.00 (CIN) TLVs, and again receive no ACK messages from the QFX Series device.
    4. Enable DCBX on the QFX Series 10-Gigabit Ethernet interface. The interface sends DCBX 1.01 (CEE) TLVs, but the other vendor’s device ignores them and replies with DCBX 1.00 (CIN) TLVs. The other vendor’s device does not attempt to send or acknowledge DCBX 1.01 TLVs, only DCBX 1.00 TLVs.

    In this case, the QFX Series device ignores the DCBX 1.00 (CIN) TLVs because the QFX Series does not support DCBX 1.00 (the QFX Series supports DCBX 1.01 and IEEE DCBX). The result is that the DCBX capabilities negotiation between the two interfaces fails.

Traffic Management

  • You cannot apply classifiers and rewrite rules to routed VLAN interfaces (RVIs) because the members of RVIs are VLANs, not interfaces. You can apply classifiers and rewrite rules to Layer 2 logical interfaces and Layer 3 physical interfaces that are members of VLANs that belong to RVIs.

Related Documentation

Modified: 2015-04-10