After you successfully set up your logical switch and attach VMs to the logical switch, you can test the network connectivity of the attached VMs.
If your network environment is configured properly, based on the topology the App2 VM can ping the App1 VM.
Procedure
- Log in to one of the VMs attached to the logical switch using SSH or the VM console.
For example, App2 VM 172.16.20.11.
- Ping the second VM attached to the logical switch to test connectivity.
$ ping -c 2 172.16.20.10
PING 172.16.20.10 (172.16.20.10) 56(84) bytes of data.
64 bytes from 172.16.20.10: icmp_seq=1 ttl=63 time=0.982 ms
64 bytes from 172.16.20.10: icmp_seq=2 ttl=63 time=0.654 ms
64 bytes from 172.16.20.10: icmp_seq=3 ttl=63 time=0.791 ms
--- 172.16.20.10 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1990ms
rtt min/avg/max/mdev = 0.654/0.809/0.902/0.104 ms
- (Optional) Identify the problem that causes the ping to fail.
- Verify that the VM network settings are correct.
- Verify that the VM network adapter is connected to the correct logical switch.
- Verify that the logical switch Admin status is UP.
- From the NSX Manager, select .
- Click the logical switch and note the UUID and VNI information.
- Run the following commands to troubleshoot the problem.
Command |
Description |
get logical-switch <vni-or-uuid> arp-table |
Displays the ARP table for the specified logical switch.
Sample output.
nsx-manager1> get logical-switch 41866 arp-table
VNI IP MAC Connection-ID
41866 172.16.20.11 00:50:56:b1:70:5e 295422
|
get logical-switch <vni-or-uuid> connection-table |
Displays the connections for the specified logical switch.
Sample output.
nsx-manager1> get logical-switch 41866 connection-table
Host-IP Port ID
192.168.110.37 36923 295420
192.168.210.53 37883 295421
192.168.210.54 57278 295422
|
get logical-switch <vni-or-uuid> mac-table |
Displays the MAC table for the specified logical switch.
Sample output.
nsx-manager1> get logical-switch 41866 mac-table
VNI MAC VTEP-IP Connection-ID
41866 00:50:56:86:f2:b2 192.168.250.102 295421
41866 00:50:56:b1:70:5e 192.168.250.101 295422
|
get logical-switch <vni-or-uuid> stats |
Displays statistics information about the specified logical switch.
Sample output.
nsx-manager1> get logical-switch 41866 stats
update.member 11
update.vtep 11
update.mac 4
update.mac.invalidate 0
update.arp 7
update.arp.duplicate 0
query.mac 2
query.mac.miss 0
query.arp 9
query.arp.miss 6
|
get logical-switch <vni-or-uuid> stats-sample |
Displays a summary of all logical switch statistics over time.
Sample output.
nsx-manager1> get logical-switch 41866 stats-sample
21:00:00 21:10:00 21:20:00 21:30:00 21:40:00
update.member 0 0 0 0 0
update.vtep 0 0 0 0 0
update.mac 0 0 0 0 0
update.mac.invalidate 0 0 0 0 0
update.arp 0 0 0 0 0
update.arp.duplicate 0 0 0 0 0
query.mac 0 0 0 0 0
query.mac.miss 0 0 0 0 0
query.arp 0 0 0 0 0
query.arp.miss 0 0 0 0 0
|
get logical-switch <vni-or-uuid> vtep |
Displays all virtual tunnel end points related to the specified logical switch.
Sample output.
nsx-manager1> get logical-switch 41866 vtep
VNI IP LABEL Segment MAC Connection-ID
41866 192.168.250.102 0x8801 192.168.250.0 00:50:56:65:f5:fc 295421
41866 192.168.250.100 0x1F801 192.168.250.0 02:50:56:00:00:00 295420
41866 192.168.250.101 0x16001 192.168.250.0 00:50:56:64:7c:28 295422
|
Results
The first VM attached to the logical switch is able to send packets to the second VM.