close

keyboard_arrow_left

Table of Contents Expand all

play_arrow Overview
play_arrow OpenFlow Basic Configuration
play_arrow Configuring OpenFlow Hybrid Interfaces
play_arrow Configuring OpenFlow Traffic Steering Across MPLS Networks
- Understanding OpenFlow Traffic Steering Across MPLS Networks Using MPLS LSP Tunnel Cross-Connects
- Example: OpenFlow Traffic Steering Across MPLS Networks Using MPLS LSP Tunnel Cross-Connects
play_arrow Configuration Statements and Operational Commands
- OpenFlow Operational Mode Commands
- Junos CLI Reference Overview

list Table of Contents

English

Configuring OpenFlow Hybrid Interfaces on EX9200 Switches

date_range 22-Nov-23

arrow_backward

arrow_forward

On EX9200 switches that support OpenFlow, you can configure a physical interface as a hybrid interface that concurrently supports OpenFlow logical interfaces and non-OpenFlow logical interfaces. If you configure an OpenFlow hybrid interface on a device running Junos OS, you must enable the reception and transmission of 802.1Q VLAN-tagged frames on all interfaces, including both hybrid and non-hybrid interfaces, and you must configure a virtual switch routing instance for the OpenFlow traffic and a separate virtual switch routing instance for the normal traffic.

The following sections detail configuring an EX9200 switch that supports OpenFlow with a mix of hybrid and normal interfaces:

Configuring the Hybrid Physical Interface

To configure the hybrid physical interface:

Enable VLAN tagging.
Configure vlan-tagging to support 802.1Q VLAN single-tag frames for both OpenFlow and non-OpenFlow traffic, or configure flexible-vlan-tagging to support both 802.1Q VLAN single-tag and dual-tag frames.
```
[edit interfaces interface-name]
user@host# set (vlan-tagging | flexible-vlan-tagging)
```
Configure flexible Ethernet services encapsulation to enable multiple per-unit Ethernet encapsulations.
```
[edit interfaces interface-name]
user@host# set encapsulation flexible-ethernet-services
```

Configuring the Hybrid Interface Logical Units

On a hybrid interface, you configure an OpenFlow or non-OpenFlow logical interface as a Layer 2 trunk interface. Additionally, you can configure a non-OpenFlow logical interface as a Layer 3 subinterface that performs traditional Layer 3 forwarding. To configure a logical interface to receive and forward VLAN-tagged frames, you must bind a VLAN ID, or a range or list of VLAN IDs, to the logical interface. Configure Layer 2 interfaces using family ethernet-switching on EX9200 switches.

To configure the hybrid interface logical units:

Configure the OpenFlow logical interfaces and any non-OpenFlow Layer 2 logical interfaces, and specify the interface mode and VLAN membership.

content_copy zoom_out_map
[edit interfaces interface-name]
user@host# set unit unit family ethernet-switching interface-mode trunk
user@host# set unit unit family ethernet-switching vlan members vlan-ids

Configure any non-OpenFlow Layer 3 logical interfaces, and specify the VLAN membership.

content_copy zoom_out_map
[edit interfaces interface-name]
user@host# set unit unit (vlan-id | vlan-id-list | vlan-id-range) vlan-ids
user@host# set unit unit family inet address address

Configuring the Non-Hybrid Interfaces

Non-hybrid interfaces support either OpenFlow traffic or non-OpenFlow traffic, but not both simultaneously.

To configure the non-hybrid interfaces:

Configure interfaces that support only OpenFlow traffic as Layer 2 trunk interfaces, and specify the interface mode and VLAN membership.

content_copy zoom_out_map
[edit interfaces interface-name]
user@host# set vlan-tagging
user@host# set unit unit family ethernet-switching interface-mode trunk
user@host# set unit unit family ethernet-switching vlan members (vlan-id | vlan-id-list)

Configure interfaces that support only normal traffic, and specify the interface mode for the Layer 2 interfaces and the VLAN membership.

For example:

content_copy zoom_out_map
[edit interfaces interface-name]
user@host# set vlan-tagging
user@host# set unit unit family ethernet-switching interface-mode trunk
user@host# set unit unit family ethernet-switching vlan members (vlan-id | vlan-id-list)