santunez2275
Enthusiast
Enthusiast

Test Parameters GUI NSX vCenter Failed

Jump to solution

Hello Guys

In my environment run the Logical Switch Test:

The source is node1 and destination is node2

The size of test packet is VXLAN Standard

Now in the GUI show

Packets sent by node1

Not all packets received by node2

Now I run the esxcli network diag ping --netstack=vxlan --host 172.23.0.66 --size=1572

Received Bytes: 1580

         Host: 172.23.0.66

         ICMP Seq: 0

         TTL: 64

         Round-trip Time: 300 us

         Dup: false

         Detail:

         Received Bytes: 1580

         Host: 172.23.0.66

         ICMP Seq: 1

         TTL: 64

         Round-trip Time: 281 us

         Dup: false

         Detail:

         Received Bytes: 1580

         Host: 172.23.0.66

         ICMP Seq: 2

         TTL: 64

         Round-trip Time: 268 us

         Dup: false

         Detail:

   Summary:

         Host Addr: 172.23.0.66

         Transmitted: 3

         Recieved: 3

         Duplicated: 0

         Packet Lost: 0

         Round-trip Min: 268 us

         Round-trip Avg: 282 us

         Round-trip Max: 299 us

Now my doubts is with the LS Switch is correct because by cli not show lost packets

Regards

0 Kudos
1 Solution

Accepted Solutions
rajeevsrikant
Expert
Expert

Good.

It should be issue related to GUI which i have observed in NSX version 6.2.2

Since the CLI output is as expected, its fine. It will not be an issue.

View solution in original post

0 Kudos
3 Replies
rajeevsrikant
Expert
Expert

Which version of NSX you are running.

I do had faced this problem earlier, when trying via GUI it shows that packets are not received.

But via CLI observed no packet loss.  It was looking more like the GUI error

Can you try with the size of 1600 via cli & check the output ?

0 Kudos
santunez2275
Enthusiast
Enthusiast

Hello

The versión is 6.3.5

I chech to 1600 and the result is OK by cli.

0 Kudos
rajeevsrikant
Expert
Expert

Good.

It should be issue related to GUI which i have observed in NSX version 6.2.2

Since the CLI output is as expected, its fine. It will not be an issue.

0 Kudos