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 QFX5100 and EX4600 Switches

This topic describes how to configure QFX5100 and EX4600 switches with interfaces that participate solely in OpenFlow.

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

  • QFX5100 switch running Junos OS Release 14.1X53-D10 or later, or EX4600 switch running Junos OS Release 17.1R1 or later

  • OpenFlow software package with a 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 (em0 or em1) of the switch and the management network

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 the switches, you configure the interfaces with protocol family ethernet-switching. Also, you can configure only a single logical port by specifying logical unit number 0.

To configure the OpenFlow interfaces:

  • Configure the logical interface and protocol family.

Configuring the OpenFlow Protocol

To configure support for OpenFlow, you must create a virtual switch, and then, configure the connection with the OpenFlow controller and the logical interfaces participating in OpenFlow for the virtual switch. 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. Create an OpenFlow virtual switch, and specify a switch name, which can contain a maximum of 60 characters.
  2. Configure the OpenFlow controller IP address and the connection protocol.
  3. Specify the logical interfaces participating in OpenFlow under this virtual switch.
  4. (Optional) Configure the default-action statement for packets that do not match 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 are sent to the controller for processing.

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

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