@@ -263,21 +263,43 @@ 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 name of the adapter on top of which the
+Hyper-V virtual switch was created, as a special name to refer to the
+physical NICs connected to the Hyper-V switch. I.e. let us suppose we
+created the Hyper-V virtual switch on top of the adapter named
+'Ethernet0'. In OVS for Hyper-V, we use that name('Ethernet0') as a special name to refer to that adapter.
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 a the
+name of that specific adapter as a special name to refer to that
+adapter. By default it is created under the following rule "vEthernet (<name of the switch>)".
- % ovs-vsctl add-port br-pif external.1
- % ovs-vsctl add-port br-pif internal
+As a whole example, if we issue the following in a powershell console:
+PS C:\package\binaries> Get-NetAdapter | select
+Name,MacAddress,InterfaceDescription
+
+Name MacAddress InterfaceDescription
+---- ---------- --------------------
+Ethernet1 00-0C-29-94-05-65 Intel(R) PRO/1000 MT Network Connection
+vEthernet (external) 00-0C-29-94-05-5B Hyper-V Virtual Ethernet Adapter #2
+Ethernet0 00-0C-29-94-05-5B Intel(R) PRO/1000 MT Network Connection #2
+
+PS C:\package\binaries> Get-VMSwitch
+
+Name SwitchType NetAdapterInterfaceDescription
+---- ---------- ------------------------------
+external External Intel(R) PRO/1000 MT Network Connection #2
+
+
+We can see that we have a switch(external) created upon adapter name 'Ethernet0'
+with an internal port under name 'vEthernet (external)'. Thus resulting
+into the following ovs-vsctl commands
+
+ % ovs-vsctl add-port br-pif Ethernet0
+ % ovs-vsctl add-port br-pif "vEthernet (external)"
* Dumping the ports should show the additional ports that were just added.
Sample output shows up as follows:
@@ -286,22 +308,23 @@ 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