If I'm replacing a device, I tend to rename the old one, disable it, and then add the new one, to help keep history for a while.
It's a eternal problem without an easy solution.
adam.
On 2014-02-14 12:31, Teixeira, Mike 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