This document  contains OpenFlow 1.3.0 features supported by the Pica8 PicOS software. For clarity, the feature names in this table are identical to the feature names found in OpenFlow Switch Specification Version 1.3.0.

OpenFlow Messages

Each OpenFlow message begins with the OpenFlow header. The OpenFlow header has several fields, including the type field. The type field identifies the type of OpenFlow message.

The OpenFlow protocol has three message types: symmetric, controller-to-switch, asynchronous. Each message type has multiple sub-types.

Symmetric Messages

Symmetric messages are unsolicited messages that may be initiated by either the switch or the controller. Symmetric messages are sent without explicit solicitation, in either direction. The following table describes PicOS support for symmetric messages:

Table 1   PicOS Support for OpenFlow Symmetric Messages

Controller-to-Switch Messages

Controller-to-switch messages are sent from the controller to the switch. These messages are used to directly manage the state of a switch. Controller-to-switch messages may or may not require a response from the switch.

The following table describes PicOS support for controller-to-switch messages:

Table 2   PicOS Support for OpenFlow Controller-to-Switch Messages

Asynchronous Messages 

Asynchronous messages are sent from the switch to the controller. These messages are used to communicate network events and switch state changes to the controller. Asynchronous messages are sent without a controller explicitly requesting them from a switch.

The following table describes PicOS support for asynchronous messages:

 Table 3   PicOS Support for OpenFlow Asynchronous Messages

Multipart Messages

The following table describes PicOS support for multipart messages: a single OpenFlow message cannot be larger than 64 kilobytes. Multipart messages are used to encode requests or replies that would carry a large amount of data, and would not always fit in a single OpenFlow message. The sender encodes the request or reply as a sequence of multipart messages, with a specific multipart type. The receiver re-assembles the request or reply.

Table 4   PicOS Support for OpenFlow Multipart Messages

Capabilities Supported by Datapath

The controller sends an OFPT_FEATURES_REQUEST message to the switch, once a session is established. The switch responds to the OFPT_FEATURES_REQUEST message with an OFPT_FEATURES_REPLY message. The OFPT_FEATURES_REPLY message has several fields, including the capabilities field. The capabilities field identifies the capabilities supported by the switch datapath.

The capabilties field is a combination of the following bits/flags:

Table 5   PicOS Support for OpenFlow Capabilities Supported by Datapath

OpenFlow Ports

OpenFlow ports are abstract network interfaces used for passing traffic between the OpenFlow switch and the rest of the network. An OpenFlow switch makes a number of OpenFlow ports available. The set of OpenFlow ports does not have to be identical to the set of physical network interfaces on the switch hardware.

Port Descriptions

The OpenFlow switch receives and sends packets on OpenFlow ports. The switch may define physical and logical ports, and the OpenFlow specification also defines some reserved ports.

Table 6   PicOS Support for OpenFlow Ports

Port Administrative Settings

The following table describes PicOS support for administrative settings of OpenFlow ports:

Table 7   PicOS Support for OpenFlow Port Administrative Settings

Port States

The following table describes PicOS support for OpenFlow port states:

Table 8   PicOS Support for OpenFlow Port States

Port Features

The following table describes PicOS support for OpenFlow port features available in the datapath:

 Table 9   PicOS Support for OpenFlow Port Features

OpenFlow Instructions

Each flow entry contains a set of instructions that are executed when a packets matches the entry. The following table details OpenFlow instructions supported by PicOS:

Table 10   PicOS Support for OpenFlow Instructions

OpenFlow Action Types

The following table details OpenFlow action types supported by PicOS:

Table 11   PicOS Support for OpenFlow Action Types

OpenFlow Match Fields

A match field may include the packet header, the ingress port, and the metadata value. A match field may use wildcards to match any value, and in some cases bitmasks. A packet is matched against a match field.

The following table details the OXM flow match field types supported by PicOS:

Table 12   PicOS Support for OpenFlow Flow Match Fields

OpenFlow Group Types

The following table describes PicOS support for OpenFlow group types:

Table 13   PicOS Support for OpenFlow Group Types