Adding new iSCSI Volumes

[Robotbeat]

Yeah, this is a huge problem. It has to be fixed. We have to know a firm ETA about this. Put this at the top of your queue, because this puts a huge limit on the type of environments this can be deployed under, but I'm sure you already know that. We all need a fix for this as soon as possible.

We're having this problem with fibre channel.

[Robotbeat]

There has to be a way of fixing this because EMC and folk don't have this problem.

[Robotbeat]

BTW, this is not an issue if you publish all of your logical volumes to the default group in fibre channel. In that case, you would have to do LUN masking on the INITIATOR side instead of on the Open-E TARGET side. If you have QLogic initiator HBAs in Windows, then use the QLconfig utility to select the luns that should be used on each initiator. This is a pain because you have to do this on every initiator machine, but it should work.

Also, you can use the QLDirect driver for fibre channel path failover (like MPIO but no active-active, it's active-passive). This is I think the only way to do fibre channel (path) failover in Windows 2003 or earlier. (Windows 2008 has a generic Fibre channel MPIO driver, I think.)

[dagar]

Maybe this will be fixed in v6. But if so that sure sounds like the M$ way of doing things to keep people buying the next version of the software. And then v6 will have some serious limitations/bugs taht won't be fixed till v7, ...

[AERCIT]

Has this issue been fixed in DSS v6? I've looked through the V6 threads and haven't seen anything pertaining to this.

[To-M]

Yes, we are coming out with a fix for this issues in this months release for V6.

[AERCIT]

Will it only affect those who are not using replication?