如何使SNMP代理忽略支持的通用MIB OID对象的值错误或不一致，并继续前进，而不是绊脚石？当前，SNMP代理偶然发现支持的MIB OID对象中的错误，无法处理和拒绝配置文件。尽管此行为完全符合DOCSIS 3.0规范。但是，此行为因供应商而异。 （意味着有一个选项可以使错误处理的严格程度降低）。
8.2.4.2 CM configuration TLV-11 elements not supported by the CM
If any CM configuration file TLV-11 elements translate to SNMP MIB OIDs
that are not MIB OID elements supported by the CM, then the CM MUST
ignore those SNMP varbinds, and treat them as if they had not been
present, for the purpose of CM configuration. This means that the CM
will ignore SNMP MIB OIDs for other vendor's private MIBs as well as
standard MIB elements that the CM does not support." ... If any CM
configuration file TLV-11 element(s) are ignored, then the CM MUST
report them via the CM configured notification mechanism(s), after the
CM is registered.
...
8.2.4.4 CM state after CM configuration file processing failure
If any CM configuration file generated SNMP PDU varbind performs an
illegal set operation (illegal, bad, or inconsistent value) to any MIB
OID/instance supported by the CM, the CM MUST reject the configuration
file.