Device with strange(?) snmp-implementation triggers bug in seeddb