iSCSI issue

Hello everyone,

I'm experimenting with iscsi san for my storage. I use open-e as the software. So far, I guess that everything works. In Vsphere, I did new data warehouses. And in my VMs, I can connect to the correct data store and use it as a player. But there is something that does not appear clear to me. When I connect a data store to a virtual machine and start to fill with data, there is no problem.

When I take a second vm and connect it to the same data store, I don't see what I put it through my other virtual machine data. Is this normal and can I change this so I can see the same information in both my VM?

Thank you very much

onkt

If I get you right... looking for a concept of disk shared between two virtual machines with your iSCSI datastore...

VMware only supports MCSC 2 NŒUD clustered VM to have a shared drive...

Please follow the link for details of configuration below: http://www.vmware.com/pdf/vsphere4/r40/vsp_40_mscs.pdf

Please consider clicking on the button 'OK' or 'Useful', if this information is useful.

Tags: VMware

Similar Questions

  • Vnic iSCSI issue

    Hi all

    I'm having a problem trying to my Iscsi paths on seprate phyical spend the vNIC phyical spreate configuration switch management. What I was going to do, install a switch management traffic and an another vmotion/iscsi. The problem occurs when I plug the vnic iscsi switch no dhcp and assign an IP address. After that I give him a grave management port IP address fail though even it is not connected to this switch.

    For me, the vNIC should be dependent on each other and I'm really confused at this point. Any help would be great.

    Steve

    After the screenshot of the network the IP address used for iSCSI (192.168.3. 1) is in the same subnet as the management network (192.168.3. 196) which most likely results in a routing problem. I would recommend that use you a dedicated subnet, not routed for traffic iSCSI, such as (192.168.1. 113) you mentioned earlier.

    André

  • vSphere on HP P2000 (aka Lefthand) - iSCSI issue

    We are looking at one of the models of the HP lefthand SAN Pxxxx I have some questions about how the device communicates via iSCSI. I read that it is extensible by adding nodes which also increases your bandwidth. I also read articles on how the writing/recieve max limitted by a single NETWORK card of 1 GB. Here is the article: http://frankdenneman.wordpress.com/2009/10/11/lefthand-san-lessons-learned/

    Now my question for ESX or vSphere on the lefthand device is, can you add NIC to increase my band bandwidth iSCSI for host of the ESX host? Say if I add a 4 HP NIC port, can I configure it to a pipe of 4 GB iSCSI and which will be by writing/recieve max speed? By section of the link, all iSCSI connections are limitted in writing/recieve in a single network adapter.

    By the link, it looks like all links and/or "allegiance connection" is limited to the unit from left to a single NETWORK card, which is of 1 GB. If this is true, then there is really no reason to buy the additional NETWORK adapter

    Any contribution is appreciated.

    Thank you

    COS,

    See the link to the doc HP running vsphere on the left.

    http://h20195.www2.HP.com/v2/GetPDF.aspx/4AA3-0261ENW.PDF

    The iscsi configuration guide is below.

    http://www.VMware.com/PDF/vSphere4/r40_u1/vsp_40_u1_iscsi_san_cfg.PDF

    Also take a look at this article

    http://virtualgeek.typepad.com/virtual_geek/2009/09/a-multivendor-post-on-using-iSCSI-with-VMware-vSphere.html

    Best regards

    DC

  • issue of configuration for the store of data/LUN iSCSI

    Hi all!  I am all new to VMWare and iSCSI, and I have a question about data warehouses regarding being mounted on an iSCSI target.

    Here's my setup.  I have a Dell PowerEdge R810 connected over a link to 10 GB dedicated to a Dell PowerEdge 2950 that I use as a SAN.  The R810 has no hard drives in it, it starts ESXi on a redundant configuration of SD card integrated into the server.  My SAN software is Server 2008 Enterprise with Microsoft iSCSI software Target 3.3 installed.  I created target 1, LUN 0, 800 GB .vhd file sitting on a NTFS partition and set up a store of data on it in VCenter.  The data store is the size of the entire iSCSI, 800 GB target.  I have my first virtual server up and get 50GB of space between the data store.

    Here is my question: can I create several virtual machines using the data store I put in place?  I know it sounds like a stupid question, but my concern comes from some reading I did on several computers, access to a single LUN.  If I set up another virtual machine, it will explode on my SAN file system as two virtual machines would be to access the same big VHD file on the NTFS partion, or I'm far from base?

    Issue of bonus points:

    I have an another R810 that I will be online soon.  Assuming that I am OK to add more virtual machines of my first machine, pourrais I connect this box in the data store as well and create virtual machines, or should I set up a separate data on another iSCSI target store?

    Thanks for your patience with a new guy.  I searched and read for hours, and I could have read too much so I thought that I had just askt experts.

    Hello and welcome to the forums.

    Can I create several virtual machines using the data store that I put in place?

    Yes.

    If I set up another virtual machine, it will explode on my SAN file system as two virtual machines would be to access the same big VHD file on the NTFS partion, or I'm far from base?

    No, you should be fine.  One thing to keep in mind is that the Windows/MS iSCSI target is not a supported storage solution.  There could be problems of scalability with iSCSI Windows/MS, but you'll be fine in a VMware perspective.

    I have an another R810 that I will be online soon.  Assuming that I am OK to add more virtual machines of my first machine, pourrais I connect this box in the data store as well and create virtual machines, or should I set up a separate data on another iSCSI target store?

    You could, but I personally would put in place a different data store on another iSCSI target.

    Good luck!

  • Reclassification of 5.0 to 5.1 issue with iSCSI

    I have a number of HP BL490c G7 SAN EMC e via flexible HP 10 virtual connect network.

    With esxi 5.0 U1, could see the LUN and boot from SAN, which was great.

    I used VUM 5.1 update after update vCenter.

    The update process failed leaving me with a black screen on the console startup esxi indicating the installation script failed, pressing enter just rebooted.

    I deleted and then re-created the boot LUN and I install from scratch, 5.1 when I boot from the ISO image, he is unable to see any external storage to install to, 5.0 U1 still shows any fine the LUN during the installation process, so I know the material is always good and esxi 5.0 U1 still works fine.

    If something has changed for the iSCSI HBA support between U1 5.0 and 5.1?

    Is that what I can do to get this working?

    Thanks in advance.

    OK, looks like the images are missing the driver necessary be2iscsi for iSCSI independent material, to ESXi vanilla as well as HP Custom ISO:

    ~ software # esxcli profile
    (Updated) HP-ESXi - 5.1.0 - standard-iso
    Name: (updated) HP-ESXi - 5.1.0 - standard-iso
    Seller: host01.local
    Creation date: 2012-09 - 17 T 05: 22:29
    Modification date: 2012-09 - 25 T 08: 57:20
    Loan without a State: false
    Description:

    2012 09-17 T 05: + 00:00 22:29.656115: are the following VIBs
    installed:
    epsec-mux 5.1.0 - 757363
    ----------
    2012 09-13 T 18: + 00:00 30:35.687583: are the following VIBs
    installed:
    VMware-fdm 5.1.0 - 799731
    ----------
    Profile of customized HP for ESXi 5.1.0 ISO Image

    [...]

    ~ List of the vib # esxcli software | grep be2net
    NET-be2net 4.1.255.11 - 1vmw.510.0.0.799733 VMware VMwareCertified 2012-09-12
    ~ List of the vib # esxcli software | grep be2iscsi

    [Nothing]

    Picture of HP information list nor a updated driver be2iscsi:

    http://h18004.www1.HP.com/products/servers/Software/VMware-ESXi/driver_version.html

    Image 5.0 has a SCSI-BE2. V00 file that contains the driver be2iscsi. I don't know why they failed in 5.1 ESXi.

    Try to manually add the be2iscsi driver to your image:

    https://my.VMware.com/Web/VMware/details?downloadGroup=DT-ESX50-Emulex-be2iscsi-413343&ProductID=229

    http://v-front.blogspot.de/p/ESXi-customizer.html

    And to your original question around change 5.1 to hardware iSCSI, they have added support for frames:

    http://cormachogan.com/2012/09/10/vSphere-5-1-storage-enhancements-part-5-storageprotocols/

  • MPIO iSCSI Config issues multiple vmKnics and natachasery several...

    Hey guys... I am trying to wrap my head around this whole MPIO and iSCSI configuration. I read all the documents there (from dell to vmware) and I'm still wrapping my head arounda couple things and I hope that someone could take a few minutes and just explain it a bit clearer for me.

    First of all. When you create a vSwitch and add vmknics to the vswitch, configuration says that you can have only ONE active adapter. If you go and delete this second card and put it in unused. Why do you need two cards when the second one is just going to be configured as unused? Even if this Teddy fails the secondary image is defined for unused and no failover then what is the point of the configuration of the other?

    In the second place. When you create a vSwitch and add several vmknics and then bind to the iSCSI initiator (I understand and have done laboratory) why some manufacturers (dell equalogic) saying create as many vmknics as natachasery you have? Is it so you all flow through that 1 GB direct as possible? Some walk through see a vmknic by iSCSI connection, what is the best practice?

    Third and last. I read that you should have vswitch as much as you do to your network iSCSI networks.  So if I have two separate iSCSI networks will my storage I will need two separate vSwitches and then bind these NICs vmk on the two vswitches to my iSCSI initiator. Its okay?

    Thanks in advance for any more detailed explanation!

    This is the document that you are referring to? http://attachments.wetpaintserv.us/Hb2187XrZtZHUBMwbBrD4A%3D%3D1015900

    I also confirmed that there is no limitation of 4 GB on LAG for PowerConnect 5424. You can LAG ports and 8 Gbps hose 8.

    Bala

    Dell Inc.

  • ISCSI software issues

    I think I'm loing my mind and I forgot a few basic things that if someone can update it please my mind that I can't find it in any documentation?http://communities.vmware.com/images/emoticons/confused.gif

    (1) different iSCSI targets how can you use simultaneously with the initator of integrated iSCSI vkernel?  This is true for ESX 3.0 and 3.5.

    (2) if I run HBA iSCSI;  can I still use software iSCSI?  For some reason, I stuck it in my mind that I can't do this (it is hardware or software... can't do both at the same time).

    Thank you all!http://communities.vmware.com/images/emoticons/grin.gif

    (1) 64 targets

    (2) use you software initiator or hardware initiator, not both

    concerning

    Jose

  • Hyper-V VSS on iSCSI

    It is possible to activate the VSS via an iSCSI connection? I'm doing a backup of a hard drive to remote servers, which is hosted on a San and connected via iSCSI. The backup client can see the virtual C drive of servers but not the E drive, which is on the SAN.

    All servers running Server R2 DC 2012.

    Thank you


    This issue is beyond the scope of this site and must be placed on Technet or MSDN

    http://social.msdn.Microsoft.com/forums/en-us/home

  • Net M4110x - Net management and iSCSI. Clarification of the configuration steps. The documentation is at best ambiguous.

    Hi guys,.

    I'm having a lot of trouble to translate what I know PS6000 table to the new M4100x.  Here's what I'm building:

    I want my iSCSI traffic that is completely isolated from all other traffic, and I want to use the CMC network to run the Board.  It must be a simple configuration, but Dell documentation for which is worse than useless.  It confuses and everyone who's read it confuses.  Why is this?

    It seems that I should be able to assign the IP addresses of management using the MCC according to DELL:

    Step 1.  Initialize the storage

    * Once in the CMC right-click on storage open storage gui initialization.

    * Member name: MY_SAN01
    * Member, IP: 192.168.101.10
    * Member gateway: 192.168.101.254
    Group name: MY_SAN
    Group IP address: 192.168.101.11
    Group of Memebersip password: groupadmin
    * Password Admin group: groupadmin

    It sounds simple enough, and when I apply this I guess I will be disconnected my M4110x simply because it currently resides on a separate network (net 2 in the image above).  Now how to set up the IP address of my CMC (net0 in the picture above) network management?

    Step 2.  Set ip management port

    According to the documentation of Dell, I have:

    To set the management port:

    * Open a telnet (ssh) session on a computer or console that has access to the PS-M4110 range. The array must be configured beforehand.
     
    * Connect the PS-M4110 modules using the following racadm command: racadm Server 15 connect
     
    * Connect to the PS-M4110 array as grpadmin

    Once I am in:

    Activate the management controller ports using the following commands in the CLI:
    0 > member select MY_SAN01
    1. (array1) > eth select 1
    2. (array1 eth_1) > 10.10.10.17 ipaddress netmask 255.255.255.0
    3. (array1 eth_1) > upward
    4. (array1 eth_1) > exit
    5. (array1) > grpparams
    6. (array1 (grpparams)) > network management-ipaddress 10.10.10.17

    (array1 (grpparams)) > exit

    My interpretation is correct?  Now my questions:

    1. in step 2. SubStep 1 - How can I know what ethernet interface to use?  Step 1 automatically assume eth0?

    2. am I correct in using the same IP address for both step 2 - substep 2 and substep 6?  Or do I have to assign a different IP address for these?  10.10.10.18 maybe.

    3. step 2 - substep 6, it doesn't seem to be that a network mask is that correct?

    4. comparison of the ps6000e - I set up an IP address for each controller (so 2) and then assigned an IP address for the group.  It's 3 IP addresses.  For this M4110, it seems that I have only one controller.  Is this correct?  The specifications make a point that there are 2 controllers.  What happened to the IP address of the controller of the 2nd?

    CLOSE-UPS

    I intend on building a VMware cluster using the algorithm of multiple paths of DELL and I built it to the DSC, but a technician Dell put in place the table initially and have not set up a dedicated management port.  Required configuration routing traffic on the net iSCSI management.  It is not recommended, and I don't want to set up this way.

    Currently, he is a blocking problemand I need to go beyond this ASAP.  I work with a large system integrator in Texas and plan on the order that these systems built this way on their part.  This means that I must be able to explain to them how to proceed.  This issue is standing in the way of progress, and I really hope I can get a satisfactory response from this forum.  Thanks for any helpful answers.

    I think I have the answers to my own questions:

    1. YES.  Step 1 automatically assume eth0.  There are TWO Ethernet interfaces and eth1 is disabled by default, and unless you use step 2 to set the management port this second Ethernet interface is never used.

    2. No. I can't use the same IP address for both lines.  In lower level 6 I need to use a different IP address on the same network 10.10.10.18 would work fine.

    3. YES.  It is correct.  Lower level 6 assumes the network mask that I have included in the point 2.

    4. it's tricky.  There is NO WAY to configure Active/active on these tables.  There are 2 controllers, but one "still asleep," unless the other fails.  Actually, the IP address is assigned to an Abstraction Layer, it maintains.  When fails another controller "awakens" and just starting to accept traffic and it doesn't care what its IP address.

    Another point.  Now that my table is initialized and my interfaces are configured, I need to know what IP address to point my ESXi hosts for their storage.  Use the IP address of the group assigned in step 1.  It is 192.168.101.11 (there is typo in the original post).

  • Issue of the journal of diagnosis

    I'm an EQL PS6100 storage array usage in a disconnected site where items must be (absolutely no exceptions) reviewed before sending. Diagnosis of the table is encrypted and is not human-readable. I was able to work with support without diagnostic logs but am now running in a recurring issue.

    I would like to get these logs to Dell in order to identify a root cause. Is there a way to generate unencrypted newspapers or a certificate of sorts offered by Dell that indicates the data found in the newspapers themselves?

    Thanks for any input.

    Hello

    There is no document like this, I know.   Does not mean that it could not be written.

    Short version is the diag newspapers are the result of various exclusive commands that dump newspapers, the DB group, info on the H/W status, network status, .drive history, cache, etc.   As a block device table doesn't have access to the flies.  Blocks are translated in the pages of 15 MB.  Each page may have different parts of a volume on the subject.  Data on the pages is not used in the order.  So, even if the controller could access the data, it's like crack an egg to the EQL OS uses to start the controller.  The management software for network, iSCSI and all admin operations are handled by code EQL.   Only HTTP: / Telenet/SSH/ftp are managed by the OS default.

    Re: RCA.  Without complete diagnostic tests, I would say that it is impossible to determine the RCA.  Moreover, newspapers are circular, so longer you wait, the more likely some data will be restored by the newspapers.

    Re: on-site.  No, field technicians are lead in order to replace the failed H/W no triage.

    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.

  • [vbscript] How to analyze "@FirewallAPI.dll,-29006 ' to 'iSCSI Service (TCP-In).

    Hello

    I have a string "@FirewallAPI.dll,-29006" and want to recover the text from the dll string. (in this case the text is "iSCSI Service (TCP-In)")

    I don't know how this notation is called, so I can't find out how its done.

    Is it possible directly from vbscript, or is it better to call an external exe to retrieve the text of the dll, if so, how?

    Thanks in advance,

    / S

    Hello Sander,

    As you try to expand a vbscript script, we have a special forum dedicated to issues of this kind. Request to display the query in the MSDN forum for better support.

    MSDN forum

    Answer if you need help with Windows, and we will be happy to help.

  • storage iSCSI with UCS

    Hi all

    Can I ask a question regarding the connection of iSCSI storage for use with UCS. Look at us with Nimble iSCSI based storage & want to understand best practice recommendations on how to connect it to UCS to get the best level of performance & reliability / resilience etc.

    Another issue is more closely how VMware deals with loss of connectivity on a path (where double connections are the installation program from the warehouse to the tissues), would he re - route traffic to the path running?

    Any suggestion would be appreciated.

    Kassim

    Hello Kassim,

    Currently the agile iSCSI storage is certified with UCS 2.0.3 firmware version.

    http://www.Cisco.com/en/us/docs/unified_computing/UCS/interoperability/matrix/r_hcl_B_rel2.03.PDF

    The following guide can serve as a reference.

    Virtualization solution Cisco with the agile storage reference Architecture

    http://www.Cisco.com/en/us/solutions/collateral/ns340/ns517/ns224/ns836/ns978/guide_c07-719522.PDF

    In above installation, ESXi software iSCSi multipath with PSP Round Robin algorithm is implemented to take care of the IO and failover with load balancing two paths.

    HTH

    Padma

  • ESXi 6.0 U1 U2 upgrade, iSCSI questions

    Hello

    First post, so I'll try and summarize my thoughts and what I did with troubleshooting.  Please let me know if I left anything out or more information is required.

    I use the free ESXi 6.0 on a Board with a CPU Intel Xeon E3-1231v3 and 32 GB of DDR3 ECC UDIMM mATX to Supermicro X10SLL-F.  I use a 4G USB FlashDrive for start-up, 75 GB 2.5 "SATA to local storage (i.e. /scratch) and part of a 120 GB SSD for the cache of the host, as well as local storage.  The main data store for virtual machines are located on a target (current running FreeNAS 9.3.x). iSCSI  This Setup worked great since installing ESXi 6.0 (June 2015), then 6.0 U1 (September 2015) and I recently made the leap to 6.0 U2.  I thought everything should be business as usual for the upgrade...

    However, after upgrading to 6.0 U2 none of the iSCSI volumes are "seen" by ESXi- vmhba38:C0:T0 & vmhba38:C0:T1, although I can confirm that I can ping the iSCSI target and the NIC (vmnic1) vSwitch and VMware iSCSI Software adapter are loaded - I did not bring any changes to ESXi and iSCSI host before the upgrade to 6.0 U2.  It was all work beforehand.

    I went then to dig in the newspapers; VMkernel.log and vobd.log all report that there is not able to contact the storage through a network issue.  I also made a few standard network troubleshooting (see VMware KB 1008083); everything going on, with the exception of jumbo frame test.

    [root@vmware6:~] tail - f /var/log/vmkernel.log | grep iscsi

    [ ... ]

    (2016 03-31 T 05: 05:48.217Z cpu0:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba38:CH:0 T: 0 CN:0: iSCSI connection is being marked "OFFLINE" (event: 5)

    (2016 03-31 T 05: 05:48.217Z cpu0:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: TARGET: TPGT (null): TSIH 0: 0]

    (2016 03-31 T 05: 05:48.217Z cpu0:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 10.xxx.yyy.195:41620 r L: 0: 10.xxx.yyy.109:3260]

    (2016 03-31 T 05: 05:48.218Z cpu4:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba38:CH:0 T:1 CN:0: connection iSCSI is being marked "OFFLINE" (event: 5)

    (2016 03-31 T 05: 05:48.218Z cpu4:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: TARGET: TPGT (null): TSIH 0: 0]

    (2016 03-31 T 05: 05:48.218Z cpu4:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 10.xxx.yyy.195:32715 r L: 0: 10.xxx.yyy.109:3260]

    [root@vmware6:~] tail - f /var/log/vobd.log

    [ ... ]

    2016 03-31 T 05: 05:48.217Z: [iscsiCorrelator] 1622023006us: [vob.iscsi.connection.stopped] iScsi connection 0 arrested for vmhba38:C0:T0

    2016 03-31 T 05: 05:48.217Z: [iscsiCorrelator] 1622023183us: [vob.iscsi.target.connect.error] vmhba38 @ vmk1 could not connect to iqn.2005 - 10.org.freenas.ctl:vmware - iscsi because of a network connection failure.

    2016 03-31 T 05: 05:48.217Z: [iscsiCorrelator] 1622002451us: [esx.problem.storage.iscsi.target.connect.error] connection iSCSI target iqn.2005 - 10.org.freenas.ctl:vmware - iscsi on vmhba38 @ vmk1 failed. The iSCSI Initiator failed to establish a network connection to the target.

    2016 03-31 T 05: 05:48.218Z: [iscsiCorrelator] 1622023640us: [vob.iscsi.connection.stopped] iScsi connection 0 arrested for vmhba38:C0:T1

    2016 03-31 T 05: 05:48.218Z: [iscsiCorrelator] 1622023703us: [vob.iscsi.target.connect.error] vmhba38 @ vmk1 could not connect to

    [root@vmware6:~] ping 10.xxx.yyy.109

    PING 10.xxx.yyy.109 (10.xxx.yyy.109): 56 bytes

    64 bytes from 10. xxx.yyy. 109: icmp_seq = 0 ttl = 64 time = 0,174 ms

    64 bytes from 10. xxx.yyy. 109: icmp_seq = 1 ttl = 64 time = 0,238 ms

    64 bytes from 10. xxx.yyy. 109: icmp_seq = 2 ttl = 64 time = 0,309 ms

    -10. ping.109 xxx.yyystats-

    3 packets transmitted, 3 packets received, 0% packet loss

    round-trip min/avg/max = 0.174/0.240/0.309 ms

    vmkping [root@vmware6:~] 10. xxx.yyy.109

    PING 10.xxx.yyy.109 (10. xxx.yyy. 109): 56 bytes

    64 bytes from 10. xxx.yyy. 109: icmp_seq = 0 ttl = 64 time = 0,179 ms

    64 bytes from 10. xxx.yyy. 109: icmp_seq = 1 ttl = 64 time = 0,337 ms

    64 bytes from 10. xxx.yyy. 109: icmp_seq = 2 ttl = 64 time = 0.382 ms

    -10. ping.109 xxx.yyystats-

    3 packets transmitted, 3 packets received, 0% packet loss

    round-trip min/avg/max = 0.179/0.299/0.382 ms

    [root@vmware6:~] NF - z 10. xxx.yyy3260.109

    Connection to 10. xxx.yyy3260.109 port [tcp / *] succeeded!

    [root@vmware6:~] vmkping 8972 10 s. xxx.yyy.109 - d

    PING 10.xxx.yyy.109 (10. xxx.yyy. 109): 8972 data bytes

    -10. ping.109 xxx.yyystats-

    3 packets transmitted, 0 packets received, 100% packet loss

    I began to watch the drivers NIC thinking maybe something got screwed up during the upgrade; not the first time I saw problems with the out-of-box drivers supplied by VMware.  I checked VMware HCL for IO devices; the physical NIC used on that host are Intel I217-LM (nic e1000e), Intel I210 (nic - igb) and Intel® 82574 L (nic-e1000e).  Lists HCL from VMware that the driver for the I217-LM & 82574L should be version 2.5.4 - I210 and 6vmw should be 5.0.5.1.1 - 5vmw.  When I went to check, I noticed that he was using a different version of the e1000e driver (I210 driver version was correct).

    [root@vmware6:~] esxcli list vib software | e1000e grep

    Name Version Date seller installation acceptance level

    -----------------------------  ------------------------------------  ------  ----------------  ------------

    NET-e1000e 3.2.2.1 - 1vmw.600.1.26.3380124 VMware VMwareCertified 2016-03-31

    esxupgrade.log seems to indicate that e1000e 2.5.4 - VMware 6vmw should have been loaded...

    [root@esxi6-lab: ~] grep e1000e /var/log/esxupdate.log

    [ ... ]

    # ESXi 6.0 U1 upgrade

    2015-09 - 29 T 22: 20:29Z esxupdate: BootBankInstaller.pyc: DEBUG: about to write payload "net-e100" of VIB VMware_bootbank_net - e1000e_2.5.4 - 6vmw.600.0.0.2494585 to "/ tmp/stagebootbank".

    [ … ]

    # ESXi 6.0 U2 upgrade

    2016-03 - 31 T 03: 47:24Z esxupdate: BootBankInstaller.pyc: DEBUG: about to write to payload "net-e100" of VIB VMware_bootbank_net - e1000e_2.5.4 - 6vmw.600.0.0.2494585 to ' / tmp/stagebootbank '

    3.2.2.1 - 1vmw e1000e is recommended for 5.5 U3 and not 6.0 U2 ESXi ESXi driver!  As these drivers are listed as "Inbox", I don't know if there is an easy way to download the drivers supplied by seller (vib) for him, or even if they exist.  I found an article online to manually update drivers on an ESXi host using esxcli; I tried check and install the new e1000e drivers.

    [root@vmware6:~] esxcli software update net-e1000e-n-d vib https://hostupdate.VMware.com/software/VUM/production/main/VMW-Depot-index.XML

    Result of the installation

    Message: The update completed successfully, but the system must be restarted for the changes to be effective.

    Restart required: true

    VIBs installed: VMware_bootbank_net - e1000e_3.2.2.1 - 2vmw.550.3.78.3248547

    VIBs removed: VMware_bootbank_net - e1000e_3.2.2.1 - 1vmw.600.1.26.3380124

    VIBs ignored:

    As you can see there is a newer version and installed it.  However after restarting it still did not fix the issue.  I even went so far as to force the CHAP password used to authenticate to reset and update on both sides (iSCSI initiator and target).  At this point, I wonder if I should somehow downgrade and use the driver of 2.5.4 - 6vmw (how?) or if there is another issue at play here.  I'm going down a rabbit hole with my idea that it is a NETWORK card driver problem?

    Thanks in advance.

    --G

    esxi6-u2-iscsi.jpg

    I found [a | the?] solution: downgrade for 2.5.4 drivers - Intel e1000e 6.0 U1 6vmw.  For the file name, see VMware KB 2124715 .

    Steps to follow:

    1. Sign in to https://my.vmware.com/group/vmware/patch#search
    2. Select ' ESXi (Embedded and Installable) ' and '6.0.0 '.  Click on the Search button.
    3. Look for the update of the release name - of - esxi6.0 - 6.0_update01 (released 10/09/2015). Place a check next to it and then download the button to the right.
    4. Save the file somewhere locally. Open archive ZIP once downloaded.
    5. Navigate to the directory "vib20". Extract from the record of the net-e1000e.  In East drivers Intel e1000e ESXi 6.0 U1: VMware_bootbank_net - e1000e_2.5.4 - 6vmw.600.0.0.2494585.vib
    6. This transfer to your ESXi Server (be it via SCP or even the file within the vSphere Client browser). Save it somewhere you will remember (c.-a-d./tmp).
    7. Connect via SSH on the ESXi 6.0 host.
    8. Issue the command to install it: software esxcli vib install v - /tmp/VMware_bootbank_net-e1000e_2.5.4-6vmw.600.0.0.2494585.vib
    9. Restart the ESXi host.  Once it comes back online your datastore (s) iSCSI / volumes should return.  You can check by issuing h df or the list of devices storage core esxcli at the CLI prompt.  vSphere Client also works

    It took some time to find the correct file (s), the steps and commands to use.  I hope someone else can benefit from this.  I love that VMware can provide for virtualization, but lately, it seems that their QA department was out to lunch.

    Do not always have a definitive explanation as to why Intel e1000e ESXi 5.5 U3 drivers were used when ESXi 6.0 U1 U2.  Maybe someone with more insight or VMware Support person can.

    & out

    --G

  • Iscsi fibre and 5.5 to 6 migration

    So I have a project going now, where I am moving from iscsi connected storage storage fiber connected using 2 data warehouses.  Addition of 2 new hosts and by removing the 4 former hosts. I have 8 guests that I need to change, but I don't have time to stop close all and migrate on and get back to the top. So I try to find the best possible scenarios for this initiative. So far, I have 3 hosts in fiber, but the other 5, that I don't have.  What I'm running into the fact that I have DRS off so I have to manually managed my vm so I'm not more taxing any one host. So I thought I'd do temp cluster to move my old 4 hosts that I do not plan to update or use this way I can keep my more critical data/vm is there while I prep and move all my other vm of connected fiber 6.0.0u1 new guests. But I don't know if it's the right way to address the issue.  And I'm sure I missed something while typing this stuff, but I'll try to find the best way to describe what I have and what I'm trying to accomplish. Looking for some thoughts or ideas that I have never done this kind of forward movement. Thanks for your time.

    I did it a couple of times in the past, and what you describe should work just fine. If you don't have a lot of settings of cluster you want to keep (ie. you can easily configure on a cluster) simply to create a new cluster, DRS/HA, with new hosts, migrate virtual machines for free a host on the old cluster removal/reinstall the old host to the new cluster and then continue with the remaining virtual machines migration. If in the new cluster hosts are compatible CPU (i.e. share the same mode of VCA) migration can be made without interruption of service.

    A few additional thoughts:

    • If you run base/Hot-add VM backups. ensure that backup devices are available on the two clusters with access to appropriate data storage.
    • According to storage systems, you can benefit (IO performance) to distribute virtual machines through more than just 2 data warehouses.

    André

Maybe you are looking for

  • Satellite L550D-136 - how many slots should memory be?

    Hello I bought this system as my first laptop from Toshiba.Satellite L550D-136Part number: PSLXSE-00E00SY4 I visited crucial.com to verify what type of memory I can put in this laptop and he came back with the result that it could not identify exactl

  • Re: Need Satellite L30 - 105 Vista - power calibration error - new firmware

    Hey guys =) Ive got a Satellite L30-105 running a Vista 32 bit. And even if I try several different (Imageburn, Nero) burning software, and with the TDK - CD, I get an error in the burning software, saying "power calibration error". Satellite L30 - 1

  • Scanning help

    I need help scanning.  The alert light is on, as it is one of the cartridge lights.  The Middle cartridge flashes.  I can copy and print correctly.  HP Deskjet F2430, Mac OS X - 10.6.8.  When I try to scan, it says "preparing to scan" and then nothin

  • question about ".tin file extension.

    I noticed a file ending with the extension "." TIN"in a temporary files folder.  I do not know what program will open this file or how to find out what this file is or how and why it was created.  Someone has an idea?  I noticed there are websites th

  • Cannot install the creative cloud desktop application

    Yes. Something is very wrong with the installation process when after only 5 attempts to install creative cloud, the installation program Adobe has once again stalled. I tried first, she for at least 3 hours.I'm on OSX El Capitan. MacBook ProI should