Users Guide

1702 OpenFlow
When using multiple hardware tables, it is possible to set up the hardware so
that, for example, the MAC Forwarding Table and OpenFlow 1.0 Rule Table
match the same packet. If the packet matches multiple slices in the IFP, the
hardware performs all non-conflicting actions on the packet. For example, the
OpenFlow 1.0 Rule Table may set the packet priority and the MAC
Forwarding Table may direct the packet to a specific output port.
If the packet actions conflict, the egress action is not predictable. The
controller-based applications should take care not to insert flow with
conflicting actions.
If the packet matches an IFP rule installed by a different component, such as
QoS. any conflicting actions are generally resolved in favor of the other
component. The IFP slices allocated to the OpenFlow component have the
lowest priority except for the system rules. The OpenFlow actions override
actions installed by the system rules.
Table 48-2. Flow Table Identifiers
ID Usage Description
0 User-Configured
table.
This table ID in the OFPT_FLOW_MOD
messages indicates that the rule should be added to
the default table configured by the administrator.
The standard OpenFlow 1.0 controllers always send
0 to the switch. Table 0 is not reported in the
OFPST_TABLE message.
1–3 Reserved Unused.
4 Source MAC VLAN
Assignment
This table is in the VLAN Field Processor.
5–23 Reserved Unused.
24 OpenFlow 1.0 Rule
Table
IFP table containing OpenFlow 1.0 rules.
25 MAC Forwarding
Table
IFP table containing multicast and unicast DA-
MAC-based forwarding rules.
26–31 Reserved Unused
32–255 Unsupported The enhanced OpenFlow 1.0 protocol only
supports table IDs 0 to 31.