I added 4 firepower appliances to my relatively fresh install of LibreNMS and it seems to be pulling in all of the data I need, but the Overall Traffic graph is not including all of the needed interfaces. It is only drawing one interface “diagnostic”, but ignoring all of the other interfaces i.e. “Adaptive Security Appliance ‘Outside’ interface”. I tried getting it to pull them using the “good_if” configuration option but it did not make any difference.
I don’t see “irtual” in the “bad_ifType” array, but I do have it under the “bad_if” array (image included below). That shouldn’t apply to this interface since “bad_if” should only match the “ifDescr” value right? I might be misunderstanding the purpose of the “good_if” option. I thought that was a way to override the default “bad_if” values to un-ignore an interface based on the “ifDescr” value. Is that not the case?
I did try it, but I will try again. This page (https://docs.librenms.org/Developing/os/Settings/) says that it should be case insensitive. Do I need to remove and add the device again after making the change to the config.php file?
Okay, I found under the FAQ (FAQ - LibreNMS Docs) that I was looking at the wrong config values. I should have been using “device_traffic_iftype”, by unsetting it and then recreating it, but commenting out the “/virtual/” entry. For example:
The only problem I have with this is that it also enables a slew of other interfaces that I had no intention of enabling in the overall traffic graphs because their ifType is also “propVirtual”, not necessarily for this device, but other devices. For example (separate device, not firepower):
NOT FIREPOWER: before removing “/virtual/” does not include port-channels
This is problematic because the throughput being added from the port-channels is already being added by the physical interface counters doubling the amount of traffic displayed for those interfaces in the Overall Traffic graph. I could manually add “/port-channel/” to the “device_traffic_descr” config as well as all of the other interfaces that have been inadvertently enabled, but I’d rather be able to whitelist an interface than have to go through and manually blacklist everything else especially given that I likely won’t notice that the traffic is being graphed twice until there is some kind of issue. Is there a way to whitelist an interface for the Overall Traffic graph? Like “device_traffic_good_descr” so you can use the ifDescr to include it?
I opened a Feature Request to have something life $config[‘device_traffic_good_ifalias’] or $config[‘device_traffic_good_ifdescr’] added so interfaces can be whitelisted to be included in the Overall Traffic graph based on the ifAlias or ifDescr values.
I’m experiencing the same for out Firepower firewalls. I read through the link above (and the other links that spawned off that) and it seems like this fizzled out. A merge request that didn’t seem to go anywhere?
Does anyone know if this hit a dead end, or is work possibly still progressing to resolve the issue?