VMware NSX

 View Only
  • 1.  Jumbo pings between transport node vtep and edge vm vtep failing

    Posted Sep 27, 2019 01:42 AM

    Setup

    I have two transport nodes and one edge VM.  The transport nodes vteps are 172.16.1.10 and 172.16.1.11 and The edge node vm vtep is 172.16.1.15.

    Issue

    Jumbo pings between transport nodes vteps works, whereas between transport node and edge vm fails.

    Jumbo ping dump between transport nodes vteps:-

    [root@srv104-26a:~] vmkping ++netstack=vxlan 172.16.1.10 -c 5 -s 9000

    PING 172.16.1.10 (172.16.1.10): 9000 data bytes

    9008 bytes from 172.16.1.10: icmp_seq=0 ttl=64 time=0.993 ms

    9008 bytes from 172.16.1.10: icmp_seq=1 ttl=64 time=0.886 ms

    9008 bytes from 172.16.1.10: icmp_seq=2 ttl=64 time=0.932 ms

    9008 bytes from 172.16.1.10: icmp_seq=3 ttl=64 time=0.872 ms

    9008 bytes from 172.16.1.10: icmp_seq=4 ttl=64 time=0.841 ms

    --- 172.16.1.10 ping statistics ---

    5 packets transmitted, 5 packets received, 0% packet loss

    round-trip min/avg/max = 0.841/0.905/0.993 ms

    Jumbo ping dumps between transport node vtep and edge vm vtep

    [root@srv104-26a:~] vmkping ++netstack=vxlan 172.16.1.15 -c 5 -s 9000

    PING 172.16.1.15 (172.16.1.15): 9000 data bytes

    --- 172.16.1.15 ping statistics ---

    5 packets transmitted, 0 packets received, 100% packet loss

    Regular ping dumps between transport node vtep and edge vm vtep

    [root@srv104-26a:~] vmkping ++netstack=vxlan 172.16.1.15 -c 5

    PING 172.16.1.15 (172.16.1.15): 56 data bytes

    64 bytes from 172.16.1.15: icmp_seq=0 ttl=64 time=0.734 ms

    64 bytes from 172.16.1.15: icmp_seq=1 ttl=64 time=0.845 ms

    64 bytes from 172.16.1.15: icmp_seq=2 ttl=64 time=0.851 ms

    64 bytes from 172.16.1.15: icmp_seq=3 ttl=64 time=0.644 ms

    64 bytes from 172.16.1.15: icmp_seq=4 ttl=64 time=0.689 ms

    --- 172.16.1.15 ping statistics ---

    5 packets transmitted, 5 packets received, 0% packet loss

    round-trip min/avg/max = 0.644/0.753/0.851 ms

    Probable Root Cause

    I observed Dropped No Memory counters incremented during jumbo frame pings. Any inputs in resolving this issue would be of great help.

    hqnsxtedge03(vrf)> get stats

    Logical Router

    UUID        : 736a80e3-23f6-5a2d-81d6-bbefb2786666

    VRF         : 0

    LR-ID       : 0

    Name        :

    Type        : TUNNEL

    Statistics

        Dropped No Memory             : 115

        Dropped No Route              : 0

    hqnsxtedge03(vrf)> get stats

    Logical Router

    UUID        : 736a80e3-23f6-5a2d-81d6-bbefb2786666

    VRF         : 0

    LR-ID       : 0

    Name        :

    Type        : TUNNEL

    Statistics

        Dropped No Memory             : 118

        Dropped No Route              : 0

    hqnsxtedge03(vrf)> get stats

    Logical Router

    UUID        : 736a80e3-23f6-5a2d-81d6-bbefb2786666

    VRF         : 0

    LR-ID       : 0

    Name        :

    Type        : TUNNEL

    Statistics

        Dropped No Memory             : 119

        Dropped No Route              : 0

    Thanks

    Mahi



  • 2.  RE: Jumbo pings between transport node vtep and edge vm vtep failing
    Best Answer

    Broadcom Employee
    Posted Sep 27, 2019 03:02 AM

    Take a look at this kb: VMware Knowledge Base

    ---------------------------------------------------------------------------------------------------------

    Was it helpful? Let us know by completing this short survey here.



  • 3.  RE: Jumbo pings between transport node vtep and edge vm vtep failing

    Posted Oct 02, 2019 05:53 PM

    Thanks a lot mauricioamorim.