From patchwork Wed Sep 23 15:40:33 2015 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Sorin Vinturis X-Patchwork-Id: 521753 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from archives.nicira.com (li376-54.members.linode.com [96.126.127.54]) by ozlabs.org (Postfix) with ESMTP id 10A05140180 for ; Thu, 24 Sep 2015 01:44:01 +1000 (AEST) Received: from archives.nicira.com (localhost [127.0.0.1]) by archives.nicira.com (Postfix) with ESMTP id 18BC5109AE; Wed, 23 Sep 2015 08:44:00 -0700 (PDT) X-Original-To: dev@openvswitch.org Delivered-To: dev@openvswitch.org Received: from mx3v1.cudamail.com (mx3.cudamail.com [64.34.241.5]) by archives.nicira.com (Postfix) with ESMTPS id 1FFAA101ED for ; Wed, 23 Sep 2015 08:43:59 -0700 (PDT) Received: from bar4.cudamail.com (bar2 [192.168.15.2]) by mx3v1.cudamail.com (Postfix) with ESMTP id 963ED6186F2 for ; Wed, 23 Sep 2015 09:43:58 -0600 (MDT) X-ASG-Debug-ID: 1443023034-03dc216fbc17ba0001-byXFYA Received: from mx3-pf3.cudamail.com ([192.168.14.3]) by bar4.cudamail.com with ESMTP id xjYRhBa7O8Gk8pnL (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 23 Sep 2015 09:43:54 -0600 (MDT) X-Barracuda-Envelope-From: svinturis@cloudbasesolutions.com X-Barracuda-RBL-Trusted-Forwarder: 192.168.14.3 Received: from unknown (HELO cbssmtp1.cloudbase.local) (91.232.152.5) by mx3-pf3.cudamail.com with SMTP; 23 Sep 2015 15:40:54 -0000 Received-SPF: pass (mx3-pf3.cudamail.com: SPF record at cloudbasesolutions.com designates 91.232.152.5 as permitted sender) X-Barracuda-Apparent-Source-IP: 91.232.152.5 X-Barracuda-RBL-IP: 91.232.152.5 Received: from localhost (localhost [127.0.0.1]) by cbssmtp1.cloudbase.local (Postfix) with ESMTP id A63F2425C5 for ; Wed, 23 Sep 2015 18:40:54 +0300 (EEST) X-Virus-Scanned: amavisd-new at cloudbasesolutions.com Received: from cbssmtp1.cloudbase.local ([127.0.0.1]) by localhost (cbssmtp1.cloudbase.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1E2mc6igGMMf for ; Wed, 23 Sep 2015 18:40:34 +0300 (EEST) Received: from CBSEX1.cloudbase.local (unknown [10.77.78.3]) by cbssmtp1.cloudbase.local (Postfix) with ESMTP id 31A964201D for ; Wed, 23 Sep 2015 18:40:34 +0300 (EEST) Received: from CBSEX1.cloudbase.local ([10.77.78.3]) by CBSEX1.cloudbase.local ([10.77.78.3]) with mapi id 14.03.0224.002; Wed, 23 Sep 2015 17:40:33 +0200 X-CudaMail-Envelope-Sender: svinturis@cloudbasesolutions.com From: Sorin Vinturis To: "dev@openvswitch.org" X-CudaMail-MID: CM-V3-922028859 X-CudaMail-DTE: 092315 X-CudaMail-Originating-IP: 91.232.152.5 Thread-Topic: [PATCH] datapath-windows: Updated documentation related to int/ext port names X-ASG-Orig-Subj: [##CM-V3-922028859##][PATCH] datapath-windows: Updated documentation related to int/ext port names Thread-Index: AQHQ9hYu4Sul9c92gkerc0feSc7NKA== Date: Wed, 23 Sep 2015 15:40:33 +0000 Message-ID: <1441170600-17773-1-git-send-email-svinturis@cloudbasesolutions.com> Accept-Language: en-US, it-IT Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.77.78.1] MIME-Version: 1.0 X-GBUdb-Analysis: 0, 91.232.152.5, Ugly c=0.291963 p=-0.529412 Source Normal X-MessageSniffer-Rules: 0-0-0-10074-c X-Barracuda-Connect: UNKNOWN[192.168.14.3] X-Barracuda-Start-Time: 1443023034 X-Barracuda-Encrypted: DHE-RSA-AES256-SHA X-Barracuda-URL: https://web.cudamail.com:443/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at cudamail.com X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.60 X-Barracuda-Spam-Status: No, SCORE=0.60 using per-user scores of TAG_LEVEL=3.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=3.0 tests=BSF_RULE7568M, RDNS_NONE X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.22823 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.50 BSF_RULE7568M Custom Rule 7568M 0.10 RDNS_NONE Delivered to trusted network by a host with no rDNS Subject: [ovs-dev] [PATCH] datapath-windows: Updated documentation related to int/ext port names X-BeenThere: dev@openvswitch.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@openvswitch.org Sender: "dev" Signed-off-by: Sorin Vinturis --- This patch is for both master and 2.4 branch. --- INSTALL.Windows.md | 52 +++++++++++++++++++++++++++------------------------- 1 file changed, 27 insertions(+), 25 deletions(-) diff --git a/INSTALL.Windows.md b/INSTALL.Windows.md index 889bb0b..132f76f 100644 --- a/INSTALL.Windows.md +++ b/INSTALL.Windows.md @@ -176,9 +176,9 @@ existing switch, make sure to enable the "Allow Management OS" option for VXLAN to work (covered later). The command to create a new switch named 'OVS-Extended-Switch' using a physical -NIC named 'Ethernet 1' is: +NIC named 'Ethernet0' is: % New-VMSwitch "OVS-Extended-Switch" -AllowManagementOS $true \ - -NetAdapterName "Ethernet 1" + -NetAdapterName "Ethernet0" Note: you can obtain the list of physical NICs on the host using 'Get-NetAdapter' command. @@ -263,21 +263,23 @@ ovs-vswitchd by running 'ovs-appctl exit'.) 07> Add the physical NIC and the internal port to br-pif. -In OVS for Hyper-V, we use 'external' as a special name to refer to the -physical NICs connected to the Hyper-V switch. An index is added to this -special name to refer to the particular physical NIC. Eg. 'external.1' refers -to the first physical NIC on the Hyper-V switch. +In OVS for Hyper-V, we use the physical NIC alias name to refer to the +physical NICs connected to the Hyper-V switch, i.e. 'Ethernet0'. Note: Currently, we assume that the Hyper-V switch on which OVS extension is enabled has a single physical NIC connected to it. -Interal port is the virtual adapter created on the Hyper-V switch using the +Internal port is the virtual adapter created on the Hyper-V switch using the 'AllowManagementOS' setting. This has already been setup while creating the -switch using the instructions above. In OVS for Hyper-V, we use a 'internal' -as a special name to refer to that adapter. +switch using the instructions above. In OVS for Hyper-V, we use the alias +name of the virtual NIC to refer to this adapter. The virtual NIC alias name +for a switch named 'OVS-Extended-Switch' is 'vEthernet (OVS-Extended-Switch)'. - % ovs-vsctl add-port br-pif external.1 - % ovs-vsctl add-port br-pif internal +Note: The alias name of all physical and virtual NICs on the host is displayed +using the 'Get-NetAdapter' command. + + % ovs-vsctl add-port br-pif "Ethernet0" + % ovs-vsctl add-port br-pif "vEthernet (OVS-Extended-Switch)" * Dumping the ports should show the additional ports that were just added. Sample output shows up as follows: @@ -286,22 +288,22 @@ as a special name to refer to that adapter. system@ovs-system: lookups: hit:0 missed:0 lost:0 flows: 0 - port 4: internal (internal) <<< 'AllowManagementOS' adapter on - Hyper-V switch + port 4: vEthernet (OVS-Extended-Switch) (internal) <<< 'AllowManagementOS' + adapter on Hyper-V switch port 2: br-pif (internal) port 1: br-int (internal - port 3: external.1 <<< Physical NIC + port 3: Ethernet0 <<< Physical NIC % ovs-vsctl show a56ec7b5-5b1f-49ec-a795-79f6eb63228b Bridge br-pif - Port internal - Interface internal Port br-pif Interface br-pif type: internal - Port "external.1" - Interface "external.1" + Port "Ethernet0" + Interface "Ethernet0" + Port "vEthernet (OVS-Extended-Switch)" + Interface "vEthernet (OVS-Extended-Switch)" Bridge br-int Port br-int Interface br-int @@ -342,19 +344,19 @@ with OVS extension enabled. system@ovs-system: lookups: hit:0 missed:0 lost:0 flows: 0 - port 4: internal (internal) + port 4: vEthernet (OVS-Extended-Switch) (internal) port 5: ovs-port-a port 2: br-pif (internal) port 1: br-int (internal - port 3: external.1 + port 3: Ethernet0 % ovs-vsctl show 4cd86499-74df-48bd-a64d-8d115b12a9f2 Bridge br-pif - Port internal - Interface internal - Port "external.1" - Interface "external.1" + Port "vEthernet (OVS-Extended-Switch)" + Interface "vEthernet (OVS-Extended-Switch)" + Port "Ethernet0" + Interface "Ethernet0" Port br-pif Interface br-pif type: internal @@ -391,7 +393,7 @@ Steps to add tunnels The Windows Open vSwitch implementation support VXLAN and STT tunnels. To add tunnels, the following steps serve as examples. -Note that, any patch ports created between br-int and br-pif MUST be beleted +Note that, any patch ports created between br-int and br-pif MUST be deleted prior to adding tunnels. 01> Add the tunnel port between 172.168.201.101 <-> 172.168.201.102