On 27 March 2011 13:29, Boris Zweimueller <[email protected]> wrote: > Instead of using an snmp v2 context (-c)
The '-c' flag is used to specify the SNMPv2 (or SNMPv1) community string, not the context. The concept of contexts was only introduced with SNMPv3. A community name can be mapped into a (non-default) context via the com2sec field. This is not needed with SNMPv3, which includes the context information automatically. > Can the two 'remotehosts' be accessed independently with: > snmpget -v 3 -n ctx_remotehost1 proxyhost sysContact.0 > and > snmpget -v 3 -n ctx_remotehost2 proxyhost sysContact.0 That should work - yes. Dave ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
