...
Platform | Agent | Extensions |
|---|---|---|
AIX | perzl has net-snmp v5+ RPMs | exec, extend |
Solaris | solaris 10+ ships with net-snmp v5.09+ | exec, extend, perl, shared |
RHEL 3,4,5 | netsnmp v5.0.9+ | exec, extend, perl, shared |
Windows | net-snmp or native service | shared |
Phones | none, would have to push n/a, but could sink traps... pie in the sky, should just say no. | n/a |
Probes to Replace
- ? (will get list when Discovery is available
Proof of Concept (UNIX)
On Linux/net-snmp 5 here's one way to do extensions (there are several).
- Use "exec" to add an extension to snmpd.conf
No Format exec echotest /bin/cat /etc/motd
- Restart snmpd and do a GET against a view which can see the extended MIBs
Code Block snmpget -v2c localhost -c public 'NET-SNMP-EXTEND-MIB::nsExtendOutputFull."echotest"'
...we may want to use SNMPv3, but the general idea is clear... we can expose arbitrary configuration data through SNMP. Since there are only a few dozen probes (and maybe only a subset of actual interest to Yale) we should be able to leverage SNMP for UNIX discovery instrumentation.
Proof of Concept (Windows)
It's not yet clear which way to go. There is a possible benefit to going SNMP for all discovery. However, it is not clear that the benefits outweigh the costs, because it might be possible to do WMI discovery without granting privilege by properly securing the WMI namespace... this might be much easier than porting another set of custom SNMP probes for Windows.
| Panel |
|---|
MID server installed as a Windows service with either Windows domain administrator privileges, or with local administrator privileges for the computers being discovered. This ensures that the MID Servers can query all Windows devices in an IP address range. Local security policies may vary. (emphasis Yale) |