Processing wrong values of MIB OID objects by SNMP agent


Processing wrong values of MIB OID objects by SNMP agent



How to make the SNMP agent ignore wrong or inconsistent value of supported generic MIB OID objects, and move ahead, not stumbling on them? Currently, the SNMP agent stumbles on errors in supported MIB OID objects, can't process and reject the configuration file. Although this behavior fully conform to DOCSIS 3.0 specification. But this behavior varies depending on the vendor.
(means there is an option to make error processing less strict).


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.









By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Comments

Popular posts from this blog

paramiko-expect timeout is happening after executing the command

Opening a url is failing in Swift

Export result set on Dbeaver to CSV