In principle, it should be possible to use the community string in a similar way, but this has not yet been implemented.
Try loading in all the MIB files: SNMP therefore includes mechanisms for controlling who has access to what information - both in terms of what can be seen, and even more importantly what can be changed. If you query this particular tables without the necessary configuration entries, then they will be empty.
As such, it is a useful tool for identifying problems with reading in MIB files. The parser doesn't handle comments properly.
How can the agent receive traps and notifications? How can I monitor my systems disk, memory, etc?
My immediate suspicion is that you may be querying a vendor-supplied full agent rather than your newly-compiled mini agent. But the output is returned in a fixed format, and it is up to the receiving application to interpret this appropriately. Archive Search: If this is the case, then you can specify this interpreter explicitly as part of the trap handle directive: See that entry for details. What's the difference between the various mib2c configuration files? See the previous entry for other potentially relevant useful options.
Though each version had matured towards rich functionalities, additional emphasis was given to the security aspect on each upgrade. Optionally, run snmpconf -g monitoring to help you set up this section of the snmpd. SNMPv1 requests will either treat such objects as an error, or skip them completely.
What protocols are supported? The main issue to be aware of is that such requests will appear to come from the local host, and this may affect how the access control mechanisms need to be set up. If you prefer to concentrate on the nitty-gritty of a given table, and are happy to trust that the rest of the processing will work correctly, then the MfD framework would be more appropriate.