MSA 2050 Direct attached iSCSI

[Alexey_78]

Hello All,

We are trying to bring up configuration if Del server with vSphere 6.5 and MSA 2050
I am trying to verify connection by just ping host port IP on MSA

On both vSphere and MSA it shows both ports are up and connected.

For configuration I did

On vSphere with Add Network Wizard >> VMkernel >> Create a standard switch and selected the NIC that connect direct to the MSA
Identified IP in same subnet as MSA port A1.
Trying to test connection by ping of that IP without any success.

MSA connected with Dell server with  HPE X240 10G SFP+ SFP+ 1.2m DAC Cable.
MSA equipped with HPE MSA 10Gb SR iSCSI SFP 4pk XCVR
Dell server NIC is DELL X520DA2: Intel 10 GB , Dual Port Karte, SFP+

Anything that I forgot?

[SupreetK]

For starters, ping by default will use the management network. If your storage network is different, use vmkping to ping the MSA IP via the storage vmkernel port.

vmkping -I vmkX MSA-IP - where vmkX is the storage vmkernel port

Cheers,

Supreet

[Alexey_78]

But if I run

tcpdump-nw -I vmk1 msa-ip

during ping I see arp packets asking where msa-ip is.

vmk0 that is managment interface.

vmk1 assigned to separate vswitch with physical device coonected to MSA .

So it does look it already use right interface for ping.

[daphnissov]

It would be very helpful to see screenshots of your host's networking configuration and vmkernel ports.

[Alexey_78]

Sure.

Here is

On MSA

A1 iSCSI iqn.2015-11.com.hpe:storage.msa2050.18173c3ac3 Up 10Gb OK

Port Details
------------
IP Version: IPv4
IP Address: 172.16.1.1
Gateway: 172.16.1.10
Netmask: 255.255.255.0
MAC: 00:C0:FF:47:B2:F4

A2 iSCSI iqn.2015-11.com.hpe:storage.msa2050.18173c3ac3 Up 10Gb OK

Port Details

------------

IP Version: IPv4

IP Address: 172.16.2.1

Gateway: 172.16.2.10

Netmask: 255.255.255.0

MAC: 00:C0:FF:47:B2:F5

On ESX as well configured IPs from same subnets for vmk interfaces

IPs are configured by pairs
MSA A1 - VMK-1-A1   172.16.1.1 - 172.16.1.11   (2,3,4 subnets used for A2,3,4)

MSA B1 - VMK-1-B1   172.16.5.1 - 172.16.5.11 (6,7,8 subnets used for B2,3,4)

Screenshot with VMKernel adapters attached

[Alexey_78]

IP connectivity issue is solved guys

It appears local man did not connected cables as described

Swapped A and B

After I've asked to keep only one cable all become clear.