Net-SNMP also works as an SNMP proxy. So, what I've done on windows boxes in the past (it's been awhile), is configured MS-SNMP to listed on 1161 (pick a port), then configure net-snmp to process the HOST-RESOURCES MIB itself and forward everything else on to MS-SNMP on 1161. This method allows you to still map OIDs to arbitrary commands in net-snmp but still let MS handle plugins, etc.
Instructions pertaining to how it needs to be set up in the MS agent can be found in the Windows HOWTO on the Net-SNMP website. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matthew Keller Sent: Tuesday, August 14, 2007 3:14 PM To: General discussion of using zenoss system Subject: Re: [zenoss-users] Net-SNMP on Windows There is quite a bit missing from the Windows port, enough to prevent it from being a viable replacement for MS SNMP + Informant (on systems that it workson) for now. The biggest limitation, honestly, is with Windows. Net-SNMP allows you to map OIDs to arbitary commands, but in Windows, there is no command-line tool, for example, to see the CPU usage without invoking GDI and thus needing to be run from an interactive user. Because of this, working around the current Net-SNMP limitations with clever config files isn't feasible. I will be working on some C-level stuff to implement more of the HOST-RESOURCES MIB, but this isn't going to be the quick templating/jury-rigging I thought it would be. _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
