Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 17 Nov 2017 10:30:11 +0200
From:      Daniel Braniss <danny@cs.huji.ac.il>
To:        "Patrick M. Hausen" <hausen@punkt.de>
Cc:        Freebsd hackers list <freebsd-hackers@freebsd.org>, =?utf-8?Q?Edward_Tomasz_Napiera=C5=82a?= <trasz@freebsd.org>, stable@freebsd.org
Subject:   Re: iscsi target and VMware/esxi timeouts -- SOLVED
Message-ID:  <E56F0449-0503-49FC-956B-6D6F41AF3F89@cs.huji.ac.il>
In-Reply-To: <6B1A4A67-D0E9-4A73-B690-60A52D144F81@punkt.de>
References:  <7779629C-A1E5-4E96-B660-A0FAD231468C@cs.huji.ac.il> <6B1A4A67-D0E9-4A73-B690-60A52D144F81@punkt.de>

next in thread | previous in thread | raw e-mail | index | archive | help


> On 14 Nov 2017, at 11:28, Patrick M. Hausen <hausen@punkt.de> wrote:
>=20
> Hello,
>=20
>> Am 14.11.2017 um 10:08 schrieb Daniel Braniss <danny@cs.huji.ac.il>:
>>=20
>> Hi,
>> we are experimenting issues with several esxi=E2=80=99s servers that =
use freebsd 10.2 stable as a iscsi target.
>> ie:
>> Nov 11 17:58:16 store-07 kernel: WARNING: 132.65.11.201 =
(iqn.1998-01.com.vmware:pe-02-2fa7cd9e): no ping reply (NOP-Out) after 5 =
seconds; dropping connection
>> Nov 11 17:58:16 store-07 kernel: WARNING: 132.65.11.201 =
(iqn.1998-01.com.vmware:pe-02-2fa7cd9e): no ping reply (NOP-Out) after 5 =
seconds; dropping connection
>> Nov 11 17:58:16 store-07 kernel: WARNING: 132.65.11.205 =
(iqn.1998-01.com.vmware:pe-03-13e8b52d): no ping reply (NOP-Out) after 5 =
seconds; dropping connection
>> Nov 11 17:58:17 store-07 kernel: WARNING: 132.65.11.203 =
(iqn.1998-01.com.vmware:pe-13-60e87d06): no ping reply (NOP-Out) after 5 =
seconds; dropping connection
>> Nov 11 17:58:17 store-07 kernel: WARNING: 132.65.11.205 =
(iqn.1998-01.com.vmware:pe-03-13e8b52d): no ping reply (NOP-Out) after 5 =
seconds; dropping connection
>>=20
>> these are 3 different esxis that almost at the same time the target =
looses connection to the initiators.
>> at the moment most =E2=80=98clients=E2=80=99  recover from the scsi =
error, but older freebsds don=E2=80=99t.
>>=20
>> in any case, increasing the timeout is not helping.
>>=20
>> any clues are welcome :-)
>>=20
>> over the weekend i=E2=80=99m planning to upgrade the target to 11.1 =
and take for the hills.
>=20
> Are you using istgt or ctld?
>=20
> We have did experience similar occasional problems with the former
> but never with the latter.
>=20
> Patrick

the iscsi initiator of the esxi=E2=80=99s (VMware) does answer to =
NOP=E2=80=99s once in a blue moon!
this was checked by sniffing the network.

setting kern.cam.ctl.iscsi.ping_timeout=3D0 solved this.

thanks,
	danny





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E56F0449-0503-49FC-956B-6D6F41AF3F89>