Hello All, I need help with the following use case of two bare metal nodes running OpenvSwitch on them and connected on a Layer 2 VLAN. I have OpenDaylight controller running on a remote VM. I'm attaching the topology below. [Description: Description: cid:image001.png@01CEC99F.FAB593F0] As you can see in the picture, I have OvS running directly on the bare metal node and not on any virtual machine/hypervisor. Both nodes are geographically distributed and are connected by a point to point VLAN 1751 through the physical interface eth2.1751
My goal: I would like to control the flows coming out of both nodes based on packet type and direct to Layer2 or Layer 3 VLAN accordingly. Current status: Installed OvS and created a OvS bridge br0 on both nodes and attached eth2.1751 physical port to the OvS bridge. I set the private ip address of eth2.1751 to OvS bridge on both nodes and added a route entry for br0. Set the ODL controller on the remote VM on both nodes and I can see that the controller detects both the OvS. Problem: I cannot ping both nodes when the controller is set since it is unable to detect the input interface of the bare metal nodes to direct the OpenvSwitch. Till now, OpenVswitch has been used most often in a virtual environment and can detect the virtual input ports and map it accordingly to the physical ports. But in my case, since I have OvS running on the physical host itself, I'm not sure how to handle this use case. Can you please suggest me if such a use case can be implemented using OpenvSwitch and OpenDaylight and provide some guidance. Thank you very much for your help. -Sripriya
<<inline: image001.png>>
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
