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

Tags: Windows

Similar Questions

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

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

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

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

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

  • 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

  • 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

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

  • ERROR: The target system must be running a 32 bit OS. When you try to open files

    Original title: Openfiles.exe

    Hello

    I am trying to identify the files opened using the command WIndows Openfiles.exe. But I get an error message "ERROR: the target system must be running a 32 bit OS.»

    I would like to understand why this error and how to get out of this.

    I understand that because of the 64-bit computer, even if it's a 64-bit machine as it should work.

    Kind regards

    Francis Amalanathan Duraisamy

    Hey Francois,.

    The question you posted would be better suited in the TechNet Forums. I would recommend posting your query in the TechNet Forums.

    http://social.technet.Microsoft.com/forums/Windows/en-us/home

  • 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
    @dellock6
    vExpert 2011
  • Local drive of virtual machine connection - iSCSI Initiator or RDM?

    Hello

    It is early in the morning here, maybe I'm not awake yet, but what is the difference between a connection a cru LUN for a machine virtual Microsoft Windows using a RDM or by installing Microsoft iSCSI Initiator in the virtual machine and connect to the logic unit number in this way? Can you Flash the drive using the road to virtual initiator iSCSI or MDM using only in compatibility mode - that is the only difference, or not at all? How about using MSCS - route decision LUN that will affect?

    Thank you

    Steve

    Hello Steve,.

    snapshots are function of the hypervisor, disks and RDM only virtual to virtual, which are presented to the virtual machine by the hypervisor can be instantaneous. With the help of the initiator iSCSI in the OS itself invited completely bypasses the hypervisor, so you can run snapshots on the side of storage for these LUNs. As far as I know, MSCS comments iSCSI is supported by MS, I don't know if this is also true for a virtual machine with iSCSI comments however.

    André

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

  • 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

Maybe you are looking for