iSCSI initiator group

[Olivia_Petrisak]

Hi Everyone, 

This could be a very stupid question but how could I create new iSCSI initiator group? I am only able to put there WWPN, but not the iSCSI IQN. 

I am maybe compleatly wrong, but on the Pure storage it works the way that I create a host and then choose add IQNs/WWNs/NQNs. 

Am I missing some configuration?

Thank you so much for any suggestions.

Olivia

[support_s]

System recommended content:

1. HPE StoreOnce 3660, 5260 and 5660 Systems User Guide for StoreOnce software version 4.3.x | Configuring the iSCSI software initiator manually using the command line

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[Olivia_Petrisak]

But those are steps for host side. I have IQN, and need to kno where to put it on Nimble.

[Olivia_Petrisak]

I tried to create iSCSI initiator group with CLI:

initiatorgrp --create PBC1 --access_protocol iscsi

And got this error:

iSCSI service is not available in current group configuration.

In the administration/network/active/interfaces/IP I have configured  iSCSI.

[CSOST]

Log on to the Nimble Storage Web interface.
1) click on "Manage" on the menu bar at the top of the screen,.
2) click on "Data Access".
3) click on the "+" (plust sign) to create a new initiator group.
    You will have a field to enter in the IQN name.

[Olivia_Petrisak]

That is the problem, that I have only field for WWPN, not for IQN.

[Sahana_S]

Hi @Olivia_Petrisak 

First, create an initiator group using the command below command:

initiatorgrp --create group_name

Then add initiators to that group using the below command:

 initiatorgrp --add_initiators group_name --initiator_name iqn..... --ipaddr 00.00.000.000

I hope you found this useful!

Please mark as solution accepted if this post answers your query.

[Olivia_Petrisak]

Nimble OS $ initiatorgrp --create PBC1

Nimble OS $ initiatorgrp --add_initiators PBC1 --initiator_name iqn.1991-05.com.microsoft:ukcpex02.rws.com --label PBC1
ERROR: Failed to add initiator(s). Incompatible access protocol between initiator and initiator group.

Nimble is awaiting WWPN, so when I put there IQN, it didn't accept it.

[Sheldon Smith]

It may be more fundamental. While the storage arrays can support iSCSI and FC, based on the data ports it normally has only one protocol enabled.
At the CLI, enter "group --info | grep enabled", and look for both FC and iSCSI. Is iSCSI enabled?

Note that a given volume can be accessed by only one protocol, either FC or iSCSI, not both.
Likewise a given initiator group can have either WWNs or IQNs not both.

[Olivia_Petrisak]

@Sheldon Smith Dear Sheldon,

looks like you were right. 

Nimble OS $ group --info | grep enabled
iSNS enabled: No
SNMP trap enabled: No
SNMP get enabled: No
Syslogd enabled: No
Alarm enabled: Yes
TLSv1.0/1.1 enabled: Yes
Common Criteria mode enabled: No

Please, is there a single command to enable iSCSI, or there is much more which needs to be set up?

Thank you

[Sheldon Smith]

Hmm. Not seeing either an "FC enabled" (yes or no) or :"iSCSI enabled" (yes or no).

The array needs at least be running NimbleOS 5.1.1.0.
Prior to NimbleOS 5.1.1.0, a Nimble Storage array could use either FC or iSCSI but not both.
It looks like you need to update the firmware on the array..

1. What model of Nimble Storage array do you have?
2. Does it have a Support contract to allow it to download the firmware?

[Sunitha_Mod]

Hello @Olivia_Petrisak,

Let us know if you were able to resolve the issue.

If you have no further query and you are satisfied with the answer then kindly mark the topic as Solved so that it is helpful for all community members.

[Olivia_Petrisak]

Today our Nimble was upgraded to the latest version and now it looks like this:

Nimble OS $ group --info | grep enabled
Auto cleanup of unmanaged Snapshots enabled: No
iSNS enabled: No
SNMP trap enabled: No
SNMP get enabled: No
Syslogd enabled: No
cloud enabled: No
iSCSI enabled: No
FC enabled: Yes
Alarm enabled: Yes
TLSv1.0/1.1 enabled: Yes
Common Criteria mode enabled: No
Software Subscription enabled: Yes

Subnet for iSCSI is configured, but I can't find anything about, how iSCSI should be enabled.
Model is HF-40

[Olivia_Petrisak · Accepted solution]

Command FOUND!

group --edit --iscsi_enabled yes

[Sunitha_Mod]

Hello @Olivia_Petrisak,

Perfect! 

We are extremely glad to know your were able to find the solution and we appreciate you for keeping us posted. 

[Sheldon Smith]

And remember, a given volume can be accessed by only one protocol, either FC or iSCSI, not both.

To switch, the volume needs to be unmounted, then removed from access. Change access to hosts using the other protocol and re-mount the volume.