Brocade Multi-Service IronWare Software Defined Networking (SDN) Configuration Guide (Supporting R05.6.00) User Manual
Page 17
Multi-Service IronWare SDN Configuration Guide
7
53-1003034-02
Overview of OpenFlow
1
•
Before you can disable OpenFlow globally on the device, you must disable OpenFlow on all
interfaces individually.
•
Spanning tree protocol and other Layer 2 or Layer 3 protocols are not supported on
OpenFlow-enabled ports.
•
Support up to three concurrent sessions with a maximum of two concurrent SSL sessions.
•
Up to 3000 configured flows are supported if all the flows are with a wildcard for the
incoming port.
•
Local and normal actions defined by the OpenFlow 1.0 protocol are not supported.
•
After a reboot, a delay of 16 seconds for Brocade NetIron CER and Brocade NetIron CES
devices, and 180 seconds for Brocade MLX Series and Brocade NetIron XMR devices is
added before any flows can be pushed. This is the default delay time to allow all modules
and ports to come up.
•
8x10GbE and 2x100GbE interface modules support all generic Ethertype value in L2
mode. All other interface modules support Ethertype 0x88CC (LLDP) only in L2 mode.
•
On OpenFlow-enabled ports, packets that do not match any flow entry are dropped by
default. Although the OpenFlow 1.0 protocol specifies sending such packets to the
controller as mandatory, the Brocade implementation adopted the latest behavior defined
in the OpenFlow 1.2 protocol, which specifies that such packets MAY be sent to the
controller or MAY be dropped by router configuration. The Brocade implementation
supports an option to send such packets to the controller. Refer to
.
In addition, the following restrictions apply:
Brocade NetIron CER and Brocade NetIron CES devices
•
Enabling ports for Layer 3 flows is not supported.
•
Either Source MAC address or Destination MAC address can be used as a matching rule. The
choice is a device-level configuration that you specify at the time of enabling OpenFlow on the
device.
•
Statistics are available only for up to 2048 flows on a first-come-first-served basis.
Brocade MLX Series and Brocade NetIron XMR devices
•
Even though modification of the source and destination MAC address fields of a packet is
supported, modification on a per-destination port basis for multi-destination flows is not
supported.
In other words, sending a packet to multiple ports and having the MAC addresses modified on
a per-destination port basis is not supported. However, sending a packet to multiple ports and
having the MAC addresses modified in the same way for all destination ports is supported.
Similar restriction applies to modifications of the DSCP field of packets.
•
Modification of VLAN tag (such as adding, removing, modifying, or modifying the PCP bits of a
tag) is supported on a per-destination port basis for tagged packets. A flow may specify
sending a copy of a packet to multiple destination ports and have each copy of the packet
tagged with a different VLAN ID.
At the same time, if the rule is to send a tagged packet to multiple outgoing ports with different
VLAN tags, and if the action for one of the outgoing ports is to send the packet as untagged,
the packet is still tagged with the VLAN ID of 0 on that port. For egress ports with the action
specifying modified VLAN tag, the specified VLAN tag itself is added.