07-03-2007 03:11 AM
07-19-2007 06:03 AM
08-13-2007 08:43 AM
09-14-2007 05:35 PM
09-17-2007 04:00 AM
09-17-2007 04:24 AM
Douglas Snyder wrote:Hello Roger;That issue is addressed in MP1 for SF5. You can download the MP here: http://www.symantec.com/enterprise/support/downloads.jsp?pid=15107Additional information about the MP is located here: http://www.symantec.com/enterprise/support/documentation.jsp?pid=15107Hope this helps.Doug SnyderSr. Systems EngineerSymantec Corp.
Sturat wrote:
Roger -I used the SourceForge iSCSI Enterprise Target for the target but I had to modify the source code so that the TestUnitReady and the SCSI inquiry would return the correct strings - including the LUNs Vendor Product and Sserial Number. When the ietd daemon loads, it would query the LUNs and load a structure so that the default VID PID and Serial were replaced with the info from the structure loaded. Remember that the target still refers to a list of "devices" so I could preload the SCSI inquiry command and just dump it into the structure when an actual query was made from the initiator - made the memory map of the ietd daemon a little larger but what the heck. This was tested successfully with the vxdmpinq command. Having multiple paths to the target(s) then allows the DMP to work. From memory though and the release notes for *nix this is unsupported.I had a debian kernel (2.6.14) for the target and RHEL4 for the initiators. On the RHEL4 I was running VxVM 4.1 and could create diskgroups etc etc and also run VCS ( Version 5 ) but again this is unsupported.Although the initiators can use multiple paths I didn;t end up setting up multiple paths using the Linux device mapper but this OR multiple targets with correct names passwords and matching initiator / target pairs would allow the VxVM DMP to work.Stuart
09-18-2007 03:55 PM
It may sound rather discouraging, but full functionality of software based iSCSI initiator on Sun Solaris is apparently not there yet. It is my understanding, that unless the initiator software component reports all that there is to be known about the target properties, there will be missing pieces that may brake the functionality of other software components that depend on it, such as Veritas DMP.
Another example of me running into the same sort of problem was trying to get backup software to use iSCSI addressable tape drive libraries. They also present themselves as iSCSI targets. Veritas Backup needed serial numbers of the tape drives in order to track licensing and to set unique device ID's of the tape drives etc.
It just did not work with a software initiator solution because of not fully described devices.
Some day Sun will fix that...
10-24-2007 06:04 AM
11-20-2007 02:53 AM
Hi, Ed,sorry for the delay but I wanted to test all of the details very well. Yes, it works with the exclusion from DMP (normally I should have known this, shame :-). Great. At least for most of the features of Storage Foundation.The only thing I found was the incompatibility with SCSI 3 persitent reservation, which is not working with iSCSI Targets (at least on Solaris 10 and Open Solaris 11). Ok, but that's a minor point. And I dont think that this will be in the driver (very soon :-).The other thing I'm working on this days is the different ID's on the disks in a cluster environment. On one host it shows correctly, on the other hosts there ist a difference in informations on the disk decription and the operating system informations, ending in the status "online,incompatible" for the disks. But thats only cosmetic, the switch from one host to another including the import of the disk groups works fine. I think I will write a preonline trigger for the cluster to prevent confusing my trainees. Or even for spending some time in long winter nigths.Again thanks for the helpRoger