Hey jffnms-folks, I've got a problem that results in some detected interfaces not being added/addable. Perhaps someone has seen this before?
To start, I am kicking off a "manual" autodiscover from the hosts menu. All the interfaces on the host will be detected and I can select them, but only some of them will show up under the post-autodiscover screen and get added to the db. The rest are ignored as if I didn't check them. It's not a browser thing, firefox and chromium both do it. This happens both on a jffnms install on debian stable that I've had around forever, and a fresh/current one I installed on a VM just to test for this problem. I have two cisco 6509s that have rather a bunch of interfaces in/on them that I've been testing with--they have different supervisors, card configurations, OS versions, etc, but both elicit this behavior. I did a discover and 'mark all interfaces' on my test install and it ends up adding all of the detected/marked interfaces down to some certain point, after which nothing else will add. If I remove one of these hosts and add it back in, then detect interfaces and add one or more of the choice of un-addable interfaces (for instance a bgp neighbor "interface", I just tried it) the next page declares "no interfaces found." Any idears? ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ jffnms-users mailing list jffnms-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jffnms-users
