You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Aug 16 10:00:48: Warning: Augment failed in module ietf-snmp-notification: node anydata 2 cannot be added to target node /snmp:snmp
Aug 16 10:00:48: Warning: Augment failed in module ietf-snmp-notification: node anydata 2 cannot be added to target node /snmp:snmp/snmp:target-params
Looks like the yang parser can't parse ietf-snmp-notification submodule properly.
The text was updated successfully, but these errors were encountered:
Actually, the warning may be misleading but it is not an error.
The yang of one of the augment nodes is:
list notify-filter-profile {
if-feature snmp:notification-filter;
key name;
and the snmp:notification-filter feature is disabled. Disabled nodes are transformed to ANYDATA nodes internally and since you cannot augment with ANYDATA, (see RFC 7950 Sec 7.17) it causes this warning message.
I will change the warning message to be more descriptive and also keep track of disabled + anydata nodes and ensure that no warning is printed in this case.
I use standard ietf-snmp yang models from https://github.com/YangModels/yang/tree/main/standard/ietf/RFC. But in runtime logs I see
Aug 16 10:00:48: Warning: Augment failed in module ietf-snmp-notification: node anydata 2 cannot be added to target node /snmp:snmp
Aug 16 10:00:48: Warning: Augment failed in module ietf-snmp-notification: node anydata 2 cannot be added to target node /snmp:snmp/snmp:target-params
Looks like the yang parser can't parse ietf-snmp-notification submodule properly.
The text was updated successfully, but these errors were encountered: