pswitch iSCSI connection

Similar Questions

• EqualLogic iSCSI connection limit exceeded - implications?

  We have an EqualLogic SAN iSCSI which exceeded the limits of iSCSI connections. The limit is 1024, but we in 1612. The thing is that nothing seems to be affected. We can still add LUN/servers etc. We are likely to hit the problems? A kind of performance problem? There only seems to be a lot of documentation to anywhere! We are firmware 5.2.2.

  I don't know what we can do to reduce the number of connections, I want to know, is what happens if we don't? Because I can say nothing serious happened. We ignore it? Panic?

  Hello

  Joe is correct, it is very important that you respect the limits of the support of the table.  For you convenience, I suggest you upgrade to EQL FW 6.0.4 and HIT or MEM products for later upgrade.  Firmware 6.x and products current EQL MPIO now work together to better manage connections.  Especially when you are above the limit.  This coordination allows to automatically reduce the number of connections.

  I wonder if you use VMware ESX?   We see quiite often with ESX.  There are a number of strategies to reduce the number of without loss of performance.

  Feel free to open a folder from supported with Dell.   We can examine your environment and make specific recommendations to correct this problem.

  It is very important that you take into account of this.

  Kind regards

• Can I use VDS with LACP to reduce on group SAN iSCSI connections?

  I'm trying to reduce the number of iSCSI connections to my EqualLogic storage group. I currently use a standard vSwitch with two ports vmk by server for SAN. Can I use a single vmk with VDS/LACP to reduce my by half by server iSCSI connections and still maintains band bandwidth/redundancy?

  I'm quite confident, it will work, but hoped for validation. Please correct me if I'm totally turned off, or if it would be not supported.

  My volumes cover several physical devices (20 paths for 7 volumes by iSCSI adapter). Can I assume that with load balancing on an OFFSET of the source and destination hash value, I would get at least some balancing between adapters?

  If you have several points of termination targets L2 - 4, Yes. For example an IP address, MAC address, unique ports or. Paths, volumes and devices are not relevant to the LACP.

  If I don't choose a LAG, I can't visualize how it would reduce my iSCSI for my storage pool connections. I'm setting targets on my Broadcom cards, the vmk connects through these cards. Is the logic that is smart enough to only connect the active paths on an adapter or another in an OFFSET? I do know that I have make sense more that I might have to play with a SHIFT on a host isolated for a bit and see exactly how it will behave.

  The adapters are more exposed. The LAG is a logical interface. Traffic can be sent or received through any physical adapter in the GAL.

  Note: I would not use an OFFSET for iSCSI on a vSphere host traffic: seriously, Stop Using Port channels for vSphere storage traffic. Wahl network

• ISCSI connection failure causing ESXi 5.1 VMs at the stop

  Hi all

  At the hope that someone may have seen the problem that we encountered during the last 2 weeks.

  Our virtual machines are performing unexpected stops. Our Exchange Server rebooted twice today

  The closing time is information that we see our Equallogic logs:

  INFO APCEQLM1 09:35:19 7.2.15 26/07/2013. 7.2.24 | 7.2.29 session iSCSI to target '192.168.43.12:3260, iqn.2001-05.com.equallogic:4-52aed6-c7ca4349e-87b00217be35059e-lon-prod-vm-1' initiator ' 192.168.43.31:58797, iqn.1998 - 01.com.vmware:apcesxhost1 - 24c73c18 "was closed. | iSCSI initiator login failure. | No response on the connection for 6 seconds.

  We have 1 Equallogic PS4100X, run the latest firmware EQL 6.0.5. We have 2 switches Powerconnect 6224 stacked. Our table and switches are configured by DELL support.

  We followed the recommendations of DELL on vSphere storage ISCSI connection. I see that our vSwitches are correctly configured.

  Someone has any ideas why we find that this behavior? I have connected this with the support of DELL, but thought I would ask on the forums in case someone knows that it emits.

  Thanks in advance!

  Lee

  Hi Julie,.

  My apologies, I thought that I had updated this discussion with the fix. It was related to a problem of driver on one of our hosts. I logged a call with VMWare and they got the answer very quickly. The problem was our host NETWORK interface card tg3 driver. I've followed this article to resolve the problem:

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=2035701

  I hope it is of some use to you!

  Thank you

  Lee

• iSCSI connection

  Can someone give me an idea about the best way to configure my connection iSCSI in vMware?

  I'm under ESXi 4.1. I have three ESX host. On each host, I have two other network connections to the outside for each host. It is advisable to configure a vmkernal port, assign an IP address and use a one as the main network connection and the other as secondary or load balancing, both.

  Or and im not having a chance at this moment doing this... install a second port of vmkernal using a separate virtual switch, assign it a second ip address and having only one main connection on for each virtual switch. Give me two connections to my iSCSI SAN for each host.

  Thank you

  Wayne

  Hi Wayne,

  The best way is to have a unique vSwitch with two other cards attached physical. Then, create two VMkernel ports for iSCSI connections. Take a look at the next section for a full description of this type of configuration.

  It will be useful.

  Concerning

  Franck

• Fabric of interconnection to Bay iSCSI connection

  I need to connect my fabric for interconnection to a new array of iSCSI.  There are a number of blades UCS that need to connect to iSCSI LUNS. The FI is currently connected to the rest of the network through switches to Nexus 7000 K.   Should I I plugged directly from the FI to the iSCSI array or go through the 7000 K and then to the table?

  Hi, this is more a matter of design, you need to think about what will need access to the storage ISCCI matrix. For example, if a single UCS blaes will have access to this storage group, you can consider plug directly such as iscsi traffic must pass your N7Ks if the two fabrics are active. If you want another type of server such as HP or IBM to access storage, you should consider to connect the storage array to the N7Ks if your tissues are configured in end-host mode. Again, this will depend on your current implementation

• groups and iSCSI connections to ports

  Hello

  We have a 5.1 esx server connected to an iSCSI-based storage device.

  the server is connected using two of the vmkernal iscsi ports.  each network card has a different ip address on the private iscsi vlan.  the configuration is according to the practices of bast vm using only one network by vmkernal port card.

  We have a migration of storage to another storage but I still have to intall it.  I would like to know if its possible to create two groups of ports additional vmkernal using the same NIC already connected to the iscsi storage.  new port groups on one vlan separate and different netwok so go looking, it seems right that I share two NICs for two networks different iscsi.

  as mentioned above, that I have not installed the hardware yet, but to test it a bit it looks like I can add groups of ports by using the network card and I was able to bind to the vmhbaxx with the adapter of storage with the path of staus as not used.  so I hope that when I connect the new buffer I would be if all goes well able to connect once I place a discovery?

  any comments welcome.

  Thank you

  I don't see why you shouldn't be able to do what you describe. It's a little unusual, but it should work to create adapters to VMK several on the same vSwitch and make the same active/unused configuration you already made, but put other id VLAN and IP address on the new adapters. Of course the two logical VMK adapters share the same network link, but you are fully aware of.

  As long as it is not indicated in some manual or KB article as a solution not supported, you should be fine.

• Differences between the ISCSI connections to the storage in vSphere 4.1 and 5.0.

  I'm in trouble of setting up the connections of storage in a new VSphere 5.0 test environment. In our environment VSphere 4.1, it was possible to create a virtual switch add two Broadcom NetXtreme II 5709 NIC. Set assets. IP Hash value as load balancing. (LACP Etherchannel on physical switches) This configuration uses a grain port and a single IP address. Then add our NetApp NFS storage and ISCSI Equillogic storage. In VSphere 5.0, I can't create this same configuration. I have to create separate with separate IP addresses vmkernal ports? The idea was to have redundant connections to the storage and flow of these two NETWORK cards. Possibly adding additional if necessary to the futuer NETWORK cards. Any help with this would be greatly appreciated.

  How can I work around this:

  "VMkernel network adapter must have an active link exactly and no waiting rising to be eligible for the iSCSI HBA connection."

  I can certainly say that the way which allows you to configure the iSCSI Multipathing is incorrect.

  The main idea is to let Native Multipathing Plugin to decide what network path to choose, not the vSwitch.

  At the level of the network layer, you must have 1 VMK by a physical NIC.

  This technique applies as well for vSphere 4.1 and 5.0, but with the 5.0 it is configured easier and more quickly.

  Here's a very brief consequence of steps

  1. get 2 VMK interfaces and assign an IP by each VMK.

  2. set each VMK to use only one physical NETWORK adapter

  3 GB with storage iSCSI software adapter, turn it on and bind your VMKs 2.

  4 connect to your iSCSI storage space

  5 rescan devices, create the VMFS datastore

  6. set the desired load balancing VMFS method or just set up a prior default create new VMFS

  and it is strongly recommended to read this guide - http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-storage-guide.pdf

• The host Isolation response / loss of iSCSI connectivity - what if scenario

  The other thread on automatic shutdown made me think at our facility:

  1. when our building lost power, we lose cooling and networking, but remains on our servers/UPS systems, as they are connected to a backup generator.

  2 Yah, so, it's not good, cooling is lost, and the servers are will heat up, then we must begin to stop them until the coolant has been restored.

  Our 2 ESX systems connect to our SAN via iSCSI - with the lost power, the SAN and the ESX servers are no longer speaks, so I turned off our ESX servers, until the coolant has been restored, as no negative consequences on the correct virtual machines?

  With the connection of networking\iSCSI lost between ESX servers and SAN, that State will be our being for most Windows virtual machines?  They're going to be trashed?  Or ESX has some kind of verification in place for this type of ailment?

  In our current situation, what would be the recommended host Isolation response parameter?

  Thanks for any idea,

  Chad

  Our 2 ESX systems connect to our SAN via iSCSI - with the lost power, the SAN and the ESX servers are no longer speaks, so I turned off our ESX servers, until the coolant has been restored, as no negative consequences on the correct virtual machines?

  It shouldn't - but this will depend on all wht that the VM, the operating system and the application were doing at the time of the accident-

  With the connection of networking\iSCSI lost between ESX servers and SAN, that State will be our being for most Windows virtual machines? They're going to be trashed? Or ESX has some kind of verification in place for this type of ailment?

  ESX does not check this condition - from your virtual machines is on the iSCSI SAN you will find crashed.

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful

• ISCSI connected storage / access it from windows / backup

  Hello

  I have successfully created a cluster of ESX Server images computer virtual running of a LUN iSCSI on the network plan. However to support this until I need to be able to access these images from a windows machine.

  I installed the windows on windows iSCSI initiator and connected successfully. However, windows cannot read the formatted file as its VMFS3 system.

  IM only using standard backup for the moment software and intended to stop the VM machines one night to do it. However with no windows is unable to read the file system I can't.

  Read VMFS I need special backup software running or have I missed something?

  Thanks for the help

  Hello

  You will need to have VCB (VMware consolidated backup) installed on the Windows computer, this will help you in the backup.

  Thank you

  Samir

  PS: If you consider this answer useful please consider rewarding points

• All share storage iscsi connect same target and volume

  Hi Alls,

  I have openfiler and do 1 iscsi volume share in two ESX hosts with even described as iscsi target.

  So a (first) ESX have dynamic config discover iscsi target and the format of finishing, so ESX block size have new data store come from iscsi.

  Another ESX must sign in with the same ip address of the iscsi target and even target iqn. then discover iscsi and rescan datastore have see the name of name identical to that found on ESX first data store.

  (Note for second ESX is not block format size but rescan HBAS/VMSF found eponymous store data like first ESX)

  Issue.

  1. for iscsi target that have one objective and correspond to a volume on openfiler can operate with 2 ESXs at the same time with the same target?

  2 if not, how to configure shared storage with openfiler that can used data volume on openfiler?

  Kind regards

  Bancha

  Like I said before, vMotion can saturate an uplink, so you will need to keep an eye on it. If you want to perform vMotion on the same vSwitch anyway, I suggest you create a group of separate ports with private IP (e.g. 192.168.x.y) addresses for her and let the two active vmnic for this group of ports allow failover in the event of an uplink failure.

  André

• VCB server with both FC and iSCSI connections

  Hello.

  Anyone know if a VCB implementation that has the FC and iSCSI LUN presented to the proxy server is possible/supported?  I see no technical reason that it wouldn't work, but I'm trying to understand whether or not this is a supported configuration.

  Thank you!

  I don't see why that would be a question of a standpoing of features, but if you didn't mind the performance hit you just the business day following mode of transport and not worry present LUNS.   I guess that maybe in the same way hotadd would work as well.

  If you have found this device or any other useful post please consider the use of buttons useful/correct to award points

• Failed to connect ISCSI Linux

  Hi all

  I have EQL 6210, box 3

  6210-1S

  2-6210-X

  3-6210-E

  Several volumes are mounted with windows and linux blade servers.

  a specific volume is mounted with linux based on physical server and SAP DB is running on it.

  I get messages in the MISTLETOE Group Manager "ISCSI connection to the target of the copycat was closed, ISCSI, Reset connection failure received on the connection: for this SAP DB volume.» Snapshot is attached.

  Please help identify and resolve the problem.

  Hello

  These resets are from the Linux server.  This can be caused by a bad configuration.

  Please see this PDF on RHEL/OEL configuration with Dell PS berries.

  http://en.community.Dell.com/TechCenter/Extras/m/white_papers/20442422?utm_source=release%20announcement&utm_medium=email&utm_campaign=document%20release

  Some clients have seen a reduction in these areas by increasing delays in the etc/iscsi/iscsid.conf file.

  # To specify the time-out to abort before answer
  # operation failed and try a reset of the logical unit change the line.
  # The value is in seconds, and the default value is 15 seconds.
  node.session.err_timeo.abort_timeout = 30

  # To specify the time-out period of a logical unit response
  # before the operation failed and trying recovery session
  # Change the line.
  # The value is in seconds, and the default value is 30 seconds.
  node.session.err_timeo.lu_reset_timeout = 60

  # To specify the timeout waiting for a response from target
  # before the operation failed and trying recovery session
  # Change the line.
  # The value is in seconds, and the default value is 30 seconds.
  node.session.err_timeo.tgt_reset_timeout = 60

  You can see that just increase one.

  Note: Editing this file does NOT spread downwards for all existing volumes.  You must find all the volumes after each change in the etc/iscsi/iscsid.conf file.

  You have opened a case of pension?    Latency on the network can also cause these resets.

  How EQL firmware revision are you currently using?

  Kind regards

  Don

• Connections iSCSI how much should I see?

  Hi all

  Also posted here - iscsi connections how do I see?-Spiceworks and here - communities.vmware.com/.../520622

  Running ESXi 5.5 and a PS4100X Equallogic, hoping someone point me in the right direction on something I noticed.

  Recently installed a MD3220i (https://community.spiceworks.com/topic/1114594-iscsi-port-binding-daft-question)

  After start installation and connection iSCSI can be quite long (as expected by using binding with several subnets iSCSI ports) but my question is not related to this.

  I came today to see what I can do to improve the time of starting, perhaps using static rather than dynamic discovery, and I noticed something weird.

  The Equallogic we have 2 NIC, 10.11.14.1 and 10.11.14.2. When using dynamic discovery I enter the IP address of the Group (10.11.14.253) and I get 8 connections, one for each IP address on the ESXi hosts to each IP addresses on the equallogic, see screenshot iscsi1.png

  Any fine.

  If I then switch to static and put 2 entries in by the data store (one for each NETWORK card on the equallogic) (see the screenshot iscsi2.png) then what I see in the equallogic is 16 connections to the host. Each data store is connected twice for each NETWORK card on the host, everyone via network cards on the equallogic, see screenshot iscsi3.png.

  I don't know if it's better or worse! I have several paths, so it should be better? Or I have many paths, and the system will get confused?

  Thank you

  Hello

  The best option to avoid the delay is for something like the broadcom iSCSI adapter unloading.  ISCSI S/W adapter would be bound to network adapters for volumes MD, (or bind something here and use several subnets rather) the unloading adapter would then manage the EQL triaffic.   This prevents the long startup delay since all related network cards trying to reach the defined all discovery addresses.

  I have never tried to use only addresses static w/ESXi, so I can't really talk about why you get the additional connections.  Unless it still makes a discovery, or the old static entries were still there after you have changed static.

  Kind regards

  Don

• connection iSCSI delivers or not?

  Hello,
  
  I'm encountering some issues with iscsi connections in my vSphere environment and my Equallogic group and wondering if I could get some input from you all. I'm curious to know if what I'm seeing is an Equallogic MEM or NLB event or if I actually have some type of issue. Here's a bit about my environment:
  
  3-ESXi Hosts - 5.0 U1 (623860)Each host has four 1Gbps cards dedicated to the iSCSI network (2 Intel and 2 Broadcom).Storage Heartbeat VMK configured and is the lowest vmk on vSwitch.Delayed ack is disabled.Dell MEM 1.1.2 installed
  
  2-HP 2910al-24g switches4 ports are dedicated to a LACP trunk group for the interswitch connectionjumbo frames enabledflow control enablediSCSI VLAN is not VLAN 1Switch logs look good with very few drops or errors.
  
  One Equallogic group with two PS4100's (One PS4100X and One PS4100XV).Both arrays on FW 5.2.2Dedicated management network.Latency looks good across the group.TCP Retransmits very low <0.1%
  
  Should I expect to see the re-balance event noted in the vmkernel.log file? From other logs I've seen online, it appears as if they all show an entry that states a re-balance request has been received from the array, but I'm not seeing that in my logs. I've provided the relevant entries from both the Equallogic group and vSphere host below. Thanks.
  
  Jake
  
  The informational events that have me somewhat concerned are logged on the group as:
  
  Severity Date and Time Member Message -------- ------------------- --------------- ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------  INFO 5/16/13 12:08:41 PM PS4100X-0 iSCSI session to target '192.168.90.103:3260, iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f' from initiator '192.168.90.53:56744, iqn.1998-01.com.vmware:VHOST05-484f029e' was closed. Logout request was received from the initiator.  INFO 5/16/13 12:08:40 PM PS4100X-0 iSCSI login to target '192.168.90.102:3260, iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f' from initiator '192.168.90.53:60923, iqn.1998-01.com.vmware:VHOST05-484f029e' successful, using Jumbo Frame length.  INFO 5/16/13 12:08:40 PM PS4100X-0 iSCSI login to target '192.168.90.101:3260, iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f' from initiator '192.168.90.51:55351, iqn.1998-01.com.vmware:VHOST05-484f029e' successful, using Jumbo Frame length.  INFO 5/16/13 12:08:40 PM PS4100X-0 iSCSI login to target '192.168.90.104:3260, iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f' from initiator '192.168.90.50:56018, iqn.1998-01.com.vmware:VHOST05-484f029e' successful, using Jumbo Frame length.  INFO 5/16/13 12:08:40 PM PS4100X-0 iSCSI login to target '192.168.90.104:3260, iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f' from initiator '192.168.90.52:62320, iqn.1998-01.com.vmware:VHOST05-484f029e' successful, using Jumbo Frame length.  INFO 5/16/13 12:08:38 PM PS4100X-0 iSCSI session to target '192.168.90.102:3260, iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f' from initiator '192.168.90.50:53740, iqn.1998-01.com.vmware:VHOST05-484f029e' was closed. Logout request was received from the initiator.  INFO 5/16/13 12:08:38 PM PS4100X-0 iSCSI session to target '192.168.90.101:3260, iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f' from initiator '192.168.90.52:62640, iqn.1998-01.com.vmware:VHOST05-484f029e' was closed. Logout request was received from the initiator.  INFO 5/16/13 12:08:38 PM PS4100X-0 iSCSI session to target '192.168.90.103:3260, iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f' from initiator '192.168.90.51:53550, iqn.1998-01.com.vmware:VHOST05-484f029e' was closed. Logout request was received from the initiator.  INFO 5/16/13 12:08:27 PM PS4100X-0 iSCSI session to target '192.168.90.104:3260, iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f' from initiator '192.168.90.50:51627, iqn.1998-01.com.vmware:VHOST05-484f029e' was closed. Logout request was received from the initiator.  INFO 5/16/13 12:08:26 PM PS4100X-0 iSCSI login to target '192.168.90.102:3260, iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f' from initiator '192.168.90.50:53740, iqn.1998-01.com.vmware:VHOST05-484f029e' successful, using Jumbo Frame length.  INFO 5/16/13 12:08:26 PM PS4100X-0 iSCSI login to target '192.168.90.101:3260, iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f' from initiator '192.168.90.52:62640, iqn.1998-01.com.vmware:VHOST05-484f029e' successful, using Jumbo Frame length.  INFO 5/16/13 12:08:26 PM PS4100X-0 iSCSI login to target '192.168.90.103:3260, iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f' from initiator '192.168.90.51:53550, iqn.1998-01.com.vmware:VHOST05-484f029e' successful, using Jumbo Frame length.  INFO 5/16/13 12:08:26 PM PS4100X-0 iSCSI login to target '192.168.90.103:3260, iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f' from initiator '192.168.90.53:56744, iqn.1998-01.com.vmware:VHOST05-484f029e' successful, using Jumbo Frame length.  INFO 5/16/13 12:08:24 PM PS4100X-0 iSCSI session to target '192.168.90.101:3260, iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f' from initiator '192.168.90.53:53109, iqn.1998-01.com.vmware:VHOST05-484f029e' was closed. Logout request was received from the initiator.  INFO 5/16/13 12:08:24 PM PS4100X-0 iSCSI session to target '192.168.90.102:3260, iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f' from initiator '192.168.90.51:53339, iqn.1998-01.com.vmware:VHOST05-484f029e' was closed. Logout request was received from the initiator.  INFO 5/16/13 12:08:24 PM PS4100X-0 iSCSI session to target '192.168.90.104:3260, iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f' from initiator '192.168.90.52:53108, iqn.1998-01.com.vmware:VHOST05-484f029e' was closed. Logout request was received from the initiator. 
  
  The host logs these events in vmkernel.log:
  
  2013-05-16T16:08:24.658Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: vmhba37:CH:1 T:6 CN:0: Failed to receive data: Connection closed by peer2013-05-16T16:08:24.658Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Sess [ISID: 00023d000006 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:24.658Z cpu3:2997)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x28 (0x41244101e280, 4863) to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" on path "vmhba37:C1:T6:L0" Failed: H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0. Act:EVAL2013-05-16T16:08:24.658Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Conn [CID: 0 L: 192.168.90.51:53339 R: 192.168.90.102:3260]2013-05-16T16:08:24.658Z cpu3:2997)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP device "naa.64ed2a85165dc1561cf7c4851a02c0d6" state in doubt; requested fast path state update...2013-05-16T16:08:24.658Z cpu1:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: vmhba37:CH:1 T:6 CN:0: Connection rx notifying failure: Failed to Receive. State=Online2013-05-16T16:08:24.658Z cpu3:2997)ScsiDeviceIO: 2309: Cmd(0x41244101e280) 0x28, CmdSN 0x800000d3 from world 4863 to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" failed H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.2013-05-16T16:08:24.658Z cpu1:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Sess [ISID: 00023d000006 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:24.658Z cpu1:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Conn [CID: 0 L: 192.168.90.51:53339 R: 192.168.90.102:3260]2013-05-16T16:08:24.658Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba37:CH:1 T:6 CN:0: iSCSI connection is being marked "OFFLINE" (Event:6)2013-05-16T16:08:24.658Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: 00023d000006 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:24.658Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 192.168.90.51:53339 R: 192.168.90.102:3260]2013-05-16T16:08:24.658Z cpu5:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: vmhba37:CH:2 T:6 CN:0: Failed to receive data: Connection closed by peer2013-05-16T16:08:24.658Z cpu5:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Sess [ISID: 00023d000007 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:24.658Z cpu5:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Conn [CID: 0 L: 192.168.90.52:53108 R: 192.168.90.104:3260]2013-05-16T16:08:24.658Z cpu5:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: vmhba37:CH:2 T:6 CN:0: Connection rx notifying failure: Failed to Receive. State=Online2013-05-16T16:08:24.659Z cpu5:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Sess [ISID: 00023d000007 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:24.659Z cpu5:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Conn [CID: 0 L: 192.168.90.52:53108 R: 192.168.90.104:3260]2013-05-16T16:08:24.659Z cpu5:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba37:CH:2 T:6 CN:0: iSCSI connection is being marked "OFFLINE" (Event:6)2013-05-16T16:08:24.659Z cpu5:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: 00023d000007 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:24.659Z cpu5:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 192.168.90.52:53108 R: 192.168.90.104:3260]2013-05-16T16:08:24.659Z cpu3:2997)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x28 (0x412441cb8500, 4863) to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" on path "vmhba37:C2:T6:L0" Failed: H:0x2 D:0x0 P:0x0 Possible sense data: 0x5 0x24 0x0. Act:EVAL2013-05-16T16:08:24.659Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: vmhba37:CH:3 T:6 CN:0: Failed to receive data: Connection closed by peer2013-05-16T16:08:24.659Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Sess [ISID: 00023d000008 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:24.659Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Conn [CID: 0 L: 192.168.90.53:53109 R: 192.168.90.101:3260]2013-05-16T16:08:24.659Z cpu0:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: vmhba37:CH:3 T:6 CN:0: Connection rx notifying failure: Failed to Receive. State=Online2013-05-16T16:08:24.659Z cpu0:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Sess [ISID: 00023d000008 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:24.659Z cpu0:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Conn [CID: 0 L: 192.168.90.53:53109 R: 192.168.90.101:3260]2013-05-16T16:08:24.659Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba37:CH:3 T:6 CN:0: iSCSI connection is being marked "OFFLINE" (Event:6)2013-05-16T16:08:24.659Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: 00023d000008 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:24.659Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 192.168.90.53:53109 R: 192.168.90.101:3260]2013-05-16T16:08:24.771Z cpu15:5735)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x28 (0x412441018980, 4863) to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" on path "vmhba37:C1:T6:L0" Failed: H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0. Act:EVAL2013-05-16T16:08:24.860Z cpu4:4828)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x2a (0x4124010a25c0, 2064) to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" on path "vmhba37:C3:T6:L0" Failed: H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0. Act:EVAL2013-05-16T16:08:24.908Z cpu10:2777)ScsiDeviceIO: 2309: Cmd(0x412440982980) 0x2a, CmdSN 0x80000059 from world 4863 to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" failed H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.2013-05-16T16:08:24.912Z cpu15:2063)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x28 (0x412441018980, 4863) to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" on path "vmhba37:C3:T6:L0" Failed: H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0. Act:EVAL2013-05-16T16:08:24.921Z cpu10:10448)WARNING: NMP: nmp_SelectPathAndIssueCommand:2693:PSP selected path "vmhba37:C1:T6:L0" in a bad state (dead)on device "naa.64ed2a85165dc1561cf7c4851a02c0d6".2013-05-16T16:08:24.921Z cpu10:10448)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x2a (0x412440b242c0, 4863) to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" on path "vmhba37:C1:T6:L0" Failed: H:0x1 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0. Act:FAILOVER2013-05-16T16:08:24.921Z cpu10:10448)WARNING: NMP: nmp_DeviceRetryCommand:133:Device "naa.64ed2a85165dc1561cf7c4851a02c0d6": awaiting fast path state update for failover with I/O blocked. No prior reservation exists on the device.2013-05-16T16:08:24.921Z cpu10:10448)WARNING: NMP: nmp_DeviceStartLoop:721:NMP Device "naa.64ed2a85165dc1561cf7c4851a02c0d6" is blocked. Not starting I/O from device.2013-05-16T16:08:24.964Z cpu7:2088)WARNING: dell_psp_eql_routed: psp_eqlUpdatePathSelection:1014:Path is reported as inactive (0x50475304)2013-05-16T16:08:24.964Z cpu7:2088)WARNING: dell_psp_eql_routed: psp_eqlUpdatePathSelection:1014:Path is reported as inactive (0x50475304)2013-05-16T16:08:24.964Z cpu7:2088)WARNING: dell_psp_eql_routed: psp_eqlUpdatePathSelection:1014:Path is reported as inactive (0x50475304)2013-05-16T16:08:24.965Z cpu0:2088)WARNING: dell_psp_eql_routed: psp_eqlUpdatePathSelection:1014:Path is reported as inactive (0x50475304)2013-05-16T16:08:24.965Z cpu0:2088)WARNING: dell_psp_eql_routed: psp_eqlUpdatePathSelection:1014:Path is reported as inactive (0x50475304)2013-05-16T16:08:24.965Z cpu0:2088)WARNING: dell_psp_eql_routed: psp_eqlUpdatePathSelection:1014:Path is reported as inactive (0x50475304)2013-05-16T16:08:24.967Z cpu6:2209)ScsiPath: 4963: DeletePath : adapter=vmhba37, channel=1, target=6, lun=02013-05-16T16:08:24.967Z cpu6:2209)WARNING: dell_psp_eql_routed: psp_eqlUpdatePathSelection:1014:Path is reported as inactive (0x50475304)2013-05-16T16:08:24.967Z cpu6:2209)WARNING: dell_psp_eql_routed: psp_eqlUpdatePathSelection:1014:Path is reported as inactive (0x50475304)2013-05-16T16:08:24.967Z cpu6:2209)WARNING: ScsiPath: 5022: Remove path: vmhba37:C1:T6:L02013-05-16T16:08:24.967Z cpu6:2206)ScsiPath: 4963: DeletePath : adapter=vmhba37, channel=2, target=6, lun=02013-05-16T16:08:24.967Z cpu6:2206)WARNING: dell_psp_eql_routed: psp_eqlUpdatePathSelection:1014:Path is reported as inactive (0x50475304)2013-05-16T16:08:24.967Z cpu6:2206)WARNING: ScsiPath: 5022: Remove path: vmhba37:C2:T6:L02013-05-16T16:08:24.967Z cpu6:2206)ScsiPath: 4963: DeletePath : adapter=vmhba37, channel=3, target=6, lun=02013-05-16T16:08:24.968Z cpu2:2206)WARNING: ScsiPath: 5022: Remove path: vmhba37:C3:T6:L02013-05-16T16:08:25.232Z cpu12:2698)WARNING: NMP: nmpDeviceAttemptFailover:599:Retry world failover device "naa.64ed2a85165dc1561cf7c4851a02c0d6" - issuing command 0x412440b242c02013-05-16T16:08:25.233Z cpu15:2063)NMP: nmpCompleteRetryForPath:321: Retry world recovered device "naa.64ed2a85165dc1561cf7c4851a02c0d6"2013-05-16T16:08:25.271Z cpu1:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410023555110 network resource pool netsched.pools.persist.iscsi associated2013-05-16T16:08:25.271Z cpu1:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410023555110 network tracker id 1 tracker.iSCSI.192.168.90.100 associated2013-05-16T16:08:25.272Z cpu1:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410023490210 network resource pool netsched.pools.persist.iscsi associated2013-05-16T16:08:25.272Z cpu1:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410023490210 network tracker id 1 tracker.iSCSI.192.168.90.100 associated2013-05-16T16:08:25.272Z cpu1:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x41002cdc23b0 network resource pool netsched.pools.persist.iscsi associated2013-05-16T16:08:25.272Z cpu1:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x41002cdc23b0 network tracker id 1 tracker.iSCSI.192.168.90.100 associated2013-05-16T16:08:25.272Z cpu1:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x41002cdc2a50 network resource pool netsched.pools.persist.iscsi associated2013-05-16T16:08:25.272Z cpu1:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x41002cdc2a50 network tracker id 1 tracker.iSCSI.192.168.90.100 associated2013-05-16T16:08:25.280Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: vmhba37:CH:1 T:6 CN:0: Failed to receive data: Connection closed by peer2013-05-16T16:08:25.280Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Sess [ISID: TARGET: (null) TPGT: 0 TSIH: 0]2013-05-16T16:08:25.280Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Conn [CID: 0 L: 192.168.90.53:49974 R: 192.168.90.100:3260]2013-05-16T16:08:25.280Z cpu1:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: vmhba37:CH:1 T:6 CN:0: Connection rx notifying failure: Failed to Receive. State=Bound2013-05-16T16:08:25.280Z cpu1:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Sess [ISID: TARGET: (null) TPGT: 0 TSIH: 0]2013-05-16T16:08:25.280Z cpu1:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Conn [CID: 0 L: 192.168.90.53:49974 R: 192.168.90.100:3260]2013-05-16T16:08:25.289Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: vmhba37:CH:2 T:6 CN:0: Failed to receive data: Connection closed by peer2013-05-16T16:08:25.289Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Sess [ISID: TARGET: (null) TPGT: 0 TSIH: 0]2013-05-16T16:08:25.289Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Conn [CID: 0 L: 192.168.90.51:59154 R: 192.168.90.100:3260]2013-05-16T16:08:25.289Z cpu1:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: vmhba37:CH:2 T:6 CN:0: Connection rx notifying failure: Failed to Receive. State=Bound2013-05-16T16:08:25.289Z cpu1:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Sess [ISID: TARGET: (null) TPGT: 0 TSIH: 0]2013-05-16T16:08:25.289Z cpu1:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Conn [CID: 0 L: 192.168.90.51:59154 R: 192.168.90.100:3260]2013-05-16T16:08:25.298Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: vmhba37:CH:3 T:6 CN:0: Failed to receive data: Connection closed by peer2013-05-16T16:08:25.298Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Sess [ISID: TARGET: (null) TPGT: 0 TSIH: 0]2013-05-16T16:08:25.298Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Conn [CID: 0 L: 192.168.90.52:53935 R: 192.168.90.100:3260]2013-05-16T16:08:25.298Z cpu1:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: vmhba37:CH:3 T:6 CN:0: Connection rx notifying failure: Failed to Receive. State=Bound2013-05-16T16:08:25.298Z cpu1:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Sess [ISID: TARGET: (null) TPGT: 0 TSIH: 0]2013-05-16T16:08:25.298Z cpu1:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Conn [CID: 0 L: 192.168.90.52:53935 R: 192.168.90.100:3260]2013-05-16T16:08:25.306Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: vmhba37:CH:4 T:6 CN:0: Failed to receive data: Connection closed by peer2013-05-16T16:08:25.306Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Sess [ISID: TARGET: (null) TPGT: 0 TSIH: 0]2013-05-16T16:08:25.306Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Conn [CID: 0 L: 192.168.90.50:49401 R: 192.168.90.100:3260]2013-05-16T16:08:25.306Z cpu1:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: vmhba37:CH:4 T:6 CN:0: Connection rx notifying failure: Failed to Receive. State=Bound2013-05-16T16:08:25.306Z cpu1:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Sess [ISID: TARGET: (null) TPGT: 0 TSIH: 0]2013-05-16T16:08:25.306Z cpu1:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Conn [CID: 0 L: 192.168.90.50:49401 R: 192.168.90.100:3260]2013-05-16T16:08:25.507Z cpu7:2055)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x1a (0x412401cfc340, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE2013-05-16T16:08:25.507Z cpu7:2055)ScsiDeviceIO: 2322: Cmd(0x412401cfc340) 0x1a, CmdSN 0x1175b from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.2013-05-16T16:08:25.560Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba37:CH:1 T:6 CN:0: iSCSI connection is being marked "OFFLINE" (Event:4)2013-05-16T16:08:25.560Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: TARGET: (null) TPGT: 0 TSIH: 0]2013-05-16T16:08:25.560Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 192.168.90.53:49974 R: 192.168.90.100:3260]2013-05-16T16:08:25.561Z cpu1:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x41002cdd7210 network resource pool netsched.pools.persist.iscsi associated2013-05-16T16:08:25.561Z cpu1:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x41002cdd7210 network tracker id 1 tracker.iSCSI.192.168.90.103 associated2013-05-16T16:08:25.561Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba37:CH:2 T:6 CN:0: iSCSI connection is being marked "OFFLINE" (Event:4)2013-05-16T16:08:25.561Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: TARGET: (null) TPGT: 0 TSIH: 0]2013-05-16T16:08:25.561Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 192.168.90.51:59154 R: 192.168.90.100:3260]2013-05-16T16:08:25.562Z cpu1:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x41002347f910 network resource pool netsched.pools.persist.iscsi associated2013-05-16T16:08:25.562Z cpu1:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x41002347f910 network tracker id 1 tracker.iSCSI.192.168.90.103 associated2013-05-16T16:08:25.562Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba37:CH:3 T:6 CN:0: iSCSI connection is being marked "OFFLINE" (Event:4)2013-05-16T16:08:25.562Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: TARGET: (null) TPGT: 0 TSIH: 0]2013-05-16T16:08:25.562Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 192.168.90.52:53935 R: 192.168.90.100:3260]2013-05-16T16:08:25.563Z cpu1:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x41002cdc23b0 network resource pool netsched.pools.persist.iscsi associated2013-05-16T16:08:25.563Z cpu1:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x41002cdc23b0 network tracker id 1 tracker.iSCSI.192.168.90.101 associated2013-05-16T16:08:25.563Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba37:CH:4 T:6 CN:0: iSCSI connection is being marked "OFFLINE" (Event:4)2013-05-16T16:08:25.563Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: TARGET: (null) TPGT: 0 TSIH: 0]2013-05-16T16:08:25.563Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 192.168.90.50:49401 R: 192.168.90.100:3260]2013-05-16T16:08:25.564Z cpu1:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x41002cdc2a50 network resource pool netsched.pools.persist.iscsi associated2013-05-16T16:08:25.564Z cpu1:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x41002cdc2a50 network tracker id 1 tracker.iSCSI.192.168.90.102 associated2013-05-16T16:08:26.869Z cpu11:2724)WARNING: iscsi_vmk: iscsivmk_StartConnection: vmhba37:CH:1 T:6 CN:0: iSCSI connection is being marked "ONLINE"2013-05-16T16:08:26.869Z cpu11:2724)WARNING: iscsi_vmk: iscsivmk_StartConnection: Sess [ISID: 00023d000008 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:26.869Z cpu11:2724)WARNING: iscsi_vmk: iscsivmk_StartConnection: Conn [CID: 0 L: 192.168.90.53:56744 R: 192.168.90.103:3260]2013-05-16T16:08:26.870Z cpu11:2724)WARNING: iscsi_vmk: iscsivmk_StartConnection: vmhba37:CH:2 T:6 CN:0: iSCSI connection is being marked "ONLINE"2013-05-16T16:08:26.870Z cpu11:2724)WARNING: iscsi_vmk: iscsivmk_StartConnection: Sess [ISID: 00023d000006 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:26.870Z cpu11:2724)WARNING: iscsi_vmk: iscsivmk_StartConnection: Conn [CID: 0 L: 192.168.90.51:53550 R: 192.168.90.103:3260]2013-05-16T16:08:26.871Z cpu11:2724)WARNING: iscsi_vmk: iscsivmk_StartConnection: vmhba37:CH:3 T:6 CN:0: iSCSI connection is being marked "ONLINE"2013-05-16T16:08:26.871Z cpu11:2724)WARNING: iscsi_vmk: iscsivmk_StartConnection: Sess [ISID: 00023d000007 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:26.871Z cpu11:2724)WARNING: iscsi_vmk: iscsivmk_StartConnection: Conn [CID: 0 L: 192.168.90.52:62640 R: 192.168.90.101:3260]2013-05-16T16:08:26.872Z cpu11:2724)WARNING: iscsi_vmk: iscsivmk_StartConnection: vmhba37:CH:4 T:6 CN:0: iSCSI connection is being marked "ONLINE"2013-05-16T16:08:26.872Z cpu11:2724)WARNING: iscsi_vmk: iscsivmk_StartConnection: Sess [ISID: 00023d010005 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:26.872Z cpu11:2724)WARNING: iscsi_vmk: iscsivmk_StartConnection: Conn [CID: 0 L: 192.168.90.50:53740 R: 192.168.90.102:3260]2013-05-16T16:08:27.085Z cpu6:3533)ScsiScan: 1098: Path 'vmhba37:C1:T6:L0': Vendor: 'EQLOGIC ' Model: '100E-00 ' Rev: '5.2 '2013-05-16T16:08:27.085Z cpu6:3533)ScsiScan: 1101: Path 'vmhba37:C1:T6:L0': Type: 0x0, ANSI rev: 5, TPGS: 1 (implicit only)2013-05-16T16:08:27.085Z cpu4:3533)ScsiScan: 1582: Add path: vmhba37:C1:T6:L02013-05-16T16:08:27.085Z cpu4:3533)ScsiScan: 1098: Path 'vmhba37:C2:T6:L0': Vendor: 'EQLOGIC ' Model: '100E-00 ' Rev: '5.2 '2013-05-16T16:08:27.085Z cpu4:3533)ScsiScan: 1101: Path 'vmhba37:C2:T6:L0': Type: 0x0, ANSI rev: 5, TPGS: 1 (implicit only)2013-05-16T16:08:27.086Z cpu4:3533)ScsiScan: 1582: Add path: vmhba37:C2:T6:L02013-05-16T16:08:27.087Z cpu4:3533)ScsiScan: 1098: Path 'vmhba37:C3:T6:L0': Vendor: 'EQLOGIC ' Model: '100E-00 ' Rev: '5.2 '2013-05-16T16:08:27.087Z cpu4:3533)ScsiScan: 1101: Path 'vmhba37:C3:T6:L0': Type: 0x0, ANSI rev: 5, TPGS: 1 (implicit only)2013-05-16T16:08:27.091Z cpu0:3533)ScsiScan: 1582: Add path: vmhba37:C3:T6:L02013-05-16T16:08:27.091Z cpu0:3533)ScsiScan: 1098: Path 'vmhba37:C4:T6:L0': Vendor: 'EQLOGIC ' Model: '100E-00 ' Rev: '5.2 '2013-05-16T16:08:27.091Z cpu0:3533)ScsiScan: 1101: Path 'vmhba37:C4:T6:L0': Type: 0x0, ANSI rev: 5, TPGS: 1 (implicit only)2013-05-16T16:08:27.092Z cpu0:3533)ScsiScan: 1582: Add path: vmhba37:C4:T6:L02013-05-16T16:08:27.092Z cpu0:3533)ScsiPath: 4541: Plugin 'NMP' claimed path 'vmhba37:C4:T6:L0'2013-05-16T16:08:27.092Z cpu0:3533)ScsiPath: 4541: Plugin 'NMP' claimed path 'vmhba37:C3:T6:L0'2013-05-16T16:08:27.092Z cpu0:3533)ScsiPath: 4541: Plugin 'NMP' claimed path 'vmhba37:C2:T6:L0'2013-05-16T16:08:27.092Z cpu0:3533)ScsiPath: 4541: Plugin 'NMP' claimed path 'vmhba37:C1:T6:L0'2013-05-16T16:08:27.189Z cpu13:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: vmhba37:CH:0 T:6 CN:0: Failed to receive data: Connection closed by peer2013-05-16T16:08:27.189Z cpu13:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Sess [ISID: 00023d000005 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:27.189Z cpu13:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Conn [CID: 0 L: 192.168.90.50:51627 R: 192.168.90.104:3260]2013-05-16T16:08:27.189Z cpu13:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: vmhba37:CH:0 T:6 CN:0: Connection rx notifying failure: Failed to Receive. State=Online2013-05-16T16:08:27.189Z cpu13:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Sess [ISID: 00023d000005 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:27.189Z cpu13:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Conn [CID: 0 L: 192.168.90.50:51627 R: 192.168.90.104:3260]2013-05-16T16:08:27.189Z cpu10:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba37:CH:0 T:6 CN:0: iSCSI connection is being marked "OFFLINE" (Event:6)2013-05-16T16:08:27.189Z cpu10:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: 00023d000005 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:27.189Z cpu10:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 192.168.90.50:51627 R: 192.168.90.104:3260]2013-05-16T16:08:27.189Z cpu14:2677)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP device "naa.64ed2a85165dc1561cf7c4851a02c0d6" state in doubt; requested fast path state update...2013-05-16T16:08:27.189Z cpu14:2677)ScsiDeviceIO: 2309: Cmd(0x412440985380) 0x28, CmdSN 0x8000003a from world 4863 to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" failed H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.2013-05-16T16:08:27.238Z cpu10:2058)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP device "naa.64ed2a85165dc1561cf7c4851a02c0d6" state in doubt; requested fast path state update...2013-05-16T16:08:27.278Z cpu15:2063)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x28 (0x412441114a40, 4863) to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" on path "vmhba37:C0:T6:L0" Failed: H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0. Act:EVAL2013-05-16T16:08:27.314Z cpu14:2062)ScsiDeviceIO: 2309: Cmd(0x41244136e280) 0x28, CmdSN 0x800000d9 from world 4863 to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" failed H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.2013-05-16T16:08:27.314Z cpu14:2062)ScsiDeviceIO: 2309: Cmd(0x412441832f00) 0x28, CmdSN 0x800000ca from world 4863 to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" failed H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.2013-05-16T16:08:27.368Z cpu10:2058)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x28 (0x412440f813c0, 4863) to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" on path "vmhba37:C0:T6:L0" Failed: H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0. Act:EVAL2013-05-16T16:08:27.456Z cpu9:2057)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x28 (0x412440f50600, 4863) to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" on path "vmhba37:C0:T6:L0" Failed: H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0. Act:EVAL2013-05-16T16:08:27.456Z cpu9:2057)ScsiDeviceIO: 2309: Cmd(0x412440f50600) 0x28, CmdSN 0x80000044 from world 4863 to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" failed H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.2013-05-16T16:08:27.478Z cpu11:2059)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x28 (0x412440f813c0, 4863) to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" on path "vmhba37:C0:T6:L0" Failed: H:0x1 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0. Act:FAILOVER2013-05-16T16:08:27.478Z cpu11:2059)WARNING: NMP: nmp_DeviceRetryCommand:133:Device "naa.64ed2a85165dc1561cf7c4851a02c0d6": awaiting fast path state update for failover with I/O blocked. No prior reservation exists on the device.2013-05-16T16:08:27.478Z cpu11:2059)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x28 (0x41244054a180, 4863) to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" on path "vmhba37:C0:T6:L0" Failed: H:0x1 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0. Act:FAILOVER2013-05-16T16:08:27.478Z cpu11:2059)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x28 (0x41244136d180, 4863) to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" on path "vmhba37:C0:T6:L0" Failed: H:0x1 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0. Act:FAILOVER2013-05-16T16:08:27.488Z cpu2:2196)WARNING: dell_psp_eql_routed: psp_eqlUpdatePathSelection:1014:Path is reported as inactive (0x50475304)2013-05-16T16:08:27.488Z cpu6:2698)WARNING: NMP: nmpDeviceAttemptFailover:599:Retry world failover device "naa.64ed2a85165dc1561cf7c4851a02c0d6" - issuing command 0x412440f813c02013-05-16T16:08:27.497Z cpu9:2057)NMP: nmpCompleteRetryForPath:321: Retry world recovered device "naa.64ed2a85165dc1561cf7c4851a02c0d6"2013-05-16T16:08:28.196Z cpu7:2206)ScsiPath: 4963: DeletePath : adapter=vmhba37, channel=0, target=6, lun=02013-05-16T16:08:28.197Z cpu14:2062)WARNING: NMP: nmp_DeviceStartLoop:721:NMP Device "naa.64ed2a85165dc1561cf7c4851a02c0d6" is blocked. Not starting I/O from device.2013-05-16T16:08:28.198Z cpu14:2062)WARNING: NMP: nmp_DeviceStartLoop:721:NMP Device "naa.64ed2a85165dc1561cf7c4851a02c0d6" is blocked. Not starting I/O from device.2013-05-16T16:08:28.201Z cpu14:2062)WARNING: NMP: nmp_DeviceStartLoop:721:NMP Device "naa.64ed2a85165dc1561cf7c4851a02c0d6" is blocked. Not starting I/O from device.2013-05-16T16:08:28.201Z cpu10:2058)WARNING: NMP: nmp_DeviceStartLoop:721:NMP Device "naa.64ed2a85165dc1561cf7c4851a02c0d6" is blocked. Not starting I/O from device.2013-05-16T16:08:28.229Z cpu14:2062)WARNING: NMP: nmp_DeviceStartLoop:721:NMP Device "naa.64ed2a85165dc1561cf7c4851a02c0d6" is blocked. Not starting I/O from device.2013-05-16T16:08:28.229Z cpu4:2206)WARNING: ScsiPath: 5022: Remove path: vmhba37:C0:T6:L02013-05-16T16:08:38.588Z cpu5:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: vmhba37:CH:2 T:6 CN:0: Failed to receive data: Connection closed by peer2013-05-16T16:08:38.589Z cpu5:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Sess [ISID: 00023d000006 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:38.589Z cpu5:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Conn [CID: 0 L: 192.168.90.51:53550 R: 192.168.90.103:3260]2013-05-16T16:08:38.589Z cpu5:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: vmhba37:CH:2 T:6 CN:0: Connection rx notifying failure: Failed to Receive. State=Online2013-05-16T16:08:38.589Z cpu5:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Sess [ISID: 00023d000006 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:38.589Z cpu5:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Conn [CID: 0 L: 192.168.90.51:53550 R: 192.168.90.103:3260]2013-05-16T16:08:38.589Z cpu5:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba37:CH:2 T:6 CN:0: iSCSI connection is being marked "OFFLINE" (Event:6)2013-05-16T16:08:38.589Z cpu5:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: 00023d000006 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:38.589Z cpu5:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 192.168.90.51:53550 R: 192.168.90.103:3260]2013-05-16T16:08:38.589Z cpu2:2701)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP device "naa.64ed2a85165dc1561cf7c4851a02c0d6" state in doubt; requested fast path state update...2013-05-16T16:08:38.589Z cpu2:2701)ScsiDeviceIO: 2309: Cmd(0x412441780f40) 0x28, CmdSN 0x80000047 from world 4863 to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" failed H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.2013-05-16T16:08:38.590Z cpu5:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: vmhba37:CH:3 T:6 CN:0: Failed to receive data: Connection closed by peer2013-05-16T16:08:38.590Z cpu5:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Sess [ISID: 00023d000007 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:38.590Z cpu5:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Conn [CID: 0 L: 192.168.90.52:62640 R: 192.168.90.101:3260]2013-05-16T16:08:38.590Z cpu5:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: vmhba37:CH:3 T:6 CN:0: Connection rx notifying failure: Failed to Receive. State=Online2013-05-16T16:08:38.590Z cpu5:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Sess [ISID: 00023d000007 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:38.590Z cpu5:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Conn [CID: 0 L: 192.168.90.52:62640 R: 192.168.90.101:3260]2013-05-16T16:08:38.590Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba37:CH:3 T:6 CN:0: iSCSI connection is being marked "OFFLINE" (Event:6)2013-05-16T16:08:38.590Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: 00023d000007 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:38.590Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 192.168.90.52:62640 R: 192.168.90.101:3260]2013-05-16T16:08:38.590Z cpu4:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: vmhba37:CH:4 T:6 CN:0: Failed to receive data: Connection closed by peer2013-05-16T16:08:38.590Z cpu4:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Sess [ISID: 00023d010005 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:38.590Z cpu4:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Conn [CID: 0 L: 192.168.90.50:53740 R: 192.168.90.102:3260]2013-05-16T16:08:38.590Z cpu4:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: vmhba37:CH:4 T:6 CN:0: Connection rx notifying failure: Failed to Receive. State=Online2013-05-16T16:08:38.590Z cpu4:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Sess [ISID: 00023d010005 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:38.590Z cpu4:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Conn [CID: 0 L: 192.168.90.50:53740 R: 192.168.90.102:3260]2013-05-16T16:08:38.590Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba37:CH:4 T:6 CN:0: iSCSI connection is being marked "OFFLINE" (Event:6)2013-05-16T16:08:38.590Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: 00023d010005 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:38.590Z cpu1:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 192.168.90.50:53740 R: 192.168.90.102:3260]2013-05-16T16:08:38.651Z cpu11:2059)ScsiDeviceIO: 2309: Cmd(0x412441cbc700) 0x28, CmdSN 0x800000dd from world 4863 to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" failed H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.2013-05-16T16:08:38.651Z cpu11:2059)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x28 (0x41244101b280, 4863) to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" on path "vmhba37:C4:T6:L0" Failed: H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0. Act:EVAL2013-05-16T16:08:38.651Z cpu11:2059)ScsiDeviceIO: 2309: Cmd(0x41244101b280) 0x28, CmdSN 0x800000b0 from world 4863 to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" failed H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.2013-05-16T16:08:38.681Z cpu11:2059)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x28 (0x41244101b280, 4863) to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" on path "vmhba37:C4:T6:L0" Failed: H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0. Act:EVAL2013-05-16T16:08:38.731Z cpu11:2059)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x28 (0x41244101b280, 4863) to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" on path "vmhba37:C4:T6:L0" Failed: H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0. Act:EVAL2013-05-16T16:08:38.796Z cpu11:4863)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x28 (0x41244101b280, 4863) to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" on path "vmhba37:C4:T6:L0" Failed: H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0. Act:EVAL2013-05-16T16:08:38.842Z cpu5:2088)WARNING: dell_psp_eql_routed: psp_eqlUpdatePathSelection:1014:Path is reported as inactive (0x50475304)2013-05-16T16:08:38.842Z cpu5:2088)WARNING: dell_psp_eql_routed: psp_eqlUpdatePathSelection:1014:Path is reported as inactive (0x50475304)2013-05-16T16:08:38.842Z cpu5:2088)WARNING: dell_psp_eql_routed: psp_eqlUpdatePathSelection:1014:Path is reported as inactive (0x50475304)2013-05-16T16:08:38.846Z cpu8:2207)ScsiPath: 4963: DeletePath : adapter=vmhba37, channel=2, target=6, lun=02013-05-16T16:08:38.846Z cpu8:2207)WARNING: dell_psp_eql_routed: psp_eqlUpdatePathSelection:1014:Path is reported as inactive (0x50475304)2013-05-16T16:08:38.846Z cpu8:2207)WARNING: dell_psp_eql_routed: psp_eqlUpdatePathSelection:1014:Path is reported as inactive (0x50475304)2013-05-16T16:08:38.846Z cpu8:2207)WARNING: ScsiPath: 5022: Remove path: vmhba37:C2:T6:L02013-05-16T16:08:38.846Z cpu8:2209)ScsiPath: 4963: DeletePath : adapter=vmhba37, channel=3, target=6, lun=02013-05-16T16:08:38.846Z cpu8:2209)WARNING: dell_psp_eql_routed: psp_eqlUpdatePathSelection:1014:Path is reported as inactive (0x50475304)2013-05-16T16:08:38.846Z cpu8:2209)WARNING: ScsiPath: 5022: Remove path: vmhba37:C3:T6:L02013-05-16T16:08:38.846Z cpu8:2209)ScsiPath: 4963: DeletePath : adapter=vmhba37, channel=4, target=6, lun=02013-05-16T16:08:38.846Z cpu8:2209)WARNING: ScsiPath: 5022: Remove path: vmhba37:C4:T6:L02013-05-16T16:08:39.199Z cpu1:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410023490210 network resource pool netsched.pools.persist.iscsi associated2013-05-16T16:08:39.200Z cpu1:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410023490210 network tracker id 1 tracker.iSCSI.192.168.90.100 associated2013-05-16T16:08:39.200Z cpu1:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410023461d30 network resource pool netsched.pools.persist.iscsi associated2013-05-16T16:08:39.200Z cpu1:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410023461d30 network tracker id 1 tracker.iSCSI.192.168.90.100 associated2013-05-16T16:08:39.200Z cpu4:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x41002cdc23b0 network resource pool netsched.pools.persist.iscsi associated2013-05-16T16:08:39.200Z cpu4:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x41002cdc23b0 network tracker id 1 tracker.iSCSI.192.168.90.100 associated2013-05-16T16:08:39.201Z cpu4:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x41002cdc2a50 network resource pool netsched.pools.persist.iscsi associated2013-05-16T16:08:39.201Z cpu4:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x41002cdc2a50 network tracker id 1 tracker.iSCSI.192.168.90.100 associated2013-05-16T16:08:39.208Z cpu4:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: vmhba37:CH:0 T:6 CN:0: Failed to receive data: Connection closed by peer2013-05-16T16:08:39.208Z cpu4:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Sess [ISID: TARGET: (null) TPGT: 0 TSIH: 0]2013-05-16T16:08:39.208Z cpu4:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Conn [CID: 0 L: 192.168.90.50:63278 R: 192.168.90.100:3260]2013-05-16T16:08:39.208Z cpu4:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: vmhba37:CH:0 T:6 CN:0: Connection rx notifying failure: Failed to Receive. State=Bound2013-05-16T16:08:39.208Z cpu4:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Sess [ISID: TARGET: (null) TPGT: 0 TSIH: 0]2013-05-16T16:08:39.208Z cpu4:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Conn [CID: 0 L: 192.168.90.50:63278 R: 192.168.90.100:3260]2013-05-16T16:08:39.217Z cpu4:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: vmhba37:CH:2 T:6 CN:0: Failed to receive data: Connection closed by peer2013-05-16T16:08:39.217Z cpu4:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Sess [ISID: TARGET: (null) TPGT: 0 TSIH: 0]2013-05-16T16:08:39.217Z cpu4:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Conn [CID: 0 L: 192.168.90.52:51827 R: 192.168.90.100:3260]2013-05-16T16:08:39.217Z cpu4:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: vmhba37:CH:2 T:6 CN:0: Connection rx notifying failure: Failed to Receive. State=Bound2013-05-16T16:08:39.217Z cpu4:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Sess [ISID: TARGET: (null) TPGT: 0 TSIH: 0]2013-05-16T16:08:39.217Z cpu4:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Conn [CID: 0 L: 192.168.90.52:51827 R: 192.168.90.100:3260]2013-05-16T16:08:39.225Z cpu4:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: vmhba37:CH:3 T:6 CN:0: Failed to receive data: Connection closed by peer2013-05-16T16:08:39.225Z cpu4:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Sess [ISID: TARGET: (null) TPGT: 0 TSIH: 0]2013-05-16T16:08:39.225Z cpu4:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Conn [CID: 0 L: 192.168.90.51:56110 R: 192.168.90.100:3260]2013-05-16T16:08:39.225Z cpu4:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: vmhba37:CH:3 T:6 CN:0: Connection rx notifying failure: Failed to Receive. State=Bound2013-05-16T16:08:39.225Z cpu4:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Sess [ISID: TARGET: (null) TPGT: 0 TSIH: 0]2013-05-16T16:08:39.225Z cpu4:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Conn [CID: 0 L: 192.168.90.51:56110 R: 192.168.90.100:3260]2013-05-16T16:08:39.233Z cpu4:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: vmhba37:CH:4 T:6 CN:0: Failed to receive data: Connection closed by peer2013-05-16T16:08:39.233Z cpu4:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Sess [ISID: TARGET: (null) TPGT: 0 TSIH: 0]2013-05-16T16:08:39.233Z cpu4:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Conn [CID: 0 L: 192.168.90.53:57285 R: 192.168.90.100:3260]2013-05-16T16:08:39.233Z cpu4:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: vmhba37:CH:4 T:6 CN:0: Connection rx notifying failure: Failed to Receive. State=Bound2013-05-16T16:08:39.233Z cpu4:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Sess [ISID: TARGET: (null) TPGT: 0 TSIH: 0]2013-05-16T16:08:39.233Z cpu4:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Conn [CID: 0 L: 192.168.90.53:57285 R: 192.168.90.100:3260]2013-05-16T16:08:39.494Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba37:CH:0 T:6 CN:0: iSCSI connection is being marked "OFFLINE" (Event:4)2013-05-16T16:08:39.494Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: TARGET: (null) TPGT: 0 TSIH: 0]2013-05-16T16:08:39.494Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 192.168.90.50:63278 R: 192.168.90.100:3260]2013-05-16T16:08:39.495Z cpu0:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x41002347f910 network resource pool netsched.pools.persist.iscsi associated2013-05-16T16:08:39.495Z cpu0:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x41002347f910 network tracker id 1 tracker.iSCSI.192.168.90.104 associated2013-05-16T16:08:39.495Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba37:CH:2 T:6 CN:0: iSCSI connection is being marked "OFFLINE" (Event:4)2013-05-16T16:08:39.495Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: TARGET: (null) TPGT: 0 TSIH: 0]2013-05-16T16:08:39.495Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 192.168.90.52:51827 R: 192.168.90.100:3260]2013-05-16T16:08:39.496Z cpu0:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410023461d30 network resource pool netsched.pools.persist.iscsi associated2013-05-16T16:08:39.496Z cpu0:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410023461d30 network tracker id 1 tracker.iSCSI.192.168.90.104 associated2013-05-16T16:08:39.496Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba37:CH:3 T:6 CN:0: iSCSI connection is being marked "OFFLINE" (Event:4)2013-05-16T16:08:39.496Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: TARGET: (null) TPGT: 0 TSIH: 0]2013-05-16T16:08:39.496Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 192.168.90.51:56110 R: 192.168.90.100:3260]2013-05-16T16:08:39.497Z cpu0:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x41002cdc23b0 network resource pool netsched.pools.persist.iscsi associated2013-05-16T16:08:39.497Z cpu0:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x41002cdc23b0 network tracker id 1 tracker.iSCSI.192.168.90.101 associated2013-05-16T16:08:39.497Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba37:CH:4 T:6 CN:0: iSCSI connection is being marked "OFFLINE" (Event:4)2013-05-16T16:08:39.497Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: TARGET: (null) TPGT: 0 TSIH: 0]2013-05-16T16:08:39.497Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 192.168.90.53:57285 R: 192.168.90.100:3260]2013-05-16T16:08:39.498Z cpu0:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x41002cdc2a50 network resource pool netsched.pools.persist.iscsi associated2013-05-16T16:08:39.498Z cpu0:2724)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x41002cdc2a50 network tracker id 1 tracker.iSCSI.192.168.90.102 associated2013-05-16T16:08:40.873Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StartConnection: vmhba37:CH:2 T:6 CN:0: iSCSI connection is being marked "ONLINE"2013-05-16T16:08:40.873Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StartConnection: Sess [ISID: 00023d000007 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:40.873Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StartConnection: Conn [CID: 0 L: 192.168.90.52:62320 R: 192.168.90.104:3260]2013-05-16T16:08:40.874Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StartConnection: vmhba37:CH:0 T:6 CN:0: iSCSI connection is being marked "ONLINE"2013-05-16T16:08:40.874Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StartConnection: Sess [ISID: 00023d000005 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:40.874Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StartConnection: Conn [CID: 0 L: 192.168.90.50:56018 R: 192.168.90.104:3260]2013-05-16T16:08:40.875Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StartConnection: vmhba37:CH:3 T:6 CN:0: iSCSI connection is being marked "ONLINE"2013-05-16T16:08:40.875Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StartConnection: Sess [ISID: 00023d000006 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:40.875Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StartConnection: Conn [CID: 0 L: 192.168.90.51:55351 R: 192.168.90.101:3260]2013-05-16T16:08:40.876Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StartConnection: vmhba37:CH:4 T:6 CN:0: iSCSI connection is being marked "ONLINE"2013-05-16T16:08:40.876Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StartConnection: Sess [ISID: 00023d010008 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:40.876Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StartConnection: Conn [CID: 0 L: 192.168.90.53:60923 R: 192.168.90.102:3260]2013-05-16T16:08:40.963Z cpu6:3533)ScsiScan: 1098: Path 'vmhba37:C0:T6:L0': Vendor: 'EQLOGIC ' Model: '100E-00 ' Rev: '5.2 '2013-05-16T16:08:40.963Z cpu6:3533)ScsiScan: 1101: Path 'vmhba37:C0:T6:L0': Type: 0x0, ANSI rev: 5, TPGS: 1 (implicit only)2013-05-16T16:08:40.964Z cpu6:3533)ScsiScan: 1582: Add path: vmhba37:C0:T6:L02013-05-16T16:08:40.964Z cpu6:3533)ScsiScan: 1098: Path 'vmhba37:C2:T6:L0': Vendor: 'EQLOGIC ' Model: '100E-00 ' Rev: '5.2 '2013-05-16T16:08:40.964Z cpu6:3533)ScsiScan: 1101: Path 'vmhba37:C2:T6:L0': Type: 0x0, ANSI rev: 5, TPGS: 1 (implicit only)2013-05-16T16:08:40.965Z cpu6:3533)ScsiScan: 1582: Add path: vmhba37:C2:T6:L02013-05-16T16:08:40.965Z cpu6:3533)ScsiScan: 1098: Path 'vmhba37:C3:T6:L0': Vendor: 'EQLOGIC ' Model: '100E-00 ' Rev: '5.2 '2013-05-16T16:08:40.965Z cpu6:3533)ScsiScan: 1101: Path 'vmhba37:C3:T6:L0': Type: 0x0, ANSI rev: 5, TPGS: 1 (implicit only)2013-05-16T16:08:40.965Z cpu6:3533)ScsiScan: 1582: Add path: vmhba37:C3:T6:L02013-05-16T16:08:40.966Z cpu6:3533)ScsiScan: 1098: Path 'vmhba37:C4:T6:L0': Vendor: 'EQLOGIC ' Model: '100E-00 ' Rev: '5.2 '2013-05-16T16:08:40.966Z cpu6:3533)ScsiScan: 1101: Path 'vmhba37:C4:T6:L0': Type: 0x0, ANSI rev: 5, TPGS: 1 (implicit only)2013-05-16T16:08:40.967Z cpu6:3533)ScsiScan: 1582: Add path: vmhba37:C4:T6:L02013-05-16T16:08:40.967Z cpu1:3533)ScsiPath: 4541: Plugin 'NMP' claimed path 'vmhba37:C4:T6:L0'2013-05-16T16:08:40.967Z cpu1:3533)ScsiPath: 4541: Plugin 'NMP' claimed path 'vmhba37:C3:T6:L0'2013-05-16T16:08:40.967Z cpu1:3533)ScsiPath: 4541: Plugin 'NMP' claimed path 'vmhba37:C2:T6:L0'2013-05-16T16:08:40.967Z cpu1:3533)ScsiPath: 4541: Plugin 'NMP' claimed path 'vmhba37:C0:T6:L0'2013-05-16T16:08:41.063Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: vmhba37:CH:1 T:6 CN:0: Failed to receive data: Connection closed by peer2013-05-16T16:08:41.063Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Sess [ISID: 00023d000008 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:41.063Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Conn [CID: 0 L: 192.168.90.53:56744 R: 192.168.90.103:3260]2013-05-16T16:08:41.063Z cpu0:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: vmhba37:CH:1 T:6 CN:0: Connection rx notifying failure: Failed to Receive. State=Online2013-05-16T16:08:41.063Z cpu0:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Sess [ISID: 00023d000008 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:41.063Z cpu0:2724)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Conn [CID: 0 L: 192.168.90.53:56744 R: 192.168.90.103:3260]2013-05-16T16:08:41.063Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba37:CH:1 T:6 CN:0: iSCSI connection is being marked "OFFLINE" (Event:6)2013-05-16T16:08:41.063Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: 00023d000008 TARGET: iqn.2001-05.com.equallogic:4-52aed6-56c15d168-d6c0021a85c4f71c-eql-esxi-vol-f TPGT: 1 TSIH: 0]2013-05-16T16:08:41.063Z cpu0:2724)WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 192.168.90.53:56744 R: 192.168.90.103:3260]2013-05-16T16:08:41.063Z cpu12:2701)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP device "naa.64ed2a85165dc1561cf7c4851a02c0d6" state in doubt; requested fast path state update...2013-05-16T16:08:41.063Z cpu12:2701)ScsiDeviceIO: 2309: Cmd(0x412441465980) 0x28, CmdSN 0x800000fd from world 4863 to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" failed H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.2013-05-16T16:08:41.063Z cpu12:2701)ScsiDeviceIO: 2309: Cmd(0x41244037cbc0) 0x28, CmdSN 0x80000080 from world 4863 to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" failed H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.2013-05-16T16:08:41.092Z cpu12:2060)ScsiDeviceIO: 2309: Cmd(0x412441bb3300) 0x28, CmdSN 0x8000002e from world 4863 to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" failed H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.2013-05-16T16:08:41.092Z cpu12:2060)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x28 (0x412441baeec0, 4863) to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" on path "vmhba37:C1:T6:L0" Failed: H:0x2 D:0x0 P:0x0 Possible sense data: 0x5 0x24 0x0. Act:EVAL2013-05-16T16:08:41.092Z cpu12:2060)ScsiDeviceIO: 2309: Cmd(0x412441baeec0) 0x28, CmdSN 0x80000059 from world 4863 to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" failed H:0x2 D:0x0 P:0x0 Possible sense data: 0x5 0x24 0x0.2013-05-16T16:08:41.146Z cpu13:5262)ScsiDeviceIO: 2309: Cmd(0x412441834100) 0x28, CmdSN 0x80000040 from world 4863 to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" failed H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.2013-05-16T16:08:41.170Z cpu12:2060)ScsiDeviceIO: 2309: Cmd(0x4124403a6c80) 0x28, CmdSN 0x8000006a from world 4863 to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" failed H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.2013-05-16T16:08:41.200Z cpu8:2056)ScsiDeviceIO: 2309: Cmd(0x41244037b5c0) 0x28, CmdSN 0x800000c9 from world 4863 to dev "naa.64ed2a85165dc1561cf7c4851a02c0d6" failed H:0x2 D:0x0 P:0x0 Possible sense data: 0x2 0x3a 0x1.2013-05-16T16:08:41.218Z cpu11:2088)WARNING: dell_psp_eql_routed: psp_eqlUpdatePathSelection:1014:Path is reported as inactive (0x50475304)2013-05-16T16:08:41.233Z cpu2:2201)WARNING: dell_psp_eql_routed: psp_eqlUpdatePathSelection:1014:Path is reported as inactive (0x50475304)2013-05-16T16:08:42.072Z cpu7:2209)ScsiPath: 4963: DeletePath : adapter=vmhba37, channel=1, target=6, lun=02013-05-16T16:08:42.074Z cpu15:2063)WARNING: NMP: nmp_DeviceStartLoop:721:NMP Device "naa.64ed2a85165dc1561cf7c4851a02c0d6" is blocked. Not starting I/O from device.2013-05-16T16:08:42.074Z cpu13:2061)WARNING: NMP: nmp_DeviceStartLoop:721:NMP Device "naa.64ed2a85165dc1561cf7c4851a02c0d6" is blocked. Not starting I/O from device.2013-05-16T16:08:42.074Z cpu7:2209)WARNING: ScsiPath: 5022: Remove path: vmhba37:C1:T6:L0
  
  Thanks for any information you can provide.
  

  When a connection is moved either by the table for IO balancing through interfaces available on the battery, page movement when you have more than three members in a pool, or with installed MEM it will periodically move connections, you will see redundancy lost messages.  As you have noted, at the time wherever you check paths, that connection has already connected as it should.   For this shorter periods, less than a second in general, this session is gone and again one is created at the same time.  The volume is always accessible via the other sessions.   Therefore, a message of info, not an indication of a problem.  When the table of balances of the slices for a new Member in the pools only three, expect to see many, simulaneous messages from all hosts to connect to the data store.  This whirlpool is quite normal.