Once you have configured your network, you can verify the connectivity from the CLI of the ESXi server. To do that, connect to your ESXi server using SSH (don't forget to start the SSH service if you have not done so already) and issue the vmkping command.

The following IP addresses should be accessible:

[root@esxi-prod-1:~] vmkping 192.168.10.1
 PING 192.168.10.1 (192.168.10.1): 56 data bytes
 64 bytes from 192.168.10.1: icmp_seq=0 ttl=128 time=0.285 ms
 64 bytes from 192.168.10.1: icmp_seq=1 ttl=128 time=0.281 ms

[root@esxi-prod-1:~] vmkping 192.168.10.2
 PING 192.168.10.2 (192.168.10.2): 56 data bytes
 64 bytes from 192.168.10.2: icmp_seq=0 ttl=128 time=0.302 ms
 64 bytes from 192.168.10.2: icmp_seq=1 ttl=128 time=0.200 ms

If any of the servers are not responding, make sure that the Windows Firewall is not blocking the communication.

You can also check the ARP table of the ESXi server by using the following command:

[root@esxi-prod-1:~] esxcli network ip neighbor list
 Neighbor Mac Address Vmknic Expiry State Type
 ------------ ----------------- ------ -------- ----- -------
 172.16.1.250 00:0c:29:ec:1c:12 vmk0 858 sec Unknown
 172.16.1.1 00:0c:29:3f:6f:3d vmk0 1099 sec Unknown
 172.16.1.2 00:0c:29:ad:b5:d4 vmk0 1102 sec Unknown
 192.168.10.2 00:0c:29:95:16:36 vmk2 1096 sec Unknown
 192.168.10.1 00:0c:29:95:16:40 vmk2 1088 sec Unknown

At this stage, you should be able to access all the network resources of our lab. It's time to take a look at the storage configuration.