Where do mcc.py get its data from

NAV 3.10.1

We have several (but not all) routers and switches where cricket try to collect data fram OIDs the devices doesn't know anything about. I fail to find any similarities in type of device or OS-version between the devices.

For a switch the offending lines in switches/navTargetTypes looks like this:

targetType brusS101-sw.infra.uit.no ds = "c1900Bandwidth, c1900Bandwidth, c1900BandwidthMax, c1900BandwidthMax, mem5minFree, mem5minFree, mem5minUsed, mem5minUsed, sysUpTime, sysUpTime, c2900Bandwidth, c2900Bandwidth, c5000Bandwidth, c5000Bandwidth, c5000BandwidthMax, c5000BandwidthMax, cpu1min, cpu1min, cpu5min, cpu5min, hpcpu, hpcpu, hpmem5minFree, hpmem5minFree, hpmem5minUsed, hpmem5minUsed" view = "bandwidth: c1900Bandwidth c1900BandwidthMax c2900Bandwidth c5000Bandwidth c5000BandwidthMax, cpu: cpu1min cpu5min hpcpu, memory: hpmem5minFree hpmem5minUsed mem5minFree mem5minUsed, sysuptime: sysUpTime"

Note that it tries to collect both c1900Bandwidth, c2900Bandwidth and c5000Bandwidth

When I check the device via https://nav.example.com/report/netboxsnmpoid?netbox id=## I don't find any OIDs relating to Bandwidth at all.

For Cisco routers the offending OID is hpcpu and hpmem*.

targetType kulth-gsw.infra.uit.no ds = "c5000Bandwidth, c5000BandwidthMax, cpu1min, cpu5min, hpcpu, hpmem5minFree, hpmem5minUsed, mem5minFree, mem5minUsed, sysUpTime" view = "bandwidth: c5000Bandwidth c5000BandwidthMax, cpu: cpu1min cpu5min hpcpu, memory: hpmem5minFree hpmem5minUsed mem5minFree mem5minUsed, sysuptime: sysUpTime"

Any ideas why mcc.py puts them in?

--Ingeborg