Hi Tim,
Today Tim Rice wrote:
> On Tue, 21 Jan 2014, Tobias Oetiker wrote:
>
> > Hi,
> >
> > we are serving ISCSI volumes from our omnios box ... in the log on
> > the client I keep seeing this pattern every few hours.
> >
> > any idea what could be causing this ?
> >
> > server and client are directly via a crossover cable over a dedicated
> > interface.
>
> It might be a good idea to tell the list what network cards you are using.
> If they are 1G cards and you are using a Cat 5e cable, do yourself a
> favor and replace it with a Cat 6 cable.
sure, we have intel on-board controllers
07:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection
(rev 01)
Subsystem: Intel Corporation Device 3584
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at d0960000 (32-bit, non-prefetchable)
I/O ports at 1060
Memory at d09b0000 (32-bit, non-prefetchable)
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [70] MSI-X: Enable+ Count=10 Masked-
Capabilities: [a0] Express Endpoint, MSI 00
Capabilities: [e0] Vital Product Data
the cable issue I have to verify ...
the odd thing about this behaviour is, that there are several kvm
virtual machines running on this box as well, and even when omnios
goes 'offline' the kvm hosts (talking over the same physical
interface) are still reachable. They themselfs can not talk to
omnios either ...
cheers
tobi
> > Jan 21 01:21:34 iscsi-client kernel: : [1048707.604535] connection1:0:
> > ping timeout of 5 secs expired, recv timeout 5, last rx 4557604012, last
> > ping 4557605264, now 4557606516 [kern.err]
> > Jan 21 01:21:34 iscsi-client kernel: : [1048707.604656] connection1:0:
> > detected conn error (1011) [kern.info]
> > Jan 21 01:21:34 iscsi-client kernel: : [1048707.604661] connection2:0:
> > ping timeout of 5 secs expired, recv timeout 5, last rx 4557604012, last
> > ping 4557605264, now 4557606516 [kern.err]
> > Jan 21 01:21:34 iscsi-client kernel: : [1048707.604763] connection2:0:
> > detected conn error (1011) [kern.info]
> > Jan 21 01:21:35 iscsi-client iscsid: Kernel reported iSCSI connection 1:0
> > error (1011) state (3) [daemon.warning]
> > Jan 21 01:21:35 iscsi-client iscsid: Kernel reported iSCSI connection 2:0
> > error (1011) state (3) [daemon.warning]
> > Jan 21 01:21:57 iscsi-client kernel: : [1048713.496478] nfs: server
> > 10.10.10.1 not responding, still trying [kern.notice]
> > Jan 21 01:21:57 iscsi-client kernel: : [1048717.843552] nfs: server
> > 10.10.10.1 not responding, still trying [kern.notice]
> > Jan 21 01:21:57 iscsi-client kernel: : [1048718.087086] nfs: server
> > 10.10.10.1 not responding, still trying [kern.notice]
> > Jan 21 01:21:57 iscsi-client kernel: : [1048730.558551] nfs: server
> > 10.10.10.1 OK [kern.notice]
> > Jan 21 01:21:57 iscsi-client kernel: : [1048730.559623] nfs: server
> > 10.10.10.1 OK [kern.notice]
> > Jan 21 01:21:57 iscsi-client kernel: : [1048730.559654] nfs: server
> > 10.10.10.1 OK [kern.notice]
> > Jan 21 01:21:59 iscsi-client iscsid: connection1:0 is operational after
> > recovery (2 attempts) [daemon.warning]
> > Jan 21 01:21:59 iscsi-client iscsid: connection2:0 is operational after
> > recovery (2 attempts) [daemon.warning]
> >
> > chers
> > tobi
> >
>
>
--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch t...@oetiker.ch ++41 62 775 9902 / sb: -9900
_______________________________________________
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss
