Exceptions; Acl Flow Exceptions; L3 Flow Exceptions - Dell Force10 Software Defined Networking Deployment Manual

Exceptions

This section describes the constraints of OpenFlow.
• Dell Force10 switches can operate as Hybrid switches (switches running OpenFlow and legacy functions
simultaneously). You cannot enable Legacy functionality (switching and routing) on OF ports or OF VLANs, as
these interfaces are controlled by an OpenFlow controller and are not available.
• Stacking OpenFlow switches is not supported for the S4810. If stacking is configured but disabled in preparation
for future stacking, the stack unit number must be zero to enable OpenFlow on S4810 switches.
• For OF ports and OF VLANs, the VLAN IDs used for OpenFlow must be unique; the VLAN IDs cannot be used for
legacy functionality on the same switch.
• Dell Force10 does not recommend using global spanning tree protocol (STP) instances on ports with both legacy
VLANs and OF VLANs.
• Transport Layer Security (TLS) connections are not supported.
• Because controllers typically run their own version of link layer discovery protocol (LLDP), legacy LLDP should
be disabled by the administrator on OF ports.
• To avoid session timeout issues if the system clock is changed, all existed OF instances should be disabled, then
re-enabled .
• Controller high availability (HA) is not supported.
• Emergency flows are not supported.
• Packet buffering is not supported.
• Data Center Bridging (DCB) and iSCSI are not supported on OpenFlow interfaces.
• The following packet types can only be copied to the controller and cannot be forwarded from a physical switch
port:
– STP BDPU
– LLDP
– GVRP
– ARP Replies
– 802.1x frames
– untagged broadcast packets received on an OF port

ACL Flow Exceptions

• Flooding (action "output=all" or "output=flood") is supported on S4810 only.
• By default, ACL flows override flows installed in the L2 or L3 tables.
• ARP opcode, sender IP, and target IP matching are not supported.

L3 Flow Exceptions

• Non-zero integers for the idle timeout are not supported and are ignored for L3 flows; L3 flows are not aged out.
• For L3 flows, flow priority is not applicable; instead, the dst-ip network mask length is used to prioritize the flow.
For example, a L3 flow with a dst-ip network mask length of 32 has priority over a flow with a dst-ip network
mask length of 31.
2
7