Example: Configuring OpenFlow Hybrid Interfaces on EX9200 Switches

This example uses the following hardware and software components:

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

• An OpenFlow software package is installed on the switch, and the software package release matches the Junos OS release running on the switch.

• The switch has a TCP connection to an OpenFlow controller, which needs to access the data plane of the switch.

• The switch is connected to the management network through the fxp0 interface and is reachable from the controller IP address.

In this example, you configure an EX9200 switch with:

• One hybrid interface, xe-2/1/0

• One non-hybrid interface, xe-2/1/1, which handles OpenFlow traffic only

• One non-hybrid interface, xe-2/1/2, which handles non-OpenFlow traffic only

On the hybrid interface, logical interface xe-2/1/0.0 participates in OpenFlow, and logical interfaces xe-2/1/0.1 and xe-2/1/0.2 do not participate in OpenFlow.

When using hybrid interfaces, you use VLAN tagging to distinguish OpenFlow traffic from non-OpenFlow traffic. Thus, you must enable VLAN tagging on all interfaces, and traffic entering the interfaces must be VLAN-tagged. If you do not configure a native VLAN, untagged traffic entering a hybrid interface is dropped. In this example, you configure the hybrid interface by using flexible-vlan-tagging, which enables VLAN tagging and supports both 802.1Q VLAN single-tag and dual-tag frames for all traffic on the interface. You also configure the OpenFlow interface xe-2/1/1 and the non-OpenFlow interface xe-2/1/2 by using vlan-tagging, which enables VLAN tagging and supports only 802.1Q VLAN single-tag frames for all traffic on the interface.

You configure the hybrid interface encapsulation as flexible Ethernet services. Note that for interfaces with this type of encapsulation, all VLAN IDs are valid. VLAN IDs from 1 through 511 are no longer reserved for normal Ethernet VLANs. In this example, VLANs 100 through 200 are used for OpenFlow traffic, and VLANs 700 and 800 are used for non-OpenFlow traffic.

All logical interfaces except xe-2/1/0.2 are configured as Layer 2 trunk interfaces by using family ethernet-switching and interface mode trunk. Logical interfaces xe-2/1/0.0 and xe-2/1/1.0 participate in OpenFlow and receive and forward traffic with OpenFlow VLAN IDs 100 through 200. Logical interfaces xe-2/1/0.1 and xe-2/1/2.0 do not participate in OpenFlow and receive and forward traffic with non-OpenFlow VLAN ID 700.

Logical interface xe-2/1/0.2 is a subinterface with the IP address 198.51.100.10/24 and performs Layer 3 routing. This interface does not participate in OpenFlow and routes traffic with VLAN ID 800.

Table 1 summarizes the logical interfaces, traffic types, and associated VLAN IDs.

You configure the OpenFlow virtual switch and OpenFlow protocol statements at the [edit protocols openflow] hierarchy level. The virtual switch 100 connects to the OpenFlow controller over a TCP connection at the IP address 198.51.100.174. The virtual switch configuration must include all of the logical interfaces participating in OpenFlow, which includes xe-2/1/0.0 and xe-2/1/1.0.

An EX9200 switch requires a separate routing instance for a virtual switch. This routing instance isolates the OpenFlow traffic from the non-OpenFlow traffic. When using hybrid interfaces, you configure a virtual switch routing instance for the OpenFlow traffic and another virtual switch routing instance for non-OpenFlow traffic. In this example, you configure routing instance OF for the OpenFlow traffic and routing instance NON-OF for the non-OpenFlow traffic.

Routing instance OF includes the interfaces participating in OpenFlow—xe-2/1/0.0 and xe-2/1/1.0. Within this routing instance, you configure a VLAN to include OpenFlow VLANs 100 through 200. Routing instance NON-OF includes the Layer 2 interfaces that do not participate in OpenFlow—xe-2/1/0.1 and xe-2/1/2.0. Within this routing instance, you configure a VLAN to include the non-OpenFlow VLAN 700.

• CLI Quick Configuration
• Configuring the Interfaces
• Configuring OpenFlow
• Configuring the Virtual Switch Routing Instances
• Results

set interfaces xe-2/1/0 flexible-vlan-tagging
set interfaces xe-2/1/0 encapsulation flexible-ethernet-services
set interfaces xe-2/1/0 unit 0 family ethernet-switching interface-mode trunk
set interfaces xe-2/1/0 unit 0 family ethernet-switching vlan members 100-200
set interfacesxe-2/1/0 unit 1 family ethernet-switching interface-mode trunk
set interfaces xe-2/1/0 unit 1 family ethernet-switching vlan members 700
set interfaces xe-2/1/0 unit 2 vlan-id 800
set interfaces xe-2/1/0 unit 2 family inet address 198.51.100.10/24
set interfaces xe-2/1/1 vlan-tagging
set interfaces xe-2/1/1 unit 0 family ethernet-switching interface-mode trunk
set interfaces xe-2/1/1 unit 0 family ethernet-switching vlan members 200
set interfaces xe-2/1/2 vlan-tagging
set interfaces xe-2/1/2 unit 0 family ethernet-switching interface-mode trunk
set interfaces xe-2/1/2 unit 0 family ethernet-switching vlan members 700
set protocols openflow switch 100 controller address 198.51.100.174
set protocols openflow switch 100 controller protocol tcp port 6633
set protocols openflow switch 100 interfaces xe-2/1/0.0
set protocols openflow switch 100 interfaces xe-2/1/1.0
set routing-instances OF instance-type virtual-switch
set routing-instances OF interface xe-2/1/0.0
set routing-instances OF interface xe-2/1/1.0
set routing-instances OF vlans OF-vlan vlan-id-list 100-200
set routing-instances NON-OF instance-type virtual-switch
set routing-instances NON-OF interface xe-2/1/0.1
set routing-instances NON-OF interface xe-2/1/2.0
set routing-instances NON-OF vlans OF-vlan vlan-id-list 700

user@switch> show configuration interfaces
xe-2/1/0 {
    flexible-vlan-tagging;
     encapsulation flexible-ethernet-services;
    unit 0 {
        family ethernet-switching {
            interface-mode trunk; 
            vlan { 
                members 100-200; 
            }
        }
    }
    unit 1 { 
        family ethernet-switching { 
            interface-mode trunk; 
            vlan { 
                members 700; 
            }
        }
    }
     unit 2 {
        vlan-id 800; 
        family inet { 
            address 198.51.100.10/24;
        }
    }
}
xe-2/1/1 { 
    vlan-tagging; 
    unit 0 { 
        family ethernet-switching { 
            interface-mode trunk; 
            vlan { 
                 members 200; 
            }
        }
    }
}
xe-2/1/2 { 
    vlan-tagging; 
    unit 0 { 
        family ethernet-switching { 
            interface-mode trunk; 
            vlan { 
                 members 700; 
            }
        }
    }
}

user@switch> show configuration protocols openflow
switch 100 {
    interfaces {
        xe-2/1/0.0;
        xe-2/1/1.0;
    }
    controller {
        protocol tcp {
            port 6633;
        }
        address 198.51.100.174;
    }
}

user@switch> show configuration routing-instances
OF {
    instance-type virtual-switch;
    interface xe-2/1/0.0;
    interface xe-2/1/1.0;
    vlans {
        OF-vlan {
            vlan-id-list 100-200;
        }
    }
}
NON-OF {
    instance-type virtual-switch;
    interface xe-2/1/0.1;
    interface xe-2/1/2.0;
    vlans {
        NOF-vlan {
            vlan-id 700;
        }
    }
}

Confirm that the configuration is working properly.

• Verifying the OpenFlow Controller Connection
• Verifying the OpenFlow Interfaces

user@switch> show openflow controller
Openflowd controller information:
Controller socket: 11
Controller IP address: 198.51.100.174
Controller protocol: tcp
Controller port: 6633
Controller connection state: up
Number of connection attempt: 5
Controller role: equal

user@switch> show openflow interfaces
Switch name: 100
Interface Name: xe-2/1/0.0
Interface port number: 41500
Interface Hardware Address: 00:00:5E:00:53:cf
Interface speed: 10Gb Full-duplex
Interface Auto-Negotiation: Disabled
Interface media type: Fiber
Interface state: Up

Switch name: 100
Interface Name: xe-2/1/1.0
Interface port number: 41501
Interface Hardware Address: 00:00:5E:00:53:d0
Interface speed: 10Gb Full-duplex
Interface Auto-Negotiation: Disabled
Interface media type: Fiber
Interface state: Up