It worked! I can ping from both sides. Thanks a lot, Alin! I really appreciate your guidance.
On Thu, Apr 20, 2023 at 5:21 PM Abu Rasheda <rcpilot2...@gmail.com> wrote: > I was able to change the name > > On Thu, Apr 20, 2023 at 4:35 PM Abu Rasheda <rcpilot2...@gmail.com> wrote: > >> PS C:\OVS-Compiled> Get-VMNetworkAdapterWithOVSPort left| grep ElementName >> ElementName : ovs-port-a >> PS C:\OVS-Compiled> Get-VMNetworkAdapterWithOVSPort right| grep >> ElementName >> ElementName : Dynamic Ethernet Switch Port >> >> >> On Thu, Apr 20, 2023 at 4:09 PM Alin Serdean <alinserd...@gmail.com> >> wrote: >> >>> You are correct. My memory was fuzzy around it. >>> >>> Can you please this function + vmname >>> >>> >>> https://github.com/openvswitch/ovs/blob/master/datapath-windows/misc/OVS.psm1#L120 >>> >>> This should give you the elementname. And that can be used inside ovs. >>> >>> There are also setters and getters in that cmdlet. >>> >>> Sent from phone >>> >>> On 21 Apr 2023, at 00:46, Abu Rasheda <rcpilot2...@gmail.com> wrote: >>> >>> >>> There is no column with ElementName. I am attaching the full output. I >>> probably missed something in the configuration. >>> >>> Thanks! >>> >>> On Thu, Apr 20, 2023 at 3:30 PM Alin Serdean <alinserd...@gmail.com> >>> wrote: >>> >>>> Can you provide the output of >>>> >>>> >>>> Get-VMNetworkAdapter left | fl >>>> >>>> >>>> Get-VMNetworkAdapter right | fl >>>> >>>> >>>> The above command will dump the whole object. >>>> I’m interested in looking at their ElementName >>>> >>>> That string will be used to match ports on the OVS side ( >>>> https://docs.openvswitch.org/en/latest/topics/windows/?highlight=Windows%20#port-management >>>> ) >>>> >>>> Sent from phone >>>> >>>> On 21 Apr 2023, at 00:15, Abu Rasheda <rcpilot2...@gmail.com> wrote: >>>> >>>> >>>> On Thu, Apr 20, 2023 at 6:17 AM Alin Serdean <alinserd...@gmail.com> >>>> wrote: >>>> >>>>> PS C:\OVS-Compiled> ovs-vsctl.exe show >>>>> ca9219b1-ceca-435e-b42a-b3e094237045 >>>>> Bridge br-int >>>>> Port ovs-port-a >>>>> Interface ovs-port-a >>>>> Port br-int >>>>> Interface br-int >>>>> type: internal >>>>> Bridge br-pif >>>>> Port NIC1 >>>>> Interface NIC1 >>>>> Port br-pif >>>>> Interface br-pif >>>>> type: internal >>>>> >>>> >>>> This is part of my confusion and likely the issue I am facing! >>>> >>>> In Linux, I can add ports of the VMs to the same bridge and traffic >>>> will flow between the VMs! >>>> >>>> However, in Windows, I don't know how to do this! >>>> >>>> PS C:\OVS-Compiled> Get-VMSwitch >>>> >>>> Name SwitchType NetAdapterInterfaceDescription >>>> ---- ---------- ------------------------------ >>>> OVS Extended Switch External Broadcom NetXtreme Gigabit Ethernet #2 >>>> >>>> Broadcom NetXtreme Gigabit Ethernet #2 is an alias for NIC1 >>>> >>>> PS C:\OVS-Compiled> Get-VMNetworkAdapter left >>>> >>>> Name IsManagementOs VMName SwitchName MacAddress >>>> Status IPAddresses >>>> ---- -------------- ------ ---------- ---------- >>>> ------ ----------- >>>> Network Adapter False left OVS Extended Switch 00155D727601 >>>> {Ok} {} >>>> >>>> >>>> PS C:\OVS-Compiled> Get-VMNetworkAdapter right >>>> >>>> Name IsManagementOs VMName SwitchName MacAddress >>>> Status IPAddresses >>>> ---- -------------- ------ ---------- ---------- >>>> ------ ----------- >>>> Network Adapter False right OVS Extended Switch 00155D727602 >>>> {Ok} {} >>>> >>>> >>>> So, I only have a choice to either connect the VM to "OVS Extended >>>> Switch" or not connect at all. >>>> >>>> I have one working NIC1 which Is associated to the OVS, the other NIC >>>> is not configured. >>>> >>>> What I am missing? >>>> >>>> Thanks for the support. >>>> >>>> >>>>> >>>>> From your config I’m not sure which adapter corresponds to which VM. >>>>> >>>>> Ca you please clarify the target and destination port you want to ping? >>>>> >>>>> Alin. >>>>> >>>>> Sent from phone >>>>> >>>>> On 20 Apr 2023, at 11:43, Abu Rasheda <rcpilot2...@gmail.com> wrote: >>>>> >>>>> >>>>> On Mon, Apr 17, 2023 at 1:44 PM Alin Serdean <alinserd...@gmail.com> >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> The issue you are facing might be because the name of the network >>>>>> adapters is the same. >>>>>> >>>>>> I wanted to emphasize the importance of the following step: >>>>>> https://docs.openvswitch.org/en/latest/intro/install/windows/#add-virtual-interfaces-vifs >>>>>> >>>>> >>>>> I followed your advice! I am able to add both Ubuntus to the bridge. >>>>> However, the ping does. not work. (The details are attached to this >>>>> email). >>>>> I think the issue is attaching the correct VM ports? Am I missing >>>>> something? >>>>> >>>>> Abu Rasheda >>>>> >>>>> This is something particularly important for Windows and not the same >>>>>> under other OS. >>>>>> >>>>>> Alin. >>>>>> >>>>>> Sent from phone >>>>>> >>>>>> On 17 Apr 2023, at 20:33, Abu Rasheda via discuss < >>>>>> ovs-discuss@openvswitch.org> wrote: >>>>>> >>>>>> >>>>>> Do you have any ideas, or if this is the wrong list, the >>>>>> recommendation for another one? >>>>>> >>>>>> On Thu, Apr 13, 2023 at 7:14 PM Abu Rasheda via discuss < >>>>>> ovs-discuss@openvswitch.org> wrote: >>>>>> >>>>>>> Hello! >>>>>>> >>>>>>> On Windows Server 2019, compiled, and loaded OVS kernel module. >>>>>>> Commands like ovs-vsctl & ovs-dpctl are running fine. >>>>>>> >>>>>>> I have two VMs (both running Ubuntu) under Hyper-V and have OVS >>>>>>> extended switch setup as described in >>>>>>> https://docs.openvswitch.org/en/latest/intro/install/windows/ >>>>>>> >>>>>>> I can connect one Ubuntu VM to the OVS switch, under the "Network >>>>>>> Adaptor" setting for the virtual machine. When I try to ping an IP >>>>>>> address get prints from the OVS datapath in the kernel! This led me >>>>>>> to >>>>>>> believe that OVS is installed and configured (I am from a Linux >>>>>>> background and Windows is new for me :)). >>>>>>> >>>>>>> However, when I try to add another Ubuntu VM to the OVS switch, I get >>>>>>> the following error: >>>>>>> >>>>>>> Synthetic Ethernet Port (Instance ID ..): Error '{Data Not Accepted} >>>>>>> The TDI client could not handle the data received during an >>>>>>> indication.' >>>>>>> >>>>>>> Failed to allocate resources while connecting to a virtual network. >>>>>>> The Ethernet switch may not exit. >>>>>>> >>>>>>> Can OVS Extended switch only connect to a single VM? (on the same >>>>>>> host), >>>>>>> >>>>>>> I can connect these two machines to Windows virtual switch and ping >>>>>>> them. So either my setup has issues for OVS or there is a limitation >>>>>>> on OVS. >>>>>>> _______________________________________________ >>>>>>> discuss mailing list >>>>>>> disc...@openvswitch.org >>>>>>> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss >>>>>>> >>>>>> _______________________________________________ >>>>>> discuss mailing list >>>>>> disc...@openvswitch.org >>>>>> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss >>>>>> >>>>>> <config.txt> >>>>> >>>>> <adaptor.txt> >>> >>>
_______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
