Conflict in confd loading SNMPv1 MIB

tried to support old SNMP interface MIB such as RFC1213-MIB.bin, but don’t know how to avoid the conflict with SNMPv2-MIB which is automatically loaded by confd, please see the content in my devel.log:

12-Sep-2016::12:09:08.626 ubuntu-mjin confd[9706]: devel-cdb loaded CDB config file: ./confd-cdb/C.cdb (v3 from 5.3.3)
12-Sep-2016::12:09:08.752 ubuntu-mjin confd[9706]: devel-snmpa loaded snmp mib: /home/mjin/Downloads/…/confd-5.3.3/lib/confd/lib/snmp/snmp/priv/mibs/SNMPv2-MIB
12-Sep-2016::12:09:08.752 ubuntu-mjin confd[9706]: devel-snmpa loaded snmp mib: /home/mjin/Downloads/…/confd-5.3.3/lib/confd/lib/snmp/snmp/priv/mibs/SNMP-FRAMEWORK-MIB
12-Sep-2016::12:09:08.752 ubuntu-mjin confd[9706]: devel-snmpa loaded snmp mib: /home/mjin/Downloads/…/confd-5.3.3/lib/confd/lib/snmp/snmp/priv/mibs/SNMP-MPD-MIB
12-Sep-2016::12:09:08.769 ubuntu-mjin confd[9706]: devel-snmpa setting snmpEngineID: 80:00:61:81:05:01
12-Sep-2016::12:09:08.809 ubuntu-mjin confd[9706]: devel-snmpa OID conflict 1.3.6.1.2.1.1.1 in MIB: RFC1213-MIB.bin

I found examples for IF-MIB etc in linuxcfg module, and it seems to be working fine, but I would like to implement a backward compatible and simplified version of ifTable in RFC1213-MIB.

It seems to me the mib annotation file can not effectively exclude MIB objects in the final bin file, although it does help to filter out them in the .yang file when doing mib2yang using noSuchObject statements.
BTW, there are also some warnings for each one of the filtered-out objects when generating the MIB bin file, e.g. “RFC1213-MIB.mib: warning: No association for ‘sysDescr’, variable won’t work properly.”

Is there a simple way to remove, for example the system object from RFC1213-MIB to avoid the above confd loading error?

Thank you very much,
Michael

ConfD requires SNMPv2-MIB to work. RFC1213-MIB that is based on RFC1155-SMI isn’t supported. You are advised to use MIBs that are based on SMIv2.

It may be better to simplify IF-MIB instead of RFC1213-MIB to meet your requirements.

Note that not every object in the MIB must have a mapping to a node in the YANG module. By using a separate MIB annotation file, ConfD can be instructed how these missing objects should be treated by the SNMP agent. The agent can treat the objects either as not implemented, or as implemented but nonexistent.

Any further help with your SNMP issue can best be addressed by our support team. Please file a RT through your account.

I will use the IF-MIB instead. Thought ConfD MIB compiler supports SMIv1 and RFC1155-SMI,etc., that’s why I tried on RFC1213-MIB in the first place.
Thanks for the quick clarification.