[ovs-discuss] Cannot dump packet capture using dpdk-pdump

[Loftus, Ciara]

> Hi
> 
> I am trying to configured dpdk-pdump to dump the packet in the OVS
> bridge, however, I am failed. no packet is capture on ingress or
> egress, any idea?

Hi,

You are capturing on port 1 but the link state is "down". Make sure your link is up and that you can see packets being rx/tx in the statistics first eg. via 'ovs-ofctl dump-ports <bridgename>'
The following might be useful as well:
https://software.intel.com/en-us/articles/dpdk-pdump-in-open-vswitch-with-dpdk

Thanks,
Ciara

> 
> 
> the command I used is
> ./dpdk-pdump -- --pdump
> port=1,queue=*,rx-dev=/tmp/pkts_rx.pcap,tx-dev=/tmp/pkts_tx.pcap
> --server-socket-path=/usr/local/var/run/openvswitch
> 
> the output on the screen is shown below.
> 
> EAL: Detected 24 lcore(s)
> EAL: Probing VFIO support...
> EAL: WARNING: Address Space Layout Randomization (ASLR) is enabled in
> the kernel.
> EAL:    This may cause issues with mapping memory into secondary processes
> EAL: PCI device 0000:04:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:150e net_e1000_igb
> EAL: PCI device 0000:04:00.1 on NUMA socket 0
> EAL:   probe driver: 8086:150e net_e1000_igb
> EAL: PCI device 0000:04:00.2 on NUMA socket 0
> EAL:   probe driver: 8086:150e net_e1000_igb
> EAL: PCI device 0000:04:00.3 on NUMA socket 0
> EAL:   probe driver: 8086:150e net_e1000_igb
> EAL: PCI device 0000:07:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:1521 net_e1000_igb
> EAL: PCI device 0000:07:00.1 on NUMA socket 0
> EAL:   probe driver: 8086:1521 net_e1000_igb
> EAL: PCI device 0000:07:00.2 on NUMA socket 0
> EAL:   probe driver: 8086:1521 net_e1000_igb
> EAL: PCI device 0000:07:00.3 on NUMA socket 0
> EAL:   probe driver: 8086:1521 net_e1000_igb
> PMD: Initializing pmd_pcap for net_pcap_rx_0
> PMD: Creating pcap-backed ethdev on numa socket 4294967295
> Port 2 MAC: 00 00 00 01 02 03
> PMD: Initializing pmd_pcap for net_pcap_tx_0
> PMD: Creating pcap-backed ethdev on numa socket 4294967295
> Port 3 MAC: 00 00 00 01 02 03
> 
> the port assignment is
> 
> # ovs-ofctl show xtp1
> OFPT_FEATURES_REPLY (xid=0x2): dpid:0000001b21a7f596
> n_tables:254, n_buffers:0
> capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS
> ARP_MATCH_IP
> actions: output enqueue set_vlan_vid set_vlan_pcp strip_vlan
> mod_dl_src mod_dl_dst mod_nw_src mod_nw_dst mod_nw_tos
> mod_tp_src
> mod_tp_dst
>  1(dpdk1): addr:00:1b:21:a7:f5:97
>      config:     0
>      state:      LINK_DOWN
>      current:    AUTO_NEG
>      speed: 0 Mbps now, 0 Mbps max
>  2(dpdk0): addr:00:1b:21:a7:f5:96
>      config:     0
>      state:      LINK_DOWN
>      current:    AUTO_NEG
>      speed: 0 Mbps now, 0 Mbps max
>  LOCAL(gtp1): addr:00:1b:21:a7:f5:96
>      config:     0
>      state:      0
>      current:    10MB-FD COPPER
>      speed: 10 Mbps now, 0 Mbps max
> OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0
> _______________________________________________
> discuss mailing list
> discuss at openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss