Date: Tue, 14 Nov 2017 11:08:55 +0200 From: Daniel Braniss <danny@cs.huji.ac.il> To: Freebsd hackers list <freebsd-hackers@freebsd.org>, =?utf-8?Q?Edward_Tomasz_Napiera=C5=82a?= <trasz@FreeBSD.org> Cc: stable@freebsd.org Subject: iscsi target and VMware/esxi timeouts Message-ID: <7779629C-A1E5-4E96-B660-A0FAD231468C@cs.huji.ac.il>
next in thread | raw e-mail | index | archive | help
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 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. in any case, increasing the timeout is not helping. any clues are welcome :-) over the weekend i=E2=80=99m planning to upgrade the target to 11.1 and = take for the hills. danny
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7779629C-A1E5-4E96-B660-A0FAD231468C>