MPIO Setup (iSCSI Target Portals Question)

[Sean Patterson_1]

Is it best to use the single Discovery IP address for the Target Portal, or use each Interface IP as Target Portals when setting up for MPIO.

Discovery IP: 192.168.110.20

Interface IPs:     192.168.110.21

192.168.210.22

192.168.110.23

192.168.210.24

I am running the Script to setup the MPIO, and set it both ways as a test. Discovery IP setups 4 paths where using each setup 16 paths. Which is correct?

[Nick_Dyer · Accepted solution]

In 1.4.x it's best to use the Discovery IP address as the target portal, although it is entirely possible to discover iSCSI volumes through any physical data port from the Nimble array.

In Nimble OS 2.0 we introduce the idea of Virtual Target IP addresses which allow for a bit more flexibility of discovering and MPIO'ing volumes through Windows and VMware, through a toolset called Nimble Connection Manager (so no more scripting for MPIO). If you're interested give your local SE a shout. You can also pull down the document for these tools from Infosight->Downloads now, although PLEASE do not install the 2.0 Windows or VMware toolkits unless you have access to 2.0 firmware on your array.

[ajb716100]

So what if the system is Linux? Which address would you use? Also, would it matter if this was a boot partition target?