I have to agree here - having the monitoring software "rediscover" where the ifindex for an interface is after a reboot isn't ideal in my opinion.....
Paul -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of martin Sent: Saturday, August 14, 2010 5:18 AM To: Chris Adams; [email protected] Subject: Re: [j-nsp] Interface Index(ifIndex) changes when router is rebooted ok, but what do you mean by fix the software? You don't poll interfaces by ifindex number? 2010/8/14 Chris Adams <[email protected]>: > Once upon a time, martin <[email protected]> said: >> As ifindex value has to be persistent in order to use >> it for SNMP based monitoring solutions(for example Nagios), > > Basically, fix the software. It isn't that hard to do; Cricket (among > others) has managed to handle it for 10+ years. There will always be > cases where instance numbers change, so you might as well go ahead and > deal with it. > > For Nagios, I use a plugin wrapper that can walk a specified tree, cache > the tree, match the desired value, and then call another plugin with the > instance number. > -- > Chris Adams <[email protected]> > Systems and Network Administrator - HiWAAY Internet Services > I don't speak for anybody but myself - that's enough trouble. > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
