NSS 324 iSCSI lun error

I have an iSCSI lun on my NSS 324 device that shows status error while the target it is mapped to shows connected. The log file shows the following error: [iSCSI] Fail to expand LUN. I cannot enable the LUN and it is not discoverable by my VMWare. How can I resolve this without losing my data?

not sure if i understand. are you mapping the iSCSI LUN to the NSS or are you mapping the iSCI LUN to your ESX server?
which device is connecting to the LUN?

Similar Messages

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!

NSS 324 - Management HTTPS Error

Hi Folks,
I've noticed if you enable SSL management, and navigate directly using https://<nss ip> the following error is displayed:
Secure Connection Failed
An error occurred during a connection to ........
SSL received a record that exceeded the maximum permissible length.
(Error code: ssl_error_rx_record_too_long)
however if you navigate via http://<ip> then it is redirected to https.
done using firefox 3.6.6.
Cheers,
Dan

I think the proxy from your browser setting can cause this error. I have experienced that some proxies can't handle secure connections.
You can find the connection setting from Firefox: Tools > Options > Advanced, Network tab : Click on Connection (check to make sure you have the right port for SSL connection. If you do not need to use a proxy to connect to internet then select No Proxy or set to auto detect proxy.
The root cause for this particular issue is a mismatch between the IP address being published for the domain between a client (PC broswer) and a server (NSS) and the IP address in Apache's httpd-ssl.conf file (Example: 127.0.0.2 (server) vs. 127.0.0.1 (client)). When the browsers (any browser) tried to do an https: type SSL connection, they were trying on port 127.0.0.1:443. Apache wasn't listening there and the fetch failed. This error is a common error when a mismatch on port number for SSL connection between client and server (if a broswer is set with a proxy- a default port is set but it can be any port determined by user which can cause this issue).
In your case, when a HTTP is connected and redirected for HTTPS port defined from NSS, your browser is using the port determined by NSS. Then everything is working fine. Your browser will be cached to the working port and it should be working fine. However, you may see this issue again if you are not resolve the port between client and server for SSL connection.
Hope this is helps! Please let me know

Can not attach older iSCSI lun to repository

I am a current Virtual Iron user and have set up OVM to replace my aging system. I have everything set up on some new hardware and up to a point where I want to set up some VMs.
I have an older VM under Virtual Iron I am no longer using, so I thought this would be a good test subject.
I assigned both my OVM servers to the volume in my iSCSI san.
The SAN and volume show correctly within the storage tab.
I have rescanned for physical disks on each server and found the volume.
I can not create a VM just using the physical disk....I wants me to use a repository...
Ok, so I tried to create a repository using the existing volume that contains my server....no go...get this error
(10/16/2012 12:38:54:518 PM)
OVMAPI_B000E Storage plugin command [storage_plugin_createFileSystem] failed for storage server [0004fb0000090000df4ea0c58186307e] failed with [com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: dispatch to server: OVMS1 failed. OVMAPI_4004E Server Failed Command: dispatch https://?uname?:[email protected]:8899/api/2 storage_plugin_createFileSystem oracle.ocfs2.OCFS2.OCFS2Plugin 0004fb00000500003beb40ffab937285 /dev/mapper/36000eb346b4e2d99000000000000012e 0, Status: OSCPlugin.InvalidValueEx:'The backing device /dev/mapper/36000eb346b4e2d99000000000000012e is not allowed to contain partitions'
Tue Oct 16 12:38:54 CDT 2012
Tue Oct 16 12:38:54 CDT 2012] OVMAPI_4010E Attempt to send command: dispatch to server: OVMS1 failed. OVMAPI_4004E Server Failed Command: dispatch https://?uname?:[email protected]:8899/api/2 storage_plugin_createFileSystem oracle.ocfs2.OCFS2.OCFS2Plugin 0004fb00000500003beb40ffab937285 /dev/mapper/36000eb346b4e2d99000000000000012e 0, Status: org.apache.xmlrpc.XmlRpcException: OSCPlugin.InvalidValueEx:'The backing device /dev/mapper/36000eb346b4e2d99000000000000012e is not allowed to contain partitions'
Tue Oct 16 12:38:54 CDT 2012
Tue Oct 16 12:38:54 CDT 2012
Tue Oct 16 12:38:54 CDT 2012
Looks like it will not use the volume because something is on it.
In Virtual Iron, I could use a virtual storage (repository), local disks, or iSCSI luns for my VMs.
So how am I to use my older server within OVM?

Ok. Found that someone else was having similar problems....
Oracle VM Manager 3.1.1: Discovering SAN Servers
My solution was to scrap the whole thing....and start over with the new beta 3.2.1. (build 258) This has given me the ability to see all my SANs now.
Edited by: Looney128 on Nov 13, 2012 8:32 AM

LDOM in iSCSI LUN - iSCSI logging in too early

Hi there,
I am having a very strange problem. I'll describe my setup first.
The hardware hosting the LDOM environment does not have enough local disk space to support the number of required domains so to get around this problem the disks used by the configuration are, in fact, iSCSI LUNS mounted from a Netapp.
This works fine once they are up and running, but I am having problems when the host server is rebooted because the services do not seem to be starting in a sensible order. If you look at the dmesg output at [http://www.joshberry.plus.com/dmesg.txt|http://www.joshberry.plus.com/dmesg.txt] this is the boot up sequence for the server.
You can see the iSCSI failing to log in first, with the associated errors where disks are unavailable:
Apr 30 14:55:21 fhw-dataarchive02 iscsi: [ID 286457 kern.notice] NOTICE: iscsi connection(7) unable to
connect to target iqn.1992-08.com.netapp:sn.101204418:vf.c254e0d0-1836-11dd-a621-00a0980aec76 (errno:128)Lower down in the boot sequence the reason for this becomes obvious:
Apr 30 14:55:26 fhw-dataarchive02 mac: [ID 469746 kern.info] NOTICE: e1000g1 registered
Apr 30 14:55:26 fhw-dataarchive02 e1000g: [ID 766679 kern.info] Intel(R) PRO/1000 Network Connection, Driver Ver. 5.1.8
Apr 30 14:55:26 fhw-dataarchive02 e1000g: [ID 801725 kern.info] NOTICE: pciex8086,105e - e1000g[1] : Adapter copper link is down.
Apr 30 14:55:29 fhw-dataarchive02 e1000g: [ID 801725 kern.info] NOTICE: pciex8086,105e - e1000g[1] : Adapter 1000Mbps full duplex copper link is up.Here, as far as I can see, the network is down when the LDOM is initiated and tries to get access to the iSCSI, which is never going to work.
So, firstly, have I got the right end of the stick here?
If I am on the right track my question is: can you change the order that the system initialises everything so that the network will be brought up before the guest domains are initialised.
Thanks
Josh

Don't use CHAP for discovery.
Enable CHAP afterwards.
Andy

Cisco NSS 324

Hi, I have two problems with this cisco NSS 324 device.
1) I have a windows server 2008 domain environment where the NSS 324 is connected to the Active directory, it sees all my users and groups on the AD. I am planning to make users H drives on this NSS 324 so that each user have full rights to 'HIS/HER' folder only. I have followed all the help files from Cisco where they guide how to make folder structure so that each user has own space to work under a folder tree. I am able to make folders via the properties of the AD users like '\\NAS\shomes\g7\%username%' it makes the persons folder. But if I logonto Web File Manager as any other user, it can see all the files and folders of the other user. So basically users can see/change each other files. How to change this behaviour?
2)iSCSII I am able to logonto iSCSII if I do not put any type of authentication, the moment I use CHAP or any other authentication I am unable to connect to the drives, I am able to see the discovered Target via the ISCSII inciator but cannot logon. Any hints?
Help plz

Adnan,
•1) Sound like you’re permission for the folders is not set correctly. First off you can set individual folders as hidden so no others can see the folder. Please make sure you’re on Latest firmware 1.5.0 this gives you greater control over sub folder permissions. Please upgrade in increments if you need to upgrade.
•2) When using CHAP authentication both the target and initiator has to match exactly or you’re not going to get connected. Usually the customer has more than one target with CHAP authentication and they have CHAP set globally and not by individual target authentication. You can use global settings for CHAP- but each target has to be set exactly with same authentication.
For quicker resolution please call into the support center @ 1-866-606-1866 and open a support case –
If you want to continue trouble shooting via support forum – please post
Firmware currently running-
Folder permissions for users’ directory-
Individual folder permissions-
Connection logs of users –
For ISCSI it’s just a matter of getting correct settings in your initiator –
Hope this helps,
Jasbryan

NSS 324 Wordpress upgrade Help...

I have the default Wordpress .pkg running on my NSS 324. It tells me that version 3.1 is available. When I select to update, it downloads the 3.1 zip file, but errors out on the install. Does this install support updating? Is there an easy way to overwrite the install with the contents of the zip?
Thanks.
EDIT: I only have the ability to write over the files of the wordpress install if I use the "Web File Manager" Application. When I ftp in, I cannot overwrite the files. I am FTP'ing on the same network. Why are the directories greyed out in "Share Folders"??

I have exactly the same issue. Limited file access to wordpress sub folders....therefore cant upgrade
Has this been resolved?
Thanks

Rsync to NSS 324

Hi,
I'm currently evaluating a NSS 324 Storage system. I want to replicate data from a central file server to many NSS systems in remote locations. This should be done via rsync and works basically as wanted.
However I have now noticed that by enabling "Allow remote Rsync server to back up data to NAS" no user account/password is checked, so anyone could replicate data to the NSS.
If I disable the setting, I will be prompted for a passwort, but it is not accepted. The command I execute on the server side is "rsync -avz SIT/* [email protected]::SIT" and it ends in "@ERROR: auth failed on module SIT" even when the correct password is used.
Any Ideas appreciated...
Thanks

One way to address this is to use the Virtual Web Host feature.
I've uploaded a simple application note to help guide you through the steps.
An alternative would be to create an html at /Web/ which forwards to /Web/Joomla. Not a great solution, I know.
I'm sure there is a way to change the setting in a linux configuration file, but I don't know which file that is in. Maybe some other linux savy community members could help out with that?

Boot ISCSI LUN from LDOM

Hi,
We are exporting bootable LUNS from a 7110 array to LDOM's on our Blades. The array was rebooted today. Since the reboot we are unable to connect to the hosts booted from the array.
I did not configure this but have the task of fixing it.....
We are running LDOM 1.2,REV=2009.06.25.09.48
So, does the LDOM boot directly from the LUN from the LDOM OBP?
The syntax in this link causes the below failure;
http://wikis.sun.com/display/OpenSolarisInfo/Configuring+iSCSI+Boot+for+SPARC+Systems
Unknown key 'iscsi-target-ip'
Unknown key 'iscsi-target-name'
Unknown key 'iscsi-lun'The ISCSI LUNS are seen by the host.
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 273>
/pci@0/pci@0/pci@2/LSILogic,sas@0/sd@0,0
1. c1t2d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 32 sec 279>
/pci@0/pci@0/pci@2/LSILogic,sas@0/sd@2,0
2. c3t600144F04B73EB660000000000000000d0 <SUN-SOLARIS-1 cyl 32766 alt 2 hd 4 sec 736>
/scsi_vhci/ssd@g600144f04b73eb660000000000000000
3. c3t600144F04B713A260000000000000000d0 <SUN-SOLARIS-1 cyl 32766 alt 2 hd 4 sec 736>
/scsi_vhci/ssd@g600144f04b713a260000000000000000
4. c3t600144F04B9910370000000000000000d0 <SUN-SOLARIS-1 cyl 32766 alt 2 hd 4 sec 1200>
/scsi_vhci/ssd@g600144f04b9910370000000000000000Nothing has changed on the LDOM controller domain.
I'm really stuck so any input would be appreciated.

Im getting the following error as well.. Was there any solution to this please ?
Im not using any LDOM. Just on the h/w platform on T5140
{0} ok boot net Boot device: /pci@500/pci@0/pci@8/network@0 File and args:
Unknown key 'iscsi-target-ip'
Unknown key 'iscsi-target-name'
Manual Configuration: Host IP, boot server and filename must be specified
ERROR: boot-read fail
Can't open boot device
{0} ok
Edited by: 836793 on Feb 15, 2011 12:36 AM

Is there a way to configure NTFS file system on an NSS 324 SmartStorage unit. So far I can setup ext 3 or ext 4 but no option for NTFS

Is there a way to configure NTFS file system on an NSS 324 SmartStorage unit. So far I can setup ext 3 or ext 4 but no option for NTFS. This unit should be joining a Windows Server 2008 R2 network and needs to be shared with all users. This unit will replace a File server running Win 2003 SP2.
Message was edited by: Hermann Koster
Thank you very much for your reply. The idea is to decommission the Windows file server which is running Windows Server 2003 SP2 operating system but is not running as a DC but just a member server. All this server is doing is providing file server services so my idea is to replace it with the NSS 324 box. My only concern is that when my NSS joins the domain all my users would be able to see and access network shares transparently, the same way they saw the former W2003 file server. After I transferred the data from File server I will use the same for NSS that was used for file server as well as same IP address and folders path as before.
Any suggestions or advice?
Once again thank you very much for your reply.
Cheers,

The internal HDDs must be formatted in either EXT3 or EXT4 file system because NSS uses Linux OS. This is mainly because the RAM designed to fit with the customized Linux OS's size.
You can connect to an external HDD via a USB or eSATA port. The external HDD's file system can be NTFS, FAT32, AFT or EXT3/4 to be recognized for read/write. You can connect a 2TB USB/eSATA drive connec to the NSS via USB port to format your HDD for NTFS, AFT, FAT32, or EXT3/4 partition.
You can join the NSS to a Windows domainr so all domain users to access NSS. You cannot replace the NSS for the Windows 2003 SP2 server. They are two different products and do different jobs. Windows server is features sets server while the NSS is the files/data server.
Hope that helps!!

After delete iSCSI LUN vacant space does not become available

px12-400r, one pool on RAID10 (5,42TB).
Pool divided into 4 iSCSI LUN (2TB+2TB+1TB+0,42TB).
After deleteting one of them (on 2TB), this vacant space in tab "System Status" (over Web Interface) shown in the diagram as the free and "Amount of available space" on Status Bar 2TB (on Device Home Page over Web Interface),
but in tab "Disk Management" shows "Allocated/Available" - "5,42TB/0B" , and new volume or iSCSI LUN can not be added ("In any storage pool does not have enough space to add an iSCSI drive"
Storage in AD. Deleting iSCSI LUN over Web Interface under AD user with storage admin rights.
Rebooting storage did not help. What to do? How to return control of this free disk space?

Hello gusev67
To be certain that the iSCSI LUN was actually delete, please try this alternate method to check if the LUN is present and if so, deleted.
Go to Drive Management and click on the "volumes" section of your storage pool
Navigate to the iSCSI LUN that should have been deleted/removed
If it is present there, please click on the iSCSI LUN name to show the iSCSI information overview for the LUN, there click on the "delete" option.
If that does not seem to resolve the issue I recommend contacting LenovoEMC support regarding the problem.
LenovoEMC Contact Information is region specific. Please select the correct link then access the Contact Us at the top right:
US and Canada: https://lenovo-na-en.custhelp.com/
Latin America and Mexico: https://lenovo-la-es.custhelp.com/
EU: https://lenovo-eu-en.custhelp.com/
India/Asia Pacific: https://lenovo-ap-en.custhelp.com/
http://support.lenovoemc.com/

Install OVM server 3.2.1 on iSCSI LUN

Hello friends,
I have a Cisco Blade and would like to boot OVM server from an iSCSI lun. I create a LUN from a SAN and presented the lun to the blade. When the server boots up, it sees the iSCSI lun just fine but when I tried to install OVM server 3.2.1, it did not detect that LUN. I tried to install Oracle Linux 6.3 and it sees the LUN ok. Is there a way to make OVM server to see that LUN.
thanks,
TD

I have done to many oel and ovs install lately such that they are blurring together...
On the OVM 3.2.1 install watch closely for a place to add support for non local storage. I remember seeing a small prompt in some of the installs but it may have been from some of the OEL installs (I have also been doing OEL 4, 5, & 6) & not OVM.
Sorry I can't remember right now. If I get a moment and try to run the install process I will and report back if no one else does.

Using iscsi luns as vdiskserverdevices

Hi
I am new to LDoms and was wondering if anyone has any experience of using iscsi luns (presented by zfs volumes on an X4500) as vdiskserverdevices . In my case the iscsi luns were presented to the service domain (in this case the control domain) and were correctly visible and accessible from it. However when presented as vdisks to the guest domains, for use as the root disk, the guest domains could not access/see the disks. When the guest domain was booted for a jumpstart install one of the first messages was that it couldn't access the vdisks and this was confirmed during the install process when a boot disk couldn't be found. AFAIK solaris can't boot of iscsi luns (without iscsi HBA's) but I figured that hiding the iscsi lun behind the vdiskserver would work -but no such luck. Any advice on whether this is possible would be most welcome.
As an unwanted work-around I created a couple of large files (aprox 420 Gb and 920Gb) and presented these instead as the vdsdevs. This time the smaller 420Gb couldn't be seen at all by the guest domain while the larger file showed up as a SUN 920Gb type disk though while partitioning it, it only showed about 100Gb as the disk size. Any pointers as to what I'm doing wrong here is also most welcome.
My hardware consists of 2* T5220 running Sol10 08/07 with latest recommended patches and firmware and an X4500 which is being used to provide all (root and data) storage for the guest domains.
Thanks
Saurav

Hi there,
I am setting up a platform when the guest domains are installed into iSCSI LUNS and it is working fine.
I am using LUN's expported from a NetApp rather than using ZFS but that shouldn't matter. They appear like this on my test platform:
root@solarisvh # iscsiadm list target -S
Target: iqn.1992-08.com.netapp:sn.********
        Alias: -
        TPGT: 2000
        ISID: 4000002a0000
        Connections: 1
        LUN: 0
             Vendor: NETAPP
             Product: LUN
             OS Device Name: /dev/rdsk/c4t0d0s2And I can add it into a guest domain by running:
ldm add-vdsdev /dev/rdsk/c4t0d0s2 examplevol1@primary-vds0I found that I had to pop in an label the disk (using format) on the first use for it to be picked up but after that it worked fine and I could boot up and install an OS into the LUN.
Josh

Oracle VM 3.1.1: Using iSCSI LUN's as Device-Backed Virtual Machine Disks?

Will Oracle VM Manager 3.1.1 support the use of iSCSI LUN's as device-backed virtual machine disks? i.e., Can iSCSI LUN's be treated like directly-attached storage (DAS) and used as virtual machine disks?
Eric Pretorious
Truckee, CA

user12273962 wrote:
I don't personally use ISCSI. BUT, I don't see why you can't create physical pass through attachments to virtual guests using ISCSI LUNS. It is no different than FC or direct attach storage. Worst case scenerio... you can create a repo on the ISCSI LUN and then create virtual disks.
Oracle VM Getting Started Guide for Release 3.1.1Chapter 7. Create a Storage Repository
A storage repository is where Oracle VM resources may reside... Resources include virtual machines, templates for virtual machine creation, virtual machine assemblies, ISO files (DVD image files), shared virtual disks, and so on. This would have the effect of using file-backed virtual machine disks but at least they'd be centrally-located on shared storage (and, therefore, the virtual machine could run as an HA guest)
budachst wrote:
I have kicked this idea around as well, but I decided do it slightly different, by providing the storage repo via multipathed iSCSI and use iSCSI within my guests if needed for better speed or lower disk latency.
If you want to use iSCSI as the virtual devices for your guests in a clustered server pool, you'd have to grant access to all of your iSCSI targets to any VM server and I was not feeling comfortable with that. I rather grant only the guest directly access to "its" iSCSI target. So I will keep all of my guests system images on the clustered server pool - and additionally also the virtual disks that don't need a high performance and have the really heavy-duty vdisks as separate iSCSI targets.That seems logical, Budy:
<ul>
<li>Use a multipathed iSCSI repository for hosting the virtual machine's disk image, and then;
<li>Utilize iSCSI LUN's for "more performant" parts of the guest's file system (e.g., /var).
</ul>
I'm still puzzled about that image, though. +i.e., the fourth image from the bottom of Chapter 7.7, "Creating a Virtual Machine" ("To add a physical disk:...") where it's clear that the exising "physical" disks are actually iSCSI LUN's that are attached to the OVM server.+
I suppose that I'll have to configure some iSCSI LUN's and try it out to be certain. Just another tool that I don't have +but will need to add to my toolbox+.

Unable to detect iSCSI LUN size change on Solaris 10

I resized (grew) an OpenFiler iSCSI LUN, but I cannot get Solaris 10 to pick up the change. Using the type -> autoconfigure in format and relabeling the disk ought to do the trick but it does not work. Does anybody know how to overcome this?

Hmm, what filesystem do you have on the disk?
.7/M.

NSS 324 iSCSI lun error

Similar Messages

Maybe you are looking for