Cacti Not Graphing correctly when Bandwidth reaches 110mb/s
Moderators: Developers, Moderators
Cacti Not Graphing correctly when Bandwidth reaches 110mb/s
If anyone can shed some light on why I am seeing this I would greatly appreaciate it.
I have 1 Foundry switch connected to a Juniper router running over a GiG-e link. At peek times the link reaches up to 130mb/s. Once it hits 110 - 114 mb/s it starts showing the traffic drop to under 10 megs. Here are 2 graphs, the first is one of the GIG-E Interface on the Switch, the Second is the GiGE interface on the Router.
as you can see, both are doing the same thing.
---
I can watch the traffic real time and see that traffic is actaully flowing and there are no problems as cacti is reporting. I have verified that there are no rate limits on either interface. I have rebuild the graphs, tried changing the MAX Value in the DataSource. Still nothing seems to work.
I am monitoring multiple ports on each of these devices and I have no problems with any other graphs.
Any Help would be great
Thanks
I have 1 Foundry switch connected to a Juniper router running over a GiG-e link. At peek times the link reaches up to 130mb/s. Once it hits 110 - 114 mb/s it starts showing the traffic drop to under 10 megs. Here are 2 graphs, the first is one of the GIG-E Interface on the Switch, the Second is the GiGE interface on the Router.
as you can see, both are doing the same thing.
---
I can watch the traffic real time and see that traffic is actaully flowing and there are no problems as cacti is reporting. I have verified that there are no rate limits on either interface. I have rebuild the graphs, tried changing the MAX Value in the DataSource. Still nothing seems to work.
I am monitoring multiple ports on each of these devices and I have no problems with any other graphs.
Any Help would be great
Thanks
It's not a cacti or rrdtool problem exactly.
The problem is that the SNMP counters that you are reading are 32bit values, and are rolling over within the 5 minute period, when you are reaching 114mbps.
You either need to upgrade your code (on the network device) to use 64 bit values, or run with a frequency of less than 5 minutes.
The problem is that the SNMP counters that you are reading are 32bit values, and are rolling over within the 5 minute period, when you are reaching 114mbps.
You either need to upgrade your code (on the network device) to use 64 bit values, or run with a frequency of less than 5 minutes.
-
- Posts: 38
- Joined: Mon Feb 16, 2004 2:01 pm
- Location: Westland, MI
- TheWitness
- Developer
- Posts: 17007
- Joined: Tue May 14, 2002 5:08 pm
- Location: MI, USA
- Contact:
From the pulldown. However, you may have to rename a bunch or old RRD files from the standard 64bit ones.
TheWitness
TheWitness
True understanding begins only when we realize how little we truly understand...
Life is an adventure, let yours begin with Cacti!
Author of dozens of Cacti plugins and customization's. Advocate of LAMP, MariaDB, IBM Spectrum LSF and the world of batch. Creator of IBM Spectrum RTM, author of quite a bit of unpublished work and most of Cacti's bugs.
_________________
Official Cacti Documentation
GitHub Repository with Supported Plugins
Percona Device Packages (no support)
Interesting Device Packages
For those wondering, I'm still here, but lost in the shadows. Yearning for less bugs. Who want's a Cacti 1.3/2.0? Streams anyone?
Life is an adventure, let yours begin with Cacti!
Author of dozens of Cacti plugins and customization's. Advocate of LAMP, MariaDB, IBM Spectrum LSF and the world of batch. Creator of IBM Spectrum RTM, author of quite a bit of unpublished work and most of Cacti's bugs.
_________________
Official Cacti Documentation
GitHub Repository with Supported Plugins
Percona Device Packages (no support)
Interesting Device Packages
For those wondering, I'm still here, but lost in the shadows. Yearning for less bugs. Who want's a Cacti 1.3/2.0? Streams anyone?
Juniper 64 oids
I had a bit of trouble getting this to work The Right Way with a Juniper Router, so I copied the graph templated and altered it to directly use an SNMP query.
The 64bit inbound counter for a juniper router (well, for mine at least) is:
1.3.6.1.4.1.2636.3.3.1.1.1.[index#]
outbound is:
1.3.6.1.4.1.2636.3.3.1.1.4.[index#]
You can figure out the index number for your interfaces through a verbose snmp interface query.
The 64bit inbound counter for a juniper router (well, for mine at least) is:
1.3.6.1.4.1.2636.3.3.1.1.1.[index#]
outbound is:
1.3.6.1.4.1.2636.3.3.1.1.4.[index#]
You can figure out the index number for your interfaces through a verbose snmp interface query.
Who is online
Users browsing this forum: No registered users and 0 guests