SNMP
We are working on a completely new SNMP for RouterOS and we are going to also support SNMP write. Could you please write what you wish to see in RouterOS SNMP support, and what network management programs you now use that have SNMP write support.
Last edited by normis on Mon Feb 19, 2007 1:20 pm, edited 1 time in total.
-
-
Denis Basta
newbie
- Posts: 48
- Joined:
- Location: Latvia, Riga
We're using self-written SNMP client script + iReasoning MIB Browser 3.0.1...
Would be great to have read/write access to:
Would be great to have read/write access to:
- interfaces
ip addresses
routes
queues
system settings
Very good! Looking forward to it.
Now we're using Ipswitch WhatsUp (fading out), InterMapper (my favorite:), Nagios (testing) and a few minor tools.
SNMP-related things springing to mind are:
Traps
Configuration access e.g. interfaces, firewall rules, activating scripts,...
(one more thing, not sure if its possible at all: custom variables by scripting, reachable through SNMP, e.g. for creating own counters or thresholds.)
Now we're using Ipswitch WhatsUp (fading out), InterMapper (my favorite:), Nagios (testing) and a few minor tools.
SNMP-related things springing to mind are:
Traps
Configuration access e.g. interfaces, firewall rules, activating scripts,...
(one more thing, not sure if its possible at all: custom variables by scripting, reachable through SNMP, e.g. for creating own counters or thresholds.)
Here are a few requests:
- More SNMP support for WDS interfaces. Currently, they support ethernet-like interfaces, but it would be nice to join or index based on the registration table so that there are wireless OIDs available along with the standard ethernet statistics. Please let me know if you need more info about this. We currently do this manually by looking up the OIDs.
- OID support for firewall connection counts. We currently do this with scripting, but after so many networks with this running, the script can "miss". What we need is the value for "/ip firewall connection tracking print count-only".
- OID support for DHCP lease count. Similar to above, we run a script that returns "/ip dhcp-server lease print count-only" to obtain lease counts. It'd be handy to poll this with SNMP.
- Apparently there is now support via SNMP for hotspot active user counts. I haven't upgraded to a version that supports this, but please retain it as this is a great one to have.
- In general, anything that supports "print count-only" would be a helpful addition.
Glad to hear you guys are working to improve SNMP support. Keep up the good work!
- More SNMP support for WDS interfaces. Currently, they support ethernet-like interfaces, but it would be nice to join or index based on the registration table so that there are wireless OIDs available along with the standard ethernet statistics. Please let me know if you need more info about this. We currently do this manually by looking up the OIDs.
- OID support for firewall connection counts. We currently do this with scripting, but after so many networks with this running, the script can "miss". What we need is the value for "/ip firewall connection tracking print count-only".
- OID support for DHCP lease count. Similar to above, we run a script that returns "/ip dhcp-server lease print count-only" to obtain lease counts. It'd be handy to poll this with SNMP.
- Apparently there is now support via SNMP for hotspot active user counts. I haven't upgraded to a version that supports this, but please retain it as this is a great one to have.
- In general, anything that supports "print count-only" would be a helpful addition.
Glad to hear you guys are working to improve SNMP support. Keep up the good work!
I would say that it would not just be nice to have everything that has a "print count-only" option, but everything that has a "print" command of any sort.
In fact, I would like to see SNMP become as full-featured as the command line. It should be quite possable, even if some parts get a bit confusing.
Also, adding something like "send SNMP-trap" as a logging action would be pretty cool.
I don't think SNMP is really all that great a management protocol, but it could certainly do the job, and would be better than the hack-job scripts I use now. (In my ideal world, each MT would make it's entire self available as a full featured CORBA object, but that is probably asking way, way too much.)
--Eric
In fact, I would like to see SNMP become as full-featured as the command line. It should be quite possable, even if some parts get a bit confusing.
Also, adding something like "send SNMP-trap" as a logging action would be pretty cool.
I don't think SNMP is really all that great a management protocol, but it could certainly do the job, and would be better than the hack-job scripts I use now. (In my ideal world, each MT would make it's entire self available as a full featured CORBA object, but that is probably asking way, way too much.)
--Eric
Yeah, I've worn a few too many hats in my time. Once upon a time, I even wrote shim code to tie ancient USDA Fortran code in with modern DoD CORBA systems, how wrong is that? 
No, I wouldn't expect the "standard router user" to know about CORBA, but MT isn't exactly a "standard router", nor are it's adherants "standard users".
It's not unheard of to use CORBA systems for network management, though. Actually it's a rather nice fit, being super abstract as it is. While "vendor C" doesn't really do that sort of thing, if you look a bit higher at the likes of Nortel, Lucent, Hauwei, or others in that class, you will find plenty of IDL files available.
I did say it was asking a bit too much, though. Didn't I?
--Eric
No, I wouldn't expect the "standard router user" to know about CORBA, but MT isn't exactly a "standard router", nor are it's adherants "standard users".
It's not unheard of to use CORBA systems for network management, though. Actually it's a rather nice fit, being super abstract as it is. While "vendor C" doesn't really do that sort of thing, if you look a bit higher at the likes of Nortel, Lucent, Hauwei, or others in that class, you will find plenty of IDL files available.
I did say it was asking a bit too much, though. Didn't I?
--Eric
-
-
kapusta_kiszona
Frequent Visitor
- Posts: 70
- Joined:
- Location: Poland
My SNMP wishes...
read access:
* MT version. There is no excuse for not having that now. I have a database to keep track of my MTs, and use SNMP to keep some of the fields updated. We do this with lots of other hardware. I don't have a way to easily determine the version in the MT.
* arp table (real handy in the ISP world since customer computers and firewalls are rarely pingable now)
* dhcp leases
* as many wireless measurements as possible. See what alvarion and other snmp-ready wireless equipment vendors provide by looking at their MIBs.
* mac address of associated/registered radios would be good for my homemade monitoring systems to automatically figure out what is associated to what.
* perhaps temperature/voltage measurements when hardware makes it possible.
* UPS status via SNMP if a Smart-UPS is attached.
Write access:
* ip configuration
* reboot
* factory reset
* bandwidth test server and client functionality. I could have a nasty bash script cronjob on my linux monitoring systems that automatically setup and take down the bandwdith server to run a test between any two systems at various times.
* sniffer streaming start/stop capture and interface selection. To automate traffic capture to my machine running trafr. A tech could enter one command on my system which would start trafr, connect to a MT, stream sniffed data for 30 seconds, stop the stream, stop trafr, and open the data up in ethereal or another program, or perhaps just archive it if I am looking to get samplings over time if the interesting traffic is intermittent.
either a default input rule to block SNMP access not from a particular IP , would be a good default security configuration as well. The user would just set the IP that is allowed and enable the rule, after setting a write community string.
For SNMP software, we use net-snmp (mostly in bash scripts to get snmp data into a text file or mysql), and MRTG on linux.
read access:
* MT version. There is no excuse for not having that now. I have a database to keep track of my MTs, and use SNMP to keep some of the fields updated. We do this with lots of other hardware. I don't have a way to easily determine the version in the MT.
* arp table (real handy in the ISP world since customer computers and firewalls are rarely pingable now)
* dhcp leases
* as many wireless measurements as possible. See what alvarion and other snmp-ready wireless equipment vendors provide by looking at their MIBs.
* mac address of associated/registered radios would be good for my homemade monitoring systems to automatically figure out what is associated to what.
* perhaps temperature/voltage measurements when hardware makes it possible.
* UPS status via SNMP if a Smart-UPS is attached.
Write access:
* ip configuration
* reboot
* factory reset
* bandwidth test server and client functionality. I could have a nasty bash script cronjob on my linux monitoring systems that automatically setup and take down the bandwdith server to run a test between any two systems at various times.
* sniffer streaming start/stop capture and interface selection. To automate traffic capture to my machine running trafr. A tech could enter one command on my system which would start trafr, connect to a MT, stream sniffed data for 30 seconds, stop the stream, stop trafr, and open the data up in ethereal or another program, or perhaps just archive it if I am looking to get samplings over time if the interesting traffic is intermittent.
either a default input rule to block SNMP access not from a particular IP , would be a good default security configuration as well. The user would just set the IP that is allowed and enable the rule, after setting a write community string.
For SNMP software, we use net-snmp (mostly in bash scripts to get snmp data into a text file or mysql), and MRTG on linux.
cacti? no problem with it already:
http://forum.mikrotik.com//viewtopic.ph ... ight=cacti
http://forum.mikrotik.com//viewtopic.ph ... ight=cacti
Re: SNMP
An oid to reboot, but not oids for reset or shutdown as they would be unnecessary and potentially harmful.We are working on a completely new SNMP for RouterOS and we are going to also support SNMP write. Could you please write what you wish to see in RouterOS SNMP support, and what network management programs you now use that have SNMP write support.
Oid's to execute scripts. E.g. write 0 => 1 (equals reboot)
Oid's to save config to specified name. E.g. "" => "myconfig" (equals saving config as myconfig.backup)
Oid's to restort config from specified name. E.g. "" => "myconfig" (equals loading myconfig.backup)
Oid's for (for example) 5-10 static oids which one may put strings and which scripts could read.
Error counters for all interfaces.
-
-
andreacoppini
Trainer
- Posts: 498
- Joined:
- Location: Malta, Europe
-
-
incoming429
just joined
- Posts: 16
- Joined:
MT version
i use this oid to get the fw version (2.9 only): .1.3.6.1.4.1.14988.1.1.4.4.0My SNMP wishes...
read access:
* MT version. There is no excuse for not having that now. I have a database to keep track of my MTs, and use SNMP to keep some of the fields updated. We do this with lots of other hardware. I don't have a way to easily determine the version in the MT.
the docs are incomplete about the oids
just do a snmpwalk and you get quite an interesting list
regards,
michal
Re: MT version
NICE! Thanks a bunch for that oid!
i use this oid to get the fw version (2.9 only): .1.3.6.1.4.1.14988.1.1.4.4.0
the docs are incomplete about the oids
just do a snmpwalk and you get quite an interesting list
regards,
michal
while I'm on the topic, how can the "upgradable-till" oid be converted from hex to text. I am basically looking for a human readable text date with year/month/day or similar.
Code: Select all
[admin@bht] > /system license print
software-id: "xxxxxxx"
upgradable-until: sep/01/2006
nlevel: 3
features:
[admin@bht] > /system license print oid
software-id: .1.3.6.1.4.1.14988.1.1.4.1.0
upgradable-until: .1.3.6.1.4.1.14988.1.1.4.2.0
level: .1.3.6.1.4.1.14988.1.1.4.3.0
mocha:/usr/local/mis/bin # snmpwalk -v1 -c public 10.0.1.5 .1.3.6.1.4.1.14988.1.1.4.2.0
SNMPv2-SMI::enterprises.14988.1.1.4.2.0 = Hex-STRING: 07 D6 09 01 00 00 00 00
-
-
incoming429
just joined
- Posts: 16
- Joined:
Hi,while I'm on the topic, how can the "upgradable-till" oid be converted from hex to text. I am basically looking for a human readable text date with year/month/day or similar.
Code: Select all[admin@bht] > /system license print software-id: "xxxxxxx" upgradable-until: sep/01/2006 nlevel: 3 features: [admin@bht] > /system license print oid software-id: .1.3.6.1.4.1.14988.1.1.4.1.0 upgradable-until: .1.3.6.1.4.1.14988.1.1.4.2.0 level: .1.3.6.1.4.1.14988.1.1.4.3.0 mocha:/usr/local/mis/bin # snmpwalk -v1 -c public 10.0.1.5 .1.3.6.1.4.1.14988.1.1.4.2.0 SNMPv2-SMI::enterprises.14988.1.1.4.2.0 = Hex-STRING: 07 D6 09 01 00 00 00 00
the first two hexs concatenated are the year, the 3rd is the month and the
4th is the day
Converted to dec it looks like this:
perl -e 'printf "%d. %d. %d\n", 0x01, 0x09, 0x07d6'
1. 9. 2006
So your copy is upgradable until 1st september 2006
Best regards,
Michal
Now, I can have my database automatically update the version and hostname of my Mikrotiks! I run this script with cron each day. I use the database both as a glorified inventory spreadsheet, and to feed other scripts such as one that makes mrtg config files.
For some reason, I can't get bash to print the month properly. I could use the perl example, but I'm almost there and don't want to need two scripting languages to convert a hex date to decimal.
Code: Select all
# more db.update.mt
#!/bin/bash
MYCMD="mysql -B -N -h 127.0.0.1 -u xxxxxxxx -s -pxxxxxx -e "
for IP in `$MYCMD " use mt; select ip from router;"` ; do
VER=`snmpget -r2 -v1 -c public -Ovq $IP .1.3.6.1.4.1.14988.1.1.4.4.0 |cut -d" " -f1|sed -e "s/\"//g"`
NAME=`snmpget -r2 -v1 -c public -Ovq $IP SNMPv2-MIB::sysName.0 |cut -d: -f4`
$MYCMD "use mt; update router set version='$VER' where IP='$IP'"
$MYCMD "use mt; update router set hostname='$NAME' where ip='$IP'"
done
Code: Select all
mocha:/usr/local/mis/bin # cat getle
#!/bin/bash
HEXDATE=`snmpget -r2 -v1 -c public -Ovq $1 .1.3.6.1.4.1.14988.1.1.4.2.0`
CDHEXDATE=`echo 0x$HEXDATE |sed -e "s/\"//g" |sed -e "s/ //g"`
echo $HEXDATE
echo 0123456789
echo $CDHEXDATE
YEAR=`echo $CDHEXDATE|cut -b0-6`
echo YEAR
printf "%d\n" $YEAR
MONTH=`echo $CDHEXDATE|cut -b7-8`
echo MONTH
printf "%d\n" $MONTH
DAY=`echo $CDHEXDATE|cut -b9-10`
echo DAY
printf "%d\n" $DAY
mocha:/usr/local/mis/bin # ./getle 10.0.1.5
"07 D6 09 01 00 00 00 00 "
0123456789
0x07D6090100000000
YEAR
2006
MONTH
./getle: line 14: printf: 09: invalid number
0
DAY
1
mocha:/usr/local/mis/bin #
-
-
incoming429
just joined
- Posts: 16
- Joined:
maybe something like this?Now, I can have my database automatically update the version and hostname of my Mikrotiks! I run this script with cron each day. I use the database both as a glorified inventory spreadsheet, and to feed other scripts such as one that makes mrtg config files.
For some reason, I can't get bash to print the month properly. I could use the perl example, but I'm almost there and don't want to need two scripting languages to convert a hex date to decimal.Code: Select all# more db.update.mt #!/bin/bash MYCMD="mysql -B -N -h 127.0.0.1 -u xxxxxxxx -s -pxxxxxx -e " for IP in `$MYCMD " use mt; select ip from router;"` ; do VER=`snmpget -r2 -v1 -c public -Ovq $IP .1.3.6.1.4.1.14988.1.1.4.4.0 |cut -d" " -f1|sed -e "s/\"//g"` NAME=`snmpget -r2 -v1 -c public -Ovq $IP SNMPv2-MIB::sysName.0 |cut -d: -f4` $MYCMD "use mt; update router set version='$VER' where IP='$IP'" $MYCMD "use mt; update router set hostname='$NAME' where ip='$IP'" done
Code: Select allmocha:/usr/local/mis/bin # cat getle #!/bin/bash HEXDATE=`snmpget -r2 -v1 -c public -Ovq $1 .1.3.6.1.4.1.14988.1.1.4.2.0` CDHEXDATE=`echo 0x$HEXDATE |sed -e "s/\"//g" |sed -e "s/ //g"` echo $HEXDATE echo 0123456789 echo $CDHEXDATE YEAR=`echo $CDHEXDATE|cut -b0-6` echo YEAR printf "%d\n" $YEAR MONTH=`echo $CDHEXDATE|cut -b7-8` echo MONTH printf "%d\n" $MONTH DAY=`echo $CDHEXDATE|cut -b9-10` echo DAY printf "%d\n" $DAY mocha:/usr/local/mis/bin # ./getle 10.0.1.5 "07 D6 09 01 00 00 00 00 " 0123456789 0x07D6090100000000 YEAR 2006 MONTH ./getle: line 14: printf: 09: invalid number 0 DAY 1 mocha:/usr/local/mis/bin #
Code: Select all
#!/bin/sh
OUT=`snmpget -r2 -v1 -c public -Ovq $1 .1.3.6.1.4.1.14988.1.1.4.2.0 |sed 's!\"!!g'`
YEAR=`echo $OUT |awk '{printf "%d", strtonum("0x" $1 $2)}'`
MONTH=`echo $OUT |awk '{printf "%d", strtonum("0x" $3)}'`
DAY=`echo $OUT |awk '{printf "%d", strtonum("0x" $4)}'`
Michal
-
-
conchalnet
Member Candidate
- Posts: 274
- Joined:
- Location: Brazil
Netwatch -> SNMP
Netwatch (tools->netwatch) status of every host will be very helpful. Just up/down flag, nothing more.
BGP peers -> SNMP
Welldone, BGP in >2.9.20 looks great. SNMP status of every peer would be fine (Instance, Remote Address, Remote AS, Remote ID, Uptime, Prefix count and State).
1. Netwatch (tools->netwatch). It should´t be a trap, but simple OIDs for every Netwatch Host and his Status and Since.Can you be more specific on you SNMP requests? What traps would you like to see? What is THE SNMP feature that you miss the most now?
2. BGP - status of every peer (Instance, Remote Address, Remote AS, Remote ID, Uptime, Prefix count and State) will be very helpful.
SNMP Community in multiple subnets
We need to be able to use the same community string in different/multiple subnets.
-
-
BrianHiggins
Forum Veteran
- Posts: 702
- Joined:
- Location: Norwalk, CT
- Contact:
COOL!actually we are also preparing an open API for configuration of the router, so you can develop your own applications that connect to the router and configure/control it. this is not connected to SNMP but i guess you will also like that
This is a really cool thing I need in RouterOS!In SNMP I'd like to see traps about extreme CPU and system temperature, extreme CPU load, failure of all the fans, that can be detected by system, change in state of serial or parallel port lines (to use it for any custom sensors like detection of opening of the box, where the router stands).
You can use a radius server for administrator authentication, quite easily. Linking device administration access to an employee database can automate the whole process, without the need to alter individual device configs (via SNMP, or otherwise).add or delete user and change their permissions.
We have tech support that come and go. They take a look from the tower at the client which is very helpful. Big pain to go do this to every access point we have manually.
--Eric
-
-
BrianHiggins
Forum Veteran
- Posts: 702
- Joined:
- Location: Norwalk, CT
- Contact:
it seems that Sergejs either A.) didn't actually read the content of my email before writing back to me, or B.) he wants me to post it here... either way, here it is...
now can we get accurate interface speeds to be reported by SNMP? I hate having 10-15mb link speeds on routers that are reported as 100mbps because it's a ethernet uplink, and 11mbps link speeds reported for 802.11a nstream links that are actually pushing 20mbps...
now can we get accurate interface speeds to be reported by SNMP? I hate having 10-15mb link speeds on routers that are reported as 100mbps because it's a ethernet uplink, and 11mbps link speeds reported for 802.11a nstream links that are actually pushing 20mbps...
Re: [Ticket#2006071416000037] SNMP interface speed
Hello Brian,
To view available OIDs,
you can type e.g. 'queue simple print oid'.
Follow this topic about SNMP,
http://forum.mikrotik.com//viewtopic.php?t=7453
Regards,
Sergejs
"Brian Higgins" wrote:
> is there any way to set the interface speed that is reported via SNMP?
> our monitoring system reads the reported speed and bases it's graphing
> off of what it reads. we have a vlan that is pushing about 8mpbs (SNMP
> says the interface speed is 10mbps), and we get constant alerts about
> the utilization because it's over 80% of the reported speed. we also
> have similar issues with our APs because they are reported as 11mbps,
> but they are 802.11a radios running at 24mbps.
>
> if this is not yet possible, can you please add this ability into 2.10
> (or sooner??)
>
> For Ethernet interfaces that are hooked into other connections such as
> a DSL modem this would be nice as well so we can specify that the
> interface speed is actually 3.0mbps even though it is a 100mbps
> Ethernet port.
-
-
BrianHiggins
Forum Veteran
- Posts: 702
- Joined:
- Location: Norwalk, CT
- Contact:
-
-
BrianHiggins
Forum Veteran
- Posts: 702
- Joined:
- Location: Norwalk, CT
- Contact:
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 speed
Hello 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
-
-
ParisDragon
newbie
- Posts: 32
- Joined:
- Location: NorthEast Texas, USA
- Contact:
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 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.
macro and micro
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'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.
-
-
ParisDragon
newbie
- Posts: 32
- Joined:
- Location: NorthEast Texas, USA
- Contact:
SNMP OID
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 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
-
-
BrianHiggins
Forum Veteran
- Posts: 702
- Joined:
- Location: Norwalk, CT
- Contact:
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)I wouldn't mind an OID for # of ppp users connected.
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...
Re: SNMP
For me, at first read access to some numbers:We are working on a completely new SNMP for RouterOS and we are going to also support SNMP write. Could you please write what you wish to see in RouterOS SNMP support, and what network management programs you now use that have SNMP write support.
- 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
-
-
stephenpatrick
Forum Veteran
- Posts: 702
- Joined:
- Location: UK
- Contact: