Problem with Multipath iscsi with vmware 6.7

Software-based VM-centric and flash-friendly VM storage + free version

Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)

denkteich
Posts: 32
Joined: Fri Jun 07, 2019 7:52 am

Fri Jun 28, 2019 10:28 am

Hi all,
I'Ve received my NFR Version of VSAN for vsphere.
Installation worked fine except that I only have one path to the target.
Multipath seems not to work.

I've set it up using this doc: https://www.starwindsoftware.com/resour ... sphere-6-5

Any suggestions?

TIA
.h
Boris (staff)
Staff
Posts: 805
Joined: Fri Jul 28, 2017 8:18 am

Fri Jun 28, 2019 11:15 am

More details on what exactly is wrong would be helpful.
denkteich
Posts: 32
Joined: Fri Jun 07, 2019 7:52 am

Fri Jun 28, 2019 12:49 pm

I followed the setupp guide, but now i see only one iscsi path to the target.
i should see both vis as paths to the target, i can only see the first one.
Boris (staff)
Staff
Posts: 805
Joined: Fri Jul 28, 2017 8:18 am

Fri Jun 28, 2019 6:20 pm

This description does not throw too much light on the issue.
How many dynamic discovery portals did you add to your iSCSI initiator configuration?
denkteich
Posts: 32
Joined: Fri Jun 07, 2019 7:52 am

Fri Jun 28, 2019 9:27 pm

Bildschirmfoto 2019-06-28 um 23.09.45.png
Bildschirmfoto 2019-06-28 um 23.09.45.png (27.8 KiB) Viewed 7821 times
Bildschirmfoto 2019-06-28 um 23.09.04.png
Bildschirmfoto 2019-06-28 um 23.09.04.png (31.18 KiB) Viewed 7821 times
Bildschirmfoto 2019-06-28 um 23.08.48.png
Bildschirmfoto 2019-06-28 um 23.08.48.png (16.73 KiB) Viewed 7821 times
maybe the pictures show it a little bit better.
nevermeind the iqn's, I've test PetaSAN before and left the dns entries.
denkteich
Posts: 32
Joined: Fri Jun 07, 2019 7:52 am

Sat Jun 29, 2019 7:12 pm

i deleted the target, created a new one, followed the documentation, double checked everything, still only one path to the target.

Any suggestion?
Oleg(staff)
Staff
Posts: 568
Joined: Fri Nov 24, 2017 7:52 am

Tue Jul 02, 2019 5:21 pm

Could you please check Access Rights list in StarWind if this interface is not banned?
denkteich
Posts: 32
Joined: Fri Jun 07, 2019 7:52 am

Wed Jul 03, 2019 8:28 am

all targets, all interfaces, allow
on both servers
denkteich
Posts: 32
Joined: Fri Jun 07, 2019 7:52 am

Thu Jul 04, 2019 7:33 pm

any other suggestion?
having only one path to the device is a single point of failure.
Oleg(staff)
Staff
Posts: 568
Joined: Fri Nov 24, 2017 7:52 am

Fri Jul 05, 2019 8:26 am

Could you please give more details, what networking scheme do you have?
Are you using separated network links and vSwitches for StarWind ISCSI and synchronization traffic?
Do you have VMkernels configured on both vSwitches for ISCSI connections?
denkteich
Posts: 32
Joined: Fri Jun 07, 2019 7:52 am

Fri Jul 05, 2019 3:18 pm

1 vswitch for the vmnetwork / Management
1 vswitch for the iscsi network with 1 kernel port on each host
1 vswitch for mirror
danswartz
Posts: 71
Joined: Fri May 03, 2019 7:21 pm

Fri Jul 05, 2019 6:02 pm

This is odd, indeed. I am running ESXi 6.7 with the same setup. I have both paths visible. Have you confirmed the windows firewall on the invisible host is not somehow blocking iSCSI?
denkteich
Posts: 32
Joined: Fri Jun 07, 2019 7:52 am

Fri Jul 05, 2019 7:26 pm

i'm using the version which runs on linux, it was imported via a ova.

I'm able to ping each svsan machine from each host using the vmkernel adapter.
Boris (staff)
Staff
Posts: 805
Joined: Fri Jul 28, 2017 8:18 am

Fri Jul 05, 2019 9:47 pm

Can you confirm you can ping each of these?
- StarWind VM1 to StarWind VM2 over the iSCSI link;
- host 1 to host 2 over the iSCSI vmkernel;
- StarWind VM1 to host 1 vmkernel and host 2 vmkernel (iSCSI;
- StarWind VM2 to host 2 vmkernel and host 1 vmkernel (iSCSI);

You may well end up having issues pinging one of the iSCSI VMkernels (the one on host 2). If that's the case, a host reboot is what is going to help you. Starting from ESXi 6.5 onwards, it's no longer possible to reboot a VMKernel for a specific adapter without rebooting the whole ESXi host.
denkteich
Posts: 32
Joined: Fri Jun 07, 2019 7:52 am

Sat Jul 06, 2019 2:47 pm

Host1 storage vmkernel adapter: 172.16.16.7
Host2 storage vmkernel adapter: 172.16.16.8
SW VM1 iscsi adapter: 172.16.16.181
SW VM2 iscsi adapter: 172.16.16.182

- StarWind VM1 to StarWind VM2 over the iSCSI link;
sometimes...
- host 1 to host 2 over the iSCSI vmkernel;
yes
- StarWind VM1 to host 1 vmkernel and host 2 vmkernel (iSCSI;
yes
- StarWind VM2 to host 2 vmkernel and host 1 vmkernel (iSCSI);
sometimes...

i think i found a trace....
the hosts are connected with nic-teaming
looks like the teaming is not running right.
I'll start investigating here...

thanks for the help so far.
Post Reply