Users Guide

Table Of Contents
OpenFlow 1697
actions are automatically assumed to be OpenFlow ports, so the switch
disables ingress and egress filtering on those ports and allows the ports to
receive and transmit traffic for any VLAN. This change in the ingress and
egress filtering behavior may affect how the switch handles the non-
OpenFlow traffic on those ports.
2
The switch supports only one bridge instance.
3
In OpenFlow 1.0 mode, the switch supports several backup OpenFlow
controllers. The backup controllers can exchange hello messages with the
switch, but cannot add flows or monitor switch status. A vendor message is
defined to allow a backup controller become a primary controller. In the
OpenFlow 1.3 mode several OpenFlow controllers can manage the switch
at the same time.
4
In the OpenFlow 1.0 mode, the switch supports multiple hardware tables
to which flows are added. The switch advertises to the controller as having
multiple tables. The multi-table support in OpenFlow 1.0 is weak because
it does not allow the OpenFlow controller to specify the table to add the
flow to.
Dell EMC Networking
OpenFlow Hybrid extends the OpenFlow
1.0 protocol to specify the table number into which the flow is inserted by
using the most significant byte of the command field in the
OFPT_FLOW_MOD message. "OpenFlow 1.0 Supported Flow Match
Criteria, Actions and Status" on page 1698 defines which flows are added
to which hardware tables.
5
In OpenFlow 1.3 mode, the switch supports only one hardware table.
6
When operating in the OpenFlow 1.3 mode, the switch supports the group
table. See "Group Table" on page 1719 for more information.
7
The switch does not support the OpenFlow 1.0 emergency flow table.
8
The switch does not support forwarding packets in software. If a flow
cannot be added to the hardware, the switch generates an error message.
9
The switch does not support adding flow match criteria and forwarding
actions for ports that are not currently present in the system. However, if
ports are removed after the flow is installed, then the flow is updated with
the correct port forwarding rules. If the match port is not present on the
switch, the switch holds the flow in a software table and applies the flow to
the hardware when the port becomes available. If the port for a forwarding
action is not present on the switch, the switch adds the flow without the