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 EX4550 Switches

The following sections configure EX4550 switches to support OpenFlow using interfaces that participate solely in OpenFlow.

Before configuring support for OpenFlow, ensure that the switch meets the following requirements:

  • EX4550 switch running Junos OS Release 13.2X51-D20 or a later release

  • OpenFlow software package with a software package release that matches the Junos OS release of the device on which it is installed

  • 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

You must configure interfaces participating in OpenFlow as Layer 2 interfaces. On EX Series Ethernet Switches, you configure the interfaces with protocol family ethernet-switching. On EX4550 switches, you can configure only a single logical port using logical unit number 0.

To configure the OpenFlow interfaces:

  • Configure the logical interface and the protocol family.

Configuring the OpenFlow Protocol

To configure support for OpenFlow, create a virtual switch instance, and specify a switch name, which must be 60 characters or less. 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 match a 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 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 with no 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 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 .