Venkateswarlu Konamki <venkat.kona...@gmail.com> writes: Sorry for the long delay in responding:
> RFC 2737: Entity MIB (Version 2) > RFC 3246: Expedited PHB Nope, we don't have support for these unfortunately. But we do for these: > RFC 2863: MIB (Interfaces Group) > RFC 3411: Architecture for SNMP Management Frameworks > RFC 3412: Message Processing and Dispatching for the Simple Network > Management Protocol (SNMP) > RFC 3413: SNMP Applications > RFC 3414: User-based Security Model (USM) for Version 3 of the Simple > Network Management Protocol (SNMPv3) > RFC 3415: View-based Access Control Model > RFC 3416: V2 of SNMP Protocol Operations > RFC 3417: Transport Mappings for the Simple Network Management Protocol > (SNMP) This there is only half-working support for I believe (it would require modifications for specific systems before deploying): > RFC 4502: Remote Monitoring Management Information Base Version 2 > ifeq ($(strip ${BR2_PACKAGE_NETSNMP_SNMPV3}),y) > NETSNMP_CONFIG += --with-default-snmp-version="3" \ > --with-mib-modules="snmpv3mibs mibII > utilities/execute" \ > --with-out-mib-modules="ucd_snmp utilities > notification > notification-log-mib target agent_mibs agentx disman/event-mib > disman/schedule host" You're removing support for the target mib, which is part of the SNMPv3 specs and is needed by some of the other mibs (snmp configurable notification support). The notification-log-mib is too, but may not be actually needed. -- Wes Hardaker Please mail all replies to net-snmp-coders@lists.sourceforge.net _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders