On 11/12/2010 01:54 PM, macmike wrote:
I'm running RHEL5 kernel 2.6.18 in a VM under VMware ESX 4.0.0,
What version of rhel5 and what kernel (uname -a will tell you the kernel). I think you just need to update the kernel. Some modules would mark a iscsi ping/nopout/noop_out as failed too quickly.
# Time interval to wait for on connection before sending a ping. node.conn[0].timeo.noop_out_interval = 5 # To specify the time to wait for a Nop-out response before failing # the connection, edit this line. Failing the connection will # cause IO to be failed back to the SCSI layer. If using dm-multipath # this will cause the IO to be failed to the multipath layer. node.conn[0].timeo.noop_out_timeout = 5
You also might want to increase these values. In one case it looked like it did take a while to get logged back in, so it might have been a valid problem.
You can reset those values by setting them in iscsid.conf then rediscoverying your targets or run
iscsiadm -m node -o update -n node.conn[0].timeo.noop_out_interval -v your_new_value iscsiadm -m node -o update -n node.conn[0].timeo.noop_out_timeout -v your_new_value
-- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
