http://defect.opensolaris.org/bz/show_bug.cgi?id=10334
--- Comment #10 from amaguire <alan.maguire at sun.com> 2009-08-13 03:44:21 PDT --- (In reply to comment #9) > The 5 second reevaluation of conditions is when an action event (add, refresh, > destroy, etc) is sent to nwamd. So, when a user modifies any object and > commits it, the conditions are reevaluated. > > When the cable is unplugged, the NCU goes to the offline state. At this > state, > only the priority groups of the NCUs are checked. It appears that anything > that can cause the checking of the priority groups of NCUs should also trigger > condition checking for locations and ENMs. > > Most of our conditions for objects depend on some network status. So, any > time > an NCU changes to online or offline state, condition checking for locations > and > ENMs should be triggered (along with priority group checking for NCUs). > > From nwamcfg, > > 'conditions' specifies the activation condition. Conditions are of the form: > ncu|enm name is|is-not active > ip-address is|is-not|is-in-range|is-not-in-range 1.2.3.4[/24] > advertised-domain is|is-not|contains|does-not-contain string > system-domain is|is-not|contains|does-not-contain string > essid is|is-not|contains|does-not-contain string > bssid is|is-not string yep, and it looks like ncu.c only reevaluates conditions when IP NCUs change. Given that 10377 now propogates phys NCU changes to IP, that would be sufficient to fix this, but in case an ENM or location depends on the state of a link NCU, we should trigger a condition check regardless. -- Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug.
