As best as I can tell this is an snmpd-generated error, the system this is reported for isn't in production yet and no snmp requests should be being made to it. All that is required to generate/stop the syslog messages is to add/delete a secondary IP address to an interface in netplan's configuration file and run 'netplan try' (which is successful). My only question (and I don't have an answer or even an opinion) is whether the snmpd rfcs have some prohibition against the situation causing the error messages.
As best as I can tell this is an snmpd-generated error, the system this is reported for isn't in production yet and no snmp requests should be being made to it. All that is required to generate/stop the syslog messages is to add/delete a secondary IP address to an interface in netplan's configuration file and run 'netplan try' (which is successful). My only question (and I don't have an answer or even an opinion) is whether the snmpd rfcs have some prohibition against the situation causing the error messages.