Dell N3200-ON Networking N-Series Switches User Guide version 6.8.0 - Page 1662

Flow Status and Statistics The OpenFlow Controller uses the OFPT_STATS_REQUEST message with the type OFPST_FLOW to request flow status and statistics. The switch supports all flow match criteria in the OFPT_STATS_REQUEST defined by the OpenFlow 1.0 standard. The switch supports packet and byte counters for the OpenFlow 1.0 Rule Table and the MAC Forwarding Table. The OFPT_STATS_REPLY message includes the flow match criteria and actions. OpenFlow 1.3 Flow Match Criteria and Actions The Policy ACL Flow Table supports wide, multi-field matching. Most fields can be wildcard matched, and relative priority must be specified in all flow entries. The Policy ACL Flow Table has actions to redirect packets to different destination groups. It can be used to output copies of packets (for example, ARP packets or BPDU frames) to the Controller. The Policy ACL Flow Table is organized into mutually exclusive logical subtables. Flow entries in the IPv6 logical tables match only packets that require matching on IPv6 header fields. The non-IPv6 logical table matches any packet that does not require matching on IPv6 header fields. Following the OpenFlow single-entry match semantics, since the Policy ACL Flow Table is considered a single table, a packet can match at most one rule in the entire table. Flow entries must conform to match field prerequisite requirements defined in the OpenFlow specification or in this document. In other words, if a prerequisite field is identified for a particular match field, it must be explicitly provided. For example, to match a TCP source port, the IP protocol must be 4 (TCP) and the EtherType must be 0x0800 (IPv4) or 0x86dd (IPv6). The default on table miss is to do nothing. The packet will be forwarded using the output or group in the action set, if any. If the action set does not have a group or output action the packet is dropped. 1662 OpenFlow