ReadyNas 3200 Raidator 4.2.21

[lovekevin]

Hi,

We have two of ReadyNAS 3200 connected to VMware ESXi/ESX server.
I checked log file on ESX server and found out that iscsi is disconnected frequently. So I upgraded to 4.2.20 and 4.2.21.
I did ping test on this storage and saw a lot of RX dropped down.
So I downgraded it to 4.2.19 but still we have a this problem.



Ping TEST
Reply from 137.52.210.8: bytes=32 time<1ms TTL=63
Request timed out.
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Request timed out.
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time<1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Request timed out.
Reply from 137.52.210.8: bytes=32 time<1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Request timed out.
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time<1ms TTL=63
Request timed out.
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Request timed out.
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Request timed out.
Request timed out.
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Request timed out.
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Request timed out.
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Request timed out.
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63
Reply from 137.52.210.8: bytes=32 time<1ms TTL=63
Reply from 137.52.210.8: bytes=32 time=1ms TTL=63

ESX messages.log file
Jul 5 15:54:33 localhost vobd: Jul 05 15:54:33.916: 712463074645us: [esx.problem.vmfs.heartbeat.recovered] 4ff537c4-9a4a094d-74c5-00a0d1e6e47e unsfarm1.
Jul 5 15:54:33 localhost vobd: Jul 05 15:54:33.934: 712463092187us: [esx.problem.vmfs.heartbeat.recovered] 4ff5380f-1a17477e-36e1-00a0d1e6e47e unsfarm2.
Jul 5 15:54:51 localhost vobd: Jul 05 15:54:51.859: 712481016918us: [esx.problem.vmfs.heartbeat.timedout] 4ff5380f-1a17477e-36e1-00a0d1e6e47e unsfarm2.
Jul 5 15:54:51 localhost vobd: Jul 05 15:54:51.861: 712481019364us: [esx.problem.vmfs.heartbeat.timedout] 4ff537c4-9a4a094d-74c5-00a0d1e6e47e unsfarm1.
Jul 5 15:55:02 localhost vobd: Jul 05 15:55:02.722: 712491885104us: [vob.scsi.scsipath.pathstate.on] scsiPath vmhba34:C0:T0:L0 changed state from dead.
Jul 5 15:55:02 localhost vobd: Jul 05 15:55:02.724: 712491882513us: [esx.clear.storage.connectivity.restored] Connectivity to storage device naa.60014052e30294000b4d001000000000 (Datastores: "unsfarm1") restored. Path vmhba34:C0:T0:L0 is active again..
Jul 5 15:55:02 localhost vobd: Jul 05 15:55:02.726: 712491885310us: [vob.scsi.scsipath.pathstate.on] scsiPath vmhba34:C0:T0:L1 changed state from dead.
Jul 5 15:55:02 localhost vobd: Jul 05 15:55:02.727: 712491885653us: [esx.clear.storage.connectivity.restored] Connectivity to storage device naa.60014052e30294000b4d002000000000 (Datastores: "unsfarm2") restored. Path vmhba34:C0:T0:L1 is active again..
Jul 5 15:55:02 localhost vobd: Jul 05 15:55:02.737: 712491895284us: [esx.problem.vmfs.heartbeat.recovered] 4ff537c4-9a4a094d-74c5-00a0d1e6e47e unsfarm1.
Jul 5 15:55:02 localhost vobd: Jul 05 15:55:02.739: 712491897542us: [esx.problem.vmfs.heartbeat.recovered] 4ff5380f-1a17477e-36e1-00a0d1e6e47e unsfarm2.
Jul 5 15:55:17 localhost vobd: Jul 05 15:55:17.407: 712506568208us: [vob.scsi.scsipath.pathstate.on] scsiPath vmhba34:C0:T0:L0 changed state from dead.
Jul 5 15:55:17 localhost vobd: Jul 05 15:55:17.410: 712506565793us: [esx.clear.storage.connectivity.restored] Connectivity to storage device naa.60014052e30294000b4d001000000000 (Datastores: "unsfarm1") restored. Path vmhba34:C0:T0:L0 is active again..
Jul 5 15:55:17 localhost vobd: Jul 05 15:55:17.412: 712506568214us: [vob.scsi.scsipath.pathstate.on] scsiPath vmhba34:C0:T0:L1 changed state from dead.
Jul 5 15:55:17 localhost vobd: Jul 05 15:55:17.413: 712506568811us: [esx.clear.storage.connectivity.restored] Connectivity to storage device naa.60014052e30294000b4d002000000000 (Datastores: "unsfarm2") restored. Path vmhba34:C0:T0:L1 is active again..
Jul 5 15:55:48 localhost vobd: Jul 05 15:55:48.647: 712537808155us: [vob.scsi.scsipath.pathstate.on] scsiPath vmhba34:C0:T0:L1 changed state from dead.
Jul 5 15:55:48 localhost vobd: Jul 05 15:55:48.649: 712537805626us: [esx.clear.storage.connectivity.restored] Connectivity to storage device naa.60014052e30294000b4d002000000000 (Datastores: "unsfarm2") restored. Path vmhba34:C0:T0:L1 is active again..
Jul 5 15:55:48 localhost vobd: Jul 05 15:55:48.650: 712537808234us: [vob.scsi.scsipath.pathstate.on] scsiPath vmhba34:C0:T0:L0 changed state from dead.
Jul 5 15:55:48 localhost vobd: Jul 05 15:55:48.652: 712537808596us: [esx.clear.storage.connectivity.restored] Connectivity to storage device naa.60014052e30294000b4d001000000000 (Datastores: "unsfarm1") restored. Path vmhba34:C0:T0:L0 is active again..
Jul 5 15:55:48 localhost vobd: Jul 05 15:55:48.670: 712537826398us: [esx.problem.vmfs.heartbeat.recovered] 4ff5380f-1a17477e-36e1-00a0d1e6e47e unsfarm2.
Jul 5 15:55:48 localhost vobd: Jul 05 15:55:48.673: 712537829672us: [esx.problem.vmfs.heartbeat.recovered] 4ff537c4-9a4a094d-74c5-00a0d1e6e47e unsfarm1.
Jul 5 15:56:18 localhost vobd: Jul 05 15:56:18.598: 712567761340us: [vob.scsi.scsipath.pathstate.on] scsiPath vmhba34:C0:T0:L0 changed state from dead.
Jul 5 15:56:18 localhost vobd: Jul 05 15:56:18.601: 712567758691us: [esx.clear.storage.connectivity.restored] Connectivity to storage device naa.60014052e30294000b4d001000000000 (Datastores: "unsfarm1") restored. Path vmhba34:C0:T0:L0 is active again..
Jul 5 15:56:18 localhost vobd: Jul 05 15:56:18.602: 712567761493us: [vob.scsi.scsipath.pathstate.on] scsiPath vmhba34:C0:T0:L1 changed state from dead.
Jul 5 15:56:18 localhost vobd: Jul 05 15:56:18.603: 712567761054us: [esx.clear.storage.connectivity.restored] Connectivity to storage device naa.60014052e30294000b4d002000000000 (Datastores: "unsfarm2") restored. Path vmhba34:C0:T0:L1 is active again..
Jul 5 15:56:18 localhost vobd: Jul 05 15:56:18.633: 712567791341us: [esx.problem.vmfs.heartbeat.recovered] 4ff537c4-9a4a094d-74c5-00a0d1e6e47e unsfarm1.
Jul 5 15:56:18 localhost vobd: Jul 05 15:56:18.635: 712567793335us: [esx.problem.vmfs.heartbeat.recovered] 4ff5380f-1a17477e-36e1-00a0d1e6e47e unsfarm2.


ReadyNas 3200 with Raidator 4.2.21.