Hi Manoj,

You need to enable ping_plugin.so and then you would be able to see the
ping CLI command

On Mon, 15 Jun, 2020, 10:11 pm Manoj Iyer, <manoj.i...@arm.com> wrote:

> Steven,
>
> vppctl does not have a ping command I am on version 20.5 (may be I did not
> compile this option?) Also not sure how to parse this trace output.
>
> When I ping System B from System A and run the trace on SystemB I get the
> following output:
>
> $ sudo vppctl show trace
> ------------------- Start of thread 0 vpp_main -------------------
> No packets in trace buffer
> ------------------- Start of thread 1 vpp_wk_0 -------------------
> Packet 1
>
> 00:06:46:741025: dpdk-input
>   bnxt0 rx queue 0
>   buffer 0x56cb7: current data 0, length 119, buffer-pool 0, ref-count 1,
> totlen-nifb 0, trace handle 0x1000000
>                   ext-hdr-valid
>                   l4-cksum-computed l4-cksum-correct
>   PKT MBUF: port 0, nb_segs 1, pkt_len 119
>     buf_len 2176, data_len 119, ol_flags 0x0, data_off 128, phys_addr
> 0x70f65c80
>     packet_type 0x1 l2_len 0 l3_len 0 outer_l2_len 0 outer_l3_len 0
>     rss 0x0 fdir.hi 0x0 fdir.lo 0x0
>     Packet Types
>       RTE_PTYPE_L2_ETHER (0x0001) Ethernet packet
>   0x0069: 18:e8:29:21:03:13 -> 01:80:c2:00:00:00
> 00:06:46:741035: ethernet-input
>   frame: flags 0x3, hw-if-index 1, sw-if-index 1
>   0x0069: 18:e8:29:21:03:13 -> 01:80:c2:00:00:00
> 00:06:46:741038: llc-input
>   LLC bpdu -> bpdu
> 00:06:46:741042: error-drop
>   rx:bnxt0
> 00:06:46:741043: drop
>   llc-input: unknown llc ssap/dsap
>
> Packet 2
>
> 00:06:48:741182: dpdk-input
>   bnxt0 rx queue 0
>   buffer 0x56ca2: current data 0, length 119, buffer-pool 0, ref-count 1,
> totlen-nifb 0, trace handle 0x1000001
>                   ext-hdr-valid
>                   l4-cksum-computed l4-cksum-correct
>   PKT MBUF: port 0, nb_segs 1, pkt_len 119
>     buf_len 2176, data_len 119, ol_flags 0x0, data_off 128, phys_addr
> 0x70f65200
>     packet_type 0x1 l2_len 0 l3_len 0 outer_l2_len 0 outer_l3_len 0
>     rss 0x0 fdir.hi 0x0 fdir.lo 0x0
>     Packet Types
>       RTE_PTYPE_L2_ETHER (0x0001) Ethernet packet
>   0x0069: 18:e8:29:21:03:13 -> 01:80:c2:00:00:00
> 00:06:48:741185: ethernet-input
>   frame: flags 0x3, hw-if-index 1, sw-if-index 1
>   0x0069: 18:e8:29:21:03:13 -> 01:80:c2:00:00:00
> 00:06:48:741186: llc-input
>   LLC bpdu -> bpdu
> 00:06:48:741186: error-drop
>   rx:bnxt0
> 00:06:48:741187: drop
>   llc-input: unknown llc ssap/dsap
>
> Packet 3
>
> 00:06:50:741453: dpdk-input
>   bnxt0 rx queue 0
>   buffer 0x56c8d: current data 0, length 119, buffer-pool 0, ref-count 1,
> totlen-nifb 0, trace handle 0x1000002
>                   ext-hdr-valid
>                   l4-cksum-computed l4-cksum-correct
>   PKT MBUF: port 0, nb_segs 1, pkt_len 119
>     buf_len 2176, data_len 119, ol_flags 0x0, data_off 128, phys_addr
> 0x70f64780
>     packet_type 0x1 l2_len 0 l3_len 0 outer_l2_len 0 outer_l3_len 0
>     rss 0x0 fdir.hi 0x0 fdir.lo 0x0
>     Packet Types
>       RTE_PTYPE_L2_ETHER (0x0001) Ethernet packet
>   0x0069: 18:e8:29:21:03:13 -> 01:80:c2:00:00:00
> 00:06:50:741455: ethernet-input
>   frame: flags 0x3, hw-if-index 1, sw-if-index 1
>   0x0069: 18:e8:29:21:03:13 -> 01:80:c2:00:00:00
> 00:06:50:741456: llc-input
>   LLC bpdu -> bpdu
> 00:06:50:741457: error-drop
>   rx:bnxt0
> 00:06:50:741457: drop
>   llc-input: unknown llc ssap/dsap
>
> Packet 4
>
> 00:06:52:741564: dpdk-input
>   bnxt0 rx queue 0
>   buffer 0x56c78: current data 0, length 119, buffer-pool 0, ref-count 1,
> totlen-nifb 0, trace handle 0x1000003
>                   ext-hdr-valid
>                   l4-cksum-computed l4-cksum-correct
>   PKT MBUF: port 0, nb_segs 1, pkt_len 119
>     buf_len 2176, data_len 119, ol_flags 0x0, data_off 128, phys_addr
> 0x70f63d00
>     packet_type 0x1 l2_len 0 l3_len 0 outer_l2_len 0 outer_l3_len 0
>     rss 0x0 fdir.hi 0x0 fdir.lo 0x0
>     Packet Types
>       RTE_PTYPE_L2_ETHER (0x0001) Ethernet packet
>   0x0069: 18:e8:29:21:03:13 -> 01:80:c2:00:00:00
> 00:06:52:741567: ethernet-input
>   frame: flags 0x3, hw-if-index 1, sw-if-index 1
>   0x0069: 18:e8:29:21:03:13 -> 01:80:c2:00:00:00
> 00:06:52:741568: llc-input
>   LLC bpdu -> bpdu
> 00:06:52:741568: error-drop
>   rx:bnxt0
> 00:06:52:741569: drop
>   llc-input: unknown llc ssap/dsap
>
> Packet 5
>
> 00:06:54:474773: dpdk-input
>   bnxt0 rx queue 0
>   buffer 0x56c63: current data 0, length 319, buffer-pool 0, ref-count 1,
> totlen-nifb 0, trace handle 0x1000004
>                   ext-hdr-valid
>                   l4-cksum-computed l4-cksum-correct
>   PKT MBUF: port 0, nb_segs 1, pkt_len 319
>     buf_len 2176, data_len 319, ol_flags 0x182, data_off 128, phys_addr
> 0x70f63280
>     packet_type 0x291 l2_len 0 l3_len 0 outer_l2_len 0 outer_l3_len 0
>     rss 0x8ae4b80f fdir.hi 0x0 fdir.lo 0x8ae4b80f
>     Packet Offload Flags
>       PKT_RX_RSS_HASH (0x0002) RX packet with RSS hash result
>       PKT_RX_IP_CKSUM_GOOD (0x0080) IP cksum of RX pkt. is valid
>       PKT_RX_L4_CKSUM_GOOD (0x0100) L4 cksum of RX pkt. is valid
>     Packet Types
>       RTE_PTYPE_L2_ETHER (0x0001) Ethernet packet
>       RTE_PTYPE_L3_IPV4_EXT_UNKNOWN (0x0090) IPv4 packet with or without
> extension headers
>       RTE_PTYPE_L4_UDP (0x0200) UDP packet
>   IP4: 18:e8:29:21:03:12 -> ff:ff:ff:ff:ff:ff
>   UDP: 0.0.0.0 -> 255.255.255.255
>     tos 0x10, ttl 64, length 305, checksum 0x79ad dscp unknown ecn NON_ECN
>     fragment id 0x0000
>   UDP: 68 -> 67
>     length 285, checksum 0x5713
> 00:06:54:474776: ethernet-input
>   frame: flags 0x3, hw-if-index 1, sw-if-index 1
>   IP4: 18:e8:29:21:03:12 -> ff:ff:ff:ff:ff:ff
> 00:06:54:474777: ip4-input-no-checksum
>   UDP: 0.0.0.0 -> 255.255.255.255
>     tos 0x10, ttl 64, length 305, checksum 0x79ad dscp unknown ecn NON_ECN
>     fragment id 0x0000
>   UDP: 68 -> 67
>     length 285, checksum 0x5713
> 00:06:54:474779: ip4-lookup
>   fib 0 dpo-idx 0 flow hash: 0x00000000
>   UDP: 0.0.0.0 -> 255.255.255.255
>     tos 0x10, ttl 64, length 305, checksum 0x79ad dscp unknown ecn NON_ECN
>     fragment id 0x0000
>   UDP: 68 -> 67
>     length 285, checksum 0x5713
> 00:06:54:474784: ip4-drop
>     UDP: 0.0.0.0 -> 255.255.255.255
>       tos 0x10, ttl 64, length 305, checksum 0x79ad dscp unknown ecn
> NON_ECN
>       fragment id 0x0000
>     UDP: 68 -> 67
>       length 285, checksum 0x5713
> 00:06:54:474785: error-drop
>   rx:bnxt0
> 00:06:54:474785: drop
>   dpdk-input: no error
>
> Packet 6
>
> 00:06:54:741669: dpdk-input
>   bnxt0 rx queue 0
>   buffer 0x56c4e: current data 0, length 119, buffer-pool 0, ref-count 1,
> totlen-nifb 0, trace handle 0x1000005
>                   ext-hdr-valid
>                   l4-cksum-computed l4-cksum-correct
>   PKT MBUF: port 0, nb_segs 1, pkt_len 119
>     buf_len 2176, data_len 119, ol_flags 0x0, data_off 128, phys_addr
> 0x70f62800
>     packet_type 0x1 l2_len 0 l3_len 0 outer_l2_len 0 outer_l3_len 0
>     rss 0x0 fdir.hi 0x0 fdir.lo 0x0
>     Packet Types
>       RTE_PTYPE_L2_ETHER (0x0001) Ethernet packet
>   0x0069: 18:e8:29:21:03:13 -> 01:80:c2:00:00:00
> 00:06:54:741671: ethernet-input
>   frame: flags 0x3, hw-if-index 1, sw-if-index 1
>   0x0069: 18:e8:29:21:03:13 -> 01:80:c2:00:00:00
> 00:06:54:741672: llc-input
>   LLC bpdu -> bpdu
> 00:06:54:741673: error-drop
>   rx:bnxt0
> 00:06:54:741673: drop
>   llc-input: unknown llc ssap/dsap
>
> Packet 7
>
> 00:06:56:741445: dpdk-input
>   bnxt0 rx queue 0
>   buffer 0x56c39: current data 0, length 119, buffer-pool 0, ref-count 1,
> totlen-nifb 0, trace handle 0x1000006
>                   ext-hdr-valid
>                   l4-cksum-computed l4-cksum-correct
>   PKT MBUF: port 0, nb_segs 1, pkt_len 119
>     buf_len 2176, data_len 119, ol_flags 0x0, data_off 128, phys_addr
> 0x70f61d80
>     packet_type 0x1 l2_len 0 l3_len 0 outer_l2_len 0 outer_l3_len 0
>     rss 0x0 fdir.hi 0x0 fdir.lo 0x0
>     Packet Types
>       RTE_PTYPE_L2_ETHER (0x0001) Ethernet packet
>   0x0069: 18:e8:29:21:03:13 -> 01:80:c2:00:00:00
> 00:06:56:741449: ethernet-input
>   frame: flags 0x3, hw-if-index 1, sw-if-index 1
>   0x0069: 18:e8:29:21:03:13 -> 01:80:c2:00:00:00
> 00:06:56:741451: llc-input
>   LLC bpdu -> bpdu
> 00:06:56:741452: error-drop
>   rx:bnxt0
> 00:06:56:741452: drop
>   llc-input: unknown llc ssap/dsap
>
> Packet 8
>
> 00:06:58:741634: dpdk-input
>   bnxt0 rx queue 0
>   buffer 0x56c24: current data 0, length 119, buffer-pool 0, ref-count 1,
> totlen-nifb 0, trace handle 0x1000007
>                   ext-hdr-valid
>                   l4-cksum-computed l4-cksum-correct
>   PKT MBUF: port 0, nb_segs 1, pkt_len 119
>     buf_len 2176, data_len 119, ol_flags 0x0, data_off 128, phys_addr
> 0x70f61300
>     packet_type 0x1 l2_len 0 l3_len 0 outer_l2_len 0 outer_l3_len 0
>     rss 0x0 fdir.hi 0x0 fdir.lo 0x0
>     Packet Types
>       RTE_PTYPE_L2_ETHER (0x0001) Ethernet packet
>   0x0069: 18:e8:29:21:03:13 -> 01:80:c2:00:00:00
> 00:06:58:741636: ethernet-input
>   frame: flags 0x3, hw-if-index 1, sw-if-index 1
>   0x0069: 18:e8:29:21:03:13 -> 01:80:c2:00:00:00
> 00:06:58:741637: llc-input
>   LLC bpdu -> bpdu
> 00:06:58:741637: error-drop
>   rx:bnxt0
> 00:06:58:741638: drop
>   llc-input: unknown llc ssap/dsap
>
> Packet 9
>
> 00:07:00:741071: dpdk-input
>   bnxt0 rx queue 0
>   buffer 0x56c0f: current data 0, length 119, buffer-pool 0, ref-count 1,
> totlen-nifb 0, trace handle 0x1000008
>                   ext-hdr-valid
>                   l4-cksum-computed l4-cksum-correct
>   PKT MBUF: port 0, nb_segs 1, pkt_len 119
>     buf_len 2176, data_len 119, ol_flags 0x0, data_off 128, phys_addr
> 0x70f60880
>     packet_type 0x1 l2_len 0 l3_len 0 outer_l2_len 0 outer_l3_len 0
>     rss 0x0 fdir.hi 0x0 fdir.lo 0x0
>     Packet Types
>       RTE_PTYPE_L2_ETHER (0x0001) Ethernet packet
>   0x0069: 18:e8:29:21:03:13 -> 01:80:c2:00:00:00
> 00:07:00:741075: ethernet-input
>   frame: flags 0x3, hw-if-index 1, sw-if-index 1
>   0x0069: 18:e8:29:21:03:13 -> 01:80:c2:00:00:00
> 00:07:00:741076: llc-input
>   LLC bpdu -> bpdu
> 00:07:00:741076: error-drop
>   rx:bnxt0
> 00:07:00:741077: drop
>   llc-input: unknown llc ssap/dsap
>
> Packet 10
>
> 00:07:01:479677: dpdk-input
>   bnxt0 rx queue 0
>   buffer 0x56bfa: current data 0, length 319, buffer-pool 0, ref-count 1,
> totlen-nifb 0, trace handle 0x1000009
>                   ext-hdr-valid
>                   l4-cksum-computed l4-cksum-correct
>   PKT MBUF: port 0, nb_segs 1, pkt_len 319
>     buf_len 2176, data_len 319, ol_flags 0x182, data_off 128, phys_addr
> 0x70f5fe00
>     packet_type 0x291 l2_len 0 l3_len 0 outer_l2_len 0 outer_l3_len 0
>     rss 0x8ae4b80f fdir.hi 0x0 fdir.lo 0x8ae4b80f
>     Packet Offload Flags
>       PKT_RX_RSS_HASH (0x0002) RX packet with RSS hash result
>       PKT_RX_IP_CKSUM_GOOD (0x0080) IP cksum of RX pkt. is valid
>       PKT_RX_L4_CKSUM_GOOD (0x0100) L4 cksum of RX pkt. is valid
>     Packet Types
>       RTE_PTYPE_L2_ETHER (0x0001) Ethernet packet
>       RTE_PTYPE_L3_IPV4_EXT_UNKNOWN (0x0090) IPv4 packet with or without
> extension headers
>       RTE_PTYPE_L4_UDP (0x0200) UDP packet
>   IP4: 18:e8:29:21:03:12 -> ff:ff:ff:ff:ff:ff
>   UDP: 0.0.0.0 -> 255.255.255.255
>     tos 0x10, ttl 64, length 305, checksum 0x79ad dscp unknown ecn NON_ECN
>     fragment id 0x0000
>   UDP: 68 -> 67
>     length 285, checksum 0x570f
> 00:07:01:479679: ethernet-input
>   frame: flags 0x3, hw-if-index 1, sw-if-index 1
>   IP4: 18:e8:29:21:03:12 -> ff:ff:ff:ff:ff:ff
> 00:07:01:479680: ip4-input-no-checksum
>   UDP: 0.0.0.0 -> 255.255.255.255
>     tos 0x10, ttl 64, length 305, checksum 0x79ad dscp unknown ecn NON_ECN
>     fragment id 0x0000
>   UDP: 68 -> 67
>     length 285, checksum 0x570f
> 00:07:01:479680: ip4-lookup
>   fib 0 dpo-idx 0 flow hash: 0x00000000
>   UDP: 0.0.0.0 -> 255.255.255.255
>     tos 0x10, ttl 64, length 305, checksum 0x79ad dscp unknown ecn NON_ECN
>     fragment id 0x0000
>   UDP: 68 -> 67
>     length 285, checksum 0x570f
> 00:07:01:479682: ip4-drop
>     UDP: 0.0.0.0 -> 255.255.255.255
>       tos 0x10, ttl 64, length 305, checksum 0x79ad dscp unknown ecn
> NON_ECN
>       fragment id 0x0000
>     UDP: 68 -> 67
>       length 285, checksum 0x570f
> 00:07:01:479682: error-drop
>   rx:bnxt0
> 00:07:01:479682: drop
>   dpdk-input: no error
>
> Packet 11
>
> 00:07:02:741171: dpdk-input
>   bnxt0 rx queue 0
>   buffer 0x56be5: current data 0, length 119, buffer-pool 0, ref-count 1,
> totlen-nifb 0, trace handle 0x100000a
>                   ext-hdr-valid
>                   l4-cksum-computed l4-cksum-correct
>   PKT MBUF: port 0, nb_segs 1, pkt_len 119
>     buf_len 2176, data_len 119, ol_flags 0x0, data_off 128, phys_addr
> 0x70f5f380
>     packet_type 0x1 l2_len 0 l3_len 0 outer_l2_len 0 outer_l3_len 0
>     rss 0x0 fdir.hi 0x0 fdir.lo 0x0
>     Packet Types
>       RTE_PTYPE_L2_ETHER (0x0001) Ethernet packet
>   0x0069: 18:e8:29:21:03:13 -> 01:80:c2:00:00:00
> 00:07:02:741173: ethernet-input
>   frame: flags 0x3, hw-if-index 1, sw-if-index 1
>   0x0069: 18:e8:29:21:03:13 -> 01:80:c2:00:00:00
> 00:07:02:741175: llc-input
>   LLC bpdu -> bpdu
> 00:07:02:741175: error-drop
>   rx:bnxt0
> 00:07:02:741175: drop
>   llc-input: unknown llc ssap/dsap
>
> ------------------- Start of thread 2 vpp_wk_1 -------------------
> No packets in trace buffer
> ------------------- Start of thread 3 vpp_wk_2 -------------------
> No packets in trace buffer
> ------------------------------
> *From:* Steven Luong (sluong) <slu...@cisco.com>
> *Sent:* Monday, June 15, 2020 11:15 AM
> *To:* Manoj Iyer <manoj.i...@arm.com>; Dave Barach (dbarach) <
> dbar...@cisco.com>; vpp-dev@lists.fd.io <vpp-dev@lists.fd.io>
> *Subject:* Re: [vpp-dev] Need help with setup.. cannot ping a VPP
> interface.
>
>
> Manoj,
>
>
>
> Because system B is running VPP, you can’t initiate the ping from system B
> in Unix Shell. Kernel does not have that interface and IP address anymore
> for you to do the ping. You have to start the ping from vppctl if you want
> to do the ping from system B running VPP.
>
>
>
> When you do the ping from system A, type
>
> vppctl show error
>
> vppctl show interface
>
> may help you to find out why the packet got dropped or if it arrives at
> all to VPP. If that still does not help, take the trace from VPP. Something
> like this
>
>
>
> vppctl trace add dpdk-input 100
>
> ping 10.1.1.10  ß ping rom system A
>
> vppctl show trace
>
>
>
> Honestly, I’ve never worked with a Broadcom NIC which you are using.
>
>     tx burst function: bnxt_xmit_pkts
>
>     rx burst function: bnxt_recv_pkts
>
> May the force be with you.
>
>
>
> Steven
>
>
>
> *From: *Manoj Iyer <manoj.i...@arm.com>
> *Date: *Monday, June 15, 2020 at 7:48 AM
> *To: *"Dave Barach (dbarach)" <dbar...@cisco.com>, "Steven Luong
> (sluong)" <slu...@cisco.com>, "vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io>
> *Subject: *Re: [vpp-dev] Need help with setup.. cannot ping a VPP
> interface.
>
>
>
> Dave/Steven,
>
>
>
> I set the netmask on both sides to 255.255.255.0 and here is how I setup
> the ip address on the 2 servers. System-B has ip address set using vppctl
> and system-A was setup using ifconfig, as below. The link is up on
> both enp2s0f1np1 on System A and bnxt0 on System B. VPP version used is
> 20.05.
>
>
>
> Also on System B where I setup 10.1.1.10 as the IP address on the VPP
> interface bnxt0, I was not able to ping that IP from the host system
> (System B). Please see below towards the end where this ping fails.
>
>
>
> (Also, I setup the exact same physical interfaces without using VPP and
> was able to ping each other.)
>
>
>
> == System A ==
>
> $ sudo ifconfig enp2s0f1np1 10.1.1.11 netmask 255.255.255.0 up
> $ ifconfig enp2s0f1np1
>
> enp2s0f1np1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>
>         inet 10.1.1.11  netmask 255.255.255.0  broadcast 10.1.1.255
>
>         ether b0:26:28:82:09:cd  txqueuelen 1000  (Ethernet)
>
>         RX packets 635  bytes 183934 (183.9 KB)
>
>         RX errors 0  dropped 0  overruns 0  frame 0
>
>         TX packets 150  bytes 20610 (20.6 KB)
>
>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> $ ethtool enp2s0f1np1
>
> Settings for enp2s0f1np1:
>
> Supported ports: [ FIBRE ]
>
> Supported link modes:   10000baseT/Full
>
> Supported pause frame use: Symmetric Receive-only
>
> Supports auto-negotiation: Yes
>
> Supported FEC modes: Not reported
>
> Advertised link modes:  10000baseT/Full
>
>                        25000baseCR/Full
>
> Advertised pause frame use: No
>
> Advertised auto-negotiation: Yes
>
> Advertised FEC modes: Not reported
>
> Speed: 10000Mb/s
>
> Duplex: Full
>
> Port: Direct Attach Copper
>
> PHYAD: 1
>
> Transceiver: internal
>
> Auto-negotiation: on
>
> Cannot get wake-on-lan settings: Operation not permitted
>
> Current message level: 0x00000000 (0)
>
>
>
> Link detected: yes
>
>
>
> == System B (vppctl for ip setup ) ==
>
> $ sudo vppctl set int ip address bnxt0 10.1.1.10/24
>
> $ sudo vppctl show interface address
>
> bnxt0 (up):
>
>   L3 10.1.1.10/24
>
> bnxt1 (dn):
>
> bnxt2 (dn):
>
> bnxt3 (dn):
>
> local0 (dn):
>
> $ sudo vppctl show hardware
>
>               Name                Idx   Link  Hardware
>
> bnxt0                              1     up   bnxt0
>
>   Link speed: 10 Gbps
>
>   Ethernet address 00:10:18:ad:05:00
>
>   Broadcom NetXtreme E/S-Series
>
>     carrier up full duplex mtu 9206
>
>     flags: admin-up pmd tx-offload rx-ip4-cksum
>
>     Devargs:
>
>     rx: queues 3 (max 73), desc 512 (min 16 max 8192 align 1)
>
>     tx: queues 4 (max 73), desc 512 (min 16 max 4096 align 1)
>
>     pci: device 14e4:d804 subsystem 14e4:8040 address 0008:01:00.00 numa 0
>
>     max rx packet len: 9600
>
>     promiscuous: unicast off all-multicast on
>
>     vlan offload: strip on filter off qinq off
>
>     rx offload avail:  vlan-strip ipv4-cksum udp-cksum tcp-cksum tcp-lro
>
>                        outer-ipv4-cksum vlan-filter vlan-extend
> jumbo-frame
>
>                        scatter timestamp keep-crc rss-hash
>
>     rx offload active: vlan-strip ipv4-cksum
>
>     tx offload avail:  vlan-insert ipv4-cksum udp-cksum tcp-cksum tcp-tso
>
>                        outer-ipv4-cksum qinq-insert vxlan-tnl-tso
> gre-tnl-tso
>
>                        ipip-tnl-tso geneve-tnl-tso multi-segs
>
>     tx offload active: vlan-insert ipv4-cksum udp-cksum tcp-cksum tcp-tso
>
>                        outer-ipv4-cksum vxlan-tnl-tso gre-tnl-tso
> ipip-tnl-tso
>
>                        geneve-tnl-tso multi-segs
>
>     rss avail:         ipv4-tcp ipv4-udp ipv4 ipv6-tcp ipv6-udp ipv6
>
>     rss active:        ipv4-tcp ipv4-udp ipv4 ipv6-tcp ipv6-udp ipv6
>
>     tx burst function: bnxt_xmit_pkts
>
>     rx burst function: bnxt_recv_pkts
>
>
>
> == Ping System A from System B ==
>
> $ ping -c1 10.1.1.11
>
> PING 10.1.1.11 (10.1.1.11) 56(84) bytes of data.
>
>
>
> --- 10.1.1.11 ping statistics ---
>
> 1 packets transmitted, 0 received, 100% packet loss, time 0ms
>
>
>
> == Ping System B from System A ==
>
> $ ping -c1 10.1.1.10
>
> PING 10.1.1.10 (10.1.1.10) 56(84) bytes of data.
>
> From 10.1.1.11 icmp_seq=1 Destination Host Unreachable
>
>
>
> --- 10.1.1.10 ping statistics ---
>
> 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
>
>
>
> == Ping System A interface from System A ==
>
> $ ping -c1 10.1.1.11
>
> PING 10.1.1.11 (10.1.1.11) 56(84) bytes of data.
>
> 64 bytes from 10.1.1.11: icmp_seq=1 ttl=64 time=0.033 ms
>
>
>
> --- 10.1.1.11 ping statistics ---
>
> 1 packets transmitted, 1 received, 0% packet loss, time 0ms
>
> rtt min/avg/max/mdev = 0.033/0.033/0.033/0.000 ms
>
>
>
> == Ping System B interface from System B ==
>
> $ ping -c1 10.1.1.10
>
> PING 10.1.1.10 (10.1.1.10) 56(84) bytes of data.
>
>
>
> --- 10.1.1.10 ping statistics ---
>
> 1 packets transmitted, 0 received, 100% packet loss, time 0ms
>
>
>
> Thanks
>
> Manoj Iyer
> ------------------------------
>
> *From:* Dave Barach (dbarach) <dbar...@cisco.com>
> *Sent:* Friday, June 12, 2020 3:21 PM
> *To:* Steven Luong (sluong) <slu...@cisco.com>; Manoj Iyer <
> manoj.i...@arm.com>; vpp-dev@lists.fd.io <vpp-dev@lists.fd.io>
> *Subject:* RE: [vpp-dev] Need help with setup.. cannot ping a VPP
> interface.
>
>
>
> +check hardware addresses with “show hardware”, to make sure you’ve
> configured the interface which is actually connected to the peer system /
> switch...
>
>
>
> HTH... Dave
>
>
>
> *From:* vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> * On Behalf Of *steven
> luong via lists.fd.io
> *Sent:* Friday, June 12, 2020 4:18 PM
> *To:* Manoj Iyer <manoj.i...@arm.com>; vpp-dev@lists.fd.io
> *Subject:* Re: [vpp-dev] Need help with setup.. cannot ping a VPP
> interface.
>
>
>
> Please correct the subnet mask first.
>
>   L3 10.1.1.10/24. ß system A
>
>    inet 10.1.1.11  netmask 255.0.0.0  broadcast 10.255.255.255  ß- system
> B
>
>
>
> Steven
>
>
>
> *From: *<vpp-dev@lists.fd.io> on behalf of Manoj Iyer <manoj.i...@arm.com>
> *Date: *Friday, June 12, 2020 at 12:28 PM
> *To: *"vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io>
> *Subject: *[vpp-dev] Need help with setup.. cannot ping a VPP interface.
>
>
>
> Hello,
>
>
>
> I am very new to VPP and I am having trouble pinging the vpp interface. I
> have a system with ip address 10.1.1.10 set up using a VPP interface, and I
> have another system with ip address 10.1.1.11 setup with no VPP. Both
> systems are connected though a switch.
>
>
>
> If I do not use VPP I am able to ping each other, but when I use VPP to
> configure one of the IPs I am unable to ping.
>
>
>
> I know this might be a very basic setup issue. Could someone please point
> me in the right direction. I have read through
>
> https://wiki.fd.io/view/VPP/How_To_Connect_A_PCI_Interface_To_VPP
>
>
>
> == on system A ==
>
> $ sudo vppctl show interface address
>
> bnxt0 (dn):
>
> bnxt1 (dn):
>
> bnxt2 (dn):
>
> bnxt3 (up):
>
>   L3 10.1.1.10/24
>
> local0 (dn):
>
>
>
> $ sudo vppctl show interface
>
>               Name               Idx    State  MTU (L3/IP4/IP6/MPLS)
> Counter          Count
>
> bnxt0                             1     down         9000/0/0/0
>
> bnxt1                             2     down         9000/0/0/0
>
> bnxt2                             3     down         9000/0/0/0
>
> bnxt3                             4      up          9000/0/0/0     rx
> packets                   498
>
>                                                                     rx
> bytes                   74839
>
>                                                                     drops
>                        498
>
>                                                                     ip4
>                        112
>
>                                                                     ip6
>                        188
>
> local0                            0     down          0/0/0/0
>
>
>
>
>
> == on system B ==
>
> $ ifconfig enp2s0f2np0
>
> enp2s0f2np0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>
>         inet 10.1.1.11  netmask 255.0.0.0  broadcast 10.255.255.255
>
>         ether b0:26:28:82:09:ce  txqueuelen 1000  (Ethernet)
>
>         RX packets 250  bytes 59677 (59.6 KB)
>
>         RX errors 0  dropped 0  overruns 0  frame 0
>
>         TX packets 103  bytes 15583 (15.5 KB)
>
>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
>
>
>
>
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the
> contents to any other person, use it for any purpose, or store or copy the
> information in any medium. Thank you.
>
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the
> contents to any other person, use it for any purpose, or store or copy the
> information in any medium. Thank you.
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the
> contents to any other person, use it for any purpose, or store or copy the
> information in any medium. Thank you.
> 
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#16735): https://lists.fd.io/g/vpp-dev/message/16735
Mute This Topic: https://lists.fd.io/mt/74846214/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to