SNMP monitoring APEX with Cacti
I am trying to use cacti to monitor the APEX but i can not integrate them in cacti graph, i downloaded the MIB from your ftp but do not know how to use them, do you have some specialized in that can help us do it?
-
Raz,
I'm not very familiar with Cacti, but typically you have to go through an import process to import the MIB. You can typically also enter OID's manually.
Have you been able to pull the data in cacti, but you can't graph it?
Since I'm not familiar with Cacti I can't give you step by step, but I'll do what I can to help.
Does anyone in our community have experience with loading the MIBs into Cacti who could possibly help us with a tutorial?
-
Raz,
It looks like it isn't very easy to import a MIB into Cacti from the few minutes I spent searching. I found this comment: "You'll find a walkthrough for that at http://www.cacti.net/downloads/docs/html/data_input_methods.html. See also http://www.cacti.net/downloads/docs/html/script_to_graph.html and the post at http://forums.cacti.net/viewtopic.php?t=4143"
Maybe somebody has made a Cacti friendly file that you could use. Otherwise you can add the OIDs you need. This may help: http://www.cacti.net/downloads/docs/html/graph_snmp_oid.html
You may have better luck on Cacti's forums, as I've found people that have posted templates for our unlicensed products: http://forums.cacti.net/about22214.html
Scott.
-
Best thing to do is to (1) set up a data template, (2) graph template, and (3) host template.
It's really not that bad. Start with the data template. Pick the 4, 8, or 12 OIDs you want to track. Then set up a data template for each one. Name them something that is consistent (start with "Trango Apex" or something like that for each one.
Then decide how you want to display them. Many times you can combine 2 or more per graph if the data representation is similar. There are shortcuts for common tasks.
Then take all the graphs, and stick them in a host template. The data templates will follow automatically.
Then add the devices to your cacti as the appropriate host type.
I will be doing this in a couple of weeks (or sooner) for our new ApexPlus radios.
bp
-
Here's the host template that we built for Cacti. It tracks BER, RSL, and Sync (whether the link is up).
cacti_host_template_trango_apexplus.xml -
I believe you must be on 2.x for this to work:
.1.3.6.1.4.1.5454.1.60.2.8.1.0.0
sysACMTxProfile
INTEGER
RO
0(QPSK), 1(16Q), 2(32Q), 3(64Q), 4(128Q), 5(256Q)
Current modulation
.1.3.6.1.4.1.5454.1.60.2.8.2.0.0
sysACMRxProfile
INTEGER
RO
0(QPSK), 1(16Q), 2(32Q), 3(64Q), 4(128Q), 5(256Q)
Current modulation
-
Sorry, the above "60's" are for Apex.
For ApexPlus and GigaPlus the OIDs for current modulation are:
.1.3.6.1.4.1.5454.1.80.2.3.5.1.0
modemACMTxProfile
.1.3.6.1.4.1.5454.1.80.2.3.5.2.0
modemACMRxProfile
It will return an integer, the logic is as follows:
For links set to QAM256: 0(QPSK), 1(16Q), 2(64Q), 3(256Q)
For links set to anything else: 0(QPSK), 1(16Q), 2(32Q), 3(64Q), 4(128Q) -
Something not right about what we get back on that. According to what I get with snmpwalk we have TX at 0(QPSK), and RX at 5(not on your chart). See below:
snmpwalk -c public -v 2c -On 10.13.110.10 .1.3.6.1.4.1.5454.1.80.2.3.5
.1.3.6.1.4.1.5454.1.80.2.3.5.1.0 = INTEGER: 0
.1.3.6.1.4.1.5454.1.80.2.3.5.2.0 = INTEGER: 5 -
Bill, do you have ACM enabled on this ApexPlus? I just ran it on one of mine which is set to qam256 acm on.
snmpwalk -c public -v 2c 10.14.1.200 .1.3.6.1.4.1.5454.1.80.2.3.5
SNMPv2-SMI::enterprises.5454.1.80.2.3.5.1.0 = INTEGER: 3
SNMPv2-SMI::enterprises.5454.1.80.2.3.5.2.0 = INTEGER: 3If ACM is off, it is possible the ACM engine is reporting what you observed.
-
With ACM off the modulation will never change from the set modulation. I suspect the RX modulation would continue to work, but have never tested it.
You could monitor the set modulation, but again this would only change if someone actually changed the setting.
.1.3.6.1.4.1.5454.1.80.3.6.2.0 is the OID for RF Modulation (the setting).
-
The normal modulation "codes" are not coming back correctly:
(xxxxxxx-config)# linktest 1
LOCK RSSI MSE BER Tx Rx
1> 1 -58.00 -29.20 0.00E+00 64QAM 256QAM[root@cacti: ~]# snmpwalk -v2c -cpublic 10.0.130.151 .1.3.6.1.4.1.5454.1.80.2.3.5
SNMPv2-SMI::enterprises.5454.1.80.2.3.5.1.0 = INTEGER: 2
SNMPv2-SMI::enterprises.5454.1.80.2.3.5.2.0 = INTEGER: 3 -
Travis, it looks like it matches. The confusion is probably over the set speed. For 256 it uses different logic than non-256.
Tx is 2 = 64QAM
Rx is 3 = 256QAMFor links set to QAM256: 0(QPSK), 1(16Q), 2(64Q), 3(256Q)
For links set to anything else: 0(QPSK), 1(16Q), 2(32Q), 3(64Q), 4(128Q)
Post is closed for comments.
Comments
19 comments