The StorageC does not work properly, but this does not prevent you for using the 660f. All you have to do is install the wwnmgr utility on a windows 2000 server, and then online the HDs for all x64 machines you have. Then you are done.

PS. It took me a month to figure it out and work around this problem.

 

I am using the qla2342

 

This worked exactly like you said..

 

But i have a question. Where is this LUN mapping stored. On the 660F, the 51F switch or something with the QLA san/surfer HBA?

 

the reason why i ask is.. what happen when a new server is added to the SAN does it try to connect to the LUN's? Or by doing this does this prevent this from happening?

 

i also got the WWname manager working on a 2003 server.

 

Thanks for the info on this.

 

Leroy L

How did you get the wwname to work on the 2003 x64 server? I was not able to do so due to some java issues.

 

The LUN Mapping is stored inside the 660f controllers, and then you can control access to the wwns from the switch (almost every small business has not configuration on the fiber switch - all can see all). So far the newly created wwns are visible on the fiber. Then you do LUN masking on the qla controller with the san surfer.

 

Notice that lun mapping and lunmasking are not the same. As far as I can tell, lun mapping is not used anymore and it was something specific to the 660f.