Wonderful! Thanks Raja
Andy Wang At 2016-06-13 01:01:54, "Rajagopalan Sivaramakrishnan" <[email protected]> wrote: Hi Andy, You can use the “vifdump” command (with similar arguments as tcpdump). It takes the vif index (from “vif –list”) instead of the interface name. For example, vifdump –i 3 would dump packets on tap23214e79-4d (from vif list below). Raja # vif --list Vrouter Interface Table Flags: P=Policy, X=Cross Connect, S=Service Chain, Mr=Receive Mirror Mt=Transmit Mirror, Tc=Transmit Checksum Offload, L3=Layer 3, L2=Layer 2 D=DHCP, Vp=Vhost Physical, Pr=Promiscuous, Vnt=Native Vlan Tagged Mnp=No MAC Proxy, Dpdk=DPDK PMD Interface, Rfl=Receive Filtering Offload, Mon=Interface is Monitored Uuf=Unknown Unicast Flood, Vof=VLAN insert/strip offload vif0/0 PCI: 0000:04:11.1 (Speed 10000, Duplex 1) Type:Physical HWaddr:90:e2:ba:33:47:b5 IPaddr:0 Vrf:0 Flags:TcL3L2VpVof MTU:1514 Ref:13 RX device packets:968259499 bytes:147153735732590 errors:0 RX port packets:1388242697372 errors:0 RX queue packets:1096941502977 errors:291301194944 RX queue errors to lcore 0 0 0 0 0 0 0 0 0 0 0 99862863518 39398504608 91969541597 46153971815 13916313401 RX packets:1096941500179 bytes:116275809011214 errors:0 TX packets:285850 bytes:40236996 errors:0 TX queue packets:285850 errors:0 TX port packets:285850 errors:0 TX device packets:285850 bytes:40236996 errors:0 vif0/1 PMD: vhost0 Type:Host HWaddr:90:e2:ba:33:47:b5 IPaddr:c0a801c1 Vrf:0 Flags:L3L2 MTU:1514 Ref:12 RX port packets:1717 errors:0 RX queue packets:9 errors:0 RX queue errors to lcore 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 RX packets:1717 bytes:103226 errors:0 TX packets:3391 bytes:203498 errors:0 TX queue packets:1 errors:0 TX port packets:3391 errors:0 vif0/2 Socket: unix Type:Agent HWaddr:00:00:5e:00:01:00 IPaddr:0 Vrf:65535 Flags:L3 MTU:1514 Ref:2 RX port packets:2093 errors:0 RX queue errors to lcore 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 RX packets:2093 bytes:183324 errors:0 TX packets:2044 bytes:227005 errors:0 TX queue packets:2044 errors:0 TX port packets:2044 errors:0 syscalls:2054 vif0/3 PMD: tap23214e79-4d Type:Virtual HWaddr:00:00:5e:00:01:00 IPaddr:0 Vrf:1 Flags:PL3L2D MTU:9160 Ref:15 RX port packets:282191 errors:0 syscalls:1 RX queue packets:271943 errors:0 RX queue errors to lcore 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 RX packets:282191 bytes:27079535 errors:0 TX packets:1096941495478 bytes:65816499876668 errors:0 TX port packets:1096866213932 errors:75281573 syscalls:282118 From: Users <[email protected]> on behalf of Andy Wang <[email protected]> Date: Sunday, June 12, 2016 at 2:25 AM To: "[email protected]" <[email protected]>, "[email protected]" <[email protected]> Subject: [Users] contrail 3.0 DPDK packet capturing issue Hi All, I met one issue that VM could not get IP address in Contrail R3.0 DPDK issue. VM use vhost-type network interface to communicated with contrail-vrouter-dpdk by unix socket in dpdk environment. In non-dpdk condition, I can use tcpdump to capture packets in tap interface and pkt0. Now the interface is in user-space, I could not use tcpdump to capture pkts. Is there any debug method to take place of tcpdump in Contrail R3.0 DPDK Environment ? Thanks Andy Wang
_______________________________________________ Dev mailing list [email protected] http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
