Deployment Guide

17
4.3.2.1 Ingress Port Flow Table
The Ingress Port Flow Table is the first table in the pipeline and, by convention, is numbered zero. OpenFlow
uses a 32 bit value for ifNums. In this version of DNOS-OF, the high order 16 bits are zero for physical ports
since no other port types are supported in 1.0.
The Ingress Port Flow Table presents what is essentially a de-multiplexing logic function as an OpenFlow table
that can be programmed from the controller. By default, packets from physical ports with null (zero) Tunnel Id
metadata go to the VLAN Flow Table. Entries in this table must admit ingress packets by matching the ingress
ifNum exactly, by matching Tunnel Id, or by some combination.
Note: DNOS-OF may prevent certain types of rules from being added to other tables unless there is
appropriate flow entry in the Ingress Port Flow Table.
The default on miss is for packets from physical ports to go to the VLAN Flow Table. There is no default rule
for data center overlay tunnel packets from logical ports, which are dropped on miss.
4.3.2.1.1 Match Criteria, Instructions, Actions/Action List/Action Set, Counters, Flow Expiry
The Ingress Port Flow Table supports the flow entry types listed in Table 1. This table would typically have one
rule enabling ingress packets from each port type. However, since in this release, only the physical port type
is supported, only one rule is enabled.
Table 1: Ingress Port Flow Table Entry Types
Type
Description
Normal Ethernet
Frames
Matches packets from local physical ports, identified by zero Tunnel Id. Normal
Ethernet rules have Goto-Table instructions that specify the VLAN Flow Table.
Table 2: Ingress Port Flow table Match Fields
Field
Bits
Maskable
Optional
Description
IN_PORT
32
No
Yes
Ingress port. Depending on rule may be omitted to match any
IN_PORT.
Table 3: Ingress Port Flow Table Instructions
The Ingress Port Flow Table supports the single Goto-Table instruction listed in Table 3.
Name
Argument
Description
Goto-Table
Table
Next table. For this release, must be the VLAN
Flow Table.
Apply-Actions
Action list
Can contain at most one instance of each of
the actions listed in Table 3.1
The Ingress Port Flow Table actions can optionally set the packet VRF using an action list.
Table 4: Ingress Port Flow Table Action List
Name
Argument
Description
Set-Field
VRF
VRF for L3 lookups. Only applicable to Normal Ethernet Frame rules.
Optional.
Table 5: Ingress Port Flow Table Counters
Name
Type
Description
Active Entries,
Table
Reference count of number of active entries in the table
Duration
Per-entry
Seconds since this flow entry was installed