How to use tcpdump on Openvswitch interfaces ?

Solution Verified - Updated -

Issue

  • Running a tcpdump on a openvswitch interface does not work.
  • This fails with the following error:
# tcpdump -npi phy-br-bond-d -vvvs0 -w /tmp/phy-br-bond-d.cap 
tcpdump: phy-br-bond-d: That device is not up
  • OR It can fail with :
# tcpdump -npi patch-tun -vvvs0 -w /tmp/int-br-ctlplane.cap
tcpdump: patch-tun: No such device exists
(SIOCGIFHWADDR: No such device)
  • How to capture a tcpdump in this case?

Environment

  • Red Hat Enterprise Linux Openstack
  • Openvswitch configured with the following configuration:
+------[ COMPUTE HOST ]------+     
|+----------+    +----------+|     
|| INSTANCE |    | INSTANCE ||     
||          |    |          ||    
|+--[eth0]--+    +--[eth0]--+|
|     |               |      | 
|+--[tapX]--+    +--[tapX]--+| 
||   qbrX   |    |   qbrX   ||    
|+--[qvbX]--+    +--[qvbX]--+|
|     |                |     |    
|     +---+        +---+     |    
|         |        |         |     
|    +--[qvoX]---[qvoY]--+   |
|    |       br-int      |   |    
|    +---[int-br-eth1]---+   |    
|              |             |    
|    +---[phy-br-bond-d]-+   |    
|    |      br-bond-d    |   |    
|    +------[bond-d]-----+   |    
|               |            |          
|     +---------+---+        |
|     |             |        |  
+---[eno1]--------[enod2]-----+
                    |     +-------------- +
                    +-----| INTERNAL VLAN |
                          +---------------+

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.