Ask Your Question

Revision history [back]

Use as comment :- When you ping 172.21.4.101. Run on compute node brctll show on compute node

brctl show

bridge name bridge id STP enabled interfaces qbr17d5d5af-34 8000.ded1f35d41b8 no qvb17d5d5af-34 qbre8837e97-91 8000.c23b488bacc1 no qvbe8837e97-91 tape8837e97-91 qbrfec6125b-76 8000.16f6bf558d0f no qvbfec6125b-76

Then run tcpdump -vv -i tape8837e97-91 && see would VM respond , then qvoe8837e97-91 from veth pair ( qvoe8837e97-91, qvbe8837e97-91), e.g. trace all devices on the way by tcpdump && locate point of failure.

Use as comment :- :-
When you ping 172.21.4.101. Run on compute node brctll show on compute node

# brctl show

show bridge name bridge id STP enabled interfaces qbr17d5d5af-34 8000.ded1f35d41b8 no qvb17d5d5af-34 qbre8837e97-91 8000.c23b488bacc1 no qvbe8837e97-91 tape8837e97-91 qbrfec6125b-76 8000.16f6bf558d0f no qvbfec6125b-76

qvbfec6125b-76

Then run tcpdump -vv -i tape8837e97-91 tape8837e97-91 && see would VM respond , then qvoe8837e97-91 tcpdump -vv -i qvoe8837e97-91 from veth pair ( qvoe8837e97-91, qvbe8837e97-91), e.g. trace all devices on the way from br-int to br-ex by tcpdump tcpdump, ovs-ofctl dump-flows br-tun && locate point of failure.