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

Darrell Ball dball at vmware.com
Wed Sep 27 16:37:37 UTC 2017



On 9/27/17, 2:56 AM, "ovs-discuss-bounces at openvswitch.org on behalf of BALL SUN" <ovs-discuss-bounces at openvswitch.org on behalf of paulrbk at gmail.com> wrote:

    retried on the setup, once tried to rrun the dpdk-pdump, the following
    command of ovs-ofctl will be hanged, any idea?
    
    #  ovs-ofctl show br0
    OFPT_FEATURES_REPLY (xid=0x2): dpid:0000001b21a7f597
    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(dpdk0): addr:00:1b:21:a7:f5:97
         config:     0
         state:      0
         current:    1GB-FD AUTO_NEG
         speed: 1000 Mbps now, 0 Mbps max
     LOCAL(br0): addr:00:1b:21:a7:f5:97
         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
    
    
    [root at dhost4 app]#
    [roott at dhost app]#
    [root at dhost app]#  ovs-ofctl show br0          <--- HANG


Is vswitchd running?; it won’t reply if it is dead.
    
    
    On Tue, Sep 26, 2017 at 8:30 PM, Sun Paul <paulrbk at gmail.com> wrote:
    > Hi
    >
    > Whenever I run the dpdk-pdump, the ova-vswitchd daemon will be dead.
    >
    > Any idea?
    >
    >
    >
    > On Monday, September 25, 2017, Loftus, Ciara <ciara.loftus at intel.com> wrote:
    >>
    >> > 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://urldefense.proofpoint.com/v2/url?u=https-3A__software.intel.com_en-2Dus_articles_dpdk-2Dpdump-2Din-2Dopen-2Dvswitch-2Dwith-2Ddpdk&d=DwICAg&c=uilaK90D4TOVoH58JNXRgQ&r=BVhFA09CGX7JQ5Ih-uZnsw&m=JAKfSE1io8bxeU__GScd0WQcz9m_yNFZz6Nefe4RY34&s=JcKO1W_KUX7Z2g1caLrkEp5TkuCKp3HGQpLrCgqmjNY&e= 
    >>
    >> 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://urldefense.proofpoint.com/v2/url?u=https-3A__mail.openvswitch.org_mailman_listinfo_ovs-2Ddiscuss&d=DwICAg&c=uilaK90D4TOVoH58JNXRgQ&r=BVhFA09CGX7JQ5Ih-uZnsw&m=JAKfSE1io8bxeU__GScd0WQcz9m_yNFZz6Nefe4RY34&s=-XCGRFAxhn6T04Sa2sMhrVzXndHORdk-fmt0gcCUOOo&e= 
    _______________________________________________
    discuss mailing list
    discuss at openvswitch.org
    https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.openvswitch.org_mailman_listinfo_ovs-2Ddiscuss&d=DwICAg&c=uilaK90D4TOVoH58JNXRgQ&r=BVhFA09CGX7JQ5Ih-uZnsw&m=JAKfSE1io8bxeU__GScd0WQcz9m_yNFZz6Nefe4RY34&s=-XCGRFAxhn6T04Sa2sMhrVzXndHORdk-fmt0gcCUOOo&e= 
    



More information about the discuss mailing list