Users Guide

1694 OpenFlow
• OpenFlow 1.0 Actions
The switch supports single-port and multi-port forwarding actions as well
as some optional packet modifications actions.
Table 48-4 defines the supported and unsupported forwarding actions.
Table 48-4. Supported/Unsupported OpenFlow Forwarding Actions
Forwarding Action Description
Forward—
Physical Port
The switch can redirect traffic to one or more ports. A valid port
can be a physical port or a LAG. When redirecting traffic to
multiple ports, a combination of physical ports and LAGs can be
specified in the actions.
Forward—
CONTROLLER
Send packet to the OpenFlow controller. The "CONTROLLER"
reserved port can also be used with switch port numbers. The flow
must not include any packet modification actions.
Forward—ALL Not Supported.
This is a "Required" action for OpenFlow, however it is not
practical on a VLAN-enabled switch.
Forward—
LOCAL
Not Supported.
This is a "Required" action, but does not make sense on an
OpenFlow-Enabled switch. The packets are sent to the switch
CPU only when directed by its bridging our routing protocol
stack.
Forward—TABLE Not Applicable.
The action is defined only for packet-out messages.
Forward—
IN_PORT
Not Supported.
This is a "Required" action, but is not supported because this
action is too dangerous on switches in production network.