ISCSI support

Hi,
has anyone experience in connecting Promise vTrack raid arrays to Solaris using iSCSI?
Solaris sees the targets but does not make conection, no matter how hard we try.
MS Initiator on the other hand works instantly, as well as linux one.
How to discover problem, find a compatibility solution?
In the messages there is no problem mentioned, just no disk - LUNs - attached.

Try cross-post to another mailing list:
http://www.opensolaris.org/jive/forum.jspa?forumID=94
http://www.opensolaris.org/os/community/storage/
M.C>

Similar Messages

Native iSCSI support in OS X

Is there any chance Apple will add native iSCSI support in OS X?

You will not get any answers from Apple about future products or enhancements. Don't waste your breath asking them. You can send them feedback for an enhancement request using the Apple Feedback site. But you won't get any reply from them.
If you wish to discuss rumors then try one of the many Mac rumor sites like macrumors.com

ISCSI support on Solaris

A recent article on Search Storage asserts that Solaris 10 will support iSCSI. Is this true or just another journalistic fantasy?

I have seen several threads that have suggested that a version of Solaris 10 will support iSCSI. Can you tell me your best estimate of when that "version" of Solaris 10 will become available ?
Also, I have seen several threads that have suggested that support for iSCSI on Solaris 10 is up to the manufactures of the adapters to create device drivers that are compliant with Solaris 10 ( i.e. Cisco ). Can you please comment on what is meant by Solaris 10 will "support" iSCSI, and what part of that "support" is left up to the manufactures of the devices interfacing with Solaris 10 ( i.e. device drivers )

Iscsi support in solaris express 03/05

Hi
To whom it may concern ..
# uname -a
SunOS tinkywinky 5.10.1 snv_07 sun4u sparc SUNW,Sun-Blade-100
# iscsiadm
Usage: iscsiadm -?,-V
Usage: iscsiadm add [-?] <OBJECT> [-?] [<OPERAND>]
Usage: iscsiadm list [-?] <OBJECT> [-?] [<OPERAND>]
Usage: iscsiadm modify [-?] <OBJECT> [-?] [<OPERAND>]
Usage: iscsiadm remove [-?] <OBJECT> [-?] [<OPERAND>]
For more information, please see iscsiadm(1M)
# man iscsiadm
No manual entry for iscsiadm.
# grep iscsiadm /var/sadm/install/contents
/usr/sbin/iscsiadm f none 0555 root sys 92408 42788 1106695271 SUNWiscsiu
There is no man page that I can find ...?
Kevin

You should probably direct SXDE queries to the forums at http://opensolaris.org, more chance of a response from the JDS developers there.
Message was edited by:
calum

ISCSI-to-FC routing in Cisco MDS 9000 Family

Hi,
I'm puzzled about support for iSCSI-to-FC routing in the MDS 9000 family. Earlier hardware such as the 9216i switch and the MPS-14/2 module had a feature to allow an iSCSI Initiator to connect transparently to an FC target. This equipment is now EOL and has been replaced by models such as the 9222i switch and the 18/4 Port Multiservice Module. The datasheets for these replacements strongly imply that they support iSCSI-to-FC routing in a similar way to the earlier products - for example "iSCSI for extension of the SAN to Ethernet attached servers - Extends the benefits of Fibre Channel SAN-based storage to Ethernet attached servers".
I tried to find some hard technical info to confirm this. Chapter 4, "Configuring iSCSI" in "Cisco MDS 9000 Family NX-OS IP Services Configuration Guide Release 5.0(1a)" says that the feature is only available on the IP Storage Module, the 9216i switch, and the MPS-14/2 module, all of which are now EOL. It doesn't mention the replacement models in connection with this functionality, though they are mentioned elsewhere in the book for other features such as FC over IP. I've searched for documentation of the iSCSI support on the new models and the only document which seems relevant is this chapter - but it says it doesn't apply to these models.
Do the replacement models support iSCSI-to-FC routing or not? The datasheets use wording nearly identical to the earlier models in this area, so I assume they do. If they do, how is it configured and where is it documented? I sent feedback on this to the documentation feedback address a while ago, but haven't had a reply.
Many Thanks,
                            jjf

The "Configuring iSCSI" chapter in both 3.3.3 and 4.1.1 documentation similarly talk about IPS and 14/2 modules but make no mention of 18/4, however I've used iSCSI on the 18/4 with both releases. I can only guess the same is true for 5.0 since I have yet to load 5.0 on any switches.
In terms of other documentation I don't think there is any, but all the required information is presented in the "Configuring iSCSI" chapters however it's not the easiest thing to understand from the documentation. Following is the overview I sent to a teammate on how to setup iSCSI.
1. configure Ethernet ports with ip addresses
1a. add a route to the host, iSCSI client, via the gigabit interface 2. enable iscsi on the switch
2a. enable iscsi on the module with the gige port
2b. 'no shut' the iscsi interface corresponding to gige port
      e.g. gige3/4 -> iscsi3/4
2c. no additional configuration of the interfaces is needed, although at some point turning on authentication would be a good idea
3. create iscsi initiator
3a. use the clients ip address as the initiator name, using the node name would be better but I haven't tried it that way so ymmv
      e.g. 'iscsi initiator ip-address xxx.xxx.xxx.xxx'
3b. use a "system assigned" nwwn and set it static
      e.g. 'static pWWN system-assign'
3c. allocate one "system assigned" pwwn and set it static
      e.g. 'static pWWN system-assign 1'
3d. assign vsans, an iscsi initiator can be in more than one vsan
      e.g. 'vsan xxx'
4. create targets
   spcsw1(config)# iscsi virtual-target name iqn.000190300646.fa02cb
   spcsw1(config-iscsi-tgt)# pwwn 50:06:04:8a:d5:f0:79:a1
   spcsw1(config-iscsi-tgt)# initiator ip address xx.xx.xx.xx permit
5. zone the iscsi initiator's pwwn to the target pwwns, use 'sh iscsi initiator configured' to see the pwwn
6. configure the hosts iscsi initiator, usually not much more than specifying the ip address of the gige port on the MDS

Cisco Nexus 5548UP

Hi
I need a switch that supports FC, FCoE and iSCSI traffic. The switch that has been suggested to us is Cisco Nexus 5548UP.
I have the following queries regarding this switch:
1)       At our end, I have AMS 2100 Hitachi Storage which has iSCSI & FC Ports. I also have Qlogic CNA card at the server end which supports both ISCSI & FCOE. For FCoE protocol based traffic, the storage to switch connection will have to be FC and the switch to server connection will be FCoE. Can you please confirm whether, if this will be possible through the proposed Cisco Nexus 5548UP switch?
2)       The specification for the Nexus 5548UP switch claims that it supports 10 Gigabit Ethernet. Can you please confirm if this relates to iSCSI support that the switch provides?
3)       We are going to use -SFP-FC4G-SW & SFP-10G-SR SFP for fiber connectivity. Can you please let us know the what these SFP are used for and whether they assist in FC and FCoE traffic forwarding?
4)       We are also going to use Nexus 5500 Storage License, 8 Ports. Does this indicate that only 8 ports of the switch can be connected to the storage? Among these ports, can we configure 4 ports for FC and 4 ports for iSCSI (keeping in mind that our storage has both FC and iSCSI ports)?
5)       Is there any License required for enable FC, FCoE and iSCSI protocols?
An early resolution of these queries will enable us to make a decision regarding the switch.
Thanks
Bhanudas Mali

The specification for the Nexus 5548UP switch claims that it supports 10 Gigabit Ethernet. Can you please confirm if this relates to iSCSI support that the switch provides?
The "UP" in the Nexus 5548 stands for Universal Port. This means that each port can support FC, FCoE and Ethernet. So, a 5548 has 32 ports of SFP/SFP+. Each port can support and push 10 Gbps at a 1:1 oversubscription rate.
There is an optional 16-port SFP/SFP+ module, N55-M16UP, which will add an additional 16 Universal Ports.
Because they are "universal" they can support 1/10 Gbps FCoE and Ethernet as well as 1, 2, 4 and 8 Gbps FC.

Cluster Validation Errors

Scenario:
Trying to do "cluster across box" with Server 2012 R2 and ESXi 5.5 using
http://pubs.vmware.com/vsphere-55/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-55-setup-mscs.pdf and I am getting some disk errors in the validation logs.
"A failure occurred while attempting to arbitrate for Test Disk 1 on node <hostname>. 0x80070022"
"Node <hostname> holds the SCSI PR on Test Disk 2 but has failed in its attempt to bring the disk online. The requested resource is in use."
The storage is a virtualized SAN serving out iSCSI LUNs to the VMWare hosts. These LUNs are then presented to the VM's as RDM. Both VM’s can see the shared disks just fine and I can even create the cluster. I have rebuilt the VM's I am
trying to cluster, destroyed the disks and started over from scratch yet the errors come back.
I am at a loss. I will be opening up support requests with VMWare and DataCore to assist but we do not have a Premium subscription for Microsoft. Any ideas?

Hi BlitzSonik,
“Node <hostname> holds the SCSI PR on Test Disk 2 but has failed in its attempt to bring the disk online. The requested resource is in use” This error is typically caused
by the MSCS incompatible storage and from the document you presented I found the iSCSI support for latest edition of MSCS is Server 2012, please confirm your design is supported.
The similar thread:
WS2012R2 SCSI-3 Persistent Reservation requirements
https://social.technet.microsoft.com/Forums/Windows/en-US/b78f0b84-4054-47c8-bd1c-878d02b464ae/ws2012r2-scsi3-persistent-reservation-requirements?forum=winserverClustering
The related VMware KB:
Microsoft Cluster Service (MSCS) support on ESXi/ESX (1004617)
http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1004617
I’m glad to be of help to you!
*** This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these
sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use
of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet. ***
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

WAAS 5.3.1 support iSCSI?

Hi, We have 3 units WAE294 and 1 for CM another 2 are located on central site and DR site for our V5000 storage data replication..
Does WAAS 5.3.1 is support iSCSI traffic? need special setting?
Regards,
Adam

Hi Adam,
WAE294 (or actually WAVE294) requires WAAS version 4.4 and later, so 4.0.19 is a nogo.
And to be honest I don't think replication mode would have helped you, basically it's just another way of carving the ressources on the WAE box.
You'll have to investigate, why it disconnects.
Does the traffic gets optimized ?
But it's a lot of traffic to transfer across a 2 Mbps line, unoptimized it would take around 900 hours, with minimal delay to transfer 800GB of data.
Does the replication ever finishes ? - Or is it a constant running task with only changes, so it's not a full transfer.
The WAVE-294 has around 55 MB of disk spaces set aside for DRE cache, so you'll have to look for cache eviction (age of DRE content).
Best Regards
Finn Poulsen

Linux Fencing Support for iSCSI switches...

Do any of the Cisco iSCSI network storage switches support Linux fencing agents? If so, which ones.
Thanks,
-Rich

There is no fencing control (port blocking) capabilities on the MDS9000 iSCSI interfaces. Port blocking control by a fencing agent is not available on the Line Card FC ports.

DPM Storage Pool on Windows Server 2012R2 iSCSI target Storage Spaces - supported?

Hi,
for migration purpose we need more space for one of our DPM 2012R2 Servers.
And we cannot buy more space for our NetAPPs..
So our idea was to use an Windows Server 2012R2 as an iSCSI target and use Storage Spaces.
I remember something that using an iSCSI target on Windows 2008 was not supported.
Is this configuration supported when usinf DPM 2012R2 on Win 2012R2 and the target is Win2012R2 aswell?
Thanks in advance
regards
/bkpfast
My postings are provided "AS IS" with no warranties and confer no rights

Hi,
This talks about
Virtual DPM servers, but the same is true for Physical DPM servers when it comes to using .VHD(x) files for DPM storage pool.
Virtual DPM installations do not support the following:
Windows 2012 Storage Spaces.
Virtual hard drives built on top of storage spaces.
Local or remote hosting of VHDX files on Windows 2012 storage spaces.
Enabling Disk Dedupe on volumes hosting virtual hard drives.
Using synthetic FC to connect to tape drives.
Windows 2012 iSCSI targets (which use virtual hard drives) as a DPM storage pool.
NTFS compression for volumes hosting VHD files used in the DPM storage pool.
Bitlocker on volumes hosting VHD files used for the storage pool.
A native 4K sector size of physical disks for VHDX files in the DPM storage pool.
Virtual hard drives hosted on Windows 2008 servers.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

ISCSI boot support on vic P81e

Hi,
Is it supported to use P81e for iSCSI boot on C200M2?
Last time I know that it's not supported and there was saying that it's on roadmap. I can't seem to find the release notes for it.
If it's already supported, what version of c-series software do I need to use?
thanks

According to the support matrix, it's not supported.
http://www.cisco.com/c/dam/en/us/td/docs/unified_computing/ucs/interoperability/matrix/r_hcl_B_rel2-21.pdf
my 2c
- even the VIC1225 doesn't show any iSCSI Boot support
- the VIC1225 is a prerequisite for single wire management, therefore I doubt, that there will be a lot of new driver development going on for P81e; Cisco PM please clarify !

Iscsi TOE... does it worthwhile to get network card that support it ?

Hi all,
I was wondering if purchasing an ethernet card that support iscsi & TOE will improve performance ?
Does the linux kernel for OVM 2.1.5 support ethernet cards with these features ?
If anyone is using successfuly iscsi ethernet cards with OVM, can you share your experience with us ?
Cheers,
Roye

At least three to five business days before you see a credit.

ISCSI volume lost, have the .img file but no access to data. Help please, WD support worthless!

Basically, I have a iSCSI target which I cannot access after re-installing windows because the CHAP "secret" I thought I knew was wrong. Although I was told there was no way to acess the .img file by WD, I was able to pull the image using an SSH connection to the EX2 from a hidden folder. So now I have that file stored locally. Of course it would just be too easy to be able to mount that file and I understand why that is. However, through research, I am seeing that it may in fact be possible some how. Can anyone please help me with the resources that I have? I have alot of info that I really do not want to lose and I dont have the funds to pay a data recovery company thousands of dollars like WD support suggested. Is the .img file encrypted or is it just a FS that windows wont recognize? Please help and I would really appreciate any info. Thank you.

if the iSCSI target is protected with a username and password. It would not do any good even with a linux tool to open it. Like WD tech support suggest to find a recovery company is all your best bet. If you still have access to your NAS, you should be able to change the iSCSI target to with CHAP enable to NONE. From your Windows try to access your iSCSI target again without a password. bda714 wrote:
After being told multiple times by WD support that there was nothing I could possibly do to access my LUN i have gotten to a point that I believe is close to where I am trying to be. Along the way, there were many times that the support tech's at WD had told me what was said to be rock solid information, was proven to be wrong. . . at this point I feel like I am better off on my own and hopefully with some help from the community. Basically, I have a iSCSI target which I cannot access after re-installing windows because the CHAP I thought I knew was wrong. Although I was told there was no way to acess the .img file by WD, I was able to pull the image using an SSH connection to the EX2. So now I have that file stored locally. Of course it would just be too easy to be able to mount that file and I understand why that is. However, through research, I am seeing that it may in fact be possible some how. Can anyone please help me with the resources that I have? I have alot of info that I really do not want to lose and I dont have the funds to pay a data recovery company thousands of dollars like WD support suggested. Is the .img file encrypted or is it just a FS that windows wont recognize? Please help and I would really appreciate any info. Thank you.

UCS Boot from iSCSI fully supported now?

I'm assuming based on Cisco's documentation that boot from iSCSI on UCS blades is now fully supported (as in TAC will provide support for an problems now)? Correct?
Cisco UCS boot from iSCSI
http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/gui/config/guide/2.0/b_UCSM_GUI_Configuration_Guide_2_0_chapter_011101.html#concept_D7BF302366F24CF5A602B0E0BD18787C
Does that cover all versions of ESXi?
Has anybody noted any caveats or issues relating to UCS boot from iSCSI for ESXi?
Just curious as all previous validated design guides from Cisco have been based on FCoE/SAN boot. Would be nice to know its a fully validated
(Cisco. Netapp, Vmware) "Flexpod" implementation .

Ahh.. Just found the new CVD "VMware vSphere Built On FlexPod With IP-Based Shared Storage"
http://www.cisco.com/en/US/docs/unified_computing/ucs/UCS_CVDs/cisco_ucs_vmware_ethernet_flexpod.html
My other question still stands.. has anybody noted any caveats or problems with utilising boot from iSCSI for ESXI?

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

ISCSI support

Similar Messages

Maybe you are looking for