ISCSI initiator for OS X ?

as topic states ... i'm about to replace my direct SCSI storage systems over iSCSI & would like to direct connect to my G5 - not having to share through my win/linux servers first .
thanks,
marco

I would also like to add my need for an iSCSI initiator for OSX. Vista has one built in, Leopard should get one too. Especially since ATTO software wants way too much money for something that should be part of the OS to begin with and is free for all other platforms besides OSX.

Similar Messages

  • Is there any iSCSI Initiator for Lion OS?

    Hi everyone. I had being using a QNAP nass for a while now. I had frew iSCSI disk for all my files. The software I used was
    globalSAN iSCSI Initiator for OS X. After installing the new Apple Lion OS my iSCSI desapear. The initiator does not work any more. I read other post and it seams that the sotware is not compatible anymore.
    Does anyone knows about any iSCSI initiator solution for Lion?
    Thanks.

    Just to you guys know, I have been in contact with Studio Network Solutions, the company behind globalSAN iSCSI initiator, and they have sent the following, rather encouraging, email back:
    Hello James,
    We are working on an update for our globalSAN iSCSI Initiator.
    Please subscribe to this forum in order to receive the latest product announcements:
    http://www.snsforums.com/index.php?showforum=3&s=b8b0b8197ebc992f2a03d92fa3b107a 2
    Thank you
    Hopefully this means that a new version, with Lion support, will be with us sooon. Just thought I'd let you know.
    Cheers,
    James

  • ISCSI Initiator for Mac OS 10.8

    Hello everyone! I need an iSCSI Initiator for Mac OS 10.8. Are there any suggestions? I've tried globalSAN, but it seems to be too expensive. Can you advise something?

    unfortunately, there is no free iSCSI Initiator. a nice competitor of globalSAN is DAEMON Tools Lite for Mac (http://www.daemon-tools.cc/products/dtMacLite). it is a software for mounting images, but it has an additional iSCSI Initiator feature that costs €50 (€56.90 together). you can try it for free to get to know whether it is good enough for you.€6.90€6.90

  • ISCSI initiator for target with size 16TBytes

    I have an iscsi target on my linux with 16TB and I can connect to the linux iscsi initiator and format with ext4. On my windows I can only open and format a iscsi disk of 8TB. When I connect to a iscsi target with 16TB the target throws a message of READ_CAPACITY_16.
    At this site http://utcc.utoronto.ca/~cks/space/blog/tech/SCSIBlocksizesDiscovery I realize this is a bug of microsoft iscsi initiator.
    Is that really a bug? Is there a hot fix to this bug of iscsi initiator?
    Thanks!  Felipe

    Did you end up purchasing the ATTO Xtend iSCSI initiator? I'm in a similar bind right now and was wondering what you ended up using for an iSCSI initiator.
    thanks!

  • ISCSI initiator not connecting after upgradation

    HI,   
    iSCSI initiator not connecting after upgradation from windows 2003 STD to windows 2008 STD R2 server, upgradation was successfully completed, except Microsoft iSCSI initiator connectivity, the initiaor interface show it as 'reconnecting'....!!!!!
    Kindly guide on this.
    Thanks in Advance

    HI Shaon Shan,
    Thanks for the info.
    While searching for the file names start with iscsi in c:\windows\system32 folder the file version is 5.2.3790.3825 in working windows 2003  server.
    Recently I've downloaded (Not yet installed) iSCSI initiator for Windows 2008 from Microsoft website in that iSCSI initiator file version shown as 6.3.4.1, instead of using inbuilt Microsoft iSCSI initiator in W2K8, shall I try installing the downloaded
    version,
    because when I checked in Windows 2008 (Upgraded version) the iSCSI file version remains the same as 5.2.3790.3825 which was found in windows 2003.
    Post to our previous discussion
    While I'm trying to install the new iSCSI initiator for Windows 2008 downloaded from Microsoft website, it shows some error "Setupcould not find the update.inf file needed to update your system" then I've updated my server, but no luck still showing the
    same....!!!!

  • Iscsi initiator  64bit support

    Hi all,
    Anyone knows if exist an iscsi initiator that support Snow Leopard 64 bit Kernel?
    I am using GlobalSAN but run only in 32bit mode.
    Thx in adv
    Kerberus

    HI Shaon Shan,
    Thanks for the info.
    While searching for the file names start with iscsi in c:\windows\system32 folder the file version is 5.2.3790.3825 in working windows 2003  server.
    Recently I've downloaded (Not yet installed) iSCSI initiator for Windows 2008 from Microsoft website in that iSCSI initiator file version shown as 6.3.4.1, instead of using inbuilt Microsoft iSCSI initiator in W2K8, shall I try installing the downloaded
    version,
    because when I checked in Windows 2008 (Upgraded version) the iSCSI file version remains the same as 5.2.3790.3825 which was found in windows 2003.
    Post to our previous discussion
    While I'm trying to install the new iSCSI initiator for Windows 2008 downloaded from Microsoft website, it shows some error "Setupcould not find the update.inf file needed to update your system" then I've updated my server, but no luck still showing the
    same....!!!!

  • (Target failed to respond in time for a logout request) - - - Two Node's Iscsi initiator is not able to connect simultaneoulsy

    Environment
    OS = Windows 2003R2
    Iscsi initiator = 2.0.8
    Microsoft Iscsi Target = 3.3
    Error in event viewer = Target failed to respond in time for a logout request.
    Source iScsiPrt, Event ID 44
    Problem
    I have two systems with Win2003 R2 installed with Iscsi initiator 2.0.8. One Iscsi initiator is connected with the target but when I connect the second system, the system is not able to connect and giving me login error mentioned above. I disconnect the
    connected system(The system which is connected with windows target) and connect the system which is failing to connect with the windows target, this time the failing system able to connect with windows target.
    My workaround
    The system which is connected with the windows target, I restarted it. While restarting the system, I connect the other system which then connected successfully. Now this time when both systems are up and running both system's iscsi initiator is connected
    with Windows target.
    Any comment will be appreciated. Thanks. Zahid Haseeb.

    Hi Zahid,
    Have you tried the suggestion above?
    Please feel free to let us know if the issue persists.
    Best Regards,
    Amy Wang

  • ISCSI Initiator favourites revert to using the IPv6 or the apipa IP address from other NICs instead of the source IP address that I specified

    Windows 2008 R2
    ISCSI Initiator favourites revert to using the IPv6 or the apipa IP address from other NICs instead of the source IP address that I specified. 
    When I manually connect to multiple targets and specify the correct ISCSI source IP address, I check the favourites and everything looks okay. But when the server is rebooted I check the favourites again and the source IP is now referencing the IPv6 and
    sometimes the apipa address. 
    I have unbound IPv6 from the ISCSI NICS but this has made no difference.
    Can anyone explain why this is happening?
    Although the server still reconnects to the storage oaky, I’m concerned that if a path goes down that is might try to use the wrong interface to re-establish a connection.
    Thanks.  

    Hi,
    IPV6 is supported with MS iSCSI. Do you have Multiple Connections per Session (MCS) configured? Is your storage configured to use both IPv4 and IPv6?
    If yes, please see if http://support.microsoft.com/kb/2014131 helps.
    Hope this helps.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Missing dependency in Solaris 10 Update8 iscsi initiator / zones not booted

    In previous Solaris 10 Releases, the iscsi_initiator smf service had the following
    dependeny:
    # svcs -D iscsi_initiator
    STATE STIME FMRI
    online Jan_11 svc:/system/metainit:default
    Because this one is missing with Update 8, the service is even started after
    the zones services.
    online 14:45:50 svc:/system/zones:default
    online 14:46:01 svc:/network/iscsi/initiator:default
    Result:
    - No filesystems on iSCSI disks mounted, no Zone on iSCSI running ... after system boot.
    Any ideas?

    Quick thought...
    What happens if you mark all you zones to not boot as a default setting so system boot you won't have this race condition. Then have an rc3highnumber script that probes the services and makes sure all drivers and filesystems are available. Once available, boot the zones, and reset the autoboot option if need be. But make sure the rc3script has the autoboot function disabled again on the way down. This should hold the problem together until Sun/Oracle fixes this issue.
    Nasty hack, but that's software for you.
    Thoughts?

  • ISCSI Initiator - Cannot Change Drive Letters

    Good afternoon-
    I added two iSCSI LUNs to one of my servers using the Microsoft iSCSI Initiator on a Windows Server 2008 R2 server. Everything seems to be working fine, except for the fact that the drive letters are reversed - Volume 1 is my F: drive and Volume 2 is E:.
    Because I need to use one script across multiple servers, I need to change these drive letters. When I right click them in Server Manager, the Change drive letter option is greyed out. Is there a different way to do this?
    Thank you!

    Please start by that:
    http://forums.cnet.com/7723-6142_102-139635/change-drive-letter-grayed-out-in-disk-management/
    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    Thanks Mr. X! I was able to fix this with DISKPART. Here are the instructions taken from your link:
    1. Open Command Prompt.
    2.Type:
    diskpart
    3.At the DISKPART prompt, type:
    list volume
    Make note of the number of the simple volume whose drive letter you want to assign, change, or remove.
    4. At the DISKPART prompt, type:
    select volume n
    Select the volume, where n is the volume's number, whose drive letter you want to assign, change, or remove.
    5.At the DISKPART prompt, type one of the following:
    assign letter=L
    Where L is the drive letter you want to assign or change.
    remove letter=L
    Where L is the drive letter you want to remove.

  • ISCSI Initiator Session Logout

    On GREPI02 (W2K3 SP2 x86, iSCSI Initiator 2.08) I can't logout the iSCSI Initiator session on the "Targets" tab and then "Details" button as I get the following error:
    The session cannot be logged out since a device on that session is currently being used.
    When I attempt this session logout I also get the following System event entries:
    Event Type:    Information
    Event Source:    MSiSCSI
    Event Category:    None
    Event ID:    116
    Date:        5/8/2010
    Time:        9:34:56 AM
    User:        N/A
    Computer:    GREPI02
    Description:
    Removal of device MPIO\DISK&VEN_IET&PROD_VIRTUAL-DISK&REV_0___\1&7F6AC24&1&343934353534303030303030303030313030303334423332303130_________0 on iSCSI session ffffffff8a0762ec-400001370000001a was vetoed by STORAGE\Volume\1&30a96598&0&Signature2E8F7689Offset7E00Length9FFABCC00.
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 06 00 00 00               ....   
    Event Type:    Information
    Event Source:    PlugPlayManager
    Event Category:    None
    Event ID:    271
    Date:        5/8/2010
    Time:        9:34:56 AM
    User:        N/A
    Computer:    GREPI02
    Description:
    The Plug and Play operation cannot be completed because a device driver is preventing the device from stopping. The name of the device driver is listed as the vetoing service name below.
     Vetoed device: MPIO\DISK&VEN_IET&PROD_VIRTUAL-DISK&REV_0___\1&7F6AC24&1&343934353534303030303030303030313030303334423332303130_________0
     Vetoing device: STORAGE\Volume\1&30a96598&0&Signature2E8F7689Offset7E00Length9FFABCC00
     Vetoing service name: FileSystem\Ntfs
     Veto type 6: PNP_VetoDevice
    When Windows attempts to install, upgrade, remove, or reconfigure a device, it queries the driver responsible for that device to confirm that the operation can be performed. If any of these drivers denies permission (query-removal veto), then the computer must
    be restarted in order to complete the operation.
    User Action
    Restart your computer.
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    I can do this same logout from another W2K3 SP2 virtual machine and it works fine so appears to be something specific to this GREPI02 node.Joe

    Hi,
    From the Event log, we can find " FileSystem\Ntfs" is trying to prevent your logout. To find out which file was opened, please try this tool:
    Handle
    http://technet.microsoft.com/en-us/sysinternals/bb896655.aspx
    Run "handle.exe path-of-iscsi-drive >>handle.txt" and post the result here.
    Thanks.
    This posting is provided "AS IS" with no warranties, and confers no rights.

  • NSS 324 iSCSI ready status, cannot connect using MS iSCSI Initiator

    I have an NSS 324 (firmware: 1.0.4) which has been running a Microsoft iSCSI target without any problems for months, until the last 7 days.  I'm now to the point where I cannot access the iSCSI target at all when I try and connect using the iSCSI Initiator, the Quick Connect window comes up with "Target Error" in the bottom of the window.
    Attached are screencaps of the three (3) tabs from the 'Disk Management, iSCSI' section on the NSS 324 management portal.
    iSCSI, Portal Management:
    iSCSI, Target Management:
    iSCSI, Advanced ACL:
    I've also attached screencaps of the six (6) tabs from the iSCSI Initiator Object.
    1.
    1a.
    2.
    3.
    4.
    5.
    6.
    Thank you for any help you may be able to offer.  I have a ton of miscellaneous files on this iSCSI target and I'd hate to try and recreate all of it again.

    Thank you very much for the reply. 
    The IP address of the NSS324 is still 192.168.0.133
    clindoan wrote:Hi John,     Is it possible that the NSS324 may have the new IP address ? The iSCSI initiator failed to communicate to 192.168.0.133 with target error. I would check following:- NSS326 IP address on each LAN port- If NSS is run single LAN port, make sure the default gateway set to that LAN port- If the RAID volume should not be full for iSCSI target to be functional While waiting for resolve the root cause of this issue, you can use the WinSCP to get data (google and download the open source version). With WinSCP, you can see all your data just like it is on the Windows PC. 1, Install WinSCP2. Login with "admin" account and password (The local account with username= admin) 3. Path to iSCSI image is /root/share/external/sdwa1/  (all you folders and files are resided in this path)4. Backup all data to your local drives.Regards,-Clint
    When I launch WinSCP is the following connection information correct, or should I be using a different username, port number, etc. 
    Again, thank you very much for your help!

  • Does iscsi initiator supported on SUN

    I have a Sun Blade 2500 with SUN 5.9 OS installed.
    I have configured ISCSI SAN and one of my Red Hat OS can accessed/mount the ISCSI SAN disk
    Now i want to access/mount another ISCSI SAN disk on SUN solaris. Is that possible ?
    Thanks

    Hi.
    iscsi initiator was introduced at Solaris 10.
    So you can't connect iscsi device to Blade2500 at Solaris 9.
    I am not sure about third party software for iscsi initiator. ( Never listen but and not never find )
    Regards.

  • ISCSI connections for guests: how to set up?

    A couple of questions:
    1. If we wanted to set up iSCSI connections for guests such as SQL servers, what is the best way to handle this? For example, if we had four 10-Gb NICs and wanted to use as few of them as possible, is it common to turn two of the NICs into Virtual Switches
    accessible by the OS, then use these to connect both the host and the SQL guests? Or would the best option be to use two 10-Gb NICs for the Hyper-V Host's iSCSI connections only, and use the other two 10-Gb NICs as virtual switches which are dedicated
    to the SQL server iSCSI connections?
    2. I know MPIO should be used for storage connections instead of teaming; if two NICs are teamed as a virtual switch, however, does this change anything? For example, if a virtual switch is created from a NIC team of two 10-Gb NICs, is it acceptable to create
    an iSCSI connection on a network adapter created on that virtual switch?

    " If we wanted to set up iSCSI connections for guests such as SQL servers, what is the best way to handle this?"
    Don't.   Use VHDX files instead.  A common reason for using iSCSI for SQL was to allow for shared storage in a SQL cluster.  2012 R2 introduces the capability to use shared vhdx files.  It is much easier to set up and will likely
    give you as good, or better performance, that iSCSI.
    But, if you insist on setting it up, set it up the same as you would on the host.  Two NICs on different subnets configured with MPIO. (Unless using Dell's software which forces a non-standard configuration of both NICs on the same subnet).  Teamed
    NICs are not supported.  For a purely best practice configuration, yes, it makes sense to have separate NICs for host and guest, but it is not an absolute requirement.
    .:|:.:|:. tim

  • When i do initializing for opening balance(2lis_03_bx) i'm getting more add

    when i do initializing for opening balance(2lis_03_bx) i'm getting more added records than transfered records.

    Hi,
    It happens. It does not create any problem.
    But Right now, I do not have answer to the question why system does like this.
    Lets hear what other says.
    With rgds,
    Anil Kumar Sharma .P

Maybe you are looking for