From: Arne R. <ar...@in...> - 2004-06-25 09:13:54
|
> > I think this isn't correct (anymore?). I've had no problems connecting > > two Cisco initiators to one UNH target version 1.5.3 (IIRC, 1.5.2 worked > > as well). > > Thanks. Could you give me the details? How can you do it? > > It would be greatly appreciate if you could show your configuration > files. There wasn't any black magic involved - besides the one described on your website to make Cisco initiators work with UNH targets by forcing Cisco initiators to use normal instead of discovery sessions (thanks for those invaluable hints btw.). On the target side, I was using the script $UNH_SRC_1.5.3/src/cmd/HP-target-install-chap (I only adjusted CHAP usernames / secrets and set "InitialR2T=No"). Btw., the same setup also works with Microsoft's Initiator IIRC. Here's the config for the Cisco initiators (3.4.1): /etc/iscsi.conf: ---------------- # iSCSI configuration file - see iscsi.conf (5) # Global settings: ImmediateData=yes InitialR2T=no HeaderDigest=Prefer-on DataDigest=Prefer-on #UNH Target settings: DiscoveryFile=/etc/iscsitarget.unh.conf SendAsyncText=no Continuous=no DefaultAddress=192.168.2.1:3260 IncomingUsername=initiator IncomingPassword=initiatorpassword OutgoingUsername=target OutgoingPassword=targetpassword -------------------------- /etc/iscsitarget.unh.conf: -------------------------- TargetName=iqn.2002-10.edu.unh.iol.iscsi.draft20-target:0 Admittedly I didn't do any benchmarking or stress tests, since target and initiators ran on a single machine with the initiators started from within User Mode Linux instances. But I was able to see all LUs from within all initiator-UMLs and perform some basic operations on them. Regards, Arne |