> > So normally when you say target you mean portal. I mean for sendtargets iSCSI Target when there is an iSCSI Name associated with it, otherwise a portal. I guess it would be clear to say Target Portal and Node instead. > we set a portals as persistent not a whole target right (this is from > jsut using iscli)? For iSNS, can't we get updates that there are new > portals popping in the san? You are not saying that normally we want to > handle this by starting up a config app and setting them as persistent. That is correct we should field SCN (state change notification) and ESI (entity status inquiry) events. > I thought we would want to dyncallically add them to the system. That is correct. > > What is the point of using iSNS and setting the targets as persistent in > the initiator DB anyways? I thought one of the benefits of iSNS is that > we would manage all the targets and initiator access from a central > location? The HBA architecture allows any iSCSI Target Node or Portal (in case of Send targets) to be made persistent. It is up to the user to determine which ones need to be persistent. - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
