6.5.1

In this example, all initiator ports and the target portal are configured in the same subnet. The target is
reachable through all bound ports. You have four VMkernel ports and one target portal, so total of four
paths are created.
Without the port binding, only one path is created.
Example 2. Multiple paths with VMkernel ports in different subnets
You can create multiple paths by configuring multiple ports and target portals on different IP subnets. By
keeping initiator and target ports in different subnets, you can force ESXi to create paths through specific
ports. In this configuration, you do not use port binding because port binding requires that all initiator and
target ports are on the same subnet.
192.168.1.1/24
vmk1 SP/Controller A:
Port 0: 192.168.1.10/24
Port 1: 192.168.2.10/24
SP/Controller B:
Port 0: 192.168.1.11/24
Port 1: 192.168.2.11/24
vmnic1
192.168.2.1/24
vmk2
vmnic2
IP
Network
ESXi selects vmk1 when connecting to Port 0 of Controller A and Controller B because all three ports are
on the same subnet. Similarly, vmk2 is selected when connecting to Port 1of Controller A and B. You can
use NIC teaming in this configuration.
Total of four paths are created.
Paths Description
Path 1 vmk1 and Port0 of Controller A
Path 2 vmk1 and Port0 of Controlled B
Path 3 vmk2 and Port1 of Controller A
Path 4 vmk2 and Port2 of Controller B
Routing with Software iSCSI
You can use the esxcli command to add static routes for your iSCSI traffic. After you configure static
routes, initiator and target ports in different subnets can communicate with each other.
Example 1. Using static routes with port binding
In this example, you keep all bound vmkernel ports in one subnet (N1) and configure all target portals in
another subnet (N2). You can then add a static route for the target subnet (N2).
vSphere Storage
VMware, Inc. 91