Persistence of data in Observium
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
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
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
That is likely the most elegant solution.
snmp ifmib ifindex persist is all that is required for 15 code (at least for all the Cisco gear we have)
Spencer Ryan | Systems Engineer Miller Canfield 150 West Jefferson, Suite 2500 Detroit, Michigan 48226 (USA) T +1.313.496.7547 | F +1.313.496.7699 | Mobile +1.734.846.2053 ryan@millercanfield.com
-----Original Message----- From: observium [mailto:observium-bounces@observium.org] On Behalf Of Adam Armstrong Sent: Friday, February 14, 2014 1:38 PM To: Observium Network Observation System Subject: Re: [Observium] Persistence of data in Observium
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
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________________________
NOTICE TO PERSONS SUBJECT TO UNITED STATES TAXATION (MCPS)
DISCLOSURE UNDER TREASURY CIRCULAR 230: The United States Federal tax advice, if any, contained in this document and its attachments may not be used or referred to in the promoting, marketing or recommending of any entity, investment plan or arrangement, nor is such advice intended or written to be used, and may not be used, by a taxpayer for the purpose of avoiding Federal tax penalties. _______________________________________________________________
In our case we did a device replacement. That idea will work for us.
I forgot about the SNMP ifmib persist idea, I think the network guys have that in place, but I will check.
Thanks everyone, Mike
-----Original Message----- From: observium [mailto:observium-bounces@observium.org] On Behalf Of Adam Armstrong Sent: Friday, February 14, 2014 10:38 AM To: Observium Network Observation System Subject: Re: [Observium] Persistence of data in Observium
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
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
participants (4)
-
Adam Armstrong -
Michael Loftis -
Ryan, Spencer J. -
Teixeira, Mike