[ovs-discuss] Troubleshooting network issues with ovn without network namespaces
russell at ovn.org
Mon Sep 18 20:21:23 UTC 2017
On Fri, Sep 15, 2017 at 12:45 AM, Vikrant Aggarwal
<ervikrant06 at gmail.com> wrote:
> Hi Folks,
> With ovs as mechanism driver in neutron, I used network namespaces often to
> troubleshoot the network related issue especially with instances which are
> not having floating ip attached to them. It's easy to take ssh session to
> instances without floating ip from network namespace and then take the
> tcpdump at various hops to troubleshoot the issue.
> With ovn, hops are reduced as all decisions are made using openflows but
> it's difficult to troubleshoot the issue.
> Do we have any mechanism to take the ssh session to instance with only
> private ip in case of ovn and take tcpdump on logical switches and ports?
If you're using the latest Neutron integration (networking-ovn), we
now create namespaces for OpenStack metadata API integration. You can
use those namespaces like you did before.
The other option would be to manually create a Neutron port, and then
manually create an interface in a namespace for that Neutron port. I
can send instructions if needed ...
More information about the discuss