![](https://secure.gravatar.com/avatar/4fad748f042c73a9d01d1ff340dbced4.jpg?s=120&d=mm&r=g)
Moreover, now that I think about, maybe a third option for MAC address (ifPhysAddress if I'm not completely wrong) would be usable as well.
On 2018-06-12 16:56, Attila Nagy wrote:
Hi Adam!
Wouldn't the concept outlined and implemented in LibreNMS solve the problem? Having a portID for every port and creating a setting for each device (with some sane default) whether this portID should get associated with an ifIndex or with an ifName. See Inconsistent port/interface graphs for unix systems #386 https://github.com/librenms/librenms/issues/386
It seems like a plausible fix to this problem, not to mention it has a side effect fixing some other possible problems like dynamically allocated VM interfaces etc.
Regards, Tylla
On 2018-06-12 16:18, Adam Armstrong wrote:
Hi Edvinas,
This is an issue with Linux not having persistent port ifIndexes. It shouldn't happen frequently, but may happen when the kernel changes the order that it enumerates ports.
There's not really a good way to mitigate it at the moment.
adam.
On 2018-06-12 15:07:31, Edvinas K edvinas.email@gmail.com wrote:
Hello,
We started to use Observium for Linux server. So far everything was good, but after reboot of Linux server some ports swaped the data and show incorrect values.
Is there any prevention to this ?
on the server we're using net-snmp-utils _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium