From: Lance V. <ope...@gh...> - 2011-05-16 22:38:36
|
What do you mean by authentication asset/provision info? I am missing something here. On Mon, May 16, 2011 at 3:00 PM, Jason Lixfeld < jas...@li...> wrote: > On 2011-05-16, at 3:33 PM, Lance Vermilion wrote: > > > I know the .cloginrc is created and populated with default entries (or > least it used to be) when you setup RANCID with ONMS. My older setup > (1.8.5...I think) does not have entries things that I didn't explicitly > add/enable. > > I set the default entries up manually. That was how I interpreted the > instructions found at http://www.opennms.org/wiki/RANCID_RWS > > > You are saying that you are seeing every node on your node page get added > to the .cloginrc right? > > No, I'm only seeing some nodes getting added to .cloginrc, but none of the > nodes that are being added have any authentication asset info or provision > info to differentiate them from any other nodes that were not added to > .cloginrc, so I think it's a bug. I've been going back and forth with > Antonio on it, but I think he thinks I'm crazy :( > > > On Sat, May 14, 2011 at 7:41 PM, Jason Lixfeld < > jas...@li...> wrote: > > I'm not sure how to answer that, Lance. I was under the assumption that > any node in OpenNMS is automatically setup to be collected by RANCID via > OpenNMS and it's up to the operator to turn off RANCID via the GUI or let > every node be polled and ignored if RANCID can't login/read it. > > > > The clogin info from Home > Admin > Admin Rancid > Clogin Info is > populated with the erroneous information, but I'm not sure where it's > getting it from. The Authentication area in the asset info for that node > has nothing configured. > > > > On 2011-05-11, at 3:40 PM, Lance Vermilion wrote: > > > > > have those nodes (the ones you don't want in the .cloginrc) ever been > setup to be collected by RANCID via OpenNMS? > > > > > > On Tue, May 10, 2011 at 2:09 PM, Jason Lixfeld < > jas...@li...> wrote: > > > My default .cloginrc looks like: > > > > > > add user * username > > > add password * password > > > add autoenable * 1 > > > add method * telnet > > > > > > After a reload of OpenNMS, something goes in and adds entries for a few > of my nodes into .cloginrc and I can't figure out what is causing it. I've > checked the asset info for the nodes that get added to .cloginrc all the > Authentication bits are empty, so I can't figure out what else might make > these nodes particularly special. > > > > > > Any ideas? > > > > ------------------------------------------------------------------------------ > > > Achieve unprecedented app performance and reliability > > > What every C/C++ and Fortran developer should know. > > > Learn how Intel has extended the reach of its next-generation tools > > > to help boost performance applications - inlcuding clusters. > > > http://p.sf.net/sfu/intel-dev2devmay > > > _______________________________________________ > > > Please read the OpenNMS Mailing List FAQ: > > > http://www.opennms.org/index.php/Mailing_List_FAQ > > > > > > opennms-discuss mailing list > > > > > > To *unsubscribe* or change your subscription options, see the bottom of > this page: > > > https://lists.sourceforge.net/lists/listinfo/opennms-discuss > > > > > > > ------------------------------------------------------------------------------ > > > Achieve unprecedented app performance and reliability > > > What every C/C++ and Fortran developer should know. > > > Learn how Intel has extended the reach of its next-generation tools > > > to help boost performance applications - inlcuding clusters. > > > > http://p.sf.net/sfu/intel-dev2devmay_______________________________________________ > > > Please read the OpenNMS Mailing List FAQ: > > > http://www.opennms.org/index.php/Mailing_List_FAQ > > > > > > opennms-discuss mailing list > > > > > > To *unsubscribe* or change your subscription options, see the bottom of > this page: > > > https://lists.sourceforge.net/lists/listinfo/opennms-discuss > > > > > > > ------------------------------------------------------------------------------ > > Achieve unprecedented app performance and reliability > > What every C/C++ and Fortran developer should know. > > Learn how Intel has extended the reach of its next-generation tools > > to help boost performance applications - inlcuding clusters. > > http://p.sf.net/sfu/intel-dev2devmay > > _______________________________________________ > > Please read the OpenNMS Mailing List FAQ: > > http://www.opennms.org/index.php/Mailing_List_FAQ > > > > opennms-discuss mailing list > > > > To *unsubscribe* or change your subscription options, see the bottom of > this page: > > https://lists.sourceforge.net/lists/listinfo/opennms-discuss > > > > > ------------------------------------------------------------------------------ > > Achieve unprecedented app performance and reliability > > What every C/C++ and Fortran developer should know. > > Learn how Intel has extended the reach of its next-generation tools > > to help boost performance applications - inlcuding clusters. > > > http://p.sf.net/sfu/intel-dev2devmay_______________________________________________ > > Please read the OpenNMS Mailing List FAQ: > > http://www.opennms.org/index.php/Mailing_List_FAQ > > > > opennms-discuss mailing list > > > > To *unsubscribe* or change your subscription options, see the bottom of > this page: > > https://lists.sourceforge.net/lists/listinfo/opennms-discuss > > > > ------------------------------------------------------------------------------ > Achieve unprecedented app performance and reliability > What every C/C++ and Fortran developer should know. > Learn how Intel has extended the reach of its next-generation tools > to help boost performance applications - inlcuding clusters. > http://p.sf.net/sfu/intel-dev2devmay > _______________________________________________ > Please read the OpenNMS Mailing List FAQ: > http://www.opennms.org/index.php/Mailing_List_FAQ > > opennms-discuss mailing list > > To *unsubscribe* or change your subscription options, see the bottom of > this page: > https://lists.sourceforge.net/lists/listinfo/opennms-discuss > |