Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Configuring Support for OpenFlow on EX9200 Switches

The following sections detail one method to configure EX9200 switches to support OpenFlow, using interfaces that participate solely in OpenFlow. For information about configuring hybrid interfaces, which concurrently support OpenFlow logical interfaces and non-OpenFlow logical interfaces, see Configuring OpenFlow Hybrid Interfaces on EX9200 Switches.

Before you begin configuring support for OpenFlow, ensure that the switch meets the following hardware and software requirements:

  • EX9200 switch running Junos OS Release 13.3 or a later release.

  • OpenFlow software package with a software package release that matches the Junos OS release running on the switch

  • TCP connection between the switch and an OpenFlow controller

  • Connection between the management interface of the switch and the management network, which is reachable from the controller IP address

Configuration tasks are described in detail in the following sections:

Configuring the OpenFlow Interfaces

To configure the OpenFlow interfaces:

  1. Specify the VLAN tagging to be used and configure the encapsulation type.
  2. Configure the logical interface and the protocol family.
  3. Configure the interface as a trunk interface and specify the VLAN members associated with OpenFlow.

Configuring the OpenFlow Protocol

To configure support for OpenFlow, create a virtual switch instance, and specify a switch name, containing a maximum of 60 characters. For the virtual switch instance, configure the OpenFlow controller information and the participating logical interfaces. Optionally, configure the default action for packets that do not have a matching flow entry, the purge timer for invalid flows, and any OpenFlow traceoptions.

To configure the OpenFlow protocol:

  1. Configure the OpenFlow controller IP address and TCP as the connection protocol.
  2. Specify the logical interfaces participating in OpenFlow under this virtual switch instance.
  3. (Optional) Configure the default-action statement for packets that do not match on an existing flow entry.

    If you do not configure the default-action statement, the default is packet-in, which indicates that packets that do not have a matching flow entry must be sent to the controller for processing.

  4. (Optional) Configure the purge-flow-timer statement, which is the number of seconds after which an invalid flow entry is purged from the flow table.
  5. (Optional) Configure OpenFlow traceoptions.

    If you do not configure a log filename, OpenFlow trace messages are logged in the default OpenFlow log file /var/log/ofd.

Configuring the OpenFlow Routing Instance

To configure the virtual switch routing instance for OpenFlow traffic:

  1. Configure the routing instance type as virtual-switch.
  2. Configure the OpenFlow logical interfaces that will be bound to the routing instance.
  3. Configure the OpenFlow VLAN members under the vlans hierarchy.
  4. (Optional) If you use the NORMAL forward action to forward OpenFlow traffic using traditional Layer 2 and Layer 3 processing, configure an integrated routing and bridging (IRB) interface, and bind the appropriate logical interface to the VLAN.