NSS as an ISCSI target

I shows that the boxes to NSS support used like a Bay of ISCSI storage for servers.  Is this a feature without notice, or are there plans to support ISCSI with these boxes?

Advertisement

The current NSS product on the market doesn't support ISCSI storage for servers.  However, the disk/volume virtualization is supported by NSS. The ISCSI function will be available in the next genreation of Cisco SMB NAS.

Tags: Cisco Support

Similar Questions

  • iSCSI target

    can we use USB HDD for the iscsi target?

    Hello Manu,

    1. which Windows operating system you are using on the computer?

    2. are you connected to a domain?

    Please provide more information to help you best.

    Suggestions for a question on the help forums

    http://support.Microsoft.com/kb/555375

  • 'Incorrect function' during the initialization of an iSCSI target

    I have problems when you try to create a partition of 3.7 TB on Windows Server 2008 R2.

    I get the following error message when I try to initialize an iscsi target:

    What I am doing wrong.  The target is not part of a cluster.

    What I am doing wrong? I tried initilizating the disk with MBR and GPT time partitions and all do the same thing.

    Have you installed the software on the server (at least the host software) and establish connections iSCSI on two raid controllers? Looks like that may connect you to a controller, but the virtual disk is owned by the other controller.

  • How to change the name of a volume iSCSI target?

    How the name of a volume iSCSI target can be changed?  I created a volume with a typo in a letter.   The volume production data on it now so I can not just it delete and recreate the problem.   It's not a big deal, but it doesn't look good either.

    It's on a PS6100.   When I go into the properties of the Volume in the advance tab I can see the iSCSI name, but cannot change it.  All I change is the public alias.  But it does no good that the name appears in the vCenter with the misspelled name.

    So how can I change the iSCSI name?

    Or am I stuck creating a new volume and telling them to migrate their data for spelling can be fixed?

    See you soon

    Part of the iSCSI specification is that target names must be unique.  Therefore, once created, you cannot change the name of the volume.

    Kind regards

  • Could not see the iSCSI target in the adapters iSCSI software under Configuration details page

    Detailed description:

    After you add the IP address of the iSCSI target in the target iSCSI dynamic discovery Tab names can be seen under static discovery. But, iSCSI target is not considered as adapters iSCSI software tab Configuration details page.

    This iSCSi target is already mounted as a data store VMFS5 with some VMS on an another ESX which is part of the different ESX cluster in the same center of work data.

    thinking the im network configuration

    You vm kernel ports configured correctly?

    you use VLAN? If so see if your config of vlan is correct

  • VMware as an iSCSI target

    Hello

    This might be a newbie question, but I looked in the documentation and online and I could not find a definitive answer.

    I want to configure my VMware machine as an iSCSI target, so that I can use additional storage to other machines in VMware.

    The hard drives are connected via SCSI on the local machine and not on a dedicated storage machine.

    Is this possible?

    Thanks for any response,

    Dorian

    Welcome to the community - Yes you can load a pack opensource like FreeNas and present as a target iSCSI in a VM - but I don't then point other virtual machines that are running on the same for your storage space because if the host fails your storage space will be would not available-

    I also move this issue a more appropriate forum

  • Need urgent help: loss of storage after rename of iSCSI target

    Hello guys,.

    I need help, I had the problem with one of my iSCSI targets with all virtual machines on it, this iSCSI target on the storage iomega NAS device, is suddenly the storage is no longer available, I tried to rename the 'VmwareStorage' to 'VmwareStorage1' iSCSI target, but his is more appropriate (his was visible on a vsphere servers) but now visible sound like a DOS partition, please help to recover to vsphere without losing any data and the virtual machines inside. Note that I use Vsphere 5.5. see attached photo:

    the selected one is 16-bit DOS > = 32 M, its must be VMFS, as all other stores, I don't want to not loose my vms, the company stops and I'm fired

    vmwarepartition.jpg

    I fixed it... I followed this vmware kb

    http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=2046610

    Thank you vmware, linux thanks<>

  • Best practices the iSCSI target LUN

    I connect to my ESX laboratory to a QNAP iSCSI target and wonder what best practices to create LUNS on the target. I have two servers each connection to its own target. Do I create a LUN for each virtual machine, I intend to create in the laboratory, or is it better to create a LUN of the largest and have multiple VMs per LUN? Place several virtual machines on a LUN has concequenses HA or FA?

    Concerning

    It is always a compromise...

    ISCSI reservations are per LUN.    If you get many guests on the same logical unit number, it becomes a problem and Yes we saw it.

    Slim sure to layout.   This way you can make your smaller LUN and still get several s VM we each their.

  • Static configuration of iSCSI targets

    I was playing with New-IScsiHbaTarget, but has problems.  Each of my iSCSI Target names has the same IP address for the iSCSI server, and he didn't like that.  I tried something like:

    New-HBA target HBA - vmhba33-address 10.0.0.10 - static Type - nomiscsi iqn.2003 - 10.com.lefthandnetworks:blah:blah - 001

    and that seems to work, but when I tried:

    New-HBA target HBA - vmhba33-address 10.0.0.10 - static Type - nomiscsi iqn.2003 - 10.com.lefthandnetworks:blah:blah - 002

    He would say that "the specified target '10.0.0.10:3260' already exists... but I can't add these volumes manually using the client vSphere...

    We have a bunch of iSCSI volumes, and we are forced to use static targets for each.  For each vmhba on each host (vmhba33, vmhba35), without a script, we have to manually add each iSCSI target name.  So for 5 guests with 2 adapters for iscsi and 10 Mon, it's 100 steps.  Or someone at - it a script that can add several static targets?-preferably something that can extend over several hosts.

    Thank you very much!

    You're right, this looks like a bug.

    Until the problem is resolved, you can use the AddInternetScsiStaticTargets method directly.

    Something like that

    $iScsiHba = "vmhba33"
    $esx = Get-VMHost MyEsx
    $hStorSys = Get-View $esx.ExtensionData.ConfigManager.StorageSystem
    
    $tgt1 = New-Object VMware.Vim.HostInternetScsiHbaStaticTarget $tgt1.address = "10.0.0.10" $tgt1.iScsiName = "iqn.2003-10.com.test.iscsiA"
    $tgt2 = New-Object VMware.Vim.HostInternetScsiHbaStaticTarget $tgt2.address = "10.0.0.10" $tgt2.iScsiName = "iqn.2003-10.com.test.iscsiB"
    $targets = @()
    $targets += $tgt1$targets += $tgt2
    $hStorSys.AddInternetScsiStaticTargets($iScsiHba,$targets)
    
  • 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é

  • ISCSI Target VM address RDM?

    I have 300 GB local disks on some of my hosts connected to our SAN.  I would like to take advantage of this local space for models and ISO files.  I intend to install the iSCSI Target Framework (tgt).  My question is...

    If this CentOS VM that turns our iSCSI Target just plug the local disks on VMFS or should I try to present the local disk as a RDM (Raw Device Mapping).

    Since the machine will use local disks, vMotion and anything that is out of the question anyway, so I think this could be a good situation for the use of RDM.

    Hello.

    If this CentOS VM that turns our iSCSI Target just plug the local disks on VMFS or should I try to present the local disk as a RDM (Raw Device Mapping).

    I would use VMFS for this. You will have more flexibility with VMFS and RDM the local approach seems to add unnecessary complexity.

    Good luck!

  • Removed VMFS3 iSCSI target volume - I'm screwed?

    Hello. I "tried" to move virtual machines between servers and the San. On a single server, ESXi 3.5, I 'got' a VMFS volume on a target iSCSI on a basic SAN device.

    The volume "was" listed in the configuration of the server/storage tab. I removed thinking it would be just to delete the reference to the volume from the point of view of the host, but he seems to have deleted the iSCSI target volume.

    Is this correct - is my missing volume? If I'm screwed? Is there anyway to recover the volume?

    Any help or advice would be really appreciated. Thanks in advance.

    We must thank Edward Haletky, not me

    In the VMware communities, his nickname is Texiwill.

    André

  • Multiple ISCSI targets and connection failed

    last week I was preparing my s/w iscsi initiator to connect to multiple iscsi targets.  I ended up not doing last week, and I thought that I removed the targets of the GUI.  looking now @ the GUI, I only show my main production target, but if I look in my Journal vmkernel, his constantly trying to connect to these targets, I had the plan on connecting the box to.  Anyone know of a way for me to look @ the console and see where they can still be defined, of cause, they are not displayed in the GUI.

    See part 3 of this post "The case of stale iSCSI LUN.

    http://apps.sourceforge.NET/MediaWiki/iscsitarget/index.php?title=The_case_of_stale_iSCSI_LUNs

  • Static iSCSI targets removal script with PowerShell

    Hi all

    Is it possible to use PowerShell for the removal of static iSCSI Targets of script? If so, how...

    Thank you!

    If I understand you correctly, you want a report of current static iSCSI on your ESX Server targets.

    This should do the trick

    $esxName = 
    
    $report = @()
    $hostStorSys = Get-View -Id (Get-VMHost $esxName | Get-View).ConfigManager.StorageSystem
    foreach($hba in $hostStorSys.StorageDeviceInfo.HostBusAdapter){
         if($hba.gettype().name -eq "HostInternetScsiHba"){
              if($hba.ConfiguredStaticTarget -ne $null){
                   foreach($target in $hba.ConfiguredStaticTarget){
                        $row = "" | Select HBAName, hostname, device
                        $row.HBAName = $hba.Device
                        $row.hostname = $target.address
                        $row.device = $target.iScsiName
                        $row.port = $target.port
                        $report += $row
                   }
              }
         }
    }
    $report
    
  • Update ISCSI 4 - Microsoft ISCSI Target 3.0

    # vmkiscsi-tool-l-T vmhba32

    -


    NAME: iqn.1991 - 05.com.microsoft:nas3 - esxvmfs-target

    ALIAS                             :

    INDICATORS OF DISCOVERY METHOD: 0

    SEND THE DISCOVERY OF DEFINABLE TARGET: 0

    SEND THE DISCOVERY OF ACTIVE TARGETS: 0

    0 Portal: 172.17.0.136:3260

    -


    -


    NAME: iqn.1991 - 05.com.microsoft:nas3 - esxvmfs-target

    ALIAS                             :

    INDICATORS OF DISCOVERY METHOD: 0

    SEND THE DISCOVERY OF DEFINABLE TARGET: 0

    SEND THE DISCOVERY OF ACTIVE TARGETS: 0

    0 Portal: 172.17.0.136:3260

    -


    # ls.. / VMFS/Devices/Disks

    vmhba0:0:0:0 vmhba0:0:0:2 vmhba0:0:0:4 vmhba0:0:0:6 vmhba0:0:0:8

    vmhba0:0:0:1 vmhba0:0:0:3 vmhba0:0:0:5 vmhba0:0:0:7

    #

    I've got netstat the NAS and its there on port 3260.

    I have 2 network cards on the Server NAS.135 et.136

    I have an another esx with 3.5 123630 and I'm able to see it without problem.

    # cd... / VMFS/Devices/Disks

    # ls

    vmhba0:0:0:0 vmhba0:0:0:8

    vmhba0:0:0:1 vmhba0:0:0:9

    vmhba0:0:0:10 vmhba0:1:0:0

    vmhba0:0:0:11 vmhba0:1:0:1

    vmhba0:0:0:2 vmhba32:0:0:0

    vmhba0:0:0:3 vmhba32:0:0:1

    vmhba0:0:0:4 vmhba32:1:0:0

    vmhba0:0:0:5 vmhba32:1:0:1

    vmhba0:0:0:6 vml.020000000060003ff64c0a3403a0609f7a8112e89d566972747561

    vmhba0:0:0:7 vml.020000000060003ff64c0a3403a0609f7a8112e89d566972747561:1

    #

    I stop my esx 3.5 123630 box last night and tried the U4 area connect, but he wouldn't.  No matter how hard I tried.

    Any help would be great.

    From my experience, you will have problems (esx targets sees do not at all) if these 2 conditions are met simultaneously:

    • -MS < 3.1 Iscsi target

    • -ESX > 3.5u2 (not sure of 3.5u3)

    In other words, you need to upgrade your Target Iscsi MS at least 3.1 if you use the latest ESX updates.

    By example, if you use HP Storage blades SB600c (like me) update of your system management of storage AiO about 1.1.19 or later version.

Maybe you are looking for