Actually quite a LOT of monitoring applications will rely on the snmp ifIndex persisting, for example with Cisco there's one or two configuration commands (below) you need to add, and most other vendors that don't persist the ifindex have an option somewhere to do such.
snmp-server ifindex persist snmp ifmib ifindex persist
I cannot recall why there are two, I think that second one is for when you go to 15.x code base (it definitely has both)... as to the other issue of moving ports around, I'll defer to someone else as I don't know the answer to that.
On Fri, Feb 14, 2014 at 10:31 AM, Teixeira, Mike mwteixeira@bendbroadband.net wrote:
Hello,
Recently our network team upgraded one of our devices. Upon doing so some of the ifIndexes changed on the device. So we lost some history on some of the ports where the ifindex changed.
Another situation, we use the port description mapping for tracking transit, peering, core ports. We moved a peer from one switch to another in one of our ports to upgrade the capacity. When we did that we lost the history in the aggregate graph because the old port doesn't have the port description anymore denoting it is a peer.
Any tips on how to keep history on ports in those situations? I was thinking of outputting the data to a separate RRD or database. But, then I don't get to use the awesome observium interface to view that data.
Thanks,
Mike
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium