ESXi 4 installed on the iSCSI target

Similar Questions

• Could not see the iSCSI target in the adapters iSCSI software under Configuration details page

  Detailed description:

  After you add the IP address of the iSCSI target in the target iSCSI dynamic discovery Tab names can be seen under static discovery. But, iSCSI target is not considered as adapters iSCSI software tab Configuration details page.

  This iSCSi target is already mounted as a data store VMFS5 with some VMS on an another ESX which is part of the different ESX cluster in the same center of work data.

  thinking the im network configuration

  You vm kernel ports configured correctly?

  you use VLAN? If so see if your config of vlan is correct

• Best practices the iSCSI target LUN

  I connect to my ESX laboratory to a QNAP iSCSI target and wonder what best practices to create LUNS on the target. I have two servers each connection to its own target. Do I create a LUN for each virtual machine, I intend to create in the laboratory, or is it better to create a LUN of the largest and have multiple VMs per LUN? Place several virtual machines on a LUN has concequenses HA or FA?

  Concerning

  It is always a compromise...

  ISCSI reservations are per LUN.    If you get many guests on the same logical unit number, it becomes a problem and Yes we saw it.

  Slim sure to layout.   This way you can make your smaller LUN and still get several s VM we each their.

• How to replace ESXi properly to keep the iSCSI datastore?

  Hi guys,.

  I explore ESXi on a usbstick. It connects

  a NAS server using iSCSI. It works fine, until I screwed something on the

  Configuration of ESXi that it cannot be managed again VI client.

  Thus,.

  I have replace the usbstick by a new one. Again install ESXi and iSCSI.

  He finds the logic unit number, but it gives warning that using this LUN will destroy

  all data in this document, which destroys fortunately when I click OK.

  Thus,.

  in this case, it is good way to regain the intact data store if we

  you will need to change the ESXi? Or, there is no such scenario?

  Thank you.

  Hello

  So a VMFS store be reintroduced to ESX or ESXi the VMFS volume must be readable and correspond to the EUI header / NAA set to paths of storage host created in the esx.conf file or the VC DB vml. If this information is not present while the volume will not be presented as a usable existing VMFS store. I have a blog with some examples to reinstate VMFS stores based on OpenSolaris and ZFS iSCSI volumes.

  http://blog.laspina.ca/roller/ubiquitous/entry/provisioning_disaster_recovery_with_zfs

  You can examine the EUI or NAA on any VMFS work and ESX volume with the following command.

  esxcfg-vmhbadevs - m

  This gives command the name of dev which are associated with the volume and this info you can use hexdump similar to the following.

  hexdump - n 1100000/dev/sda1

  The hexagonal header data will present it as this example output, the value in bold is the guid of stores.

  0100000 d00d 0003 0000 0010 0000 1602 0002 c001

  0100010 0600 5553 204th 2020 2020 4f43 534 d 4154

  0100020 2052 2020 2020 2020 2020 2e31 2030 0160

  0100030 f044 0004 0000 2 a 49 142F 0400 4f43 d47e

  0100040 0000 0000 0000 0000 0000 0000 534 d 4154

  0100050 0000 0000 0000 0000 0000 0200 0000 f800

  0100060 0031 0000 0001 0000 0000 031f 031f ffd4

  0100070 0000 0321 0000 0000 0000 0000 0110 0000

  0100080 0000 3eee 492 has 7cb8 960f 2-0200-6755 16 c

  4e14 0100090 7fda dec9 5 c 68 0004 cf98 managenment 5 c 68

  01000a 0 0004 0000 0000 0000 0000 0000 0000 0000

  01000b 0 0000 0000 0000 0000 0000 0000 0000 0000

  With this information, you can recreate the vml, but it is difficult you should know the format, but for example, we can go.

  Use the following command to see what exists in a lot of work.

  cat /etc/vmware/esx.confcat /etc/vmware/esx.conf | grep vml

  /Storage/LUN/VML.0200020000600144f07ed404000000492a2e140004434f4d535441/adapteriqn.1998-01.com.VMware:vh0.1/targetiqn.1986-03.com.Sun:02:1eddb8ec-CC09-62d0-B867-8da28dee9609/

  Here we see the part that must match in blue.

  Also a little advice on usb based ESXi priming devices, you should not run this type of config at least as the creator of the image usb provided a virtual disk for the swap area.

  Flash multi layer devices will fail quickly if the swap partition area is on the flash device.

  Kind regards

  Mike

• Unable to see the iSCSI target

  Hello

  I just configured an Openfiler area supposed to be some storage additional iSCSI for backup of the virtual computer.

  The target seems to be configured fine that I am able to connect to storage successfully from a machine of W2K3.

  However when I try a scan of the host ESX 3.02 they fail to find the storage.

  I entered the details contained in the dynamic discovery, the service console is in the same subnet and I opened the necessary firewall port.

  Our main storage is a SAN DS3400 of fiber and they use LUNS 0 & 1

  When I try to map a LUN to the target in Openfiler he tries to use LUN 0, this could be the cause, or am I missing something else?

  Any help would be appreciated

  What you added is good news: vSwitch0 1) speaks through a NIC team, and 2) vSwitch0 only SC and VMotion only: you can go ahead, put your Openfiler box on your network admin/VMotion. If your vmkping did not before, I guess it's because the VMotion IP subnet field is different from the ordinary SC subnet IP field, right? If so, adds an extra port SC vSwitch0 in VMotion, to get the subnet of the ping responses and vmkping in the table. Otherwise, if the VMotion network, it's the same as SC network, so I don't understand why your old vmkpings didn't work. Well... This solution is simple, but what I don't like in it, it's that time VMotion traffic and iSCSI will use the same physical link because you don't have a single vmkernel port, that is too bad, when you have 2 physical links. You would think something even more intelligent. The idea would be to force the VMotion traffic to run priority through a vmnic and iSCSI traffic running through the other, each vmnic being the road to recovery on the other.

  To achieve this, at first glance, I would say that should you be the Openfiler box on a subnet dedicated Y. Then, on vSwitch0, create 1 SC port and port 1 vmkernel having both a subnet address Y. Then play with team vSwitch0 NIC settings, the idea would be to configure ports VMK and SC on the subnet Y with an explicit failover of vmnic0 command then vmnic1, and then configure the port VMotion and the SC current port with also an explicit failover command, but with an order of vmnic1 then vmnic0 (i.e., the opposite direction). In this way, iSCSI through vmnic0, VMotion, through vmnic1, and even if there is some VMotion overnight, everyone will not work correctly. And if a vmnic fails, it will suffer a degraded mode, both using the same link, but it will be temporary... The limitation of this solution will potentially come from your physical network architecture: your physical switches will allow all these subnets routed properly through these 2 vmnic? May be that VLAN would help...

  Let me know how it goes!

  Kind regards

  Pascal.

• Having dead path to the iSCSI target

  What I had:

  1 host: ESX3.5i

  2 host: Solaris 10 (SunOS 5.10 Sun Generic_138889-02 i86pc i386 i86pc)

  2 parts ZFS on it - 1 iSCSI share and 1 NFS Sharing.

  What I did:

  Upgrade to ESX4i

  What I have so far:

  Everything works but iSCSI.

  It shows 'path of death' for me, but vmkping to host Sun is ok.

  tail of unpacking here:

  20 June at 16:24:07 vmkernel: 0:01:22:15.659 cpu1:11899) WARNING: iscsi_vmk: iscsivmk_TransportConnSendPdu: vmhba37:CH:0 T: 0 CN:0: didn't request passthru queue: no connection

  20 June at 16:24:07 iscsid: send_pdu failed rc - 22

  20 June at 16:24:07 vmkernel: 0:01:22:15.659 cpu1:11899) WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba37:CH:0 T: 0 CN:0: iSCSIconnection is marked 'OFFLINE '.

  20 June at 16:24:07 iscsid: reported core connection iSCSI error state (1006) (3) 1:0.

  20 June at 16:24:07 vmkernel: 0:01:22:15.659 cpu1:11899) WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess ISID: 00023 000001 d TARGET: iqn.1986-03.com.sun:02:3dd0df28-79b2-e399-fe69-e34161efb9f0 TPGT: TSIH 1: 0

  20 June at 16:24:07 vmkernel: 0:01:22:15.659 cpu1:11899) WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn CID: 0 L: 10.0.0.2:51908 r: 10.0.0.1:3260

  20 June at 16:24:10 vmkernel: 0:01:22:18.538 cpu1:11899) WARNING: iscsi_vmk: iscsivmk_StartConnection: vmhba37:CH:0 T: 0 CN:0: iSCSI connection is marked as "ONLINE."

  20 June at 16:24:10 iscsid: connection1:0 is operational after recovery (2 attempts)

  20 June at 16:24:10 vmkernel: 0:01:22:18.538 cpu1:11899) WARNING: iscsi_vmk: iscsivmk_StartConnection: Sess ISID: 00023 000001 d TARGET: iqn.1986-03.com.sun:02:3dd0df28-79b2-e399-fe69-e34161efb9f0 TPGT: TSIH 1: 0

  20 June at 16:24:10 vmkernel: 0:01:22:18.538 cpu1:11899) WARNING: iscsi_vmk: iscsivmk_StartConnection: Conn CID: 0 L: 10.0.0.2:55471 r: 10.0.0.1:3260

  20 June at 16:24:10 vmkernel: 0:01:22:18.538 cpu1:11899) WARNING: iscsi_vmk: iscsivmk_ConnSetupScsiResp: vmhba37:CH:0 T: 0 CN:0: Invalid residual of the SCSI response overflow: residual 0, expectedXferLen 0

  20 June at 16:24:10 vmkernel: 0:01:22:18.538 cpu1:11899) WARNING: iscsi_vmk: iscsivmk_ConnSetupScsiResp: Sess ISID: 00023 000001 d TARGET: iqn.1986-03.com.sun:02:3dd0df28-79b2-e399-fe69-e34161efb9f0 TPGT: TSIH 1: 0

  20 June at 16:24:10 vmkernel: 0:01:22:18.538 cpu1:11899) WARNING: iscsi_vmk: iscsivmk_ConnSetupScsiResp: Conn CID: 0 L: 10.0.0.2:55471 r: 10.0.0.1:3260

  20 June at 16:24:10 vmkernel: 0:01:22:18.538 cpu1:11899) iscsi_vmk: iscsivmk_ConnRxNotifyFailure: vmhba37:CH:0 T: 0 CN:0: connection failure notification rx: residual invalid. State = online

  20 June at 16:24:10 vmkernel: 0:01:22:18.538 cpu1:11899) iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Sess ISID: 00023 d 000001 TPGT TARGET:iqn.1986-03.com.sun:02:3dd0df28-79b2-e399-fe69-e34161efb9f0: TSIH 1: 0

  20 June at 16:24:10 vmkernel: 0:01:22:18.538 cpu1:11899) iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Conn CID: 0 L: 10.0.0.2:55471 r: 10.0.0.1:3260

  20 June at 16:24:10 vmkernel: 0:01:22:18.538 cpu1:11899) WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba37:CH:0 T: 0 CN:0: event CLEANING treatment

  20 June at 16:24:10 vmkernel: 0:01:22:18.538 cpu1:11899) WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess ISID: 00023 000001 d TARGET: iqn.1986-03.com.sun:02:3dd0df28-79b2-e399-fe69-e34161efb9f0 TPGT: TSIH 1: 0

  20 June at 16:24:10 vmkernel: 0:01:22:18.538 cpu1:11899) WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn CID: 0 L: 10.0.0.2:55471 r: 10.0.0.1:3260

  20 June at 16:24:10 vmkernel: 0:01:22:18.789 cpu1:11899) WARNING: iscsi_vmk: iscsivmk_TransportConnSendPdu: vmhba37:CH:0 T: 0 CN:0: didn't request passthru queue: no connection

  20 June at 16:24:10 iscsid: failure of send_pdu rc-22

  20 June at 16:24:10 vmkernel: 0:01:22:18.789 cpu1:11899) WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba37:CH:0 T: 0 CN:0: iSCSIconnection is marked 'OFFLINE '.

  20 June at 16:24:10 iscsid: reported core connection iSCSI error state (1006) (3) 1:0.

  20 June at 16:24:10 vmkernel: 0:01:22:18.789 cpu1:11899) WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess ISID: 00023 000001 d TARGET: iqn.1986-03.com.sun:02:3dd0df28-79b2-e399-fe69-e34161efb9f0 TPGT: TSIH 1: 0

  20 June at 16:24:10 vmkernel: 0:01:22:18.789 cpu1:11899) WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn CID: 0 L: 10.0.0.2:55471 r: 10.0.0.1:3260

  and so on.

  What I did wrong, and how can I remedy this situation?

  Out of curiosity, I advanced and tried the target solaris. It seems that there is a problem in the target solaris before «solaris 10 update7» I tried u6 and I see the question and this is clearly the problem of the target.

  ...

  iSCSI (SCSI command)

  Opcode: SCSI Command (0x01)

  .0... ... = I: in queue delivery

  Flags: 0x81

  1... = final F: PDU sequence

  .0... ... = R: no data is read from target

  .. 0... = w: no data will be written in the target

  .... . 001 = Attr: Simple (0x01)

  TotalAHSLength: 0x00

  DataSegmentLength: 0x00000000

  MON: 0000000000000000

  InitiatorTaskTag: 0xad010000

  ExpectedDataTransferLength: 0x00000000

  CmdSN: 0x000001ab

  ExpStatSN: 0x000001ad

  SCSI CDB Test Unit Ready

  MON: 0X0000

  Set command: Direct Access Device (0x00) (using default commandset)

  Opcode: Test Unit Ready (0x00)

  Single vendor = 0, NACA = 0, link = 0

  ...

  iSCSI (SCSI response)

  Opcode: SCSI response (0 x 21)

  Flags: 0 x 82

  ... 0... = o: no overflow to only read a part of two-way remote

  .... 0... = sup: No exceedances of the ability to only read a part of two-way remote

  .... . 0 = o: no residual overflow occurred

  .... .. 1 = sup: residual overflow occurred < < < < < =.

  Answer: Command completed at the target (0x00)

  Condition: Good (0x00)

  TotalAHSLength: 0x00

  DataSegmentLength: 0x00000000

  InitiatorTaskTag: 0xad010000

  Statsdon't: 0x000001ad

  ExpCmdSN: 0x000001ac

  MaxCmdSN: 0x000001ea

  ExpDataSN: 0x00000000

  BidiReadResidualCount: 0x00000000

  ResidualCount: 0x00000000

  Demand: 10

  Request time: 0.001020000 seconds

  SCSI response (Test Unit Ready)

  MON: 0X0000

  Set command: Direct Access Device (0x00) (using default commandset)

  SBC Opcode: Test Unit Ready (0x00)

  Demand: 10

  Request time: 0.001020000 seconds

  Condition: Good (0x00)

  ...

  14:02:12:42.569 cpu2:7026) WARNING: iscsi_vmk: iscsivmk_ConnSetupScsiResp: vmhba35:CH:0 T:2 CN:0: Invalid residual of the SCSI response overflow: residual 0, expectedXferLen 0

  14:02:12:42.584 cpu2:7026) WARNING: iscsi_vmk: iscsivmk_ConnSetupScsiResp: Sess ISID: 00023 000001 d TARGET: iqn.1986-03.com.sun:02:fa2cdf18-2141-e633-b731-f89f47ddd09f.test0 TPGT: TSIH 1: 0

  14:02:12:42.602 cpu2:7026) WARNING: iscsi_vmk: iscsivmk_ConnSetupScsiResp: Conn CID: 0 L: 10.115.153.212:59691 r: 10.115.155.96:3260

  14:02:12:42.614 cpu2:7026) iscsi_vmk: iscsivmk_ConnRxNotifyFailure: vmhba35:CH:0 T:2 CN:0: Connection failure notification rx: residual invalid. State = online

  14:02:12:42.628 cpu2:7026) iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Sess ISID: 00023 000001 d TARGET: iqn.1986-03.com.sun:02:fa2cdf18-2141-e633-b731-f89f47ddd09f.test0 TPGT: TSIH 1: 0

  14:02:12:42.644 cpu2:7026) iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Conn CID: 0 L: 10.115.153.212:59691 r: 10.115.155.96:3260

  14:02:12:42.655 cpu2:7026) WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba35:CH:0 T:2 CN:0: Treatment of CLEANING event

  14:02:12:42.666 cpu2:7026) WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess ISID: 00023 000001 d TARGET: iqn.1986-03.com.sun:02:fa2cdf18-2141-e633-b731-f89f47ddd09f.test0 TPGT: TSIH 1: 0

  14:02:12:42.683 cpu2:7026) WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn CID: 0 L: 10.115.153.212:59691 r: 10.115.155.96:3260

  14:02:12:42.731 cpu2:7026) WARNING: iscsi_vmk: iscsivmk_TransportConnSendPdu: vmhba35:CH:0 T:2 CN:0: Didn't request passthru queue: no connection

  14:02:12:42.732 cpu3:4119) vmw_psp_fixed: psp_fixedSelectPathToActivateInt: "Unregistered" device has no way to use (APD).

  14:02:12:42.745 cpu2:7026) iscsi_vmk: iscsivmk_SessionHandleLoggedInState: vmhba35:CH:0 T:2 CN:-1: State of Session passed of "connected to" to "in development".

  14:02:12:42.756 cpu3:4119) vmw_psp_fixed: psp_fixedSelectPathToActivateInt: "Unregistered" device has no way to use (APD).

  14:02:12:42.770 cpu2:7026) WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba35:CH:0 T:2 CN:0: iSCSI connection is marked as 'offline'

  14:02:12:42.782 cpu3:4119) NMP: nmp_DeviceUpdatePathStates: the PSP has not selected a path to activate for NMP device 'no '.

  14:02:12:42.794 cpu2:7026) WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess ISID: 00023 000001 d TARGET: iqn.1986-03.com.sun:02:fa2cdf18-2141-e633-b731-f89f47ddd09f.test0 TPGT: TSIH 1: 0

  14:02:12:42.823 cpu2:7026) WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn CID: 0 L: 10.115.153.212:59691 r: 10.115.155.96:3260

  In response, 'U' bit must not be set. Solaris 10 update7 seem to have this problem.

• Kickstart install the iscsi disk not found

  I can't get my order of kickstart to install the iscsi disk.

  the line

  install - firstdisk = distance does not sutable found records

  I also tried

  Installer--disk=/vmfs/devices/disks/EUI.XXXXXXXXXXXXXXXXXXXXXXXXX

  install - disk = mpx.vmhba32:C0:T0:L0

  None of them sees the iscsi drive

  But if I run the Setup manually, I don't see the iscsi drive.

  any idea?

  I think that I understand it. In cisco ucs, I had to change my font of startup and add iscsi as secondary targets.

  the policy must be

  1 LAN

  2. the ISCSI targets

  The kickstart file can always use install - firstdisk

• How do I know if ESXi 4 OS installed on the local hard drive or SAN?

  Hello

  As above, how can I know if ESXi 4 OS installed on the local hard drive or SAN? average is ESXi SAN hard drive boot?

  Thank you

  The output looks like that ESXi is installed on the local disk (vmhba0).

      1 root     root       146778685440 Jul  8 11:16 mpx.vmhba0:C0:T0:L0
      119 917504 -rw-------    1 root     root          939524096 Jul  8 11:16 mpx.vmhba0:C0:T0:L0:1
      121 4193280 -rw-------    1 root     root         4293918720 Jul  8 11:16 mpx.vmhba0:C0:T0:L0:2
      123 138223680 -rw-------    1 root     root       141541048320 Jul  8 11:16 mpx.vmhba0:C0:T0:L0:3
      125 4080 -rw-------    1 root     root            4177920 Jul  8 11:16 mpx.vmhba0:C0:T0:L0:4
      127 255984 -rw-------    1 root     root          262127616 Jul  8 11:16 mpx.vmhba0:C0:T0:L0:5
      129 255984 -rw-------    1 root     root          262127616 Jul  8 11:16 mpx.vmhba0:C0:T0:L0:6
      131 112624 -rw-------    1 root     root          115326976 Jul  8 11:16 mpx.vmhba0:C0:T0:L0:7
      133 292848 -rw-------    1 root     root          299876352 Jul  8 11:16 mpx.vmhba0:C0:T0:L0:8
  

  Sizes, looks like you are using 2x146GB hard drives in RAID1.

  BTW. ls-lisa and fdisk-lu are two separate commands.

  André

• Error in invoking target 'install' in the makefile

  Hi all

  When I install EM12C then I got this error is "Error" by invoking the 'install' in the makefile target

  Please help me to solve this error.

  INFO: / usr/bin/ld: cannot find-lclntsh -.

  collect2: ld returned 1 exit status

  INFO: make [1]: leaving directory ' / u01/app/oracle/product/middleware/who/sqlplus/lib '.

  INFO: make [1]: * [/ u01/app/oracle/product/middleware/who/sqlplus/bin/sqlplus32] error 1

  make: * [newsqlplus32] error 2

  INFO: End of the generated process exit.

  INFO: ----------------------------------

  INFO: Exception thrown from action: do

  Exception name: MakefileException

  Exception string: error in invoking target 'install' of makefile ' / u01/app/oracle/product/middleware/oms/sqlplus/lib/ins_sqlplus.mk'. See ' / u01/app/oraInventory/logs/installActions2013-07-26_08-43-01-AM.log ' for details.

  The exception severity: 1

  INFO: POPUP of WARNING: error in invoking target 'install' of makefile ' / u01/app/oracle/product/middleware/oms/sqlplus/lib/ins_sqlplus.mk'. See ' / u01/app/oraInventory/logs/installActions2013-07-26_08-43-01-AM.log ' for details.

  Click 'Retry' to try again.

  Click "Ignore" to ignore this error and continue.

  Click 'Cancel' to stop this installation.

  Best regards

  Kong Kosal

  Check for 2 things-

  (a) is the directory where you extracted your software (disc 1) and under Disk1, you should see the following files. WT.zip is this?

  a@adcxxxxxxx Disk1] $ ls

  install plugins response stage WT.zip libskgxn

  JDK SGD runInstaller wls

  (b) as mentioned Courtney, you ignore a failure of pre - req and I suspect that you have not the glibc package on your host.

  Review required packages-http://docs.oracle.com/cd/E24628_01/install.121/e22624/preinstall_req_packages.htm#CHDEHHCA

  Examine the log files

  installActions/logs /.log

  / cfgtoollogs/Yes/installActions.log

• ISCSI Target VM address RDM?

  I have 300 GB local disks on some of my hosts connected to our SAN.  I would like to take advantage of this local space for models and ISO files.  I intend to install the iSCSI Target Framework (tgt).  My question is...

  If this CentOS VM that turns our iSCSI Target just plug the local disks on VMFS or should I try to present the local disk as a RDM (Raw Device Mapping).

  Since the machine will use local disks, vMotion and anything that is out of the question anyway, so I think this could be a good situation for the use of RDM.

  Hello.

  If this CentOS VM that turns our iSCSI Target just plug the local disks on VMFS or should I try to present the local disk as a RDM (Raw Device Mapping).

  I would use VMFS for this. You will have more flexibility with VMFS and RDM the local approach seems to add unnecessary complexity.

  Good luck!

• Removed VMFS3 iSCSI target volume - I'm screwed?

  Hello. I "tried" to move virtual machines between servers and the San. On a single server, ESXi 3.5, I 'got' a VMFS volume on a target iSCSI on a basic SAN device.

  The volume "was" listed in the configuration of the server/storage tab. I removed thinking it would be just to delete the reference to the volume from the point of view of the host, but he seems to have deleted the iSCSI target volume.

  Is this correct - is my missing volume? If I'm screwed? Is there anyway to recover the volume?

  Any help or advice would be really appreciated. Thanks in advance.

  We must thank Edward Haletky, not me

  In the VMware communities, his nickname is Texiwill.

  André

• iSCSI target

  can we use USB HDD for the iscsi target?

  Hello Manu,

  1. which Windows operating system you are using on the computer?

  2. are you connected to a domain?

  Please provide more information to help you best.

  Suggestions for a question on the help forums

  http://support.Microsoft.com/kb/555375

• 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

• 'Incorrect function' during the initialization of an iSCSI target

  I have problems when you try to create a partition of 3.7 TB on Windows Server 2008 R2.

  

  I get the following error message when I try to initialize an iscsi target:

  

  What I am doing wrong.  The target is not part of a cluster.

  

  What I am doing wrong? I tried initilizating the disk with MBR and GPT time partitions and all do the same thing.

  Have you installed the software on the server (at least the host software) and establish connections iSCSI on two raid controllers? Looks like that may connect you to a controller, but the virtual disk is owned by the other controller.

• I share the same target iSCSI with multiple hosts?

  I have an iSCSI LUN target that appears when I discovered the storage for an ESXi host, but when I discovered the storage for another host, it does not appear. I added the suitable adapter software network and iSCSI on the second host, dynamic analysis and he sees the same iSCSI target, however when I go to 'Add a storage' there is no displayed LUN.

  I'm obviously missing something, I just can't understand what it is.

  Any help would be greatly appreciated!

  Storage Area Network - FC and iSCSI - do not automatically appear LUN to all hosts that connect to them. This is also called masking and prevents accidental access to LUNS of the host that is not allowed access to that LUN. You must configure the storage system, access to the LUN - once you do this for the other hosts will be displayed in the list and you will be able to access all hosts logic unit number.

  To avoid trampling of the ESXi put a lock on the VMDK so that a subsequent host will not be able to power of the virtual machine and write than disj virtuak