v6.47beta [testing] is released!

emils · December 10, 2019, 2:49pm

Version 6.47beta8 has been released.

Before an upgrade:

Remember to make backup/export files before an upgrade and save them on another storage device;
Make sure the device will not lose power during upgrade process;
Device has enough free storage space for all RouterOS packages to be downloaded.

What’s new in 6.47beta8 (2019-Dec-10 10:33):

Changes in this release:

*) console - fixed “clear-history” restoring historic actions after power cycle;
*) console - removed “edit” and “set” actions from “System/History” menu;
*) crs3xx - fixed “ingress-rate” property on CRS309-1G-8S+, CRS312-4C+8XG, CRS326-24S+2Q+ devices;
*) defconf - fixed default configuration loading after fresh install (introduced in v6.46);
*) dhcpv6-client - improved error logging when when renewed address differs;
*) fetch - fixed “User-Agent” usage if provided by “http-header-field”;
*) health - fixed health reporting on OmniTIK 5 PoE ac;
*) health - improved health reporting on CCR1072-1G-8S+;
*) ipsec - improved system stability when processing decrypted packet on unregistred interface;
*) l2tp - improved system stability when disconnecting many clients at once;
*) lora - improved confirmed downlink forwarding;
*) lte - do not reset modem when setting the same SIM slot on LtAP;
*) lte - fixed multiple APN reactivation after deactivation by operator;
*) lte - show SIM error when no card is present;
*) netinstall - removed “Flashfig” from Netinstall;
*) netinstall - removed “Make Floppy” from Netinstall;
*) netinstall - signed netinstall.exe with Digital Signature;
*) ppp - prioritize “remote-ipv6-prefix-pool” from PPP secret over PPP profile;
*) snmp - added “dot1qTpFdbTable” OID reporting for Q-BRIDGE-MIB;
*) snmp - fixed “dot1dBasePort” index offset for BRIDGE-MIB;
*) snmp - fixed health related OID polling (introduced in v6.46);
*) snmp - improved stability when polling MAC address related OID;
*) supout - fixed autosupout.rif file generation (introduced in v6.46);
*) w60g - use “arp” and “mtu” parameters from master interface when creating a new station;
*) winbox - added “auto-erase” option to “Tool/SMS” menu;
*) winbox - fixed “allowed-number” parameter setting invalid value in “Tool/SMS” menu;
*) winbox - show “LCD” menu only on boards that have LCD screen;
*) wireless - improved compatibility by adding default installation mode and gain for devices with integrated antennas;
*) wireless - improved compatibility for Switzerland wireless country profile to improve compliance with ETSI regulations;

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as expected or after crash.

bnw · December 10, 2019, 2:53pm

Could you elaborate please ?
Did not experience any SNMP heath issue with 6.46 yet.
Thank you !

bnw · December 10, 2019, 2:56pm

http://forum.mikrotik.com/t/missing-mikrotik-snmp-oids/105182/1

I opened #2019032822004818 a few months ago, many SNMP hardware OIDs are missing for the CCR1072, compared to what Winbox shows :

Board temperature

Board temparature 2

Fan speed 3

Fan speed 4

PSU1 status (should be OID .15 (*))

PSU2 status (should be OID .16 ())
() as seen on other models such as the CRS317-1G-16S+.

We are then clearly at risk with our CCR1072-1G-8S+, not being able to monitor all their hardware components, which is a rather tricky situation for core devices.

And hope to see this in 6.47 finally !
Many thx !

emils · December 10, 2019, 3:10pm

bnw, should affect only a few CRS devices (CRS3xx).

anuser · December 10, 2019, 8:02pm

Will we already get MU-MIMO support within 6.47beta release?

strods · December 11, 2019, 5:12am

In v6.47beta there is a new menu added - “/system health gauges”. You should use this for polling “Health” related data from all the RouterBOARDs.

joegoldman · December 11, 2019, 6:59am

Does this come with new associated MIBs / OID’s? Or more for polling via API?

bnw · December 11, 2019, 7:29am

Interesting. And if available through SNMP, will these “gauges” give the PSUs status (which are for now missing on CCR1072 as stated above) ?

ivicask · December 11, 2019, 9:22am

When is ROMON getting fixed?I need some other fixes from new betas, but they also break ROMON..

mistry7 · December 11, 2019, 9:26am

shure on xmas, but you don’t will get any year…

strods · December 11, 2019, 10:37am

ivicask - Have you reported this problem to support@mikrotik.com or https://help.mikrotik.com/servicedesk/customer/user/login?destination=portals ?? We are not aware of any RoMON problems;

CoMMyz · December 11, 2019, 5:09pm

*) netinstall - removed “Flashfig” from Netinstall;

Can you please elaborate? Is this feature removed completely or just moving to a standalone executable ?

kmrue · December 14, 2019, 5:26pm

as no UPS-bugfixing is listed I tested anyhow:
UPS still not working with APC SMT750I, SMT1000I, SMT1500I (to name just 3 models). All of them connected via their USB-port. They all get identified, but only a few parameters get transferred to the routerboard. Tested using CRS125.

Is there anything you guys @ mikrotik want me to further check out?

ivicask · December 14, 2019, 7:08pm

But some of your support confirmed it here, post #5
http://forum.mikrotik.com/t/v6-46rc-testing-is-released/135019/3

Guscht · December 14, 2019, 10:43pm

Hoped the snmp-IP-Forward MIB is fixed as well.

We get still a “no such object” error with 6.47beta8:

Testing OIDs...
14.12.2019 23:31:27 (98726 ms) : SNMP Datatype: ASN_UNSIGNED
Test 1.3.6.1.2.1.4.24.3.0: value=3 #
14.12.2019 23:31:28 (99944 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.1.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
14.12.2019 23:31:30 (101377 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.1.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
14.12.2019 23:31:31 (102658 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.1.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #
14.12.2019 23:31:32 (103789 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.2.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
14.12.2019 23:31:33 (104495 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.2.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
14.12.2019 23:31:33 (105034 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.2.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #
14.12.2019 23:31:35 (106269 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.3.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
14.12.2019 23:31:36 (107475 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.3.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
14.12.2019 23:31:37 (108783 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.3.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #
14.12.2019 23:31:39 (110254 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.4.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
14.12.2019 23:31:40 (111267 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.4.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
14.12.2019 23:31:40 (111839 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.4.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #
14.12.2019 23:31:41 (112396 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.5.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
14.12.2019 23:31:42 (113092 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.5.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
14.12.2019 23:31:42 (113881 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.5.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #
14.12.2019 23:31:43 (114760 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.6.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
14.12.2019 23:31:44 (115728 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.6.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
14.12.2019 23:31:45 (116158 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.6.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #
14.12.2019 23:31:45 (116616 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.7.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
14.12.2019 23:31:46 (117546 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.7.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
14.12.2019 23:31:47 (118558 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.7.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #
14.12.2019 23:31:48 (119709 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.8.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
14.12.2019 23:31:50 (121071 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.8.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
14.12.2019 23:31:51 (122398 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.8.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #
14.12.2019 23:31:52 (123440 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.10.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
14.12.2019 23:31:53 (124483 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.10.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
14.12.2019 23:31:54 (125600 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.10.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #
14.12.2019 23:31:55 (126839 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.11.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
14.12.2019 23:31:56 (127828 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.11.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
14.12.2019 23:31:58 (129141 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.11.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #
14.12.2019 23:31:58 (129730 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.12.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
14.12.2019 23:31:59 (130054 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.12.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
14.12.2019 23:31:59 (130798 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.12.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #
14.12.2019 23:32:00 (131935 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.13.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
14.12.2019 23:32:01 (132994 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.13.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
14.12.2019 23:32:03 (134092 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.13.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #
14.12.2019 23:32:04 (135693 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.14.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
14.12.2019 23:32:05 (136548 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.14.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
14.12.2019 23:32:06 (137167 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.14.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #
14.12.2019 23:32:06 (137965 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.15.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
14.12.2019 23:32:07 (138930 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.15.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
14.12.2019 23:32:09 (140092 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.15.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #
14.12.2019 23:32:10 (141385 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.16.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
14.12.2019 23:32:11 (142697 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.16.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
14.12.2019 23:32:13 (144062 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.16.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #

With 6.45.7 (or less) a good result:

Testing OIDs...
14.12.2019 23:34:53 (6895 ms) : SNMP Datatype: ASN_UNSIGNED
Test 1.3.6.1.2.1.4.24.3.0: value=3 #
14.12.2019 23:34:53 (7012 ms) : SNMP Datatype: ASN_IPADDRESS
Test 1.3.6.1.2.1.4.24.4.1.1.0.0.0.0.0.0.0.0.0.10.10.0.1: value=0.0.0.0 #
14.12.2019 23:34:53 (7128 ms) : SNMP Datatype: ASN_IPADDRESS
Test 1.3.6.1.2.1.4.24.4.1.1.10.10.0.0.255.255.252.0.0.10.10.0.70: value=10.10.0.0 #
14.12.2019 23:34:53 (7245 ms) : SNMP Datatype: ASN_IPADDRESS
Test 1.3.6.1.2.1.4.24.4.1.1.192.168.11.0.255.255.255.0.0.192.168.11.1: value=192.168.11.0 #
14.12.2019 23:34:53 (7361 ms) : SNMP Datatype: ASN_IPADDRESS
Test 1.3.6.1.2.1.4.24.4.1.2.0.0.0.0.0.0.0.0.0.10.10.0.1: value=0.0.0.0 #
14.12.2019 23:34:53 (7620 ms) : SNMP Datatype: ASN_IPADDRESS
Test 1.3.6.1.2.1.4.24.4.1.2.10.10.0.0.255.255.252.0.0.10.10.0.70: value=255.255.252.0 #
14.12.2019 23:34:54 (7937 ms) : SNMP Datatype: ASN_IPADDRESS
Test 1.3.6.1.2.1.4.24.4.1.2.192.168.11.0.255.255.255.0.0.192.168.11.1: value=255.255.255.0 #
14.12.2019 23:34:54 (8054 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.3.0.0.0.0.0.0.0.0.0.10.10.0.1: value=0 #
14.12.2019 23:34:54 (8172 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.3.10.10.0.0.255.255.252.0.0.10.10.0.70: value=0 #
14.12.2019 23:34:54 (8288 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.3.192.168.11.0.255.255.255.0.0.192.168.11.1: value=0 #
14.12.2019 23:34:54 (8447 ms) : SNMP Datatype: ASN_IPADDRESS
Test 1.3.6.1.2.1.4.24.4.1.4.0.0.0.0.0.0.0.0.0.10.10.0.1: value=10.10.0.1 #
14.12.2019 23:34:55 (8753 ms) : SNMP Datatype: ASN_IPADDRESS
Test 1.3.6.1.2.1.4.24.4.1.4.10.10.0.0.255.255.252.0.0.10.10.0.70: value=10.10.0.70 #
14.12.2019 23:34:55 (8878 ms) : SNMP Datatype: ASN_IPADDRESS
Test 1.3.6.1.2.1.4.24.4.1.4.192.168.11.0.255.255.255.0.0.192.168.11.1: value=192.168.11.1 #
14.12.2019 23:34:55 (8997 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.5.0.0.0.0.0.0.0.0.0.10.10.0.1: value=11 #
14.12.2019 23:34:55 (9161 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.5.10.10.0.0.255.255.252.0.0.10.10.0.70: value=11 #
14.12.2019 23:34:55 (9375 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.5.192.168.11.0.255.255.255.0.0.192.168.11.1: value=12 #
14.12.2019 23:34:55 (9626 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.6.0.0.0.0.0.0.0.0.0.10.10.0.1: value=4 #
14.12.2019 23:34:56 (9831 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.6.10.10.0.0.255.255.252.0.0.10.10.0.70: value=3 #
14.12.2019 23:34:56 (9979 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.6.192.168.11.0.255.255.255.0.0.192.168.11.1: value=3 #
14.12.2019 23:34:56 (10094 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.7.0.0.0.0.0.0.0.0.0.10.10.0.1: value=3 #
14.12.2019 23:34:56 (10210 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.7.10.10.0.0.255.255.252.0.0.10.10.0.70: value=2 #
14.12.2019 23:34:56 (10325 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.7.192.168.11.0.255.255.255.0.0.192.168.11.1: value=2 #
14.12.2019 23:34:56 (10581 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.8.0.0.0.0.0.0.0.0.0.10.10.0.1: value=0 #
14.12.2019 23:34:57 (10794 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.8.10.10.0.0.255.255.252.0.0.10.10.0.70: value=0 #
14.12.2019 23:34:57 (10907 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.8.192.168.11.0.255.255.255.0.0.192.168.11.1: value=0 #
14.12.2019 23:34:57 (11043 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.10.0.0.0.0.0.0.0.0.0.10.10.0.1: value=0 #
14.12.2019 23:34:57 (11156 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.10.10.10.0.0.255.255.252.0.0.10.10.0.70: value=0 #
14.12.2019 23:34:57 (11270 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.10.192.168.11.0.255.255.255.0.0.192.168.11.1: value=0 #
14.12.2019 23:34:57 (11384 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.11.0.0.0.0.0.0.0.0.0.10.10.0.1: value=1 #
14.12.2019 23:34:57 (11617 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.11.10.10.0.0.255.255.252.0.0.10.10.0.70: value=0 #
14.12.2019 23:34:58 (11814 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.11.192.168.11.0.255.255.255.0.0.192.168.11.1: value=0 #
14.12.2019 23:34:58 (11918 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.12.0.0.0.0.0.0.0.0.0.10.10.0.1: value=4294967295 #
14.12.2019 23:34:58 (12132 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.12.10.10.0.0.255.255.252.0.0.10.10.0.70: value=4294967295 #
14.12.2019 23:34:58 (12236 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.12.192.168.11.0.255.255.255.0.0.192.168.11.1: value=4294967295 #
14.12.2019 23:34:58 (12342 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.13.0.0.0.0.0.0.0.0.0.10.10.0.1: value=4294967295 #
14.12.2019 23:34:58 (12587 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.13.10.10.0.0.255.255.252.0.0.10.10.0.70: value=4294967295 #
14.12.2019 23:34:59 (12785 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.13.192.168.11.0.255.255.255.0.0.192.168.11.1: value=4294967295 #
14.12.2019 23:34:59 (12889 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.14.0.0.0.0.0.0.0.0.0.10.10.0.1: value=4294967295 #
14.12.2019 23:34:59 (12999 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.14.10.10.0.0.255.255.252.0.0.10.10.0.70: value=4294967295 #
14.12.2019 23:34:59 (13103 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.14.192.168.11.0.255.255.255.0.0.192.168.11.1: value=4294967295 #
14.12.2019 23:34:59 (13208 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.15.0.0.0.0.0.0.0.0.0.10.10.0.1: value=4294967295 #
14.12.2019 23:34:59 (13312 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.15.10.10.0.0.255.255.252.0.0.10.10.0.70: value=4294967295 #
14.12.2019 23:34:59 (13458 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.15.192.168.11.0.255.255.255.0.0.192.168.11.1: value=4294967295 #
14.12.2019 23:35:00 (13755 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.16.0.0.0.0.0.0.0.0.0.10.10.0.1: value=1 #
14.12.2019 23:35:00 (13992 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.16.10.10.0.0.255.255.252.0.0.10.10.0.70: value=1 #
14.12.2019 23:35:00 (14193 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.16.192.168.11.0.255.255.255.0.0.192.168.11.1: value=1 #

emils · December 16, 2019, 7:01am

Guscht You need to send supout.rif file to support@mikrotik.com and brief problem description. We are currently unable to reproduce such issue.
ivicask Have you tried the 6.46 stable and 6.47 testing versions? RoMoN works for me now. Make sure both the end user and the agent is updated. If it is not working in the latest versions, please open a support ticket with supout.rif file from your routers.

Guscht · December 16, 2019, 12:28pm

Hi,

I did this already when V6.46 was released, but I got no response from you…

Try the SNMP-Tester (https://downloads.paessler.com/tools/SNMP+Tester+5.2.3.zip) from PRTG.
The OID-LIB (IP-FORWARD.MIB) is attached.

Then simply run the OID-LIB against a RouterOS device with ROS V6.46 or greater. It will fail in the way I posted I above (SNMP Error 222).
ROS V6.45.7 (or lower) report valid data back.

IP-FORWARD-MIB.zip (4.34 KB)

bnw · December 16, 2019, 12:54pm

Good news, here is what we now have (as of 6.47b8) for the CCR1072 :

$ snmpwalk ... .1.3.6.1.4.1.14988.1.1.3
.1.3.6.1.4.1.14988.1.1.3.9.0 = STRING: "n/a"
.1.3.6.1.4.1.14988.1.1.3.11.0 = INTEGER: 370
.1.3.6.1.4.1.14988.1.1.3.12.0 = INTEGER: 435
.1.3.6.1.4.1.14988.1.1.3.14.0 = INTEGER: 1000
.1.3.6.1.4.1.14988.1.1.3.17.0 = Gauge32: 4169
.1.3.6.1.4.1.14988.1.1.3.18.0 = Gauge32: 4182
.1.3.6.1.4.1.14988.1.1.3.100.1.16 = STRING: "power-consumption"
.1.3.6.1.4.1.14988.1.1.3.100.1.17 = STRING: "cpu-temperature"
.1.3.6.1.4.1.14988.1.1.3.100.1.7001 = STRING: "fan1-speed"
.1.3.6.1.4.1.14988.1.1.3.100.1.7002 = STRING: "fan2-speed"
.1.3.6.1.4.1.14988.1.1.3.100.1.7003 = STRING: "fan3-speed"
.1.3.6.1.4.1.14988.1.1.3.100.1.7004 = STRING: "fan4-speed"
.1.3.6.1.4.1.14988.1.1.3.100.1.7101 = STRING: "board-temperature1"
.1.3.6.1.4.1.14988.1.1.3.100.1.7102 = STRING: "board-temperature2"
.1.3.6.1.4.1.14988.1.1.3.100.1.7201 = STRING: "psu1-voltage"
.1.3.6.1.4.1.14988.1.1.3.100.1.7202 = STRING: "psu2-voltage"
.1.3.6.1.4.1.14988.1.1.3.100.1.7301 = STRING: "psu1-current"
.1.3.6.1.4.1.14988.1.1.3.100.1.7302 = STRING: "psu2-current"
.1.3.6.1.4.1.14988.1.1.3.100.2.16 = Gauge32: 435
.1.3.6.1.4.1.14988.1.1.3.100.2.17 = Gauge32: 37
.1.3.6.1.4.1.14988.1.1.3.100.2.7001 = Gauge32: 4169
.1.3.6.1.4.1.14988.1.1.3.100.2.7002 = Gauge32: 4182
.1.3.6.1.4.1.14988.1.1.3.100.2.7003 = Gauge32: 4182
.1.3.6.1.4.1.14988.1.1.3.100.2.7004 = Gauge32: 4222
.1.3.6.1.4.1.14988.1.1.3.100.2.7101 = Gauge32: 25
.1.3.6.1.4.1.14988.1.1.3.100.2.7102 = Gauge32: 25
.1.3.6.1.4.1.14988.1.1.3.100.2.7201 = Gauge32: 0
.1.3.6.1.4.1.14988.1.1.3.100.2.7202 = Gauge32: 121
.1.3.6.1.4.1.14988.1.1.3.100.2.7301 = Gauge32: 0
.1.3.6.1.4.1.14988.1.1.3.100.2.7302 = Gauge32: 36
.1.3.6.1.4.1.14988.1.1.3.100.3.16 = INTEGER: 5
.1.3.6.1.4.1.14988.1.1.3.100.3.17 = INTEGER: 1
.1.3.6.1.4.1.14988.1.1.3.100.3.7001 = INTEGER: 2
.1.3.6.1.4.1.14988.1.1.3.100.3.7002 = INTEGER: 2
.1.3.6.1.4.1.14988.1.1.3.100.3.7003 = INTEGER: 2
.1.3.6.1.4.1.14988.1.1.3.100.3.7004 = INTEGER: 2
.1.3.6.1.4.1.14988.1.1.3.100.3.7101 = INTEGER: 1
.1.3.6.1.4.1.14988.1.1.3.100.3.7102 = INTEGER: 1
.1.3.6.1.4.1.14988.1.1.3.100.3.7201 = INTEGER: 3
.1.3.6.1.4.1.14988.1.1.3.100.3.7202 = INTEGER: 3
.1.3.6.1.4.1.14988.1.1.3.100.3.7301 = INTEGER: 4
.1.3.6.1.4.1.14988.1.1.3.100.3.7302 = INTEGER: 4

.1.3.6.1.4.1.14988.1.1.3.100 is the new interesting part, the gauges.

Same new gauges on a RB4011 :

$ snmpwalk ... .1.3.6.1.4.1.14988.1.1.3
.1.3.6.1.4.1.14988.1.1.3.9.0 = STRING: "n/a"
.1.3.6.1.4.1.14988.1.1.3.10.0 = INTEGER: 270
.1.3.6.1.4.1.14988.1.1.3.14.0 = INTEGER: 1400
.1.3.6.1.4.1.14988.1.1.3.100.1.13 = STRING: "voltage"
.1.3.6.1.4.1.14988.1.1.3.100.1.14 = STRING: "temperature"
.1.3.6.1.4.1.14988.1.1.3.100.2.13 = Gauge32: 238
.1.3.6.1.4.1.14988.1.1.3.100.2.14 = Gauge32: 27
.1.3.6.1.4.1.14988.1.1.3.100.3.13 = INTEGER: 3
.1.3.6.1.4.1.14988.1.1.3.100.3.14 = INTEGER: 1

We’ll now be able to properly monitor CCR1072
Many thanks MikroTik for this !

bnw · December 16, 2019, 2:12pm

One thing perhaps following my post above.
We have the PSUs’ voltage and current in these new gauges.
We could then monitor PSUs checking for example that voltage >12.
Will you however add a psu-state OID ?

Could you also provide us with the new MIB containing these gauges’ part please ?

Thank you again !

mducharme · December 19, 2019, 5:48am

I am curious - how many more 6.4x versions are expected given that 7 is now in beta? Is 6.47 or 6.48 possibly the last RouterOS 6.x? Or will there be a longer period of overlap while 7.x is released and 6.x is still being developed?