Membuat VLAN dalam OpenVSwitch - implementasi OpenFlow

Salah satu feature yang banyak dicari untuk memaksimalkan kemampuan suatu switch adalah kemampuan VLAN. OpenVSwitch memilikinya.

VLANs

Topic:

Isolating VM traffic using VLANs

Setup:

Two Physical Networks:

• Data Network:  Ethernet network for VM data traffic, which will carry VLAN tagged traffic between VMs.  Your physical switch(es) must be capable of forwarding VLAN tagged traffic and the physical switch ports should be VLAN trunks (Usually this is default behavior.  Configuring your physical switching hardware is beyond the scope of this document).
• Management Network: This network is not strictly required, but it is a simple way to give the physical host an IP address for remote access, since an IP address cannot be assigned directly to eth0.  
  

Two Physical Hosts:

Host1, Host2.  Both hosts are running Open vSwitch.  Each host has two NICs:

• eth0 is connected to the Data Network.  No IP address can be assigned on eth0.
• eth1 is connected to the Management Network (if necessary).   eth1 has an IP address that is used to reach the physical host for management.

Four VMs:

VM1,VM2 run on Host1.  VM3,VM4 run on Host2.

Each VM has a single interface that appears as a Linux device (e.g., “tap0″) on the physical host.  (Note: for Xen/XenServer, VM interfaces appears as Linux devices with names like “vif1.0″)

Goal:

Isolate VMs using VLANs on the Data Network.
VLAN 1: VM1,VM3
VLAN 2: VM2,VM4

Configuration:

Perform the following configuration on Host 1:

Create an OVS bridge:

ovs-vsctl add-br br0

Add eth0 to the bridge (by default, all OVS ports are VLAN trunks, so eth0 will pass all VLANs):

ovs-vsctl add-port br0 eth0

Add VM1 as an “access port” on VLAN 1:

ovs-vsctl add-port br0 tap0 tag=1

Add VM2 on VLAN 2:

ovs-vsctl add-port br0 tap1 tag=2

On Host 2, repeat the same configuration to setup a bridge with eth0 as a trunk:

ovs-vsctl add-br br0

ovs-vsctl add-port br0 eth0

Add VM3 to VLAN 1:

ovs-vsctl add-port br0 tap0 tag=1

Add VM4 to VLAN 2:

ovs-vsctl add-port br0 tap1 tag=2

Trouble-Shooting:

Ping from VM1 to VM3, this should succeed.

Ping from VM2 to VM4, this should succeed.

Ping from VM1/VM3 to VM2/VM4, this should not succeed (unless you have a router configured to forward between the VLANs, in which case, packets arriving at VM3 should have the source MAC address of the router, not of VM1).

If you have problems with this cookbook entry, please send them to the OVS discuss email list.

OpenVSwitch - salah satu implementasi OpenFlow

Salah satu implementasi OpenFlow, adalah OpenVSwitch.

What is Open vSwitch?

Open vSwitch is a production quality, multilayer virtual switch licensed under the open source Apache 2.0 license. It is designed to enable massive network automation through programmatic extension, while still supporting standard management interfaces and protocols (e.g. NetFlow, sFlow, SPAN, RSPAN, CLI, LACP, 802.1ag). In addition, it is designed to support distribution across multiple physical servers similar to VMware's vNetwork distributed vswitch or Cisco's Nexus 1000V. 

Features

Open vSwitch supports the following features:

• Visibility into inter-VM communication via NetFlow, sFlow(R), IPFIX, SPAN, RSPAN, and GRE-tunneled mirrors
• LACP (IEEE 802.1AX-2008)
• Standard 802.1Q VLAN model with trunking
• A subset of 802.1ag CCM link monitoring
• STP (IEEE 802.1D-1998)
• Fine-grained QoS control
• Support for HFSC qdisc
• Per VM interface traffic policing
• NIC bonding with source-MAC load balancing, active backup, and L4 hashing
• OpenFlow protocol support (including many extensions for virtualization)
• IPv6 support
• Multiple tunneling protocols (Ethernet over GRE, CAPWAP, IPsec, GRE over IPsec)
• Remote configuration protocol with local python bindings
• Compatibility layer for the Linux bridging code
• Kernel and user-space forwarding engine options
• Multi-table forwarding pipeline with flow-caching engine
• Forwarding layer abstraction to ease porting to new software and hardware platforms

Open vSwitch can operate both as a soft switch running within the hypervisor, and as the control stack for switching silicon. It has been ported to multiple virtualization platforms and switching chipsets. It is the default switch in XenServer 6.0, the Xen Cloud Platform and also supports Xen,KVM, Proxmox VE and VirtualBox. It has also been integrated into many virtual management systems includingOpenStack, openQRM, OpenNebulaand oVirt. The kernel datapath is distributed with Linux, and packages are available for Ubuntu, Debian, andFedora. The Open vSwitch release in development also supports FreeBSD.

The bulk of the code is written in platform-independent C and is easily ported to other environments.