the speed already is available… the problem is that it doesn’t always show anything even close to accurate… all 802.11 links, even if it’s a 5.8Ghz NStream Dual show as 11mbps
I was thinking about speed decription.
Sergejs’s response to this issue, and then my response to him (at the top)
I would like to simply set the interface speed in my monitoring application, but that is not an option, it’s not an option in many monitoring applications. I am also emailing the vendor of my monitoring system(IPSwitch What Up Professional 2006) for the ability to change it in there.
I am asking you to change it as well, as ROS is reporting things incorrectly (see my comments about my wireless links) so when you go to fix that, I would just like to see the following option added to any available interface ex. snmpinterfacespeed=######## then when any SNMP probe reads the standard 1.3.6.1.2.1.2.2.1.5.# OID, it reports the value specified by snmpinterfacespeed. Then when I probe my wlan interfaces, they do not show up as 11mbps, regardless of what radio and config I have, or when I have a interface connected to a wireless bridge (like an orthogon link) I can change the interface speed to reflect the speed of the link in the middle, not the speed of the ethernet port that it’s connecting to…
Brian
-----Original Message-----
From: MikroTik Support [Sergejs] [mailto:> support@mikrotik.com> ]
Sent: Tuesday, July 18, 2006 7:47 AM
To: Brian Higgins
Subject: Re: [Ticket#2006071416000037] SNMP interface speedHello Brian,
Probably you can set appropriate configuration in external monitoring server, that will show desired values, e.g. traffic below 8 Mbps.
It’s possible to set name to each monitored value (interface, queue simple, queue tree etc.), where you can set ‘VLAN1 8mbps limit’, that will indicate it’s VLAN1 interface with ‘8 mbps’ limit.Regards,
Sergejs
Right now the only SNMP I find missing in 2.9.27 is I cant pull the signal strengths and trasmits speeds from an Nstreme Dual Link. I have written a procedure to log the levels into a file, but then I must download it, convert it to the proper format, import it etc., big pain when all my half duplex single radio links/clients signals are readily availiable via SNMP.
It would also be nice if you could have ONLY a certain set of items return for the public community. For example I put all this nice info good for me in and public could read too much info. I would like Public to only be able to pull name, system name, contact and nothing else, so if they see my radio and SNMP poll it they know how to reach me if interference is occuring.
It would be nice to have OID´s for noise floor, Signal to noise and Tx/Rx CCQ.
I’m new to this forum. But I’m probably gonna be lurkin quite a bit.
I’m new to microtik too. I’m here, of course, 'cause it seems likely to be a solution to my problems.
It’s been a long, long time since I last had to mess with subnet masks, and IOS syntax. So in some areas, I’m starting over.
I’m not new to Networks, Systems, or the care and feeding thereof.
This includes Large Enterprise, Network Management systems, Operations Systems,
I’d like to suggest that we break this thread into at least 2 parts.
the First being EMS/NMS/OSS architecture and design as it applies to RouterOS, Dude, and foreign NMS compatibility.
Others could be operational details such as agents, Active OIDs, Traps and trap contents, etc.
On a Macro Level, I’d like to suggest that;
Just about any Security issue that’s gonna get fixed, will be first approached with rigorous SNMP V3 compliance. Any, and every other hole will have to be dealt with at other layers. A decent Key Manager would be heaven at this point.
When mentioning things like CORBA, or any other ORB or Message Bus,
If you needed Middleware, You’d be running WebSphere already.
IBM will give it to you if you ask nice.
SNMP exists, because IP exists. If you’re not aware of the difference between TCP and UDP, or the effects of Connection Overhead, then your not gonna understand why XML (or any other) based messaging for management automation is tough to do.
As Hairy, Hoary, and Old fashioned as ANS is, it works well if done well.
If your desperate enough, You might want to take a look at CA’s press on the latest Unicenter.
The most lightweight ORB you’re gonna find, is not gonna fit on a Routerbox anytime soon. various gateways abound that’ll repackage
SNMP as messages. But, I’d not ask Microtik to spend manhours on them.
There’s some nice PeertoPeer stuff around that looks like it may overlay meshes quite nicely. When We see multiprocessor Routerboards and Multigigabyte Flash that runs at multiples of bus speed, the software may be ready.
If, in our Lifetime, We see solid SNMP v3 with active OIDs for the majority of volatile variables and tables, We’ll be way ahead of the game.
We can get a decent picture of how to prioritize OID development and release by concentrating First, on the ones that help avoid Truck Rolls.
RouterOS exists to keep us off towers in the dark and cold. It may be worthwhile to keep that in mind.
In the meantime, All your scripts and code snippets, If shared out and tested, will fill in the gaps while the Microtik team concentrates on the good stuff.
It’s nice to hear that you have a solution for your problem. It’d be even nicer to hear that you have a solution for mine.
I am grateful that the mac address is used to pinpoint the OID of a remote radio, what I dont understand is why the UID for signal strength ends with different numbers, sometimes its always .4, update the OS and it might become .1835 on one box but remain .4 on another, which breaks monitoring scripts I use on MRTG externally. For example:
I was pulling the signal Strength on a backhaul using the OID:
1.3.6.1.4.1.14988.1.1.1.2.1.3.0.96.179.92.190.20.4
it remained this OID from v 2.9.27 (when I first did it) until I went to 2.9.30 the OID changed to 1.3.6.1.4.1.14988.1.1.1.2.1.3.0.96.179.92.190.20.1835 for the same registrered client.
So I thought, ok they switch the ending OID entry for signal strength from .4 to .1835. So I checked other backhauls I upgraded, some remained .4, others changed to .1835 and some to .3 on the end when upgrading. If this isnt by design please look into fixing it, if this is by design then please consider making signal strength OIDs remain the same on a box unless of course the remote radio MAC changes so as to keep remote SNMP monitoring and graphing from halting or falsely reporting issues. Thanks
I wouldn’t mind an OID for # of ppp users connected.
I’ll 2nd that request (usefull for seeing if you have connection issues causing users to drop off durring storms or something, as well as tracking IP allocations)
It would be nice to have OID´s for noise floor, Signal to noise and Tx/Rx CCQ.
I think I asked for this once before… would be very nice to track for historical trending…
I’ve writen that many times:
get full info from wireless registration table
I need at least: tx-signal-strenght,interface,SNR
For me, at first read access to some numbers:
- number of dhcp leases (how many all, radius, pool and so on)
- number of hotspot entries (how many authenticated, how many not),
- number of entries in routing table (how many ospf, bgp, static)
And write access I would need mostly for ip address-lists. I use address lists for several things and sometimes there is a need to update the lists on all routers. SNMP write access could help us a lot.
Regards,
Gregor
Can we have write access to the interface byte counters?
I would like to have read access to /ip neighbour print
Is there going to be support for SNMPV3 ?
[asked for by some major potential customers]
Regards
CableFree Solutions
So..when the support of new snmp features will be ready to try?