S
Sheen Ismhael A. Lim
I have a Windows Server 2016 with 2 NICs.
1 for Management with address
IP: 10.0.0.11
SM: 255.255.255.0
GW:10.0.0.1
1 for iSCSI with address
IP: 10.0.1.10
SM: 255.255.255.0
GW: NONE
I have one Cisco Switch
E0/0 - connects to the Windows Server Management Port (VLAN 1)
E0/1 - connects to the Windows Server iSCSI Port (VLAN 10)
E1/0 - connects to a ESXI-1 Management port (VLAN 1)
E1/1 - connects to a ESXI-1 iSCSI port (VLAN 10)
E2/0 - connects to a ESXI-2 Management port (VLAN 1)
E2/1 - connects to a ESXI-2 iSCSI port (VLAN 10)
Interface VLAN 10 on the Cisco Switch has an IP 10.0.1.2
iSCSI port of the ESXI-1 has an IP of 10.0.1.101
iSCSI port of the ESXI-2 has an IP of 10.0.1.102
Now, theoretically, traffic for 10.0.1.X on the Windows Server (iSCSI Server) should use its 10.0.1.10 NIC to communicate to the ESXi's iSCSI Port. Here the kicker,
Ping to 10.0.1.2
C:\Users\Administrator>ping 10.0.1.2
Pinging 10.0.1.2 with 32 bytes of data:
Reply from 10.0.1.2: bytes=32 time=2ms TTL=255
Reply from 10.0.1.2: bytes=32 time=1ms TTL=255
Reply from 10.0.1.2: bytes=32 time=1ms TTL=255
Reply from 10.0.1.2: bytes=32 time=1ms TTL=255
Ping statistics for 10.0.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms
Ping to 10.0.1.101
C:\Users\Administrator>ping 10.0.1.101
Pinging 10.0.1.101 with 32 bytes of data:
Reply from 10.0.1.101: bytes=32 time=2ms TTL=64
Reply from 10.0.1.101: bytes=32 time=2ms TTL=64
Reply from 10.0.1.101: bytes=32 time=1ms TTL=64
Reply from 10.0.1.101: bytes=32 time=1ms TTL=64
Ping statistics for 10.0.1.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms
Ping to 10.0.1.102
C:\Users\Administrator>ping 10.0.1.102
Pinging 10.0.1.102 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 10.0.1.102:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Now, I though it was an issue with the ESXI 10.0.1.102, as i diagnose it I could not find any issue. so I tried to tracert test from iSCSI Server (Window Server) and here's what I've got
C:\Users\Administrator>tracert -d 10.0.1.101
Tracing route to 10.0.1.101 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 10.0.1.101
Trace complete.
C:\Users\Administrator>tracert -d 10.0.1.102
Tracing route to 10.0.1.102 over a maximum of 30 hops
1 3 ms 10 ms 9 ms 10.0.0.1
2 17 ms * 19 ms 192.168.137.1
3 * * * Request timed out.
4 16 ms 20 ms 21 ms 192.168.1.1
5 26 ms 33 ms 31 ms 100.83.0.1
6 * ^C
Why is traffic for my 10.0.1.102 going through the management nic of the iSCSI server? What I do not understand is that 10.0.1.101 and 10.0.1.102 is on the same subnet and VLAN with 10.0.1.10, why does windows server uses a different path for a IP that is basically on the same subnet on one of its NIC?
Below is the route print result on the iSCSI Server.
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.0.0.1 10.0.0.12 271
10.0.0.0 255.255.255.0 On-link 10.0.0.12 271
10.0.0.12 255.255.255.255 On-link 10.0.0.12 271
10.0.0.255 255.255.255.255 On-link 10.0.0.12 271
10.0.1.0 255.255.255.0 On-link 10.0.1.10 16
10.0.1.10 255.255.255.255 On-link 10.0.1.10 271
10.0.1.255 255.255.255.255 On-link 10.0.1.10 271
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 10.0.1.10 271
224.0.0.0 240.0.0.0 On-link 10.0.0.12 271
255.255.255.255 255.255.255.255 On-link 127.0.0.1 331
255.255.255.255 255.255.255.255 On-link 10.0.1.10 271
255.255.255.255 255.255.255.255 On-link 10.0.0.12 271
===========================================================================
For God, and Country.
Continue reading...
1 for Management with address
IP: 10.0.0.11
SM: 255.255.255.0
GW:10.0.0.1
1 for iSCSI with address
IP: 10.0.1.10
SM: 255.255.255.0
GW: NONE
I have one Cisco Switch
E0/0 - connects to the Windows Server Management Port (VLAN 1)
E0/1 - connects to the Windows Server iSCSI Port (VLAN 10)
E1/0 - connects to a ESXI-1 Management port (VLAN 1)
E1/1 - connects to a ESXI-1 iSCSI port (VLAN 10)
E2/0 - connects to a ESXI-2 Management port (VLAN 1)
E2/1 - connects to a ESXI-2 iSCSI port (VLAN 10)
Interface VLAN 10 on the Cisco Switch has an IP 10.0.1.2
iSCSI port of the ESXI-1 has an IP of 10.0.1.101
iSCSI port of the ESXI-2 has an IP of 10.0.1.102
Now, theoretically, traffic for 10.0.1.X on the Windows Server (iSCSI Server) should use its 10.0.1.10 NIC to communicate to the ESXi's iSCSI Port. Here the kicker,
Ping to 10.0.1.2
C:\Users\Administrator>ping 10.0.1.2
Pinging 10.0.1.2 with 32 bytes of data:
Reply from 10.0.1.2: bytes=32 time=2ms TTL=255
Reply from 10.0.1.2: bytes=32 time=1ms TTL=255
Reply from 10.0.1.2: bytes=32 time=1ms TTL=255
Reply from 10.0.1.2: bytes=32 time=1ms TTL=255
Ping statistics for 10.0.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms
Ping to 10.0.1.101
C:\Users\Administrator>ping 10.0.1.101
Pinging 10.0.1.101 with 32 bytes of data:
Reply from 10.0.1.101: bytes=32 time=2ms TTL=64
Reply from 10.0.1.101: bytes=32 time=2ms TTL=64
Reply from 10.0.1.101: bytes=32 time=1ms TTL=64
Reply from 10.0.1.101: bytes=32 time=1ms TTL=64
Ping statistics for 10.0.1.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms
Ping to 10.0.1.102
C:\Users\Administrator>ping 10.0.1.102
Pinging 10.0.1.102 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 10.0.1.102:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Now, I though it was an issue with the ESXI 10.0.1.102, as i diagnose it I could not find any issue. so I tried to tracert test from iSCSI Server (Window Server) and here's what I've got
C:\Users\Administrator>tracert -d 10.0.1.101
Tracing route to 10.0.1.101 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 10.0.1.101
Trace complete.
C:\Users\Administrator>tracert -d 10.0.1.102
Tracing route to 10.0.1.102 over a maximum of 30 hops
1 3 ms 10 ms 9 ms 10.0.0.1
2 17 ms * 19 ms 192.168.137.1
3 * * * Request timed out.
4 16 ms 20 ms 21 ms 192.168.1.1
5 26 ms 33 ms 31 ms 100.83.0.1
6 * ^C
Why is traffic for my 10.0.1.102 going through the management nic of the iSCSI server? What I do not understand is that 10.0.1.101 and 10.0.1.102 is on the same subnet and VLAN with 10.0.1.10, why does windows server uses a different path for a IP that is basically on the same subnet on one of its NIC?
Below is the route print result on the iSCSI Server.
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.0.0.1 10.0.0.12 271
10.0.0.0 255.255.255.0 On-link 10.0.0.12 271
10.0.0.12 255.255.255.255 On-link 10.0.0.12 271
10.0.0.255 255.255.255.255 On-link 10.0.0.12 271
10.0.1.0 255.255.255.0 On-link 10.0.1.10 16
10.0.1.10 255.255.255.255 On-link 10.0.1.10 271
10.0.1.255 255.255.255.255 On-link 10.0.1.10 271
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 10.0.1.10 271
224.0.0.0 240.0.0.0 On-link 10.0.0.12 271
255.255.255.255 255.255.255.255 On-link 127.0.0.1 331
255.255.255.255 255.255.255.255 On-link 10.0.1.10 271
255.255.255.255 255.255.255.255 On-link 10.0.0.12 271
===========================================================================
For God, and Country.
Continue reading...