Users Guide

1688 OpenFlow
missing port and modifies the flow when the port becomes available. This
behavior can cause a flow to be added with no egress ports, which causes
packets matching the flow to be dropped.
10 When the switch loses connection to the OpenFlow controller it
continues to forward traffic using the flows previously programmed by the
controller. When the switch reconnects to the controller, it keeps using the
previously programmed flows until the OpenFlow controller tells it
otherwise.
11 At boot time, when the switch does not have any flows, it forwards traffic
normally using the Layer-2/Layer-3 forwarding rules.
12 The switch supports sending data packets to the controller. However, the
controller must explicitly install a flow to forward packets to the controller.
Packets that do not match any flow entries are forwarded normally using
the Layer-2 or Layer-3 logic.
13 The switch supports the ability for the controller to inject packets into the
network via the switch. This means that the controller can inject packets
into the network.
14 The switch supports only a limited set of flow match criteria and actions.
See "OpenFlow 1.0 Supported Flow Match Criteria, Actions and Status"
on page 1688.
15 The switch supports flows for physical ports and LAGs. These ports can be
used as destinations and match criteria. Status and statistics are reported
for these ports.
16 The switch supports eight CoS queues per physical port. Redirection to
queues is supported only for the OpenFlow 1.3 protocol. Queue status
reporting is supported.
17 The switch supports flow aging. The switch checks the flow install time
and idle time every 30 seconds. If either of the timers exceeds the
configured values for the flow, the switch deletes the flow. For hardware
tables that do not support flow statistics, the switch does not support the
idle timeout.
OpenFlow 1.0 Supported Flow Match Criteria, Actions and Status
The Dell EMC Networking OpenFlow Hybrid switch supports a limited set of
match criteria and actions. This section defines which match criteria and flow
actions are supported in each hardware table.