PicOS Support for OpenFlow 1.3
The following table contains OpenFlow 1.3 features supported by PicOS. For clarity, the feature names in this table are identical to the feature names found in OpenFlow Switch Specification Version 1.3.0.
Table 1 OpenFlow 1.3 Features Supported by PicOS
OpenFlow V1.3 Section # | Title | Features | Additional Feature Specification | R2.0OVS | R2.0XF TCAM | R2.1OVS | R2.1XF TCAM | R2.0 Limitation |
1 | Introduction | NA |
|
|
|
|
|
|
2 | Switch Components | Flow tables |
| Y | Y | Y | Y |
|
|
| Group table |
| Y | N | Y | Y | Select & fast Fail over are not supported |
3 | Glossary |
|
|
|
|
|
|
|
4 | OpenFlow Ports | See Section 4.3 - 4.5 |
| Y | Y | Y | Y |
|
4.1 | OpenFlow Ports | See Section 4.3 - 4.5 |
| Y | Y | Y | Y |
|
4.2 | Standard Ports | See Section 4.3 - 4.5 |
| Y | Y | Y | Y |
|
4.3 | Physical Ports | Ingress | OpenFlow packets are received on an ingress port, processed by the OpenFlow pipeline. The packet ingress port is a property of the packet throughout the OpenFlow pipeline and represents the OpenFlow port on which the packet was received into the OpenFlow switch | Y | Y | Y | Y |
|
|
| Output | The OpenFlow pipeline can decide to send the packet on an output port using the output action (see 5.9), which defines how the packets goes back to the network | Y | Y | Y | Y |
|
|
| Groups |
| Y | Y | Y | Y |
|
|
| Hardware interface |
| N | N | N | N |
|
|
| Virtual slicing of hardware interface |
| Y | Y | Y | Y |
|
4.4 | Logical Ports | Logical ports are switch defined ports that don't correspond directly to a hardware interface of the switch | Logical ports are higher level abstractions that may be defined in the switch using non-OpenFlow methods |
|
|
|
|
|
|
|
| LAG | Y | N | Y | Y |
|
|
|
| Tunnels | Y | N | Y | N |
|
|
|
| Loopback interface | N | N | N | N |
|
|
| Ingress |
| Y | Y | Y | Y |
|
|
| Output |
| Y | Y | Y | Y |
|
|
| Groups |
| Y |
| Y | Y |
|
|
| Map to various physical port |
| N | N | N | N |
|
|
| PACKET_IN reports logical port and its underlying physical port (GRE & LAG) |
| N | N | N | N | only logical port |
4.5 | Local Reserved Port | Ingress |
| N | N | N | N |
|
|
| Output |
| Y | Y | Y | Y |
|
|
| Groups |
| Y | N | Y | Y |
|
|
| ALL | Only as an output port | Y | Y | Y | Y |
|
|
| CONTROLLER | Represent the control channel with the OpenFlow controller | Y | Y | Y | Y |
|
|
| TABLE | Represent the start of the OpenFlow pipeline | Y | Y | Y | Y |
|
|
| IN_PORT | Used only as an output port, send the packet out its ingress port | N | N | N | N |
|
|
| ANY | Cannot be used as an ingress port nor as an output port | Y | Y | Y | Y |
|
|
| LOCAL | Represent the switch's local networking stack. Can be used as an ingress port or as an output port | Y | Y | Y | Y | Linux networking stack |
|
|
| The local port enables remote entities to interact with the switch via the OpenFlow network, rather than via a separate control network. it can be used to implement an in-band controller connection |
|
|
|
|
|
|
| NORMAL | Non-OpenFlow pipelineused only as an output port | N | N | N | Y |
|
|
| FLOOD | Flooding using the normal pipeline of the switch, used only as an output port | Y | Y | Y | Y |
|
|
|
| Packet out all standard ports | Y | Y | Y | Y |
|
|
|
|
Copyright © 2025 Pica8 Inc. All Rights Reserved.