iSCSI Reporting

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

Tags: Dell Products

Similar Questions

vSphere is reporting that the iSCSI disk is empty after adding it

First, when, after boot iSCSI service on Win7, then vSphere host, the iSCSI (form VMFS) drive often may not appear on the storage. After adding it, it's Ok.
But yesterday, he deleted an NTFS partition on the physical disk where the image iSCSI file is on another partition NTFS, which totally has 3 primary partitions before, today, after you add the iSCSI drive, vSphere displays an error message:
Configuring the host error: could not get disk partition information
After clicking the Ok button, he said: the disc is empty.
In my view, the virtual disk partition (image file) would not be affected by any change in the physical disk partition. I can't lose my data on this drive. How can I solve this problem?
Thank you!
George

It is a good guide: http://www.vladan.fr/mounting-your-vmdk-disks-directly-to-your-windows-box-how-to/

SAN reports nearly full volume. Windows reports volume only 50%

PS6000 v7.0.9

2 host of 2012 R2 Hyper V Server Cluster

The volume is 620GB

Director of Group reports 525GB in use

Management of Windows disk and the two report 349GB in use failover cluster manager.

Why the difference and where/how I have not these 175 GB?

Because you use iSCSI to the EQL which is a block of storage. The EQL is not that someone gave above deleted. If a deletets OS given it just the brand like deletet in the allocation table.

Think when formatting a disc format and NOT the quick HELP. The operating system writes zeros and for storage, it looks like valid data... but the OS it will appear as free space later. For the EQL Volume, that means 100% usage.

Windows 2012R2 supports unmap aka space recovery. It depends on your FW EQL and HIT Version and a few other dependencies as Thinpro Volume on the EQL iirc. With that you say the EQL blocks can be removed to obtain a logical space left.

Concerning

Joerg

install new PS6510e - no communication on Iscsi network

Getting desperate here now.

bought refurbished ps6510e of third-party reseller - have been categorically denied access to the site of dell for support on that basis.

connected to 2 servers R720 via grouped 10 gb SFP + cables through a switch of 8024F to SAN with redundant connections of 10 GB on two controllers. configured on the private network for iscsi only traffic with addresses private to each server, switch, Saint Nic individual and the Group ip san.

set up in business / management network for servers / san / management switch with works perfectly.

2 (2012r2) servers can communicate with each other via the links of 20 GB. No communication with san via ping or connecting iscsi connectors at all. servers can ping each other and switch, not san. CLI in san - cannot ping anything - not even his own individual ip addresses. SAN web interface reports that snap ports (15 + 16), it is plugged into the switch so that he knows that she is and that she connects to her apparently happy.

configured according to the guidelines of dell white papers, frames, LAG switch. I swapped 10 GB connections between servers and san groups, and regardless of the combination of connections, servers talk, san does not work.

interface Web and SAN HQ all report everything is hunky dory. one mistake is on the free space that we have configured volumes while.

bright ideas about what was fundamentally wrong very favorably received.

Hello

Re: refurbished. Sorry, but Dell does not offer without PS Series in this way. Dell partners cannot provide these services either. Support requires the table under warranty or support contract access to firmware, and other downloads. In addition, the license to use the table is maintained in the contract, not the hardware. This license may not be transferred or resold.

Re: is associated. PS Do not support series without grouping at all. You need to configure MPIO on servers instead. Almost sure that tagging VLAN is not in use, or stripped of all PS Series ports.

In the GUI, network ports show online?

On the switch, make sure that you have the current firmware, and data center bridging (DCB) is disabled.

Given you cannot ping anything, I suspect the cable or switch configuration. If you use TWINAX cables be PASSIVE, Active cables are not supported.

Kind regards

Don

Session INFO iscsi target - has been closed - sign-out request received from the initatior

today all of a sudden equallogic Group Manager of its getting flooded

target iSCSI session - was closed - sign-out request received from the initatior

target iSCSI session - was closed – iscsi inittator connection fauilure
no response on the connection for 6 seconds

been trying to figure out what has changed since yesterday, nothing has changed

the Member of 4100 not showing this info, all connected to the 6100 Member?

side esxi 5.5 its projection lost way, restoration of path error messages

clues

Hello Dan,.

This first message is normal, because this is a message of level INFO, not WARN or ERROR. It only means that a connection has been disconnected so that it can be moved to another port in the group. I suspect that you run MEM? Who's going to move, start, stop to need iSCSI sessions to hold the input/output symmetrical on the ports available on the berries.

ESXi 5.x will always report any kind of connection as an error problem. Even when he is projected as here. EQL uses a mandatory iSCSI command under the title "async logout" say disconnect the iSCSI initiator then go to discovery and connect immediately. However, this time it will be moved to another port on a table. MEM regularly consults the current connections and may decide to change the layout of the connection.

The 6100 is probably the head of the group. So it stores and displays all messages from all members of the group. Buried in the text it can show you that some are from the 4100.

The other message on the "6 sec timeout" is different. This means that, during this period, the table failed this server. Periodically, initiator and Exchange EQL keep packages of persistent delay. (KATO for short). This is so that the two are always answer. If it fails repeatedly, this message appears and the connection is complete. Once the initiator (server) is back, he will open a new iSCSI session to replace. You see this message when you restart a server, or there are problems with the network.

If you are really interested, you can open a case of pension with Dell. Please gather the diags table (all members), config switch logs, and supports the VM node ESXi. They can check this info and verity that the configuration is OK. They can examine the nodes ESXI to ensure they are in compliance with the best practices with Dell's best practices. There is a Tech report. TR1091 that covers this.

You can find a copy here.

en.Community.Dell.com/.../Download

Many problems have been resolved by choosing ESXi for current construction, set up in accordance with this document and Sunrise switches to spec as well.

Make sure also that the EQL table running 6.0.7 or later. Running current firmware is much better. Earlier than 6.0.7 saw potential for corruption VMFS Datastore. Therefore, it is very important to keep up-to-date.

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.

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

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

ASM & iSCSI - disk has gone forever

I installed Centos 5.9 (don't ask...), my storage is a drive Bay of 10 scsi drives connected via the iscsi Protocol, and I installed grid Infrastructure 11.2.0.3 (software only).
I was setting up ASM, but when I added the candidate disks, it never ended, then I canceled. After several futile attempts to get it to work, I decided to reboot the server.
I think I saw her because before restarting the server, I had uninstalled ASMLib.
The server wouldn't start due to errors related to the disks. After doing a bit of magic, I disabled the connection on the discs and was able to start, but now I have some problems when you try to connect to the disks:
starting at $ /etc/init.d/iscsid
$ chkconfig--add iscsi
$ chkconfig iscsi on
$ iscsiadm m - t sendtargets Pei 10.9.254.2 discovery
10.9.254.1:3260, 1 iqn.1986 - 03.com.hp:storage.p2000g3.121514b3cc
10.9.254.9:3260, 2 iqn.1986 - 03.com.hp:storage.p2000g3.121514b3cc
10.9.254.2:3260, 3 iqn.1986 - 03.com.hp:storage.p2000g3.121514b3cc
10.9.254.10:3260, 4 iqn.1986 - 03.com.hp:storage.p2000g3.121514b3cc
10.9.254.3:3260, 5 iqn.1986 - 03.com.hp:storage.p2000g3.121514b3cc
10.9.254.11:3260, 6 iqn.1986 - 03.com.hp:storage.p2000g3.121514b3cc
10.9.254.4:3260, 7 iqn.1986 - 03.com.hp:storage.p2000g3.121514b3cc
10.9.254.12:3260, 8 iqn.1986 - 03.com.hp:storage.p2000g3.121514b3cc
Then I try to connect to the Portal 10.9.254.2 (I'm not sure how to determine what portal should I use, but it used to work before):
$ iscsiadm, node m t iqn.1986 - 03.com.hp:storage.p2000g3.121514b3cc - l Pei 10.9.254.2
But it never ends, so I have to cancel it. Looks like it's connected and work:
$ iscsiadm-m session
TCP: [8] 10.9.254.1:3260, 1 iqn.1986 - 03.com.hp:storage.p2000g3.121514b3cc
TCP: [9] 10.9.254.3:3260, 5 iqn.1986 - 03.com.hp:storage.p2000g3.121514b3cc
.. .but it does not work:
$ iscsiadm m - session-P3
(...)
Attached SCSI devices:
************************
The host number: 5 status: running
SCSI5 Channel 00 Id 0 Lun: 0
Attached scsi disk sda status: unknown
Furthermore, I can't see the disks! (sda, sdb, sdc,...)
$ ls-l/dev/s *.
lrwxrwxrwx 1 root root 3 6 Feb 17:05 / dev/scd0-> sr0
CRW - 1 root root 0, 21 6 Feb 17:05 / dev/sg0
CRW - 1 root root 1, 21 feb 26 12:30 / dev/sg1
CRW - 1 root root 21, 10 Feb 26 14:31 / dev/sg10
CRW - 1 root root 21, 2 feb 26 12:32 / dev/sg2
CRW - 1 root root 21, 3 Feb 26 13:02 / dev/sg3
CRW - 1 root root 21, 4 feb 26 13:02 / dev/sg4
CRW - 1 root root 21, 5 feb 26 13:31 / dev/CE5
CRW - 1 root root 21, 6 feb 26 13:33 / dev/CE6
CRW - 1 root root 21, 7 feb 26 14:01 / dev/CE7
CRW - 1 root root 21, 8 Feb 26 14:01 / dev/sg8
CRW - 1 root root 21, 9 Feb 26 14:30 / dev/sg9
CRW - 1 root root 10, 231 6 Feb 17:05 / dev/snapshot
BRW - rw - 1 root disk 11, 0 6 Feb 17:05 / dev/sr0
lrwxrwxrwx 1 root root 15 6 Feb 17:05 / dev/stderr->/proc/self/fd/2
lrwxrwxrwx 1 root root 15 6 Feb 17:05 / dev/stdin->/proc/self/fd/0
lrwxrwxrwx 1 root root 15 6 Feb 17:05 / dev/stdout->/proc/self/fd/1
CRW - 1 root root 4, 0 6 Feb 14:04 / dev/systty
The strange thing here is just beginning, in/proc/partitions I can see only of sda. But the remaining machines appear progresively... after an hour, I can see all the:
$ cat/proc/partitions
name major minor #blocks
292935982 0 104 cciss/c0d0
104 1 104391 cciss/c0d0p1
cciss/c0d0p2 2 104 292824787
253 0 286720000 dm - 0
1 253 6094848 dm - 1
8 0 96679680 sda
8 16 96679680 sdb
8 32 96679680 SDC
8 48 96679680 SDS
8 64 96679680 sde
8 80 96679680 homeless
96679680 96 8 sdg
8 112 96679680 sdh
8 128 96679680 sdi
8 144 96679680 LDS
8 160 96679680 sdk
8 176 96679680 sdl
At the end of the day, I see 2 devices as 'unknown' and others as 'running '. But I can't even fdisk them:
$ fdisk-l/dev/sda
Nothing is returned. We will try to create a partition:
$ fdisk/dev/sda
Unable to open/dev/sda
I can't access any device of sdX, because there is not one in/dev.
This is the log that I got when I tried to connect to the target using the iscsiadm command:
6 Feb 15:16:55 kernel bat-cvracdb02: scsi5: iSCSI Initiator on TCP/IP
6 Feb 15:16:55 bat-cvracdb02 kernel: vendor: HP model: P2000 G3 iSCSI Rev: T250
6 Feb 15:16:55 kernel bat-cvracdb02: Type: the Direct access ANSI SCSI revision: 05
6 Feb 15:16:55 bat-cvracdb02 kernel: SCSI device sda: 193359360 512-byte hdwr (99000 MB) sectors
6 Feb 15:16:55 bat-cvracdb02 kernel: sda: write protect is off
6 Feb 15:16:55 bat-cvracdb02 kernel: SCSI device sda: drive cache: write back
6 Feb 15:16:55 bat-cvracdb02 kernel: SCSI device sda: 193359360 512-byte hdwr (99000 MB) sectors
6 Feb 15:16:55 bat-cvracdb02 kernel: sda: write protect is off
6 Feb 15:16:55 bat-cvracdb02 kernel: SCSI device sda: drive cache: write back
6 Feb 15:16:56 bat-cvracdb02 iscsid: Connection1:0 to [target: iqn.1986 - 03.com.hp:storage.p2000g3.121514b3cc, Portal: 10.9.254.2,3260] by [iface: default] now works
6 Feb 15:17:05 bat-cvracdb02 kernel: sda: < 3 > connection1:0: ping timeout of 5 seconds, recv timeout expires 5, last rx 4295476749, last ping 4295481749, now 4295486749
6 Feb 15:17:05 core bat-cvracdb02: connection1:0: detected error conn (1011)
6 Feb 15:17:06 iscsid bat-cvracdb02: kernel reported connection iSCSI error state (1011) 1:0 (3)
6 Feb 15:17:06 bat-cvracdb02 udevd-event [3628]: wait_for_sysfs: waiting for ' / sys/devices/platform/host5/session1 / target5:0:0 / 5:0:0:0 / ioerr_cnt' failed
6 Feb 15:17:09 iscsid bat-cvracdb02: could not online LUN 0 err 2.
6 Feb 15:17:09 iscsid bat-cvracdb02: connection1:0 is operational after recovery (1 attempts)
6 Feb 15:17:24 core bat-cvracdb02: connection1:0: ping timeout of 5 seconds, recv timeout expires 5, last rx 4295495002, last ping 4295500002, now 4295505002
6 Feb 15:17:24 core bat-cvracdb02: connection1:0: detected error conn (1011)
6 Feb 15:17:24 iscsid bat-cvracdb02: kernel reported connection iSCSI error state (1011) 1:0 (3)
6 Feb 15:17:27 iscsid bat-cvracdb02: could not online LUN 0 err 2.
6 Feb 15:17:27 iscsid bat-cvracdb02: connection1:0 is operational after recovery (1 attempts)
6 Feb 15:17:37 core bat-cvracdb02: connection1:0: ping timeout of 5 seconds, recv timeout expires 5, last rx 4295508253, last ping 4295513253, now 4295518253
6 Feb 15:17:37 core bat-cvracdb02: connection1:0: detected error conn (1011)
6 Feb 15:17:38 iscsid bat-cvracdb02: kernel reported connection iSCSI error state (1011) 1:0 (3)
6 Feb 15:17:40 iscsid bat-cvracdb02: could not online LUN 0 err 2.
6 Feb 15:17:40 iscsid bat-cvracdb02: connection1:0 is operational after recovery (1 attempts)
6 Feb 15:17:50 kernel bat-cvracdb02: connection1:0: ping timeout of 5 seconds, recv timeout expires 5, last rx 4295521254, last ping 4295526254, now 4295531254
6 Feb 15:17:50 kernel bat-cvracdb02: connection1:0: detected error conn (1011)
6 Feb 15:17:51 iscsid bat-cvracdb02: kernel reported connection iSCSI error state (1011) 1:0 (3)
6 Feb 15:17:53 bat-cvracdb02 iscsid: could not online LUN 0 err 2.
6 Feb 15:17:53 bat-cvracdb02 iscsid: connection1:0 is operational after recovery (1 attempts)
6 Feb 15:18:03 core bat-cvracdb02: connection1:0: ping timeout of 5 seconds, recv timeout expires 5, last rx 4295534255, last ping 4295539255, now 4295544255
6 Feb 15:18:03 core bat-cvracdb02: connection1:0: detected error conn (1011)
6 Feb 15:18:04 bat-cvracdb02 iscsid: reported core connection iSCSI error state (1011) 1:0 (3)
6 Feb 15:18:06 iscsid bat-cvracdb02: could not online LUN 0 err 2.
6 Feb 15:18:06 iscsid bat-cvracdb02: connection1:0 is operational after recovery (1 attempts)
6 Feb 15:18:12 bat-cvracdb02 avahi-daemon [3321]: invalid query package.
6 Feb 15:18:16 bat-cvracdb02 last message repeated 6 times
6 Feb 15:18:16 core bat-cvracdb02: connection1:0: ping timeout of 5 seconds, recv timeout expires 5, last rx 4295547259, last ping 4295552259, now 4295557259
6 Feb 15:18:16 core bat-cvracdb02: connection1:0: detected error conn (1011)
6 Feb 15:18:16 bat-cvracdb02 kernel: sd 5:0:0:0: error code not supported
6 Feb 15:18:16 bat-cvracdb02 kernel: sd 5:0:0:0: SCSI error: return code = 0x000e0000
6 Feb 15:18:16 bat-cvracdb02 kernel: result: hostbyte = DID_TRANSPORT_DISRUPTED driverbyte = DRIVER_OK, SUGGEST_OK
6 Feb 15:18:16 bat-cvracdb02 kernel: error of the buffer i/o on device sda, logical block 0
6 Feb 15:18:17 bat-cvracdb02 iscsid: reported core connection iSCSI error state (1011) 1:0 (3)
6 Feb 15:18:19 bat-cvracdb02 iscsid: could not online LUN 0 err 2.
6 Feb 15:18:19 bat-cvracdb02 iscsid: connection1:0 is operational after recovery (1 attempts)
I also tried to reinstall ASMLib, network and iscsi tools.
I'm tired of this problem, please kindly share ideas. No one could help me on the Centos forum.

Finally, I solved this.

I had to use MPIO, because when I accesed drives node of the wave, all was fine, but when I accessed the other node disks, disks began to show problems.

Failed to create data store on LUN ISCSI

Get the following error when attempting to create a new data store after a new installation of ESXi 5.5U2.
Location:
- UCS B200 servers using the VIC-1280 map and
- Interfaces ISCSI connected directly from the fabric of interconnection to the NetApp FAS2552 with TwinAx cables
- MTU is set for extended frames (9000) on the interface of NetApp, vNIC for ISCSI vKernel vSwitch and group interface ports
- During the initial setup of the vSwitches, I forgot the MTU setting Port and interfaces group wouldn't even ping, so all the MTU setting are good
- ISCSI connection is green and LUN created and present storage warehouses are considered as available on the ESX Server to create a data store (sizes 1 TB and 2 TB tested times)
- The NetApp storage have been created as a thin provisioned and thick provisioned - neither works and gets the same error
Any ideas would be very useful. Technical support has not yet responded.
Thanks in advance.
DM

OK, after working with NetApp and VMware on a conference call (after both made each other) bottom line "fix" was to remove the iSCSI port bindings, remove broken paths, remove the vSwitches and rebuild again.

1. create vKernel vSwitch with appropriate port group

2. set the MTU to 9000 on the port group and vSwitch

3. create the bindings for each interface iSCSI Port

4 re-scan

5 successfully create the data store

Oddly enough, I had to repeat this process 3 times for one of the blades, but it worked the first time for 3 other involved blades.

VMware technical support did provide the following as a look at the LUN of the CLI:

1. / vmfs/devices/disks cd

ls-l

We see and out of all the available discs

Identify the Lun Naa.xxxxxxxx

2. run the Naa.xxxxx reported in step 2

partedUtil getptbl /vmfs/devices/disks/naa.xxxxxxx

If there is a partition, you might see something similar to

1 63 2249099 131 128 > 1 is the partition number

or

You can see and error, if error please contact technical support

3. If there is partition, you can delete

partedUtil remove /vmfs/devices/disks/naa.xxxxxxx 1

NOTE: This process did not work, but is still useful nonetheless. It could work if the LUN has been used by another operating system and need cleaning. But my situation was all greenfield.

iSCSI storage problem ESXi 5 u1

Hello
We have six ESXi 5 u1 servers connected to the storage unit Dell EqualLogic 65xx series. On ESXi systems we use the iSCSI Software and PSP is set to RoundRobin. We investigated a question where randomly throughout the day that we receive the following warning:
VCenter:
Failed to write command to write-suspended partition naa.6090a08890b27eeab8cee499fb01a0f6:1
VMKernel:
WARNING: ScsiDeviceIO: 3075: order of writing-suspended bulkhead 6090a08890b27eeab8cee499fb01a0f6:1 write failure
Capability3: 13359: Max (10) attempts exceeded for appellant Fil3_FileIO (status "IO has been abandoned by VMFS via virt-reset of the unit")
BC: 1858: cannot write (couriers) object '. iormstats.SF': level core exceeded Maximum attempts
Also, we see a lot of messages indicating a loss of connectivity, iSCSI volumes:
Lost access to the volume (LUN_NAME) 4f58ac5f-ef525322-XXXXXXXXXXXXXXX because of connectivity issues. Recovery attempt is underway and the result will be
reported in no time.
This event is generated by all six guests at random time intervals and LUN iSCSI target different. At the same time, we notice a very high spike in CPU usage of 100% on the host that generates the message
One thing we found through tests of vmkping is that ESXi hosts are configured for extended frames (9000 MTU vmk, vswitch and adapters), but the storage network, does not allow frames.
This could be an indication of serious IP fragmentation on iSCSI? How we measure this?

conraddel wrote:

One thing we found through tests of vmkping is that ESXi hosts are configured for extended frames (9000 MTU vmk, vswitch and adapters), but the storage network, does not allow frames.

This could be an indication of serious IP fragmentation on iSCSI? How we measure this?

Do you know if the side SAN is configured for frames? If not, then it should probably not be a problem, given that the TCP connection will take care of the other so-called MSS sizes and your guests should get off by default the images of sizes.

The worst situation would be if both the ESXi and the SAN supports jumbo frames, but not the switches between the two. Because the switches are 'invisible' problems don't happen, until you actually start sending larger images and those will arrive in silence by switches, i.e. no IP fragmentation.

Have you also checked with vmkping what kind of end-to-end connectivity, you have? Options-d and s are very important get right: http://rickardnobel.se/archives/992

the iSCSI LUN mapping

How ESXi is mapped LUN vmfs iSCSI extends? The reason why I ask, is that in my opinion, he should do a mapping to make it persistent after a reboot?

fajarpri wrote:

@Rikard, similar like that. How ESX knows that Lun0 will extent1 and Lun1 goes to extend2 in this store a data?

Wouldn't there is possibility that ESX detects Lun1 first than Lun0 and thus risk recognizing as extent1?

I guess it's a bit 'Internal ESXi', but it should be the NAA or T10 number reported by the SAN and no id LUN itself using ESXi to recognize discs. Given that these numbers never change, there is risk of errors between reboots. I have a vague memory of which is a kind of question on the 3.x versions, but do not these days.

Reports of changing CP senario scuh CPU, RAM based and exception systems

Hi Team CP,

I have an assasment of report so that you can find in attach file

(a) I want to learn can us display the senerio model: 4 cores of the processor w / 16 GB of RAM

I want to say that 4 cores, 64 GB of Ram, or which depends on?

(b) and in the report, it says 10 systems of exceptional? I want to know why they are exceptions, and can I virtualize this system or not?

Can you explain please

Regads

2.2.4 material selection

The script has been configured to reuse the material where possible.

Number of systems by processor use number systems of memory capacity

Brand: VMware, Inc..

Model: 4 cores of the processor w / 16 GB RAM

Hardware component number size, speed

4 3000 MHz CPU

16384 MB OF RAM

Network interface cards 2 1000 MB/s

Disk IO 50 MB/s

1000 GB storage drive

Servers which is related

Cisco UCS w / 8 CPUs@2260MHz 98304 MB RAM	Cisco UCS w / 8 CPUs@2260MHz 98304 MB RAM	Cisco HW	2009-07-21 09:47:44	2
Dell PowerEdge 1950 w / 2 CPUs@3730MHz 16384 MB RAM	Dell PowerEdge 1950 w / 2 CPUs@3730MHz 16384 MB RAM	Reference Dell HW	08/12/2006 20:22:32	2
Dell PowerEdge 1950 w/2 Quad Core 2.66 GHz CPU, 32 GB of Ram	Dell PowerEdge 1950 w/2 Quad Core 2.66 GHz CPU, 32 GB of Ram	Reference Dell HW	2007-08-24 12:45:26	2
Dell PowerEdge 1955 w / 2 CPUs@3730MHz 16384 MB RAM	Dell PowerEdge 1955 w / 2 CPUs@3730MHz 16384 MB RAM	Reference Dell HW	08/12/2006 20:22:32	2

? fuseaction = Admin & Page = NewHardwareTemplate.cfm & TemplateTypeID = 6 & TemplateID = 3599449 "rel ="nofollow"> Dell PowerEdge 1955 w/2 Quad Core 2.66 GHz 16 GB Ram CPU - fiber

Dell PowerEdge 1955 w/2 Quad Core 2.66 GHz CPU, 16 GB of Ram - fiber

Reference Dell HW

2007-08-24 12:45:26

Dell PowerEdge 1955 w/2 Quad 2.66 GHz 16 GB Ram CPU Core - iSCSI

Reference Dell HW

2007-08-24 12:45:26

Dell PowerEdge 2950 w / 2 CPUs@3730MHz 16384 MB RAM

Reference Dell HW

08/12/2006 20:22:32

Dell PowerEdge 2970 w/2 Dual-Core 3.0 GHz CPU, 32 GB of Ram

Reference Dell HW

2007-08-24 12:45:26

? fuseaction = Admin & Page = NewHardwareTemplate.cfm & TemplateTypeID = 6 & TemplateID = 32 "rel ="nofollow"> Dell PowerEdge 6850 w / 4 CPUs@3600MHz 65536 MB RAM

Dell PowerEdge 6850 w / 4 CPUs@3600MHz 65536 MB RAM

Reference Dell HW

08/12/2006 20:22:32

Dell PowerEdge 6850 w/4 Dual-Core 3.4 GHz CPU 64 GB of Ram

Reference Dell HW

2007-08-24 12:45:26

Dell PowerEdge 6950 w / 4 CPUs@2800MHz 65536 MB RAM

Reference Dell HW

08/12/2006 20:22:32

Dell PowerEdge 6950 w/4 Dual-Core 3.0 GHz CPU 64 GB of Ram

Reference Dell HW

2007-08-24 12:45:26

? fuseaction = Admin & Page = NewHardwareTemplate.cfm & TemplateTypeID = 6 & TemplateID = 4037301 "rel ="nofollow"> FUJITSU SIEMENS GROUND RX300 S4 w/2 [email protected] processors, 32 GB of RAM

FUJITSU SIEMENS GROUND RX300 S4 w/2 [email protected] 32 GB of RAM

Fujitsu-Siemens HW

2009-02-13 12:55:14

FUJITSU SIEMENS GROUND RX600 S4 w/4 [email protected] processors, 32 GB of RAM

FUJITSU SIEMENS GROUND RX600 S4 w/4 [email protected] 32 GB of RAM

Fujitsu-Siemens HW

2009-02-13 13:00:05

HITACHI Advanced Server HA8000 series RS210AL (E5503 4cores)

Xeon E5503 (2 Core, 2.00GHz) x 2, 16 GB memory DDR3 x 12

HW Hitachi

2011-04-08 13:44:05

HITACHI Advanced Server HA8000 series RS210AL (8cores E5603)

Xeon E5603 (4 Core, 1.60GHz) x 2, 16 GB memory DDR3 x 12

HW Hitachi

08/04/2011-13:43:04

? fuseaction = Admin & Page = NewHardwareTemplate.cfm & TemplateTypeID = 6 & TemplateID = 4066143 "rel ="nofollow"> series HITACHI Advanced Server HA8000 RS210AL (8cores E5620)

Xeon E5620 (4 Core, 2.40GHz) x 2, 16 GB memory DDR3 x 12

HW Hitachi

08/04/2011-13:42:33

HITACHI Advanced Server HA8000 series RS210AL (E5649 12cores)

Xeon E5649 (6 Core, 2.53GHz) x 2, 16 GB memory DDR3 x 12

HW Hitachi

08/04/2011-13:41:47

HITACHI Advanced Server HA8000 series RS210AL (8cores L5630)

Xeon L5630 (4 Core, 2.13GHz) x 2, 16 GB memory DDR3 x 12

HW Hitachi

08/04/2011-13:43:36

HITACHI Advanced Server HA8000 series RS210AL (X 5675 12cores)

X 5675(6 Core, 3.06GHz) Xeon x 2, 16 GB memory DDR3 x 12

HW Hitachi

2011-04-08 13:40:05

? fuseaction = Admin & Page = NewHardwareTemplate.cfm & TemplateTypeID = 6 & TemplateID = 4062374 "rel ="nofollow"> HITACHI Advanced Server HA8000 series RS210KK (E5503 4cores)

Xeon E5503 (2 Core, 2.00GHz) x 2, 8 GB memory DDR3 x 12

HW Hitachi

06/12/2010 13:17:52

HITACHI Advanced Server HA8000 series RS210KK (8cores E5620)

Xeon E5620 (4 Core, 2.40GHz) x 2, 8 GB memory DDR3 x 12

HW Hitachi

06/12/2010 13:17:52

HITACHI Advanced Server HA8000 series RS210KK (8cores E5640)

Xeon E5640 (4 Core, 2.66GHz) x 2, 8 GB memory DDR3 x 12

HW Hitachi

06/12/2010 13:17:51

HITACHI Advanced Server HA8000 (X 5670 12cores) RS210KK series

X 5670(6 Core, 2.93GHz) Xeon x 2, 8 GB memory DDR3 x 12

HW Hitachi

06/12/2010 13:17:51

? fuseaction = Admin & Page = NewHardwareTemplate.cfm & TemplateTypeID = 6 & TemplateID = 4066140 "rel ="nofollow"> HITACHI Advanced Server HA8000 series RS220AL (E5503 4cores)

Xeon E5503 (2 Core, 2.00GHz) x 2, 16 GB memory DDR3 x 12

HW Hitachi

08/04/2011-13:33:58

HITACHI Advanced Server HA8000 series RS220AL (8cores E5603)

Xeon E5603 (4 Core, 1.60GHz) x 2, 16 GB memory DDR3 x 12

HW Hitachi

08/04/2011-13:32:45

HITACHI Advanced Server HA8000 series RS220AL (8cores E5620)

Xeon E5620 (4 Core, 2.40GHz) x 2, 16 GB memory DDR3 x 12

HW Hitachi

08/04/2011-13:31:22

HITACHI Advanced Server HA8000 series RS220AL (E5649 12cores)

Xeon E5649 (6 Core, 2.53GHz) x 2, 16 GB memory DDR3 x 12

HW Hitachi

2011-04-08 13:28:56

? fuseaction = Admin & Page = NewHardwareTemplate.cfm & TemplateTypeID = 6 & TemplateID = 4066138 "rel ="nofollow"> series HITACHI Advanced Server HA8000 RS220AL (8cores L5630)

Xeon L5630 (4 Core, 2.13GHz) x 2, 16 GB memory DDR3 x 12

HW Hitachi

08/04/2011-13:33:15

HITACHI Advanced Server HA8000 series RS220AL (X 5675 12cores)

X 5675(6 Core, 3.06GHz) Xeon x 2, 16 GB memory DDR3 x 12

HW Hitachi

08/04/2011 13:27:33

HITACHI Advanced Server HA8000 (X 5690 12cores) RS220AL series

X 5690(6 Core, 3.46GHz) Xeon x 2, 16 GB memory DDR3 x 12

HW Hitachi

2011-04-08 13:20:34

HITACHI Advanced Server HA8000 series RS220KK (E5503 4cores)

Xeon E5503 (2 Core, 2.00GHz) x 2, 8 GB memory DDR3 x 12

HW Hitachi

06/12/2010 13:17:51

? fuseaction = Admin & Page = NewHardwareTemplate.cfm & TemplateTypeID = 6 & TemplateID = 4062365 "rel ="nofollow"> series HITACHI Advanced Server HA8000 RS220KK (8cores E5620)

Xeon E5620 (4 Core, 2.40GHz) x 2, 8 GB memory DDR3 x 12

HW Hitachi

06/12/2010 13:17:51

HITACHI Advanced Server HA8000 series RS220KK (8cores E5640)

Xeon E5640 (4 Core, 2.66GHz) x 2, 8 GB memory DDR3 x 12

HW Hitachi

06/12/2010 13:17:13

HITACHI Advanced Server HA8000 (X 5670 12cores) RS220KK series

X 5670(6 Core, 2.93GHz) Xeon x 2, 8 GB memory DDR3 x 12

HW Hitachi

06/12/2010 13:17:13

HITACHI Advanced Server HA8000 series RS440AK (16cores E7520)

Xeon E7520 (4 Core, 1.86GHz) x 4, 8 GB memory DDR3 x 64

HW Hitachi

06/12/2010 13:17:13

? fuseaction = Admin & Page = NewHardwareTemplate.cfm & TemplateTypeID = 6 & TemplateID = 4062358 "rel ="nofollow"> HITACHI Advanced Server HA8000 series RS440AK (E7540 24cores)

Xeon E7540 (6 Core, 2.00GHz) x 4, 8 GB memory DDR3 x 64

HW Hitachi

06/12/2010 13:17:13

HITACHI Advanced Server HA8000 (X 7550 32cores) RS440AK series

X 7550(8 Core, 2.00GHz) x 4, 8 GB memory DDR3 x 64 Xeon

HW Hitachi

06/12/2010 13:17:13

HITACHI Advanced Server HA8000 series RS440AK (X 7560 32cores)

X 7560(8 Core, 2.26GHz) x 4, 8 GB memory DDR3 x 64 Xeon

HW Hitachi

06/12/2010 13:17:13

HITACHI Advanced Server HA8000 series TS20AL (E5503 4cores)

Xeon E5503 (2 Core, 2.00GHz) x 2, 16 GB memory DDR3 x 6

HW Hitachi

08/04/2011-13:53:27

? fuseaction = Admin & Page = NewHardwareTemplate.cfm & TemplateTypeID = 6 & TemplateID = 4066152 "rel ="nofollow"> series HITACHI Advanced Server HA8000 TS20AL (8cores E5603)

Xeon E5603 (4 Core, 1.60GHz) x 2, 16 GB memory DDR3 x 6

HW Hitachi

08/04/2011-13:52:58

HITACHI Advanced Server HA8000 series TS20AL (8cores E5620)

Xeon E5620 (4 Core, 2.40GHz) x 2, 16 GB memory DDR3 x 6

HW Hitachi

08/04/2011-13:52:19

HITACHI Advanced Server HA8000 series TS20AL (E5649 12cores)

Xeon E5649 (6 Core, 2.53GHz) x 2, 16 GB memory DDR3 x 6

HW Hitachi

08/04/2011-13:51:46

HITACHI Advanced Server HA8000 series TS20AL (X 5675 12cores)

X 5675(6 Core, 3.06GHz) Xeon x 2, 16 GB memory DDR3 x 6

HW Hitachi

08/04/2011-13:49:56

? fuseaction = Admin & Page = NewHardwareTemplate.cfm & TemplateTypeID = 6 & TemplateID = 4062382 "rel ="nofollow"> HITACHI Advanced Server HA8000 series TS20KK (E5503 4cores)

Xeon E5503 (2 Core, 2.00GHz) x 2, 8 GB memory DDR3 x 6

HW Hitachi

06/12/2010 13:17:52

HITACHI Advanced Server HA8000 series TS20KK (8cores E5620)

Xeon E5620 (4 Core, 2.40GHz) x 2, 8 GB memory DDR3 x 6

HW Hitachi

06/12/2010 13:17:52

HITACHI Advanced Server HA8000 series TS20KK (8cores E5640)

Xeon E5640 (4 Core, 2.66GHz) x 2, 8 GB memory DDR3 x 6

HW Hitachi

06/12/2010 13:17:52

HITACHI Advanced Server HA8000 (X 5670 12cores) TS20KK series

X 5670(6 Core, 2.93GHz) Xeon x 2, 8 GB memory DDR3 x 6

HW Hitachi

06/12/2010 13:17:52

? fuseaction = Admin & Page = NewHardwareTemplate.cfm & TemplateTypeID = 6 & TemplateID = 4062350 "rel ="nofollow"> HITACHI BladeSymphony BS320 H5 2CPUs@2000MHz 98304 MB RAM

Xeon E5503 (2 Core, 2 GHz) x 2, 96Go

HW Hitachi

2010-12-06 13:16:45

HITACHI BladeSymphony BS320 H5 2CPUs@2130MHz 98304MB RAM

you have 10 exceptions listed subnet restrictions. Please modify your script to merge subnets on the scenario settings page.

See: http://kb.vmware.com/kb/1000256/

Also, if you want to increase the ram for your scenario, then make this change later in the scenario Settings Wizard.

If you want to change the scenario that is used for your reports, they begin with the "*" on the page of the Consolidation scenarios.

Best regards

Jon Hemming

iSCSI freeNAS failing to create the file system

Hey guys,.
IM pretty new to the present and iv tried to work this point for some time now...
I got a box of freenas with an array of 5 TB in it... I would like to make a 1 TB logical unit number and mount it on my ESXi 4 server.
my configuration is:
FreeNAS < = 10.10.10.1 = > 2x1GB links using the FEC (Fast or channel) [10.10.10.0/24] < = 10.10.10.2 = > ESXi
I managed to configure the FreeNAS successfully [as far as I can tell...], when I add the target to the iSCSI software storage card it finds the logic unit number and everything seems good.
the problem starts when I try to add as a data store... I select:
Disk/LUN > freeNas LUN > leave default primary partition > give it a simple name > chose the minimum file size of 512 GB > finish
and I get the following error...
Call "HostDatastoreSystem.CreateVmfsDatastore" of object "ha-datastoresystem" on ESXi '192.168.2.202' failed.
Operation failed, the diagnostic report: unable to create the file system, please see VMkernel connect you for more details.
I am unshore where this newspaper VMkernal but that's what I'm going to start hunting for the next...
in which case it may be useful, I am attaching screenshots of all my configs...
Here, any help would be great!
Thank you

Hi, you can follow this tutorial video and see if you have missed at all stages: http://www.youtube.com/watch?v=Dc20IT1msAk

Error creating the store of data on iSCSI LUN (EMC CX4/120)

I run an error when you try to create a data store on a Clariion CX4/120 system. Connectivity to the San is performed via iSCSI. I exhibited with success the target on the storage card and it shows in Configuration > storage adapters > vmhba33 > Details. It has a capacity of 5.37 to.
When I go to Configuration > storage and select Add..., I can select the disk/LUN. The LUN appears here as well. When I click Next, it fills the device information and location and also reported "the HDD is empty." After 10 minutes, it generates the following error...
Call "HostDatastoreSystem.QueryVmfsDatastoreCreateOptions" of object "ha-datastoresystem" on ESXi '172.20.100.78' failed.
I did some research on Google and looked around here on the website of VMware, and I can't find any references to this error. Are there log files for the process that I can look into? I must engage EMC and see if there is a problem with the SAN itself?

It has a capacity of 5.37 to.

VMFS data storage limit is 2 TB less than 512 bytes. Try presenting small LUN, then it should work.

André

iSCSI LUN DS shows as blank hard drive

I had an iSCSI directory store with a single VM on it. The ESX 3.5i server no longer recognizes the LUN as a directory store. When I click on 'Add a storage' can see the LUN but reports that "the hard drive is empty.
I have not conducted through the add storage wizard because I don't want to lose the virtual machine that resides on the subject.
Does anyone know of a method that will allow me to add that LUN as a DS so I can recover the data?

If you have a backup and you want to try, you can go through the steps outlined in 'Recovering a lost on a VMFS volume partition table' http://kb.vmware.com/kb/1002281

Make sure that you have read the warning, however.

Good luck.

André

iSCSI Reporting

Similar Questions

Steps to follow:

Maybe you are looking for