balancing of iSCSi
I noticed in one of the guides, they reocmmend that you use two vmkernal different ports with two different subnets to balance the load a guard of active/active storage. Need two different subnets. If so, why? Our entire storage solution is currently a subnet and make some changes to is not an option at this time.
obstacle wrote:
I noticed in one of the guides, they reocmmend that you use two vmkernal different ports with two different subnets to balance the load a guard of active/active storage. Need two different subnets. If so, why? Our entire storage solution is currently a subnet and make some changes to is not an option at this time.
For many suppliers, it is a recommendation of the SAN vendor.
Follow the recommendations of your provider, if they recommend that you use a single subnet, then you should be fine.
Tags: VMware
Similar Questions
-
ID mapping session Iscsi MPIO path
Hello
I'm playing ISCSI with MPIO. I get the connection information iscsi of the cmdlet "Get-IscsiConnection". It gives the target portals to which the initiator is connected. Then I have the mpclaim - v command which gives me the current state of the railways. In my case, I have an active/optimized path and other avenues of relief. This information on mpio path statements is shown with regard to the path ID. I want a way to find out what connection/target portal is this track Id matches. In the GUI, tab window mpio initiator iscsi has this information. Is there a way to get this info through PowerShell?
Reference for the mpclaim - v output:
MPIO Storage Snapshot on Tuesday, 05 May 2009, at 14:51:45.023 Registered DSMs: 1 ================ +--------------------------------|-------------------|----|----|----|---|-----+ |DSM Name | Version |PRP | RC | RI |PVP| PVE | |--------------------------------|-------------------|----|----|----|---|-----| |Microsoft DSM |006.0001.07100.0000|0020|0003|0001|030|False| +--------------------------------|-------------------|----|----|----|---|-----+ Microsoft DSM ============= MPIO Disk1: 02 Paths, Round Robin, ALUA Not Supported SN: 600D310010B00000000011 Supported Load-Balancing Policy Settings: FOO RR RRWS LQD WP LB Path ID State SCSI Address Weight --------------------------------------------------------------------------- 0000000077030002 Active/Optimized 003|000|002|000 0 Adapter: Microsoft iSCSI Initiator... (B|D|F: 000|000|000) Controller: 46616B65436F6E74726F6C6C6572 (State: Active) 0000000077030001 Active/Optimized 003|000|001|000 0 Adapter: Microsoft iSCSI Initiator... (B|D|F: 000|000|000) Controller: 46616B65436F6E74726F6C6C6572 (State: Active) MPIO Disk0: 01 Paths, Round Robin, ALUA Not Supported SN: 600EB37614EBCE8000000044 Supported Load-Balancing Policy Settings: FOO RR RRWS LQD WP LB Path ID State SCSI Address Weight --------------------------------------------------------------------------- 0000000077030000 Active/Optimized 003|000|000|000 0 Adapter: Microsoft iSCSI Initiator... (B|D|F: 000|000|000) Controller: 46616B65436F6E74726F6C6C6572 (State: Active) Microsoft DSM-wide default load-balancing policy settings: Round Robin No target-level default load-balancing policy settings have been set.The reference for iscsi connection and session info: PS C:\> Get-IscsiConnection ConnectionIdentifier : ffffe001e67f4020-29fInitiatorAddress : 0.0.0.0InitiatorPortNumber : 44996TargetAddress : 10.120.34.12TargetPortNumber : 3260PSComputerName : ConnectionIdentifier : ffffe001e67f4020-2a0InitiatorAddress : 0.0.0.0InitiatorPortNumber : 46020TargetAddress : 10.120.34.13TargetPortNumber : 3260PSComputerName : ConnectionIdentifier : ffffe001e67f4020-2a1InitiatorAddress : 0.0.0.0InitiatorPortNumber : 47044TargetAddress : 10.120.34.14
TargetPortNumber : 3260PSComputerName : ConnectionIdentifier : ffffe001e67f4020-2a2InitiatorAddress : 0.0.0.0InitiatorPortNumber : 46788TargetAddress : 10.120.34.15
TargetPortNumber : 3260PSComputerName : PS C:\>I basically want to know which target portal does this pathid "0000000077030002" correspond to ?
Hello
Please post your question on the TechNet forums:
Here is the link:
https://social.technet.Microsoft.com/forums/Windows/en-us/home?category=w7itpro
Kind regards
-
Hello
We do experience the fun problems with iSCSI connections drop and in. I was wondering if there is a newspaper report or verification that this would provide a volume of specfic? Thank you!
In the UI under events.
In the CLI, you can run GrpName > show recentevents
If you haven't already done so, install SANHQ, which is available on the site Web of EQL.
The table will periodically balance connections on the ports available in the group in order to balance the IO. These disconnections / connections are quite normal.
Usually connection drops are caused by network problems.
Can you give us some examples of the error or informational messages?
You can open a folder from supported so they can review the logs and configuration of your switch.
Kind regards
-
ISCSI in VMware guest - slow speed
SAN is a PS4100 with dedicated switches.
In VMware, I have a Setup vSwitch according to EQ DELL Documentation. The VMKernal properties are:
- VLAN ID = None (0)
- vMotion = unchecked
- Fault tolerance = unchecked Logging
- Management traffic = unchecked
- iSCSI Port Binding = Enabled
- MTU = 9000
NIC Teaming settings tab:
- Load balancing = unchecked
- Failover detection network = unchecked
- Notify the switches = unchecked
- Failback = check = No
- Failover = checked to Override switch control failover
One in which adapter is set to Active the other place in is not used. This command is enabled for the second VMKernal iSCSI connection.
The DELL MPIO extension has been added to the VMware host and the connection is configured to use DELL_PSP_EQL_ROUTED for the managed to the ISCSI target paths.
Managed paths show also active / active status.
Flow tests with a physical server through a single initiator iSCSI LUNs dedicated show speeds completely saturate the link with 99 MB/s of throughput. All I can manage to inside the guest OS of Server 2012 with NIC vmxnet3, who is also on the SAN is around 30 MB throughput.
Drops of speed even more during transfer of a network SAN Fibre Channel AX150 hosted VMware guest OS, with an Intel Pro 1000 MT network card, on the one hand of SAN PS4100, it falls to 13 MB/s.
What I missed, and where should I look to make changes?
What I should look to increase flow?
Hello
There's not much info here to go. I would like to start by making sure that the server is configured by Dell best practices doc.
en.Community.Dell.com/.../20434601.aspx
VMware iSCSI configuration will not affect the speed of connection iSCSI comments. Ideally, comments iSCSI traffic should have its own NIC, separated from the ESXi NIC use because it is the iSCSI traffic.
Make sure that the VMware tools is installed as well. Who will ensure that the network driver is optimized. Run the current version of ESXi is too important. There was a few KBs on performance with the VMXNET3 adapter problems. Sometimes change to the E1000 might better work.
-
How to configure das MD3200i load balancing
I would like to connect a MD3200i (with two raid controllers) to one of our Windows 2003 R2 servers without the aid of a switch.
After most of the documentation, some things remain pretty obscure to me. I'm new to MPIO/balancing and cannot figure how to set up.
Is it possible to connect 1 nic host to RAID 0 and another host nic to RAID 1 and then combine the bandwidth? Thus having 2Gbs instead of 1Gbs? Or is it only a redundant path sollution, happening the other controller in case of failure of the first line. How can I configure this regarding the IP addresses, subnets. And where is the configuered to load balancing. This is explained in the documentation? I can't find it. I found a few examples that include the use of a switch, but none with das sollutions.
What I have is 4 the MD3200i UTP cables to connect to the host. 2 the high raid controller and 2 on the lower raid controller. And use that I have 4x1Gbs, resulting a connection 4Gbs to a single partition on the MD3200i of load balancing.
Thanks for any help.
Multiple paths and in windows 2003 load balancing is managed by the driver MPIO is installed when you install the 'host' or 'full' version install MD Storage Manager. There is no need to separately aggregated network adapters to get the aggregate bandwidth. The pilot, by default, uses repetition alternated on all ports connected to a single controller.
Also, for a single virtual disk, all i/o through a single controller and the second controller acts as a redundant path. So, if you have 2 x 1 Gbps connections to each controller, you will have, at most, 2 Gbps for each partition. Now, each controller can have virtual disks, so the second controller may have a second partition that will also have a separate between 2 x 1 Gbps connection.
You can set IP addresses and subnets that are similar to the way that you would with a switch as long as you can test the connection port. It would be wise for each NETWORK card on the host on a different subnet and each port on the MD3200i on the corresponding subnet. This will make it easier when you set up your iSCSI.
You can use the configuration utility to MD in place your iSCSI sessions too
-Mohan
-
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.
-
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
-
Increase throughput for iSCSI with multiple NICs
I'm implementing a new host ESXi 6 using a Synology NAS as an iSCSI target. I have 4 nic of the Synology stuck in 1 connection, so it has 4 GB of throughput. So far, over my hosting provider, I have two nic I dedicated to iSCSI traffic. So far, I put vSwitch under 1 two NICs and I was playing with patterns. I put two 1 vmkernel network cards and set as active adapters. However when I watch the iSCSI network traffic I only see traffic on a network adapter. This of course caps my speed to 1 GB. I would like to be able to bind several network cards so I can get a flow more. I tried changing the selection of the path for the warehouses of data in Round Robin are therefore at least two active nic. But which always leaves me with two individual connections of 1 GB instead of 2 GB connection. Is it possible for me to get there or I'm better off just having several 1 GB NIC load balanced?
I'm not familiar with the Synology. However, what is generally - in the case where the storage system supports - is to set up several uplinks on the side of the target of storage/as well as on the initiator/ESXi side, each with their own IP address. Once configured, you can use multiple paths to access the target. According to the capabilities of the target, Round-Robin (if supported) will send traffic through all the links, i.e. using the bandwidth of all the links.
André
-
design for the iSCSI SAN review
Hi all
I intend to implement a storage shared in our vmware infrastructure. And we'll buy DELL or iSCSCI SAN NETAPP.
Could someone pls review the design of SAN attached. Please note that we do not have a vCenter in the environment. And also we have not yet finalized on behalf of initiator SCSI, whether to use a software or iSCSI HBA for this purpose. Is it worth investing in the hardware initiator. Please suggest.
Kind regards
Nithin
To use several vmks iSCSI, you cannot assign two network adapters to the iSCSI vmks.
You cannot have an active nic by vmk and the other the vSwitch network adapter must be moved down to "unused controller. Then you can bind to port in the software iSCSI hba adapter. It is the only way to achieve real multichannel, load balancing and failover for multiple iSCSI vmks.
Here's a KB on how do: http://kb.vmware.com/kb/2045040
But if you google, it has quite a few tutorials with pictures detailed, etc..
Tim
-
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
-
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
-
Multipathing with SW iSCSI initiators
Hi all
Just curious about the multiple and iSCSI paths. Summer hope to clarify a certain number of things.
Taking an example of a single ESXi 4.0 host to connect to a device iSCSI via a network using a software initiator.
A vSwitch was created on the host with two rising vmnic (two assets), which are connected to the storage network. A unique VMkernel port group was created on the vSwitch with an IP address on the storage network.Issues related to the:
1 have I reason to think that the configuration above do not use the two vmnic for redundancy? I assume this is the case, because it shows only a single path under the storge device?
2. assuming that the above is correct, that if I lost any vmnic is used, I'd lose access to my storage of this host?
3. in order to provide redundancy in case of a failure vmnic, do I need to follow the steps in the configuration guide for iSCSI SAN? (http://www.vmware.com/pdf/vsphere4/r40/vsp_40_iscsi_san_cfg.pdf) That is to create two groups of ports on the vSwitch using vmnic active replacement (with the other unused) and use the CLI to create paths?
4. If the default config is indeed only using a single VMnic, how can that be used?
I think I already know the answer above but would like to have a validation...
Thank you
Chris.
Tru Multipathing, your storage space must have at least 2 IP addresses.
Do not confuse redundancy with multiple paths.
While the two work together, you can have one without the other.
To get full redundancy and multiple paths, at a minimum, your storage server needs at least two interface IP. you need to implement a vSwitch with 2 groups of VMKernel ports, as you mentioned below. #3 and port, then bind using the CLI.
The political path roundrobin when value over (if your table is compatible). You should then have 2 active channels.
In your current config.
# 1 there is redundancy, but no multipath
# 2 No.
#3-Oui - preferred method for many reasons with HA, path table and load balancing selection.
#4-is not easy to find (at least not for me). It really depends on how your political grouping vswitch is implemented. Bad this refer to the experts. Don't want to confuse.
-
iSCSI / vmkernel multipathing vs NIC teaming
Hello
I know of Configuration of VMware SAN Guide provides information about how to configure iSCSI multipath with vmkernel interfaces double on various uplinks.
What are the disadvantages of using basic NIC teaming instead? Just an interface of vmkernel on a vswitch (d) with two uplinks. It will work properly about redundancy and failover?
Kind regards
GreyhoundHH wrote:
What are the disadvantages of using basic NIC teaming instead? Just an interface of vmkernel on a vswitch (d) with two uplinks. It will work properly about redundancy and failover?
I guess the difference is while using "Port Binding" iSCSI initiator uses vSphere Pluggable Storage Architecture to handle the load balancing/redundancy, that can make better use of multiple paths to NETWORK card available. Otherwise, the initiator will use vmkernel stack ensures redundancy network and balancing in the same way as a normal network traffic.
I suggest that you look at the great post on iSCSI multi-vendor, I think the 2 statements below will summarize the difference:
"
- However, the biggest gain of performance allows the storage system to scale the number of network adapters available on the system. The idea is that multiple paths to the storage system can make better use multiple paths, he has at his disposal than the consolidation of NETWORK cards on the network layer.
- If each physical NETWORK adapter on the system looks like a port to a path to the storage, the storage path selection policies can make best use of them.
"
-
Comments iSCSI - NLB on vSwitch?
I have a vSwitch with 2 natachasery in it. The vSwitch is dedicated to iSCSI traffic.
I have different guests who can access volumes on our SAN the initiator iSCSI MS within the guest.
One of the guests is my primary file server that has 2 vNIC for iSCSI.
What is the policy load balancing optimal to use between Port-ID and hash MAC Source Please?
I did a ton of reading and I'm still a bit confused that one should I choose to try to get the best distribution of iSCSI sessions invited through both my iSCSI NIC.
(Please note I'm only request for comments iSCSI traffic, traffic iSCSI host is configured to use MPIO with a nic explicitly linked to each vmkernel on iSCSI switch)
Thank you
Paul
MAC basic goes back to ESX 1 and 2 of ESXX, wa sthe default load option balancing with the thought that, given that the MAC address has been uniqiue it would be a high probability to distribute the load evenly - in practice, it wasn't the case. It has been found that the hash has not distributed the load evenly even to the point that you could have a team of three natachasery nic and one or two have been used - thatís why in vSphere Port base becomes by default - you add maps for each network is assigned to a different port id and where will come out a different bear - in terms of performance and your physical to your switches configuration physical, there is no difference-
-
Reviews for iSCSI NFS e 3100 & Catalyst 2960-S vs?
I'll put up my first SAN, a 3100 e with 2 NICs by MS. We chose a pile of Cisco 2960-S for redundancy at the network level, and during the planning phase, I had chosen to use NFS. E does not deduplication with iSCSI support (someone?), and the performance is roughly equal to this environment. It is 3 guests with approximately 15 production MV; I expect a usage rate of 20% per host based on statistics collected from the current production environment.
The glitch is 2960-S is limited to 6 ports-channels, even in a pile! Initially, my plan was simple enough, and a commercial engineer. Create channel-port on each host to storage traffic and traffic VM vMotion/HA. Each of them would be 2 gigabit NIC in a VLAN dedicated. But, now that I have that 6 Channel ports to work with, what is the best solution? I would go with NFS, if possible, but I can't understand a good way to provide a high availability and balancing at the network level (yes I know that the effectiveness of IP hash is questionable in a port channel).
In the past, I have Setup iSCSI multipathing in environments of test with good results, but it is a little more complex that I want to get for such a small environment, and we lose deduplication.
Is back to the original question - possible to NFS, highly available, without aggregation of links? I am referring to each element of the stack - host, network and SAN. Is there another method would you recommend, and if so, why?
A few thoughts I had:
Wouldn't be better to put the vMotion/HA NIC on access ports with 1 NIC in standby mode and use the port for NFS instead channels? Once the environment is fully migrated, I expect vMotion will be made during failures and maintenance periods.
If I assigns an IP address to a store NFS SP A and it fails, MS B will remain passive until a failure and then take control of this IP/action? Or the store NFS appears twice in my list of data stores?
Thanks for your comments!
Here is my attempt at bad taking a picture to help visualize this
I had to redact the names and IP addresses
MGMT use vmnic1 as a primary vmnic5, as a backup. It is the VLAN 125
vMOTION uses vmnic5 as a primary vmnic1, as a backup. It is 126 VLAN.
vmnic1 and vmnic5 are shared resources at the level of the physical switch to allow the 125 & 126 VLAN.
Maybe you are looking for
-
Display driver stopped responding and has recovered
Product: HP Pavilion dv7-6015tx Entertainment Notebook PC OS: Windows 7 32-bit Status: Clean installed Windows 7 Ultimate 32 - bit Windows 7 Home Premium 64-bit Hello I had several cases where the computer seems 'lag '. then, after a few flickers on
-
5742e: lost 2 sides scan option for HP5742e after the software update
HP Support Assistant told me to update the drivers and software for my 5742 all-in-in-one. After I did that the scan dialog changed (from 2014 2015 version) and I can scan is more 2-sided, the dialog box allows only the selection 1-side. It's less co
-
White screen on startup of the satellite C850
I bought a Toshiba Satellite C850 PSCBWA-05E001 so 18 months out of warranty now.I bought it for a few friends, I gave him to who are in the Philippines, so it is difficult for me to check and repair. My friends lack the funds to get it checked if an
-
Cannot add Pitchfork-organized playlists to my music (music from Apple)
In iTunes/Apple music, I am unable to add Pitchfork-organized playlists to my music. Any other reading list, I can click on the plus sign or "Add to my music", and they appear instantly on my playlists on my Mac and on my other devices synced. When I
-
Hello is there a chance to print documentation in TestStand, like VI - documentation in LabVIEW (file-online Print => select VI-VI Documentation Online)? Thank youPatrick