I am looking for some help in organizing hosts. I see two methods in jffnms maybe I'm missing something, but here's the picture I get:
1) maps. Maps seem cool, but they are actually for organizing interfaces, not hosts. If an iterface or two is added to a particular map the host shows up, but upon clicking the host you only get the interfaces that have been added. Any newly discovered interfaces will be missing and trick a person into thinking they aren't there. This might be useful for organizing hosts if it were possible to add an AD default map (or several default maps). 2) customers. Customers works well for keeping hosts organized. With AD and all, but the problem being that only one customer is allowed per interface. So if I do have a "real" customer that needs access to their interfaces, those interfaces will be missing from the virtual customer I mave have set up to group a particular region. I hope I'm missing something and there is a better way to organize hosts, What I want to be able to do is group the hosts into various groups, and be able to know with certainty that if I select a host out of any of these groups, I will see all of it's interfaces, and not have to have a human check every day for new interfaces and assign them to the appropriate groups. is there a better way? Thanks for your consideration! -- Kenny Dail <[EMAIL PROTECTED]> ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ jffnms-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jffnms-users
