sammybendover wrote:i did get mpio working, i had to use CHAP to restric what ip to what initiator (weird?) i would expect this to be an option of the target, not under security.
Also, i had to manually create every MPIO connection myself, that is alot more work that i am used to compared to microsoft iscsi target or OpenIndiana.
Performance seemed decent, i have a raw disk raid 0 device presented into iscsi, i get about 495 MB/sec write, and 492 MB/sec read through 4 1GbE links via atto disk benchmark
Could you please explain in more details what exactly would you like to change in StarWind Management console?
Right now it is possible:
1) Set CHAP authentication for StarWind management connection (TCP 3261 port).
These are server-side and management console side settings:
1.a)Configuration->under Server Settings ->Management Interface -> Authentication Parameters ->Modify
1.b) Configuration->under Management Console Settings ->Management Interface -> Authentication Parameters ->Modify
Note: Be aware 1.b case can be performed only if the Management Console is disconnected from the StarWind server.
You should conform server-side and management console side settings manually. The default authentication type is basic. To use CHAP authentication: modify server-side authentication parameters settings specifying necessary auth type with chap name and chap secret (1a), disconnect form the server, modify management console side auth settings specifying the same auth type and the same chap name and chap secret.
It works in such way because several StarWind servers can be managed remotely with single StarWind Management Console and 1.a and 1.b steps are server-dependent. I mean you can add several StarWind servers in the Managemet console and set different auth settings for each of them.
2) Set Global CHAP permission for all iSCSI targets. It will be applied for existing targets and for the newly created ones.
Targets -> CHAP Permissions
In order to connect the target you should specify "Enable CHAP log on" (example for MS iSCSI initiator) and specify the CHAP credentials (the same as you provided under Targets -> CHAP Permissions)
3) Set Per-target CHAP permissions.
Under the Target List click the target you are going to set CHAP permissions. Look lower. You will see: Devices, iSCSI Sessions and CHAP Permissions tabs. Switch to the CHAP Permissions tab.
Specify the necessary CHAP settings.
In order to connect the target you should specify "Enable CHAP log on" (example for MS iSCSI initiator) and specify the CHAP credentials.
4) Set High Availability device CHAP permissions.
If you use CHAP for HA devices, they are also used for synchronization connections.
So, in order to set CHAP auth:
4.a) On the first HA node set the Global or Per-target CHAP (as described above)
4.b) On the second HA node under the Target List select the necessary target, look down at Devices tab, right click over the HA device and select Change Partner Authentication Settings; In the wizard that appears select the Partner (the one you have set the Global or Per-target CHAP permissions), under authentication type select CHAP and specify the same credentials.
4.c) Repeat the same steps for other HA Partners.
StarWind also has Access Rights settings where you can restrict client initiator connections by IP, DNS Name or IQN.
Please let us know if you have any questions or suggestions.
Could you please also clarify with more details and examples about MPIO connection in StarWind compared to compared to microsoft iscsi target or OpenIndiana.
