On Wednesday 09 Jun 2010 16:53:47 Michal Suchanek wrote: > I guess the issue is that it is non-obvious if you log in into a target > that has no luns and thus no devices are created. > > If it's not the job of iscsiadm to diagnose issues with the iscsi target > then where are the issues supposed to be diagnosed?
You can always be logged into the target, for example, to test if the auth models are working or not. It does not have to reflect a device appearance on the initiator. As for the typo on the target side that you mentioned in the initial post, it is the target that should error out on start-up. The iscsiadm utility's job is Discovery, Login, Rescan and a bunch of other stuff. It does not bother if the target that you discovered, has LUNs for your initiator or not. Nothing to do with the initiator. For the Linux iscsitarget, ietadm is what should do the diagnosis for the target. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs
signature.asc
Description: This is a digitally signed message part.
