The ISCSI initiator problem

Similar Questions

• 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.

• 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

• Change the iSCSI initiator name

  Hello

  I am writing a script to configure the initiator iscsi on several hosts and led to this

  Import-Csv-Path "c:\Tools\Powershell\CSV\hostconfig.csv" | %{

  $StorageSystem = get-View (Get-VMHostStorage - VMHost (Get-VMHost-name _.esxHost $)) USER.USER

  $StorageSystem.UpdateSoftwareInternetScsiEnabled ($true)

  $StorageSystem.StorageDeviceInfo.HostBusAdapter | where {$_.} GetType(). Name - eq "HostInternetScsiHba"} | %{

  $HbaName = $_. Device

  }

  $initName = $_.initname

  $StorageSystem.UpdateInternetScsiName $initName

  $iSendTarget1 = new-Object VMware.Vim.HostInternetScsiHbaSendTarget

  $iSendTarget1.Address = "10.10.10.1".

  $iSendTarget1.Port = '3260.

  $SendTargets = $iSendTarget1

  $StorageSystem.AddInternetScsiSendTargets ($HbaName, $SendTargets)

  Get-VMHostStorage - $hst - RescanAllHba - RescanVmfs-VMHost

  }

  However, I'm stuck as to changing the name of the initiator.  I need to do for my SAN security.  I used a csv file for the main variables and can extract the new name I want to put, but I can't understand how to set it up.

  Any help would be appreciated.

  Thank you

  Alasdair...

  The UpdateInternetScsiName method needs 2 parameters, the current name and the new name.

  Can try you this?

  Import-Csv -Path "c:\Tools\Powershell\CSV\hostconfig.csv" | %{
       $esxImpl = Get-VMHost $_.esxHost
       $esx = $esxImpl | Get-View
       $StorageSystem = Get-View $esx.ConfigManager.StorageSystem
  
       $StorageSystem.UpdateSoftwareInternetScsiEnabled( $true )
  
       $StorageSystem.StorageDeviceInfo.HostBusAdapter | where {$_.GetType().Name -eq "HostInternetScsiHba"} | %{
            $HbaName = $_.Device
       }
  
       $StorageSystem.UpdateInternetScsiName($HbaName,$_.initName)
  
       $iSendTarget1 = New-Object VMware.Vim.HostInternetScsiHbaSendTarget
       $iSendTarget1.Address = "10.10.10.1"
       $iSendTarget1.Port = "3260"
       $SendTargets = $iSendTarget1
       $StorageSystem.AddInternetScsiSendTargets( $HbaName, $SendTargets )
  
       Get-VMHostStorage -VMHost $esxImpl -RescanAllHba -RescanVmfs
  }
  

  ____________

  Blog: LucD notes

  Twitter: lucd22

• 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

• RDM v ISCSI initiator in comments

  Hi all

  We are looking at a Sharepoint deployment and Server index MS requires that its application data on a LUN.
  Telling me two options:

  -Use RDM

  -Use the guest VM iSCSI initiator

  Is there a reason why I should not use the iSCSI initiator in the comments?
  My reason for thinking this is a much simpler configuration.
  We go to a lot of Ribbon burocratique until we can make changes to a production environment
  It would be rather not configure ESX with iSCSI. We use NFS as back-end storage

  Have you seen performance problems when you use the ISCSI initiator in the guest VM?
  I didn't notice anything during a vmotion for example. What should I look for?

  Any thoughts appreciated!

  See you soon

  Hello

  If your back-end spinning is the same, so if you want to use iSCSI or RDM depends on how much you want to manage storage from the virtual machine. Using the Software in an average VM iSCSI initiators, you must deal with this, when you upgrades, etc. If you use RDM you leave such management to vSphere.

  It is also one of the reasons I prefer RDM. least to me when I manage VMs and if my vSphere host uses iSCSI devices or can make unloading iSCSI (like HP Flex-10) and then I win all the way around.

  Best regards

  Edward L. Haletky

  Host communities, VMware vExpert,

  Author: VMware vSphere and Virtual Infrastructure Security,VMware ESX and ESXi in the 2nd business edition

  Podcast: the Podcast for security virtualization of resources: the virtual virtualization library

• Make Accessible iSCSI SAN-VM via Windows iSCSI initiator

  I have a "total newbie" question that I hope can respond quickly enough.

  I added a new DELL MD3000i SAN to my storage network in order to use this SAN exclusively for Windows virtual machines. I have the vdisks large (2) 4 to 7 to each (Yes, I REALLY need unique and large volumes) defined on the MD3000i. (4) the MD3000i ports are connected to my iSCSI VLANS and have the id default host port 192.168.130.101/102 and 192.168.131.101/102.

  I have a MD3220i installed in the network and working with hosts ESXi 4.1 (2) (192.168.230.101/102, 192.168.231.101/102 of the subnets). I am quite familiar with how to make the storage available to the host via the initiator of the iSCCI, but I know not how to make accessible storage for virtual machines WITHOUT using the host to connect to the iSCSI SAN, create a data store, and then add a new virtual disk to the virtual machine.

  Only the vmnic dedicated to the iSCSI initiator have physical links to iSCSI VLANS (vSwitch01). The network switch has (2) network adapters connected to the network via vSwitch0 "inside".

  Any ideas on the best way to "get there from here"?

  Hello.

  You will need to create a group of ports in virtual machine on the same vSwitch created in your iSCSI ports group.  Give the virtual machine a 2nd NETWORK card and then assign it to the created virtual machine port group previously.

  Good luck!

• 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.

• 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é

• How to set up the new switch/ports/NIC for MS iSCSI initiator

  Hello

  I'm looking for data on our main server snapshot and then include it with our VM through scripted admsnap commands. I found that the only way to attach/detach when the server is running must be involved in the Microsoft initiator path.

  I am now tripping over the implementation of networks necessary for this virtual machine display the SAN using the initiator.

  Our up to date is:

  vSwitch0 that vmnic0 & 1 (range 192.168.1.x) and is used for LAN traffic for the virtual machine

  vSwitch1 that vmnic3 (192.168.252.x range) and is used for SAN storage processor has

  vSwitch2 that vmnic2 (range 192.168.253.x) and is used for SAN B storage processor

  http://i44.Tinypic.com/20pezr4.gif [line] 

  Our ESX box can connect to the LUNS on the area of SAN ok but I just can't get the same ping VM after the addition of two new network cards and to configure them with the correct IP address, which I suppose is because the 192.168.252.x and 192.168.253.x ranges are not present on the virtual machine and there is this problem I would appreciate some advice on SAN storage processors. How you allow the virtual machine is to use vSwitch0 & 1

  Thank you.

  Hello.

  vSwitch0 that vmnic0 & 1 (range 192.168.1.x) and is used for LAN traffic for the virtual machine

  vSwitch1 that vmnic3 (192.168.252.x range) and is used for SAN storage processor has

  vSwitch2 that vmnic2 (range 192.168.253.x) and is used for SAN B storage processor

  Our ESX box can connect to the LUNS on the area of SAN ok but I just can't get the same ping VM after the addition of two new network cards and to configure them with the correct IP address, which I suppose is because the 192.168.252.x and 192.168.253.x ranges are not present on the virtual machine and there is this problem I would appreciate some advice on SAN storage processors. How you allow the virtual machine is to use vSwitch0 & 1

  I'm guessing that you have added two new adapters with the label 'VM Network' network to this virtual machine?  I'm also guessing that vSwitch0 has no access or routing to the storage network.  If so, you will need to do is change the vSwitch1 and vSwitch2 to add a new type of virtual machine connection.  Click on the 'Properties' link beside vSwitch1/vSwitch2 and in the tab "Ports" click on the button 'Add '.  Choose 'Virtual Machine' in the type of connection, it give a descriptive label and click Finish. Then return to the virtual machine (change settings) and change the network connections in your virtual machine to point to the new label, that you just created.  Finally, configure or verify) addressing IP in Windows and try the Ping again.

  Good luck!

• at the level of the ESX iSCSI initiator

  Hey guys,.

  I have a hard time trying to imagine if the iscsi initiators software for vmware esx is a bunch of installable software that I need to download, or TI a bunch of settings that I need the value of the vmnic.

  Please help. If I need to download and install them on the esx host, can you guide me as to where I can find them.

  We run a free version of esx 3.5i, I don't see that would be a problem during the installation or the loading of the iscsi initiators, or would it?

  Thank you

  RJ

  Under adapters for storage in the Control Panel, you should see a SoftwareAdapter iSCSI.  Click it and then click Properties.  This should help you pointed in the right direction.  Under the security profile, you need to activate the customer iSCSI as well.  Otherwise it will be blocked by the firewall.

  Let me know if you need more information.

  Charles nights, VCP

  If you have found this or other useful information, please consider awarding points to 'Correct' or 'useful '.

• 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é

• 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.

• error of target iSCSI initiator 0xEFFF0012

  After upgrade to windows Server 2003 enterprise x 86 to windows Server 2008 Server Enterprise x 86, the SCSI initiator gives me error of target, the event viewer here is the increases to warning:
  «Discovery iSCSI via SendTargets failed with error 0xefff0012 for target portal code * 192.168.130.1 0003260 Root\UNKNOWN\0000_0.»

  Please help and advice.

  Concerning

  Hello

  Because the problem is with windows server 2008, I suggest you post this question in the Windows Server forum.

  http://social.technet.Microsoft.com/forums/en-us/winservergen/threads

• 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