at the level of the ESX iSCSI initiator

Similar Questions

• Guest VM, or additional hard drives ESX iSCSI initiator?

  We'll install Exchange 2010 on a Server 2008 R2 VM... is there disadvantages of adding several hard drives and for dealing with the ESX iSCSI traffic?  Or would it be better to use the initator iSCSI in the VM guest to connect to the San (EqualLogic PS4000)?

  If we continue the road of iSCSI initiator that I'll have to do some networking finageling since our iSCSI traffic is spread over a separate... switch then I'll probably have to add a VM network to the virtual switch and add a second NETWORK card to the guest VM... It would be simpler just to add more hard drives, but I don't know what is the (positive or negative) impact it would have on performance.

  Thank you.

  Hello

  the difference in performance between a vmdk and a RDM is something that can be ignored safely, there are many autour benchmarks that show how VMDK is basically fast a RDM disk, but you can avoid all the complexities of managing iscsi RDM inside virtual machines by going with vmdk.

  Basically, the only need IMHO to use a RDM is if you need to create a Microsoft Cluster inside VMware.

  Ciao,.

  Luca.

  --
  Luca Dell'Oca
  http://www.vuemuer.it
  @dellock6
  vExpert 2011

• Clean shutdown for EqualLogic PS6100 without stopping the host/iSCSI initiator

  In fact, I've known the procedure on how to stop the Equallogic PS storage. But I have a question as well as the procedure.

  Do you really need to stop the iSCSI initiator or the host connected to the storage before you shut down the storage controller?

  Because we move the Equallogic box on the rack on the other. I just want to stop the Equallogic without stopping the hosts.

  Hello

  The hosts are connected to some other storage that you want to keep as you move the table EQL?  If you stop the storage, it is similar to pulling on a hard drive in its operation.  Most of the time nothing bad will happen.  But all entries that did not allow the storage is lost.   For applications such as SQL or Exchange is not something you want.

  If you need to keep the server up, stop all applications accessing the volumes, then disconnect all EQL volumes first, and then stop the EQL table.  Will be served waiting for the written word.

  Kind regards

  Don

• Help with the hardware iSCSI initiator help

  Hi all

  I don't know if this is the right place... Please forgive me if I'm in the wrong community. I am a newbie in VMWare and attempt to install my first server VMWare (ESX 4.0)... I have a HP DL 380 G6 server and a storage Equallogic PS 5000 array. I have a card HBA Qlogic ELQ 4060C on the server. I installed successfully ESX 4 and when I am connected to the console of the VI Client service and checked the configuration tab, I could see the HBA Qlogic cards there. This means that ESX recognize the HBA. I have install a volume on the Equallogic configuration / control box by using the IP address I have set up for the Qlogic HBA. But even after several reboots and renumerisations BH is unable to see the volume. I'm doing something wrong here? What is the right way to install the HBA? Should I do something else to put in place? Any help or advice or pointers to documentation is greatly appreciated.

  Thank you and best regards,

  Rupesh

  Hi Rupesh

  First of all, you need not configure vmkernel for HWiSCSI network. As you say, it is only necessary for SWiSCSI.

  Then, to configure HWiSCSI, make sure that you have provided the IP address, subnet, etc on the iscsi adapter. If not, configure this first either through the client adapter's bios vi/vc or hwiscsi. Make sure that this IP address can speak for the iscsi storage network.

  Now, on the side of storage, MAPE to the IQN HWiSCSI iscsi lun. Provide the IP address of storage in the discovery address (dynamic discovery) or storage ip and IQN (Statici discovery)

  Rescan the HBAS and you should be able to see the LUNS.

  Thank you

  Sangaré

• Where and how to get the downgraded version iSCSI initiator?

  Is there a place for older versions of the microsoft iSCSI initiator?

  We are trying to install a piece of legacy equipment and the last confirmed the version that has been tested is V1.05a

  Kind regards

  Drew

  Hi Brainojack

   

  Please refer to the below provided links and check if the provided versions help you. -

  http://www.Microsoft.com/windowsserver2003/technologies/storage/iSCSI/default.mspx

  http://www.Microsoft.com/downloads/en/details.aspx?FamilyId=12cb3c1a-15d6-4585-b385-befd1319f825&displaylang=en

   

  But it does not seem you can get versions older than those set forth above. So I suggest you use your favorite search engine search for third party links that can provide you the version you need.

  
  NOTE- Using third-party software, including hardware drivers can cause serious problems that may prevent your computer from starting properly. Microsoft cannot guarantee that problems resulting from the use of third-party software can be solved. Software using third party is at your own risk.

   

  I hope this helps.

• Logic unit number must be manually replaced by the iSCSI initiator

  I have a VM server that once restarted the logic unit number must be manually replaced by the iSCSI initiator. Does anyone have an idea how I can get this auto re - join when the server is restarted?

  EqualLogic PS4100

  Win2008 R2 64 bit server VM

  When you logged into the volume, there is a checkbox to restore the connection.  It was supposed to end upward in the Favorites tab in the MS iSCSI initiator utility.

• Reattach the EqualLogic iSCSI for 2012 Windows volumes

  Hello

  We use EqualLogic, Windows 2008R2, HIT and initiator iSCSI access volumes. Now I'm re - install OS to Windows 2012. All materials, IP addresses, volumes, host name will be the same on the new operating system. BONES of some changes. Will it be the right way to remap the iSCSI volumes to the new operating system:

  1. on windows 2008 R2 take the volume offline in the disk management console.
  2. disconnect "Discovered targets" in the Windows iSCSI initiator.
  3 collect volumes offline in Manager Dell EqualLogic Group (to restore the connections).
  4. the new 2012 Windows Installer 4.5 HIT and set (is this version of the correct software for Windows 2012?)
  5 activate the volumes in the Dell EqualLogic Group Manager.
  6. Discovery target and connect to targets.
  7 collect volumes online in the OS disk management console.

  These steps are correct?
  Are they all necessary?
  Is a correct software 4.5 for windows 2012 HIT?

  Thank you

  Re: connections.  Are you referring to the iSCSI to table sessions?   If so, those are dynamic.  When you stop they will disappear.

  If everything is the same, so technically Yes.  Shutdown, you can reload and bring it to the top.

• Microsoft iSCSI Initiator with MPIO software

  Use the Microsoft MPIO Software iSCSI initiator installed from an OS supported by VMware guest? Can you tell me analysis that supports this or not?

  Setup would be:

  (1) FAS of NetApp with two Ethernet ports, two IP addresses and two VLANS

  (2) guest operating system (2000, 2003, 2008) with the Microsoft iSCSI initiator installed/enabled and configured for failover or MPIO load balancing

  (3) don't know how to put in place the ESX network, either:

  (i) two physical ESX NIC physical, connected to two different physical switches and two vSwitches, each physical NETWORK adapter on the VLANS separated mentioned in point (1). Guest operating system with two network cards for, each vNIC connected to the separate vSwitches - MPIO configured to load balance/failover.

  (II) active/passive team ESX physical NIC (not the choice here for active/active), connected to a unique vSwitch, both VLAN present at vSwitch. Guest operating system with two network adapters, each vNIC connected to the separate vSwitches - MPIO provisions set up two paths to the storage.

  Other ideas would be appreciated, thanks.

  Hi Tao2,

  Welcome to the forum.

  NetApp site information: "MPIO is not supported in a guest OS." ( http://now.netapp.com/NOW/knowledge/docs/snapdrive/relsnap62/html/software/admin/GUID-5341E2D6-4BFD-41E1-8AAE-0D643D2596EC.html ).

  Most of the time, we ensure the redundancy of storage iSCSI network through the VMware network design:

  • a vNic dedicated for storing the virtual machine

  • vNic attached to a vSwitch with two physical in failover mode maps

  It may be useful

  Concerning

  Franck

• I want to use MPIO to Ms iscsi initiator How get/install MPIO support and MSDSM to windows 7?

  How to enable MPIO are MS Inititator and MS DSM iscsi on window 7?

  Hi Parag Blangy,

  Thank you for visiting Microsoft Answers.

  As this problem is related to the MS iscsi initiator MPIO, it will be better suited in the Technet community.

  Please visit the link below to find a community that will provide the best support.

  http://social.technet.Microsoft.com/forums/en-us/category/windowsvistaitpro

  Installation and configuration of Microsoft iSCSI Initiator:

  http://TechNet.Microsoft.com/en-us/library/ee338480 (WS.10) .aspx

  Microsoft iSCSI Software Initiator Version 2.X users guide:

  http://download.microsoft.com/download/A/E/9/AE91DEA1-66D9-417C-ADE4-92D824B871AF/uGuide.doc.

  Microsoft Multipath i/o: frequently asked Questions:

  http://www.Microsoft.com/windowsserver2003/technologies/storage/MPIO/FAQ.mspx

  Kind regards
  Amal-Microsoft Support.
  Visit our Microsoft answers feedback Forum and let us know what you think.

• iSCSI initiator error - cannot add target

  I am currently using a MD3000i in a test environment.

  The installation is very simple:

  The MD3000i is directly connected to a Windows Server 2003 (x 64 Enterprise edition).

  The management software is completely installed on this server. Only one controller is used to manage the PowerVault (partially managed)

  All default settings are used. I have configure the system according to the guide online "Board installation and configuring iSCSI" found on the installation CD.

  I get an error when configuring the Mirosoft iSCSI initiator. As soon as I try to add a port for iSCSI (iSCSI initiator properties panel-> discovery-> target portals tab), I get the following error message:

  "invalid sendtargets response text was detected.

  After accepting this error, the port is added to the list, but will not appear in the tab target, it is therefore impossible to connect to this port. The port of host iSCSI on the table and the address source on the server IP responds to ping without problem.

  At this point, I am only able to connect to the MD3000i with the out of band management and cannot access the storage in any way.

  Any help would be greatly appreciated

  Robert

  
  

• iSCSI Initiator Port Group error

  Problem adding in the vmk second to an existing iSCSI vSwitch.  Original config was 2 vmks - all worked successfully.  1 vmk has been removed to solve network problems.

  Re-created the 2nd vmk, but when going down one of the cards the unused category as soon as active network OK is selected the message "this vmkernel port group contains a NETWORK card.

  which is related to an iSCSI initiator.  Change its settings could disrupt the connection to the iSCSI data store"is displayed.  The response options are Yes or no.  A screenshot is attached.

  vCenter is version 5.0 U1b.  The host is ESXi5.0 U2 and mode of maintenance with none of the guests.  The host on the local disk not stop SAN.  I can safely click Yes, then go back and

  move the vmnic or is there a better way to fix this problem.  Thank you.

  Thanks for sharing the information. Please try below steps:

  Step 1. Remove links in the existing port and reboot the host.

  Step 2. Change the port iSCSI and vmnic preferred value to active group and move the second unused NETWORK card.

  Step 3. Change group 2-port iSCSI and vmnic preferred value in the active State and move the other card unused NETWORK.

  Step 4. Add vmk1 and vmk2 under links in the port iScsi initiator network configuration.

  I hope steps above will help to solve the problem. If you encounter the error even if you please let me know.

• Migration of the iscsi initiator software to hardware initiator on 2012 Hyper-v cluster.

  Hello

  We have 10 blades x M620 with Broadcom 10gig 57810 M1000e CMC card dedicated for iSCSI Equallogic PS 6110 San.

  Currently software used on cluster hyper-v Windows 2012 connect SAN PS6110 iscsi initiator.

  150 VMS are in production on 15 CSVs.

  We want to change the initiator of the software to the hardware on all our existing blades without CSV output.

  Is it possible on hyper-v cluster 2012 to have 5 blades with initiator software and remaining 5 blades with hardware initiator with same CSV cluster?

  If coexistence of initiator software and material as possible through hosting then I can apply this change a bit on our 10 blades without cluster downtime.

  Hello

  What version of FW EQL do you use?

  Yes, it is possible, however a couple of updates warn first.

  1.) install the latest firmware / boot code and driver for Broadcom cards.

  2.) put the node into maint mode then you can disconnect the SW iSCSI provenance and sign in using the HW iSCSI adapter.

  3.) do not try to do it with an active node / online.

  The advantage of the HW iSCSI adapter reduces the CPU Overload, if you are maxing out the CPU not now, do not expect a large increase in performance after HW iSCSI card.

  Kind regards

• The ISCSI initiator problem

  Another problem of beginner.  I learned a lot about my new virtual world, and the box Logic Equal Dell.  But I still have a fundamental problem that must be an easy fix, or something I do not understand from a technical perspective.  I want to be able to connect to a snapshot and be able to recover a file if necessary.

  I brought the snapshot online and I could even get on vSphere so I could see him there.  But, for the life of me I can't all iscsi initiator to see the snapshot at all.  I have a few guesses, but I can't seem to understand my problem.

  I can't get the initiator to see all the targets... it just tells me the connection fails.  I think I know why, but my skills of network management are not real strong.  When we had an outside company come in and set up the environment, they put everything on 192.168.100.x or 192.168.101.x.  Since I arrived here (more than 15 years ago), our network has always been 129.1.x.x ip addresses.  I'm programmer for the most part and I got a guy of networking which is solid to the networking but I don't know if he can answer my question either.

  In any case, when I try to add my portal target to the initiator, what IP address or the name am I supposed to point to?  I can't ping the 192 addresses because I'm on an IP 129.1.x.x, correct?  So, this is why I have no chance to find snapshots using the initiators?  I know the vCenter server has an address 129 and the SAN itself has a 129 address and I tried to connect to who but did not work.

  I think I gave permission to the snapshot to be seen by several initiators.

  I think it's my lack of networking, but maybe not.  Any help would be greatly appreciated.

  Thank you

  Ryan Kotowski

  The snapshot will not be a set of files that you can view. This will be a copy of exactly what the LUN looked like when you took the photograph, you need to mount it in vSphere just like you would ride the regular LUN. Then you will see all the VMX and VHDX files for virtual machines that you instantly. Then you can add one in vSphere and power to recover his files. Don't forget that you'll want to disable networking all on this virtual machine so that it is not in conflict with the actual VM on the network.

• After that stright connected to iSCSI (initiator) Host cannot ping the server iSCSI (target), but the target can, why?

  After that host on vSHere 4.0 strightly connected to iSCSI (initiator) host cannot ping the server iSCSI (target), but target can.  And iSCSI works well. I mean I can create and use the iSCSI disk, why? It makes me confused.

  Thank you!

  Geoarge,

  iSCSI traffic uses a VMkernel port, instead of using the command 'ping', use 'vmkping '.

  André

• Two displayed like device the same ISCSI LUN? I'm very confused...

  Hello

  I have a little problem that I can't get my head around. I have two ISCSI Thecus SAN devices on two separate subnets.

  Thecus1 is on 192.168.17.155 and Thecus2 on 192.168.18.156

  I added both in the SW initiator but one show in the storage view.

  When I look in the devices it shows a single disc, but when I look in the paths - it shows two.

  It seems that vmware is the same device two separate paths for a reason any. Where it should show two separate devices and a path to each! Does anyone have anyone pointers or advice to help? I just can't get my head around it all. Ive restarted it this way. I think that the thecus runs some open

  source ISCSI stuff under the hood, but that really shouldn't affect what I do not. These boxes are marked 'VMWare ready' show should be compatible. I contacted Thecus support but they isn't much use. When I look on the thecus iscsi targets I see the attached both esx host. I would add also, I have two hosts, both with the same problem. Each thecus has received a different logical unit number ID, we have 1 and 4.

  Gahh... I hope it's something obvious I've missed.

  

  

  Your table exports the two volumes with the same UUID (WWN) so ESX think it's the same volume via different paths.

  Your provider of storage have you will tell how to fix this.