Configuring OpenFlow Hybrid Interfaces on MX Series Routers
On MX Series routers 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 MX Series router that supports OpenFlow with a mix of hybrid and normal interfaces:
Configuring the Hybrid Physical Interface
To configure the hybrid physical interface:
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 or MPLS-based 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 bridge
on MX Series routers.
To configure the hybrid interface logical units:
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:
Configuring OpenFlow
To configure the OpenFlow virtual switch instance:
Configuring the Virtual Switch Routing Instances
Configure separate virtual switch routing instances for the OpenFlow traffic and the non-OpenFlow traffic. The configured interface names must include a logical unit number.
To configure the virtual switch routing instances: