It is possible get information about snr, ack, noise by snmp in mt 3.30 at wds/ap/client mode?
I only can get information about: signal, band, ssid, frequency, tx/rx rate.
in wi pr oid
0 tx-rate=.1.3.6.1.4.1.14988.1.1.1.1.1.2.3
rx-rate=.1.3.6.1.4.1.14988.1.1.1.1.1.3.3
strength=.1.3.6.1.4.1.14988.1.1.1.1.1.4.3
ssid=.1.3.6.1.4.1.14988.1.1.1.1.1.5.3
bssid=.1.3.6.1.4.1.14988.1.1.1.1.1.6.3
frequency=.1.3.6.1.4.1.14988.1.1.1.1.1.7.3
band=.1.3.6.1.4.1.14988.1.1.1.1.1.8.3
Hello,
you can get little more info with this about people connected or your links:
interface wireless registration-table pri oid
0 ;;; gigtech
strength=.1.3.6.1.4.1.14988.1.1.1.2.1.3.0.14.142.12.16.41.16
tx-bytes=.1.3.6.1.4.1.14988.1.1.1.2.1.4.0.14.142.12.16.41.16
rx-bytes=.1.3.6.1.4.1.14988.1.1.1.2.1.5.0.14.142.12.16.41.16
tx-packets=.1.3.6.1.4.1.14988.1.1.1.2.1.6.0.14.142.12.16.41.16
rx-packets=.1.3.6.1.4.1.14988.1.1.1.2.1.7.0.14.142.12.16.41.16
tx-rate=.1.3.6.1.4.1.14988.1.1.1.2.1.8.0.14.142.12.16.41.16
rx-rate=.1.3.6.1.4.1.14988.1.1.1.2.1.9.0.14.142.12.16.41.16
but there isnt snr.
it is possile get information about snr by snmp? whats oid responsible for snr ?
Whats is oid for noise-floor? i can calculate snr from signal and noise.
When i check:
[admin@acht] /interface wireless> monitor 3
status: running-ap
band: 5ghz
frequency: 5180MHz
noise-floor: -102dBm
overall-tx-ccq: 100%
registered-clients: 1
authenticated-clients: 1
current-ack-timeout: 38
nstreme: no
current-tx-powers: 6Mbps:17(17),9Mbps:17(17),12Mbps:17(17),18Mbps:17(17),24Mbps:17(17),36Mbps:16(16),48Mbps:14(14),54Mbps:13(13)
notify-external-fdb: no
Why i cant get this information by snmp? i can get signal but cant get ack, snr, noise… !!! think that isnt very difficult upgrade mt for code to provide this data to snmp? snmp is standart for monitoring network routers.
it is possible to get snr, ack, noise by api ?
you already found out how to do the “print oid” command. that’s all there is. there are no hidden oids
if i good understand that mean that i cant get information about ack, snr, noise by snmp by oids. right?
only api?
GringoZ,
There isnt an OID for everything you might need to have. However, the answer lies within the interface. As Normis says, you already used a command to show the OIDs. In the same case, the radio certainly knows what the SNR is, as well as many other valuable metrics. The radio is calculating, or acquiring from internal hardware the SNR value, and RouterOS is displaying it. In using MT for years, I have learned that if it is displayed somewhere, it is a value that is available, but not necessarily through SNMP.
Enter into the world of the command line, and then graduate to scripting. Try manually ‘getting’ or ‘setting’ values in areas you are familiar with. Once you discover how to create your own variable for the value you desparately need (as always!), use the Dude ros_command, and grab the value of the variable you have created. It can be created with a script if necessary, or you can carefully execute ros_command statements right from the label in the device icon, as you would have using the oid. You will have then created your own set of ‘oid’s’ that will become very useful in all areas of monitoring using The Dude. It takes a while, and is frustrating at times, but when you figure out that the radio has it, you wont be far from displaying or using the value in many different ways. Some command line techniques are quite esoteric, and you will swear all night that you ‘just tried it before and it didnt work’, and suddenly it works, but you just cant remember how you got there.
Discover the ways of the Mikrotik paradigm, i.e. knowledge and an open pallete of capability that ROS delivers allows the operator to create whatever environment works for your specific application. Thats the only way I ever figured out how to develop ‘never before seen’ displays. These things are a great benefit of the ROS environment, but at the price of finding the correct way to extract the functionality and/or data yourself.
You will feel great accomplishment once something finally works and is just what you needed.
BTW, learn by example (hint, hint). There is a great wealth of knowledge in the scripting section of the wiki. There are many examples of working scripts that show you how to do some not so obvious tasks. I know it helped me a great deal, and we really owe a lot to the many gratious developers who have submitted these scripts. There is no shame, and in fact, there is great joy in cutting and pasting something, and it works!
I would like also to vote for adding following oids.
rx-ccq
tx-ccq
signal-to-noise
Thanks. Maybe sometime in the far future 
does anyone know how to get source and compile the tinysnmpd mikrotik.so file? I see it included in ubnt and madwifi stuff, I think if we can update that module mikrotik will inherit it.
This post was really excellent advice and made me think about several other ways to get data into the Dude. Many thanks. 
If you need to monitor some of the MT router and you can find on the router by a cli command, you can use script and send it ut using Syslog.
Look at the prosject in my Signature. The you will see that much of the information I do graph are coming from Script that sends it out to Splunk using Syslog. Nice thing with that is that I do not need to telle the monitor system to add a new device. All devices with script in them shows up automatically.