HPE Nimble with Windows 10

[EWidjaya]

Hi amazing people.

Need enlightenment from you.

So, i have to set up HPE Nimble Storage.

My first time using iSCSI.

I'm able to connect to web management and do several stuff. Such as.

- creating folder

- creating volume

- updating the NimbleOS.

Now, i want to connect this storage to windows 10. for trial. before going to production using Windows server 2019.

I use iSCSI initiator.  up to this point. I'm able to discover the device and see it on the favorite targets. but for some reason cannot see the volume. even though i already created 2 volumes using the web console.

when i set up the nimble storage, i only have 2 cables for management.

i don't have cable for the data yet. is this the one that caused it?

really appreciate your help.

[Sheldon Smith]

I think it's a limitation of Windows 10. Be aware Windows 10 is not a supported host OS. Depending on the version of NimbleOS on the array, it will support various versions of Windows Server. 
Windows Server 19 is supported by select versions of NimbleOS 5.0.x and later. Installing the HPE Storage Toolkit for Windows on the Windows Server 19 host is Best Practice. 

Let's see how things are set up. SSH to the Nimble and capture the output of
array --list
to show the version of NimbleOS on the array.

I suspect there may be just one network defined which is doing both management and data. 
nic --list
netconfig --info active
For each subnet shown in the netconfig command, capture the output of
subnet --info subnet_label
Note the subnet labels are case-sensitive. (As are all names on the Nimble).

[EWidjaya]

Hi Sheldon here it is

array --list
---------------------+-----------------+-----------+----------------+-----------
Name Serial Model Version Status
---------------------+-----------------+-----------+----------------+-----------
Nimble AF-232940 HF20 6.1.1.100-1013503-opt reacha ble
Nimble OS $ clear
Nimble OS $ array --list
---------------------+-----------------+-----------+----------------+-----------
Name Serial Model Version Status
---------------------+-----------------+-----------+----------------+-----------
Nimble AF-232940 HF20 6.1.1.100-1013503-opt reachable
Nimble OS $ nic --list
---------+---------+---------+-----------------+----------------+-------------
Name Link Link MAC Subnet IP Addresses
Status Speed
A/B A/B
---------+---------+---------+-----------------+----------------+-------------
eth0a up/up 10G/10G A4:BF:01:7A:24:D9 management 192.168.2.61, 192.168.2.61, 192.168.2.61, 192.168.2.62, 192.168.2.63, 192.168.2.64
eth0b down/down -/- A4:BF:01:7A:24:DA management 192.168.2.65
eth1a down/down -/- B4:96:91:B0:20:14 management 192.168.2.66
eth1b down/down -/- B4:96:91:B0:20:16 management 192.168.2.67
Nimble OS $ netconfig --info active
Group Management IP: 192.168.2.61
Group leader array: Nimble
Member array(s): Nimble
ISCSI Automatic connection method: Yes
ISCSI Connection rebalancing : Yes

Routes:
---------------+---------------+---------------
Destination Netmask Gateway
---------------+---------------+---------------
0.0.0.0 0.0.0.0 192.168.2.1

Subnets:
------------------------+------------------+---------+---------------+----+-----
Label Network Type Discovery IP VLAN MTU
------------------------+------------------+---------+---------------+----+-----
management 192.168.2.0/24 Mgmt,Data 192.168.2.61 0 1500

Array Network Configuration: Nimble
Controller A IP: 192.168.2.62
Controller B IP: 192.168.2.63
---------+------------------------+---------------+------
NIC Subnet Label Data IP Address Tagged
---------+------------------------+---------------+------
eth0a management 192.168.2.64 No
eth0b management 192.168.2.65 No
eth1a management 192.168.2.66 No
eth1b management 192.168.2.67 No

Nimble OS $ subnet --info management
Label: management
Network/Masklen: 192.168.2.0/24
Type: Mgmt,Data
Allow iSCSI: Yes
Allow group: Yes
Network Affinity Zone Type: Single
Discovery IP: 192.168.2.61
VLAN Id: 0
MTU: 1500
Failover: Enabled
Failover Enable Time: N/A

[Sheldon Smith]

At the moment, management and iSCSI is all over a single 10Gb connection: eth0a on controller A (the Active controller).
For link redundancy, consider connecting both eth0b ports and adding them to the "management" subnet as well.

Ultimately as a Best Practice, you would have two switches, with all four eth*A ports going to one switch, and all four eth*B ports going to the other switch.

You could even take it further, setting up a second subnet, perhaps call it "data", give it the Data characteristic and assign the eth1* ports to that. Then change the management subnet to only Mgmt. That will give the iSCSI traffic dedicated ports (eth1a and eth1b).

Have you contacted Nimble Support?

[Thomas_Lam_HK]

As mentioned, it's not a good idea using Windows client as it missing MPIO component.  

Just disregard on the multipathing but solely on connecitivty, I just did a quick simulation on Win10 and able to connect the array''s volume over iSCSI.

Have you check if all entries in "iSCSI initiator" as well as host assignment are correct?

[EWidjaya · Accepted solution]

Hi everyone

its solved thanks.

I'm able to attached it. 

the windows 10 is only for test purpose. eventually i will use it for citrix xen