Sean Hefty wrote: > Randomize the starting local comm ID to avoid getting a rejected connection > due to a stale connection after a system reboot or reloading of the ib_cm.
Hi Sean, As i wrote you patching the CM it works fine and the problem i could reproduce with our iser target is solved. However, we wonder what is your opinion (and if positive, work estimation...) to make the CM get "GID OUT" traps, which are generated by the SM when a node IB restarts (eg a node reboot). Once the CM gets the trap, it can scan the internal data structures and emulate a disconnect for all relevant (*) connections ??? (*) there are some technical issues here: the GID OUT is on a PORT GID and the CM uses NODE GUIDS, also does openib stack has the means for a client to register on getting **traps** ??? Other then the CM there might be more potential consumers to this trap, and also to "GID IN". Or. _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
