SNMP is less resource-intensive and faster than NETCONF. I would use SNMP for the things you can and NETCONF for the things you can't. If you consider NETCONF, it would probably be best to do so in a threaded, asynchronous, or multi-process fashion. I've seen a few SNMP pollers that don't use threads or multiple processes or callbacks, and they can get away with it. I don't think NETCONF can.
--tc On Sat, Aug 30, 2014 at 9:01 AM, Morgan McLean <wrx...@gmail.com> wrote: > Hi all, > > Just curious if anybody opts to use netconf instead of snmp for monitoring > purposes? Any known downsides? > > SNMP seems to never really be up to date with everything that you might > want to have a peek at. > > Thanks, > Morgan > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp