Print Page - Change iqn number?

Title: Change iqn number?
Post by: rhenson on April 02, 2009, 11:36:58 AM

I'm using a Buffalo TeraStation Pro... Haven't had any problems with this one unit, however over the weekend I added a second Buffalo and one of my servers immediately started picking it up as one of it's discovered disks... it's difficult to explain, but here is a link to what I'm seeing... http://app4.websitetonight.com/projects/1/1/7/9/1179427/_mygallery/Image3.jpg. What I've discovered is that the iqn identifier for both units is the same. Is there a way to change the iqn of one of these? I've checked the web interface and iscsi initiator, but don't see anything that will allow me to change one of them...

thanks
Randy

Title: Re: Change iqn number?
Post by: rhenson on April 02, 2009, 02:36:19 PM

Sorry I didn't mean change the iqn, I need to change the LUN identifier that the buffalo broadcasts to the virtual machine.

Title: Re: Change iqn number?
Post by: Dustrega on April 04, 2009, 02:08:15 PM

Since the LUNs are hardcoded we can't change them without modifying the firmware and doing that would void your warranty. My apologies.

Title: Re: Change iqn number?
Post by: 1parkplace on June 04, 2009, 08:05:24 PM

We NEED this to happen. Why can Buffalo not create a new firmware with a modifiable LUN ID?

This is a MUST for anyone attempting to use this system with VMWare products without conflict.

VMWare does not like LUN ID's to equal 0.

Basically, if the answer is no, it renders this product completely useless to me and I will need to find a way to get my money back.

Title: Re: Change iqn number?
Post by: devnull1369 on July 15, 2009, 04:07:05 PM

Bump.

So Buffalo, I guess you want to lose another customer because your product is worthless without being able to modify the LUN. Who the hell in their right mind would implement iSCSI without the ability to have multiple LUN IDs? Um, you, that's who. So now let's see if you can make this right or I too will figure out how to get my money back.

Oh, and just so you are aware, I don't care about voiding my warranty on something that will not function as it was intended. IF I need to hack it to get it work correctly please don;t hesitate to let me know. I'd love to make this hunk of crap useful..

Thanks.

Title: Re: Change iqn number?
Post by: drmemory on July 15, 2009, 05:24:13 PM

The mods should be getting with you shortly, to check iSCSI initiator settings in your setup. We need to identify the parameters of your entire setup, in order to duplicate the issue.

Title: Re: Change iqn number?
Post by: IKnowStuff on July 15, 2009, 07:09:31 PM

I am sure there is a logical answer to your problems. Lets clearify the question.

You have two TeraStation Pro iSCSIs:

Which firmware version are they running?

What is the hostname of each Unit?

It looks like one unit is setup as 4 independent drives, and the other unit is configured as a type of volume. Is this correct?

You mentioned something about VMware. You are working with VMware, it doesn't really matter which version of VMware, but how are you trying to use VMware in connection with the TeraStations?

You are trying to connect both TeraStations to one server, or different servers?

Which version of Windows are ytou connecting the TeraStations to?

I also noticed that you are using 'Virtual Iron VI-Center'. I do not have a copy of that program, and I am not familiar with it. Do you get a similar error when using the standard Microsoft iSCSI initiator ? Would you be able to post a screen shot of the MS iSCSI client when you try to connect it to both TeraStations?

Best Regards.

Title: Re: Change iqn number?
Post by: Colin137 on July 15, 2009, 07:26:05 PM

I agree with your first sentence completely, IKnowStuff.

I'm confused as to why the LUN designation matters... That is the most specific of all the identifiers. The LUN is 0 for each volume set up on any Terastation. Separate volumes (LUNs) on the Terastation show up as different iSCSI Targets. Each Terastation's volumes are differentiated by the IQN name: it identifies the Targets with the hostname and MAC address of the parent Terastation, along with the name of the volume as set up on the Terastation.

I'm even MORE confused by the four identical hex numbers in the OP's screenshot (something close to 142554646414c4f000000004000000002000000). What does that number signify? Can anyone clue me in?

rhenson, 1parkplace, devnull1369

Please try it with the MS iSCSI Initiator and post screenshots of relevant details, and answer IKnowStuff's excellent questions.

Message Edited by Colin137 on 07-15-2009 07:27 PM

Title: Re: Change iqn number?
Post by: rinthos on July 15, 2009, 11:08:53 PM

@All,

Being able to Mask the iSCSI LUN #'s to the host is indeed a practical requirement.

Take Rhel 4.5 Linux for example. Without different LUN numbers, you'll likely be required to persistantly bind the devices on each target, otherwise you could lose the target numbering on a system-reboot.

If you're making the LUNs available to an ESX server, the Target identifier should be different and should be enough. W/ ESX 3.5u2, and vSphere 4,differenciating between targets (even w/ duplicate LUN #'s) should be adequate....validated that on some of my systems w/o any issues...

Are you running ESX, or VMWare Server on top of another OS?

Buffalo Forums

Products => Storage => Topic started by: rhenson on April 02, 2009, 11:36:58 AM