Ad blocker detected: Our website is made possible by displaying online advertisements to our visitors. Please consider supporting us by disabling your ad blocker on our website.
cacti_question wrote:How is the OID that I see in the logs determined?
By the script/template. In the case of this, it's the xml file which has the base OID cacti is to use, and then it figures out the last OID to append.
For a newbie, I strongly suggest you get your basic cacti installation up and running. using the included templates. then, you can expand out using user created templates, plugins, etc.
Data Query Debug Information
+ Running data query [14].
+ Found type = '3' [snmp query].
+ Found data query XML file at '/var/www/cacti/resource/snmp_queries/RFC1213.xml'
+ XML file parsed ok.
+ Executing SNMP walk for list of indexes @ '.1.3.6.1.2.1.7.2'
+ Index found at OID: '1.3.6.1.2.1.7.2.0' value: '26'
+ index_parse at OID: '1.3.6.1.2.1.7.2.0' results: '0'
+ Inserting index data for field 'Index' [value='0']
+ Found data query XML file at '/var/www/cacti/resource/snmp_queries/RFC1213.xml'
+ Found data query XML file at '/var/www/cacti/resource/snmp_queries/RFC1213.xml'
+ Found data query XML file at '/var/www/cacti/resource/snmp_queries/RFC1213.xml'
upd
I think this problem connected with oid_index in RFC1213.XML
My snmpd server response:
[root@backup snmp_queries]# snmpwalk -v2c -c pub c2 .1.3.6.1.2.1.7.2
UDP-MIB::udpNoPorts.0 = Counter32: 130
Name of TCP states graph are different from
CLOSING
ESTABLISHED
FIN_WAIT1
FIN_WAIT2
LAST_ACK
LISTEN
SYN_RECV
TIME_WAIT
Are these the same things just with different names? If so, how do they map to each other?
i'm trying to compare results of this command with the results from this graph
mxxcon wrote:Are these the same things just with different names? If so, how do they map to each other?
It's the names pulled from the RFC1213 MIB file. Sample:
tcpActiveOpens OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times TCP connections have made a
direct transition to the SYN-SENT state from the
CLOSED state."
::= { tcp 5 }
tcpPassiveOpens OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times TCP connections have made a
direct transition to the SYN-RCVD state from the
LISTEN state."
::= { tcp 6 }
tcpAttemptFails OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times TCP connections have made a
direct transition to the CLOSED state from either
the SYN-SENT state or the SYN-RCVD state, plus the
number of times TCP connections have made a direct
transition to the LISTEN state from the SYN-RCVD
state."
::= { tcp 7 }
tcpEstabResets OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times TCP connections have made a
direct transition to the CLOSED state from either
the ESTABLISHED state or the CLOSE-WAIT state."
::= { tcp 8 }
tcpCurrEstab OBJECT-TYPE
SYNTAX Gauge
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of TCP connections for which the
current state is either ESTABLISHED or CLOSE-
WAIT."
::= { tcp 9 }
tcpRetransSegs OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of segments retransmitted - that
is, the number of TCP segments transmitted
containing one or more previously transmitted
octets."
::= { tcp 12 }
I understand that graph is sampled every so often, but still, numbers seem to be outrageously high.
also, should there be decimal digits when we are talking about number of connections? .5 connection? perhaps that should be rounded up/down?
Notice the vertical axis title? Instead of the typical 'per second' view, I've changed it to 'per 5 minutes' -- the default cacti polling interval. You can change it back by simply removing the CDEF... on each graph template item, heh.
I think these are really neat looking data points in the graph..
My question is one of information and education for myself.
The data I see on the graphs is for counters if I walk the rfc1213 mib (like 9878563) but on the graphs they show up as M m k with maybe a decimal value.
I am having a hard time wrapping my arms around what the data means. If you could explain what I should be expecting to see and why that would be great.
Like for the Combined Protocol Graph Templates seen in your example screen shots. I would expect to see more of an exact number "counter" as opposed to one displayed in m or k.
That's where I am having a hard time interpreting and validating my data (or the data shown in the example screen shots in this post). What does icmpOutMsgs 2.52m mean exactly on your screen shots ans d why is it that way?
I am going to post some screenshots here... maybe I simply need to be educated more.. screenshots to come. I am having a real hard time making sense of the raw data I see on an SNMP query and how that data is represented in these graphs. I am sure it is me so i will send screen shots and qury outputs in a few.
I thank you for these graphs as they are really nice I just need to understand the data I am seeing so i can then explain it to end users. I cannot do that at this time hence my education request.
That graph is no different than the existing Cacti traffic graphs were data is displayed in per/second fashion. The other graphs for the RFC1213 templates I've altered to display data per/5 min instead.
As for the specific counter, it's defined as the following:
udpInDatagrams OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of UDP datagrams delivered to
UDP users."
::= { udp 1 }
Thanks.. honestly the big piece I was missing was the background calc of (current counter - previous counter) / (poll cycle current - poll cycle previous)
that was confusing the heck out of me causing me to question my sanity on all my graphs... good to go no and back on track. Had to read the rrdtool tutorials again...