Hi Raja

Please find the below tcpdump -x output at vhost0 interface when ping is
running..



*192.168.1.11 is the compute node IP.192.168.1.1 is the Ip of other laptop.*

tcpdump -x -i vhost0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vhost0, link-type EN10MB (Ethernet), capture size 65535 bytes
00:53:30.463444 IP 192.168.1.11.ssh > 192.168.1.1.47959: Flags [P.], seq
855860805:855860917, ack 2569895894, win 329, options [nop,nop,TS val
17203641 ecr 1258224], length 112
    0x0000:  4510 00a4 229d 4000 4006 944a c0a8 010b
    0x0010:  c0a8 0101 0016 bb57 3303 6645 992d 7fd6
    0x0020:  8018 0149 ca34 0000 0101 080a 0106 81b9
    0x0030:  0013 32f0 5072 a094 5c53 1c72 c246 bc3b
    0x0040:  9687 3d3a beac e02d f90d 0c1e e776 f898
    0x0050:  cb23 9892 9e86 fa96 7ef5 811a 9676 9b8a
    0x0060:  7bf5 b90d 3b9f 096d 63bc 9d8a 7254 ef9b
    0x0070:  d157 cb03 acea 54a2 864d 6766 83bb b9ed
    0x0080:  fabb 42aa 35c8 d7e9 8df5 d968 81ba 3fa7
    0x0090:  346e 4b0d 7d49 0050 3a9d 5b28 44bc fa2e
    0x00a0:  0eb3 9a03
00:53:30.463525 IP 192.168.1.11.ssh > 192.168.1.1.47959: Flags [P.], seq
112:224, ack 1, win 329, options [nop,nop,TS val 17203641 ecr 1258224],
length 112
    0x0000:  4510 00a4 229e 4000 4006 9449 c0a8 010b
    0x0010:  c0a8 0101 0016 bb57 3303 66b5 992d 7fd6
    0x0020:  8018 0149 1f6b 0000 0101 080a 0106 81b9
    0x0030:  0013 32f0 ac93 ac9b da0b 6d93 877e 96d9
    0x0040:  0e52 6af3 a59b 4e1f 97f3 9dc3 b559 6ef7
    0x0050:  a6af f40c f497 57f7 980e 80db cef8 7a43
    0x0060:  38ae b81e 09fa 1fc1 8125 dc4d 2b46 076d
    0x0070:  47e9 705b c985 1fa9 1250 b43b 8ca1 7ecf
    0x0080:  1bf8 1d9e 8ad4 8e49 ebaa 4b25 6551 9c11
    0x0090:  56b8 0ea4 a9ba 4843 7b22 39ec 9e2c 92e6
    0x00a0:  bdd8 3a4a
00:53:30.463704 IP 192.168.1.1.47959 > 192.168.1.11.ssh: Flags [.], ack
112, win 184, options [nop,nop,TS val 1258239 ecr 17203641], length 0
    0x0000:  4500 0034 778e 4000 4006 3fd9 c0a8 0101
    0x0010:  c0a8 010b bb57 0016 992d 7fd6 3303 66b5
    0x0020:  8010 00b8 ceac 0000 0101 080a 0013 32ff
    0x0030:  0106 81b9
00:53:30.464186 IP 192.168.1.1.47959 > 192.168.1.11.ssh: Flags [.], ack
224, win 184, options [nop,nop,TS val 1258239 ecr 17203641], length 0
    0x0000:  4500 0034 778f 4000 4006 3fd8 c0a8 0101
    0x0010:  c0a8 010b bb57 0016 992d 7fd6 3303 6725
    0x0020:  8010 00b8 ce3c 0000 0101 080a 0013 32ff
    0x0030:  0106 81b9
00:53:31.381118 IP 192.168.1.11 > 192.168.1.1: ICMP echo request, id 6847,
seq 36, length 64
    0x0000:  4500 0054 e3b7 4000 4001 d394 c0a8 010b
    0x0010:  c0a8 0101 0800 0100 1abf 0024 560c ca5b
    0x0020:  0005 d0ac 0809 0a0b 0c0d 0e0f 1011 1213
    0x0030:  1415 1617 1819 1a1b 1c1d 1e1f 2021 2223
    0x0040:  2425 2627 2829 2a2b 2c2d 2e2f 3031 3233
    0x0050:  3435 3637
00:53:31.381399 IP 192.168.1.1 > 192.168.1.11: ICMP echo reply, id 6847,
seq 36, length 64
    0x0000:  4500 0054 db4b 0000 4001 1c01 c0a8 0101
    0x0010:  c0a8 010b 0000 0900 1abf 0024 560c ca5b
    0x0020:  0005 d0ac 0809 0a0b 0c0d 0e0f 1011 1213
    0x0030:  1415 1617 1819 1a1b 1c1d 1e1f 2021 2223
    0x0040:  2425 2627 2829 2a2b 2c2d 2e2f 3031 3233
    0x0050:  3435 3637
00:53:31.466470 IP 192.168.1.11.ssh > 192.168.1.1.47959: Flags [.], seq
224:1672, ack 1, win 329, options [nop,nop,TS val 17203892 ecr 1258239],
length 1448


Please find the below tcpdump -x output at eth0 interface when ping is
running..


 tcpdump -x  -i eth0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth13, link-type EN10MB (Ethernet), capture size 65535 bytes
00:47:57.448047 IP 192.168.1.11.ssh > 192.168.1.1.46976: Flags [P.], seq
1538147764:1538147956, ack 3851106437, win 329, options [nop,nop,TS val
17120387 ecr 1174970], length 192
    0x0000:  4510 00f4 048b 4000 4006 b20c c0a8 010b
    0x0010:  c0a8 0101 0016 b780 5bae 45b4 e58b 3885
    0x0020:  8018 0149 227d 0000 0101 080a 0105 3c83
    0x0030:  0011 edba 903e f1db 1817 121b a33c 0c83
    0x0040:  ccd7 ae31 1c43 bc55 6428 7e3b dc4f ef4d
    0x0050:  e60f f06b 2d60 14ce 49af 1c38 1bcf 510b
    0x0060:  cbaa 2ccd 3e6f 439b b428 4861 0b3f 089b
    0x0070:  922e 5cf7 6f6a 7875 6c27 9257 0245 d67e
    0x0080:  8c88 5f88 0039 367c 5425 db64 419d 6023
    0x0090:  85cb 3b5f 6dc6 1a61 4e1b 6e73 ef90 97fb
    0x00a0:  b6f9 c55a dc39 73b2 bbce b722 4ab9 a615
    0x00b0:  2de8 f265 c21a d22b c154 71e9 0593 3332
    0x00c0:  9bb7 047b c0f0 5221 d37e f16b 7fd3 6315
    0x00d0:  b196 c925 0404 458d f359 4c71 6f26 0343
    0x00e0:  c63f 6e40 e274 3dcf 98c5 c27e e3a7 d475
    0x00f0:  5a6a 43e5
00:47:57.448332 IP 192.168.1.1.46976 > 192.168.1.11.ssh: Flags [.], ack
192, win 252, options [nop,nop,TS val 1174985 ecr 17120387], length 0
    0x0000:  4500 0034 d33c 4000 4006 e42a c0a8 0101
    0x0010:  c0a8 010b b780 0016 e58b 3885 5bae 4674
    0x0020:  8010 00fc 4f37 0000 0101 080a 0011 edc9
    0x0030:  0105 3c83
00:47:58.341139 IP 192.168.1.11 > 192.168.1.1: ICMP echo request, id 6685,
seq 11, length 64
    0x0000:  4500 0054 3668 4000 4001 80e4 c0a8 010b
    0x0010:  c0a8 0101 0800 9f45 1a1d 000b 560c c90e
    0x0020:  0005 346f 0809 0a0b 0c0d 0e0f 1011 1213
    0x0030:  1415 1617 1819 1a1b 1c1d 1e1f 2021 2223
    0x0040:  2425 2627 2829 2a2b 2c2d 2e2f 3031 3233
    0x0050:  3435 3637
00:47:58.341406 IP 192.168.1.1 > 192.168.1.11: ICMP echo reply, id 6685,
seq 11, length 64
    0x0000:  4500 0054 da1d 0000 4001 1d2f c0a8 0101
    0x0010:  c0a8 010b 0000 a745 1a1d 000b 560c c90e
    0x0020:  0005 346f 0809 0a0b 0c0d 0e0f 1011 1213
    0x0030:  1415 1617 1819 1a1b 1c1d 1e1f 2021 2223
    0x0040:  2425 2627 2829 2a2b 2c2d 2e2f 3031 3233
    0x0050:  3435 3637

On Thu, Oct 1, 2015 at 11:13 AM, Rajagopalan Sivaramakrishnan <
[email protected]> wrote:

> Can you please send the output of tcpdump –x on both interfaces for a few
> seconds when ping is running?
>
> Raja
>
> From: abhishek jain <[email protected]>
> Date: Wednesday, September 30, 2015 at 10:27 PM
>
> To: Rajagopalan Sivaramakrishnan <[email protected]>
> Cc: "[email protected]" <[email protected]>, "
> [email protected]" <[email protected]>
> Subject: Re: [opencontrail-dev] Checksum offload error with
> contrail-vrouter-agent running on compute node
>
> Hi Rajagopalan
>
> I captured packets using tcpdump on vhost0 and eth0 on compute node.The
> checksum is correct when capturing packets at vhost0 interface.However the
> checksum incorrect error occurs when I'm capturing packets at eth0
> interface of the compute node.
>
> Please find the attached screanshot for the same.
>
>
>
> On Thu, Oct 1, 2015 at 12:03 AM, Rajagopalan Sivaramakrishnan <
> [email protected]> wrote:
>
>> Hi Abhishek,
>>     Can you please run “tcpdump –x” on vhost0 and the physical interface
>> (eth0) concurrently and compare the packets to see if anything changed
>> between vhost0 and eth0 (I.e. after vrouter processed the packet)?
>>
>> Raja
>>
>> From: abhishek jain <[email protected]>
>> Date: Wednesday, September 30, 2015 at 8:41 AM
>> To: Rajagopalan Sivaramakrishnan <[email protected]>
>> Cc: "[email protected]" <[email protected]>, "
>> [email protected]" <[email protected]>
>>
>> Subject: Re: [opencontrail-dev] Checksum offload error with
>> contrail-vrouter-agent running on compute node
>>
>> Hi Raja
>>
>> Below are the inline answers for your queries..
>>
>>
>> Are you seeing any checksum errors go up on the receiver of the ping
>> (using netstat)?
>>
>> The Below fields are incresing at the receiver side when ping is
>> initiated from the compute node running contrail-vrouter-agent..
>>
>>
>> netstat  -s
>>
>> Ip:
>>     4666082 total packets received
>>     4051 with invalid headers
>>     2 with invalid addresses
>>     22 forwarded
>>     0 incoming packets discarded
>>     4558747 incoming packets delivered
>>     4493351 requests sent out
>>     12 outgoing packets dropped
>>     13 fragments dropped after timeout
>>     42 reassemblies required
>>     7 packets reassembled ok
>>     13 packet reassembles failed
>> Icmp:
>>     17279 ICMP messages received
>>     32 input ICMP message failed.
>>     ICMP input histogram:
>>         destination unreachable: 2068
>>         timeout in transit: 14
>>         echo requests: 13570
>>         echo replies: 1627
>>     17190 ICMP messages sent
>>     0 ICMP messages failed
>>     ICMP output histogram:
>>         destination unreachable: 1776
>>         redirect: 12
>>         echo request: 1832
>>         echo replies: 13570
>> IcmpMsg:
>>         InType0: 1627
>>         InType3: 2068
>>         InType8: 13570
>>         InType11: 14
>>         OutType0: 13570
>>        OutType3: 1776
>>         OutType5: 12
>>         OutType8: 1832
>> Tcp:
>>     251330 active connections openings
>>     127809 passive connection openings
>>     118574 failed connection attempts
>>     170 connection resets received
>>     24 connections established
>>     3254207 segments received
>>     3777193 segments send out
>>     11826 segments retransmited
>>     144 bad segments received.
>>
>> The above coloured  field is increasing at the receiver only after ping
>> is initiated from the compute node.
>>
>>
>> Not having the dropstats command on powerpc ubuntu.
>>
>>
>> When we try to run droptstat command, we got the below prints
>> #############################################
>> dropstats
>>
>> Usage: dropstats [--help]
>> Usage: dropstats [--core|-c] <core number>
>>
>> --core <core number>     Show statistics for a specified CPU core
>> ###################################################
>>
>> Then when we analyse the dropstats.c program, we found that it is getting
>> error at the main function itself.
>>
>> The variable "opt" is not getting any valid values, so the switch case is
>> going to the default case and it prints the above prints..
>>
>> When I print the opt value, it is giving some garbage value itseems,
>> ##################################################
>> dropstats
>>
>> OPT VAlue : �
>> Usage: dropstats [--help]
>> Usage: dropstats [--core|-c] <core number>
>>
>> --core <core number>     Show statistics for a specified CPU core
>> ##################################################
>>
>>
>> Please help us regarding this.
>>
>> Thanks
>>
>> On Wed, Sep 30, 2015 at 11:24 AM, Rajagopalan Sivaramakrishnan <
>> [email protected]> wrote:
>>
>>>
>>> >Not having the dropstats command on powerpc ubuntu.
>>>
>>> This should be built when you build vrouter utils. If you have “rt” and
>>> “nh” utilities working, this should work too.
>>>
>>> Are you seeing any checksum errors go up on the receiver of the ping
>>> (using netstat)?
>>>
>>> Please check if any counters are going up corresponding to the reception
>>> of the pings. The absolute values of the counters are not useful.
>>>
>>>  netstat -s
>>> Ip:
>>>     621360 total packets received
>>>     1722 with invalid headers
>>>     2 with invalid addresses
>>>     1 forwarded
>>>     0 incoming packets discarded
>>>     596580 incoming packets delivered
>>>     490572 requests sent out
>>>     1 outgoing packets dropped
>>>     3 fragments dropped after timeout
>>>     8 reassemblies required
>>>     1 packets reassembled ok
>>>     3 packet reassembles failed
>>> Icmp:
>>>     5542 ICMP messages received
>>>     10 input ICMP message failed.
>>>     ICMP input histogram:
>>>         destination unreachable: 180
>>>         timeout in transit: 12
>>>         echo requests: 3730
>>>         echo replies: 1620
>>>     5717 ICMP messages sent
>>>     0 ICMP messages failed
>>>     ICMP output histogram:
>>>         destination unreachable: 180
>>>         redirect: 1
>>>         echo request: 1806
>>>         echo replies: 3730
>>> IcmpMsg:
>>>         InType0: 1620
>>>         InType3: 180
>>>         InType8: 3730
>>>         InType11: 12
>>>         OutType0: 3730
>>>         OutType3: 180
>>>         OutType5: 1
>>>         OutType8: 1806
>>> Tcp:
>>>     46413 active connections openings
>>>     23428 passive connection openings
>>>     21350 failed connection attempts
>>>     45 connection resets received
>>>     42 connections established
>>>     434130 segments received
>>>     431999 segments send out
>>>     938 segments retransmited
>>>     32 bad segments received.
>>>     22332 resets sent
>>> Udp:
>>>     182146 packets received
>>>     21 packets to unknown port received.
>>>     0 packet receive errors
>>>     51965 packets sent
>>> UdpLite:
>>> TcpExt:
>>>     24030 TCP sockets finished time wait in fast timer
>>>     2774 delayed acks sent
>>>     Quick ack mode was activated 154 times
>>>     36 packets directly queued to recvmsg prequeue.
>>>     2176 bytes directly received in process context from prequeue
>>>     68980 packet headers predicted
>>>     4 packets header predicted and directly queued to user
>>>     81153 acknowledgments not containing data payload received
>>>     50692 predicted acknowledgments
>>>     20 times recovered from packet loss by selective acknowledgements
>>>     Detected reordering 2 times using SACK
>>>     Detected reordering 6 times using time stamp
>>>     7 congestion windows fully recovered without slow start
>>>     59 congestion windows partially recovered using Hoe heuristic
>>>     1 congestion windows recovered without slow start by DSACK
>>>     309 congestion windows recovered without slow start after partial ack
>>>     20 fast retransmits
>>>     11 forward retransmits
>>>     11 retransmits in slow start
>>>     584 other TCP timeouts
>>>     1 SACK retransmits failed
>>>     212 DSACKs sent for old packets
>>>     29 DSACKs sent for out of order packets
>>>     240 DSACKs received
>>>     272 connections reset due to unexpected data
>>>     22 connections reset due to early user close
>>>     30 connections aborted due to timeout
>>>     TCPDSACKIgnoredOld: 1
>>>     TCPDSACKIgnoredNoUndo: 50
>>>     TCPSackShiftFallback: 198
>>>     IPReversePathFilter: 120
>>>     TCPRcvCoalesce: 15109
>>>     TCPChallengeACK: 37
>>>     TCPSYNChallenge: 32
>>> IpExt:
>>>     InMcastPkts: 57521
>>>     OutMcastPkts: 4516
>>>     InBcastPkts: 54973
>>>     OutBcastPkts: 521
>>>     InOctets: 128287765
>>>     OutOctets: 58739537
>>>     InMcastOctets: 14558645
>>>     OutMcastOctets: 372894
>>>     InBcastOctets: 7484935
>>>     OutBcastOctets: 92175
>>>
>>>
>>>
>>>
>>> On Wed, Sep 30, 2015 at 11:08 AM, Rajagopalan Sivaramakrishnan <
>>> [email protected]> wrote:
>>>
>>>> Hi Abhishek,
>>>>    Are you still able to ping when the agent is not running?  Did you
>>>> try using “dropstats" to see if there are any drops inside vrouter?
>>>> Are you seeing any checksum errors go up on the receiver of the ping
>>>> (using netstat)?
>>>>
>>>> Raja
>>>>
>>>> From: Dev <[email protected]> on behalf of abhishek
>>>> jain <[email protected]>
>>>> Date: Tuesday, September 29, 2015 at 10:50 AM
>>>> To: "[email protected]" <[email protected]>, "
>>>> [email protected]" <[email protected]>
>>>> Subject: Re: [opencontrail-dev] Checksum offload error with
>>>> contrail-vrouter-agent running on compute node
>>>>
>>>> CCing Omartsyniuk
>>>>
>>>> On Tue, Sep 29, 2015 at 7:36 PM, abhishek jain <[email protected]>
>>>> wrote:
>>>>
>>>>> Hi Team
>>>>>
>>>>>
>>>>> We are getting checksum error from the powerpc  ubuntu 32 bit as
>>>>> compute node when the contrail-voruter-agent userspace agent is running
>>>>> after ping is initiated from the compute node.Please find the attached
>>>>> screanshot for the same.We have  disabled checksum offload at both eth0 as
>>>>> well as vhost0 on the powerpc ubuntu.
>>>>>
>>>>>
>>>>>
>>>>> *ethtool -K eth0 tx off   ethtool -k vhost0 | grep checksum  *
>>>>> rx-checksumming: off [fixed]
>>>>> tx-checksumming: off
>>>>>         tx-checksum-ipv4: off [fixed]
>>>>>         tx-checksum-ip-generic: off [fixed]
>>>>>         tx-checksum-ipv6: off [fixed]
>>>>>         tx-checksum-fcoe-crc: off [fixed]
>>>>>         tx-checksum-sctp: off [fixed]
>>>>>
>>>>>
>>>>> However still we are not able ping the outside world with
>>>>> contrail-vrouter-agent binary running and we are facing same ipv4 checksum
>>>>> offload incorrect error when we capture packets after ping is initiated
>>>>> from the compute node.
>>>>>
>>>>> Do we need to make changes in contrail-vrouter-agent code regarding
>>>>> this?
>>>>>
>>>>>
>>>>> Please help regarding this.
>>>>> Thanks
>>>>>
>>>>
>>>>
>>>
>>
>
_______________________________________________
Dev mailing list
[email protected]
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

Reply via email to