Bug #1996435 “service and flow status are down after successful ...” : Bugs : tap-as-a-service

Revision history for this message

Lajos Katona (lajos-katona) wrote on 2022-11-17 (last edit on 2022-11-17):

#1

Hi, taas works with OVS or sriov driver, if you use OVS the logs are in the ovs-agent log (in devstack it will be q-agt), the mirroring only works with tunneled networks, to list just a few things of what you can expect.

I started to write some in-depths documentation on how the mirroring works, that can also help to see if you see such bridges and flows on your host:
https://review.opendev.org/c/openstack/tap-as-a-service/+/828382

If you can give me more details and you still have issues I try to help you.
So please tell me which driver you use (OVS, sriov), logs of ovs-agent perhaps the most important

Revision history for this message

Ehsan Khodayarseresht (ehsankhodayar) wrote on 2022-11-17:

#2

Download full text (23.5 KiB)

Hi Lajos,

Thank you very much for your reply. In fact, I wanted to use Zeek on the monitoring Instance to capture the network traffic. But I couldn't solve this issue. Then, I understood that the network interfaces of instances are accessible through the host machine where OpenStack is installed. So, at the moment, I tried to capture those data through the host machine. However, I also like to solve this issue. My OpenStack version is based on DevStack Stable/Yoga, which I think it uses OVS because I saw its logs during the installation. I went to this directory: /var/log/openvswitch. Then there were multiple log files. I opened ovs-vswitchd.log, which is as follows:

I just remove the previous tap services and flows and added them again and copied these logs at the end.

Hi Lajos,

Thank you very much for your reply. In fact, I wanted to use Zeek on the monitoring Instance to capture the network traffic. But I couldn't solve this issue. Then, I understood that the network interfaces of instances are accessible through the host machine where OpenStack is installed. So, at the moment, I tried to capture those data through the host machine. However, I also like to solve this issue. My OpenStack version is based on DevStack Stable/Yoga, which I think it uses OVS because I saw its logs during the installation. I went to this directory: /var/log/openvswitch. Then there were multiple log files. I opened ovs-vswitchd.log, which is as follows:

I just remove the previous tap services and flows and added them again and copied these logs at the end.

I don't know why I have these interface errors because I have created two instances only; an Ubuntu VM as the mirror destination and a Cirros VM for monitoring its network traffic. Both of them are working fine.

Revision history for this message

Lajos Katona (lajos-katona) wrote on 2022-11-25:

#3

Hi, Could you please check if you have ovs-agent running? If I understand well you use devstack, so you should have a service <email address hidden> (check in systemctl).
Checking ovs-vswitchd.log is not necessary, and actually doesn't tell if you use Neutron with OVS backend or OVN.

Sorry for late reply, for some reason I still didnt' recevice notification mail for your comment, I have to check my settings. You can also find me on IRC on #openstack-neutron channel on oftc.net

Lajos Katona (lajos-katona) on 2023-09-11

Changed in tap-as-a-service:
status:	New → Incomplete

Revision history for this message

Launchpad Janitor (janitor) wrote on 2023-11-11:

#4

[Expired for tap-as-a-service because there has been no activity for 60 days.]

Changed in tap-as-a-service:
status:	Incomplete → Expired

tap-as-a-service

service and flow status are down after successful creation

Bug Description

Other bug subscribers

Remote bug watches