Flow validation, Flow action – Brocade Multi-Service IronWare Software Defined Networking (SDN) Configuration Guide (Supporting R05.6.00) User Manual
Page 28
18
Multi-Service IronWare SDN Configuration Guide
53-1003034-02
Configuring OpenFlow
1
You can specify Layer 2 or Layer 3 or both layers in hybrid mode as Layer23 matching mode to be
supported on the interface. By default, interfaces on these devices support Layer 2 matching
mode. If you enable Layer 2 matching mode on the specified interface, only Layer 2 matching fields
are supported on that interface.
Flow validation
These validations are required before programming flows on Layer23 port.
•
When IP fields exist in rule then ether_type must be 0x800.
•
IPv6 rules are not supported on Layer23 port. (But IPv6 ether_type without IPv6 parameters is
supported.)
Flow action
OpenFlow actions are not changed for Layer23 support. All actions currently supporting to Layer 2
or Layer 3 flows will continue to be supported. Actions currently supported are listed separately for
Brocade MLX Series and Brocade NetIron XMR devices, Brocade NetIron CER and Brocade NetIron
CES devices.
On Brocade MLX Series and Brocade NetIron XMR devices:
When a matching flow entry is found, a set of actions can be applied for processing the packet. The
system supports the following actions:
•
Forward to a port.
•
Forward to a set of ports.
•
Forward to a controller.
•
Forward a packet received from a controller to a port or set of ports.
•
Drop the packet.
•
Keep, add, modify or remove VLAN ID, VLAN priority. Modify VLAN ID per port is also supported,
i.e., each destination port can send a packet with a different VLAN ID for the same matching
rule.
•
Modify source MAC address and destination MAC address for both Layer 2 and Layer 3 IPv4
flows.
On Brocade NetIron CER and Brocade NetIron CES devices:
When a matching flow entry is found, a set of actions can be applied for processing the packet. The
system supports the following actions:
•
Forward to a port.
•
Forward to a set of ports.
•
Forward to a controller.
•
Forward a packet received from a controller to a port or set of ports.
•
Drop the packet.
•
Keep, add, modify or remove VLAN ID, VLAN priority. Modify VLAN ID per port is also supported,
i.e., each destination port can send a packet with a different VLAN ID for the same matching
rule.