Connecting MSA 2050 to Windows Server 2016 by SFP+

[Limo]

Hello, 
I am having problem connecting followings to each other:
MSA 2050 SFF Storage array
HPE DL380 gen10 with HPE 530SFP+ 10Gb Network card for connetion to storage (no HBA card present)
HPE  Aruba J9283d SFP+ DAC Cable.

All the tutorials i found explain how to connect MSA to server using HBA card, but i have only SFP+ card with me. Can I connect using SFP+?
The operating system used is Windows Server 2016. when i connect MSA to my network card they can ping each other, but i can't make them see each other in MSA SMU.
Just checking on Windows server but need to connect ESXi to MSA finally.

Loolinig for tutorial how to connect MSA to iSCSI SFP+ with OS WinServer and ESXi
Thanx in advance

[ArunKKR]

Hi,

As per HPE SPOCK compatibility document direct connection is only supported between Proliant NIC cards and Windows 2016. However, direct connection is not supported between ESXI and Proliant NIC cards 

Compatibility matrix is available for download at the below link:

https://h20272.www2.hpe.com/SPOCK/index.aspx?lang=en&cc=in&hpappid=117135_SPOCK_PRO_HPE

Select Configuration Set ZIP Files under the topic "SAN Compatibility" on the left side of the page.
Click on download next to HPE MSA 2050/2052 iscsi Storage.

Extract the downloaded zip file and it will contain the pdf files with information for each supported operating system version.

Have you tried launching windows iscsi initiator and connecting to MSA controller host port IP address?

This will ensure that the host server shows up in MSA SMU interface.

[ArunKKR]

Hi,

Please let us know whether the information shared helped.

[Shawn_K]

Hello,

The HPE 530SFP+ 10Gb Network card is not supported with the MSA product line. Additionally, direct connect is not supported with ESXi for iSCSI. 

The HPE  Aruba J9283d SFP+ DAC Cable is supported with the MSA but not the SPP+ card. 

You need to get into a more supported hardware solution to ensure you have full connectivity. Please refer to SPOCK as mentioned.

I work for Hewlett Packard Enterprise. The comments in this post are my own and do not represent an official reply from HPE. No warranty or guarantees of any kind are expressed in my reply.

Cheers,
Shawn