On Thursday, August 6, 2020 at 1:42:35 AM UTC-7, Amit Bawer wrote: > > Another point i'd like to ask about is iSER fallback that we have: > > Currently we check during connection flow if 'iser' is set on > iscsi_default_ifaces in our configuration. > If yes, it is first checked if its working on server side by attempting > > iscsiadm -m node -T target -I iser -p portal -l > iscsiadm -m node -T target -I iser -p portal -u > > If the login/logout worked it is kept as 'iser' instead of 'default' > interface setup, otherwise it fallbacks to 'default'. > This is used later for the actual node login. > The thing is that this check can also waste valuable time when the portal > is down, is there a way to fallback in the iscsiadm command itself, or > prefer a specific interface type when trying all/parallel logins for same > target+portal but with different interfaces types? > > There is no way to have the iscsi subsystem "fall back" to default from iser given the current code. The problem is when to fallback? Also, falling back to a secondary interface could add an addition 180 seconds, if it times out, as well. So it's up to the higher-level code (you, in this case) to make decisions like that.
-- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/open-iscsi/709390a8-7a98-4990-afbb-4b54bef2d4dao%40googlegroups.com.
