On 07/04/2013 06:18 PM, Dustin Frisch wrote: > Is any use case for this behavior?
This is a slightly lame use case, better ones exist. It's a holiday here :P Imagine we have two load-balancers, each of which requires its worker servers all to be in a separate subnet. We might make a set of poller packages like this: <package name="lb-oops"> <filter>catincApp_A | catincApp_B</filter> <service name="LB_Happy"> <parameter key="is-supported" value="false" /> </service> </package> <package name="lb-A"> <filter>catincApp_A & IPLIKE 10.0.10.*</filter> <service name="LB_Happy"> <parameter key="is-supported" value="true" /> </service> </package> <package name="lb-B"> <filter>catincApp_B & IPLIKE 10.0.11.*</filter> <service name="LB_Happy"> <parameter key="is-supported" value="true" /> </service> </package> If ever somebody accidentally numbers into the wrong subnet an interface on a node in the App_A or App_B category, the "LB_Happy" service on that interface will go into outage. This works because the last service definition that matches a given IfService is the one that the poller will use. I hope this makes some small amount of sense. -jeff ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Please read the OpenNMS Mailing List FAQ: http://www.opennms.org/index.php/Mailing_List_FAQ opennms-devel mailing list To *unsubscribe* or change your subscription options, see the bottom of this page: https://lists.sourceforge.net/lists/listinfo/opennms-devel
