Community discussions

MikroTik App
  4. RouterOS
  5. General

SNMP LTE signal strength

Post Reply
 
lHopital
just joined
Topic Author
Posts: 1
Joined: Thu Feb 05, 2015 10:43 am

SNMP LTE signal strength

Thu Feb 05, 2015 10:59 am

Hello,

We use the RB912UAG-5HPnD with the LTE Modul HUAWEI ME909u-521. Everything here works!

When I check the signal strength in the console I get following informations:
Code: Select all
/interface lte info lte1 once
Code: Select all
				status: call in progress 
			pin-status: no password required
		functionality: full
       manufacturer: Huawei Technologies Co., Ltd.
              model: ME909u-521
           revision: 11.234.77.00.00
   current-operator: Sunrise Lebara
     current-cellid: 29356047
  access-technology: 3G
     signal-strengh: -87 dBm
   frame-error-rate: n/a
               imei: 860461024041678
               imsi: 228023546234210
  subscriber-number: +CNUM: "@","",129+CNUM: "@","",129+CNUM: "@","",129
We try to develope a software which can show the signal strength on the pc. It would be nice, if we can receive the signal strength with snmp, but I have really no idea how.

SNMP walk:
Code: Select all
snmpwalk -c public -v 2c 192.168.88.1
Code: Select all
iso.3.6.1.2.1.1.1.0 = STRING: "RouterOS RB912UAG-5HPnD"
iso.3.6.1.2.1.1.2.0 = OID: iso.3.6.1.4.1.14988.1
iso.3.6.1.2.1.1.3.0 = Timeticks: (12700) 0:02:07.00
iso.3.6.1.2.1.1.4.0 = ""
iso.3.6.1.2.1.1.5.0 = STRING: "MikroTik"
iso.3.6.1.2.1.1.6.0 = ""
iso.3.6.1.2.1.1.7.0 = INTEGER: 78
iso.3.6.1.2.1.2.1.0 = INTEGER: 4
iso.3.6.1.2.1.2.2.1.1.1 = INTEGER: 1
iso.3.6.1.2.1.2.2.1.1.2 = INTEGER: 2
iso.3.6.1.2.1.2.2.1.1.3 = INTEGER: 3
iso.3.6.1.2.1.2.2.1.1.4 = INTEGER: 4
iso.3.6.1.2.1.2.2.1.2.1 = STRING: "ether1"
iso.3.6.1.2.1.2.2.1.2.2 = STRING: "wlan1"
iso.3.6.1.2.1.2.2.1.2.3 = STRING: "bridge-local"
iso.3.6.1.2.1.2.2.1.2.4 = STRING: "lte1"
iso.3.6.1.2.1.2.2.1.3.1 = INTEGER: 6
iso.3.6.1.2.1.2.2.1.3.2 = INTEGER: 71
iso.3.6.1.2.1.2.2.1.3.3 = INTEGER: 209
iso.3.6.1.2.1.2.2.1.3.4 = INTEGER: 1
iso.3.6.1.2.1.2.2.1.4.1 = INTEGER: 1500
iso.3.6.1.2.1.2.2.1.4.2 = INTEGER: 1500
iso.3.6.1.2.1.2.2.1.4.3 = INTEGER: 1500
iso.3.6.1.2.1.2.2.1.4.4 = INTEGER: 1500
iso.3.6.1.2.1.2.2.1.5.1 = Gauge32: 0
iso.3.6.1.2.1.2.2.1.5.2 = Gauge32: 11000000
iso.3.6.1.2.1.2.2.1.5.3 = Gauge32: 100000000
iso.3.6.1.2.1.2.2.1.5.4 = Gauge32: 10000000
iso.3.6.1.2.1.2.2.1.6.1 = Hex-STRING: 4C 5E 0C 80 03 4C 
iso.3.6.1.2.1.2.2.1.6.2 = Hex-STRING: 4C 5E 0C 80 03 4D 
iso.3.6.1.2.1.2.2.1.6.3 = Hex-STRING: 4C 5E 0C 80 03 4C 
iso.3.6.1.2.1.2.2.1.6.4 = Hex-STRING: 00 1E 10 1F 00 00 
iso.3.6.1.2.1.2.2.1.7.1 = INTEGER: 1
iso.3.6.1.2.1.2.2.1.7.2 = INTEGER: 1
iso.3.6.1.2.1.2.2.1.7.3 = INTEGER: 1
iso.3.6.1.2.1.2.2.1.7.4 = INTEGER: 1
iso.3.6.1.2.1.2.2.1.8.1 = INTEGER: 2
iso.3.6.1.2.1.2.2.1.8.2 = INTEGER: 1
iso.3.6.1.2.1.2.2.1.8.3 = INTEGER: 1
iso.3.6.1.2.1.2.2.1.8.4 = INTEGER: 1
iso.3.6.1.2.1.2.2.1.9.1 = Timeticks: (0) 0:00:00.00
iso.3.6.1.2.1.2.2.1.9.2 = Timeticks: (0) 0:00:00.00
iso.3.6.1.2.1.2.2.1.9.3 = Timeticks: (0) 0:00:00.00
iso.3.6.1.2.1.2.2.1.9.4 = Timeticks: (0) 0:00:00.00
iso.3.6.1.2.1.2.2.1.10.1 = Counter32: 0
iso.3.6.1.2.1.2.2.1.10.2 = Counter32: 195382
iso.3.6.1.2.1.2.2.1.10.3 = Counter32: 179800
iso.3.6.1.2.1.2.2.1.10.4 = Counter32: 976
iso.3.6.1.2.1.2.2.1.11.1 = Counter32: 0
iso.3.6.1.2.1.2.2.1.11.2 = Counter32: 894
iso.3.6.1.2.1.2.2.1.11.3 = Counter32: 877
iso.3.6.1.2.1.2.2.1.11.4 = Counter32: 4
iso.3.6.1.2.1.2.2.1.12.1 = Counter32: 0
iso.3.6.1.2.1.2.2.1.12.2 = Counter32: 0
iso.3.6.1.2.1.2.2.1.12.3 = Counter32: 0
iso.3.6.1.2.1.2.2.1.12.4 = Counter32: 0
iso.3.6.1.2.1.2.2.1.13.1 = Counter32: 0
iso.3.6.1.2.1.2.2.1.13.2 = Counter32: 0
iso.3.6.1.2.1.2.2.1.13.3 = Counter32: 0
iso.3.6.1.2.1.2.2.1.13.4 = Counter32: 0
iso.3.6.1.2.1.2.2.1.14.1 = Counter32: 0
iso.3.6.1.2.1.2.2.1.14.2 = Counter32: 0
iso.3.6.1.2.1.2.2.1.14.3 = Counter32: 0
iso.3.6.1.2.1.2.2.1.14.4 = Counter32: 0
iso.3.6.1.2.1.2.2.1.15.1 = Counter32: 0
iso.3.6.1.2.1.2.2.1.15.2 = Counter32: 0
iso.3.6.1.2.1.2.2.1.15.3 = Counter32: 0
iso.3.6.1.2.1.2.2.1.15.4 = Counter32: 0
iso.3.6.1.2.1.2.2.1.16.1 = Counter32: 0
iso.3.6.1.2.1.2.2.1.16.2 = Counter32: 570057
iso.3.6.1.2.1.2.2.1.16.3 = Counter32: 568158
iso.3.6.1.2.1.2.2.1.16.4 = Counter32: 2468
iso.3.6.1.2.1.2.2.1.17.1 = Counter32: 0
iso.3.6.1.2.1.2.2.1.17.2 = Counter32: 1009
iso.3.6.1.2.1.2.2.1.17.3 = Counter32: 968
iso.3.6.1.2.1.2.2.1.17.4 = Counter32: 15
iso.3.6.1.2.1.2.2.1.18.1 = Counter32: 0
iso.3.6.1.2.1.2.2.1.18.2 = Counter32: 0
iso.3.6.1.2.1.2.2.1.18.3 = Counter32: 0
iso.3.6.1.2.1.2.2.1.18.4 = Counter32: 0
iso.3.6.1.2.1.2.2.1.19.1 = Counter32: 0
iso.3.6.1.2.1.2.2.1.19.2 = Counter32: 0
iso.3.6.1.2.1.2.2.1.19.3 = Counter32: 0
iso.3.6.1.2.1.2.2.1.19.4 = Counter32: 0
iso.3.6.1.2.1.2.2.1.20.1 = Counter32: 0
iso.3.6.1.2.1.2.2.1.20.2 = Counter32: 0
iso.3.6.1.2.1.2.2.1.20.3 = Counter32: 0
iso.3.6.1.2.1.2.2.1.20.4 = Counter32: 0
iso.3.6.1.2.1.2.2.1.21.1 = Gauge32: 0
iso.3.6.1.2.1.2.2.1.21.2 = Gauge32: 0
iso.3.6.1.2.1.2.2.1.21.3 = Gauge32: 0
iso.3.6.1.2.1.2.2.1.21.4 = Gauge32: 0
iso.3.6.1.2.1.2.2.1.22.1 = OID: ccitt.0
iso.3.6.1.2.1.2.2.1.22.2 = OID: ccitt.0
iso.3.6.1.2.1.2.2.1.22.3 = OID: ccitt.0
iso.3.6.1.2.1.2.2.1.22.4 = OID: ccitt.0
iso.3.6.1.2.1.4.1.0 = INTEGER: 1
iso.3.6.1.2.1.4.2.0 = INTEGER: 255
iso.3.6.1.2.1.4.20.1.1.10.149.255.254 = IpAddress: 10.149.255.254
iso.3.6.1.2.1.4.20.1.1.192.168.88.1 = IpAddress: 192.168.88.1
iso.3.6.1.2.1.4.20.1.2.10.149.255.254 = INTEGER: 4
iso.3.6.1.2.1.4.20.1.2.192.168.88.1 = INTEGER: 3
iso.3.6.1.2.1.4.20.1.3.10.149.255.254 = IpAddress: 255.255.255.252
iso.3.6.1.2.1.4.20.1.3.192.168.88.1 = IpAddress: 255.255.255.0
iso.3.6.1.2.1.4.20.1.4.10.149.255.254 = INTEGER: 1
iso.3.6.1.2.1.4.20.1.4.192.168.88.1 = INTEGER: 1
iso.3.6.1.2.1.4.20.1.5.10.149.255.254 = INTEGER: 65535
iso.3.6.1.2.1.4.20.1.5.192.168.88.1 = INTEGER: 65535
iso.3.6.1.2.1.4.21.1.1.0.0.0.0 = IpAddress: 0.0.0.0
iso.3.6.1.2.1.4.21.1.1.10.149.255.252 = IpAddress: 10.149.255.252
iso.3.6.1.2.1.4.21.1.1.192.168.88.0 = IpAddress: 192.168.88.0
iso.3.6.1.2.1.4.21.1.2.0.0.0.0 = INTEGER: 4
iso.3.6.1.2.1.4.21.1.2.10.149.255.252 = INTEGER: 4
iso.3.6.1.2.1.4.21.1.2.192.168.88.0 = INTEGER: 3
iso.3.6.1.2.1.4.21.1.3.0.0.0.0 = INTEGER: 0
iso.3.6.1.2.1.4.21.1.3.10.149.255.252 = INTEGER: 0
iso.3.6.1.2.1.4.21.1.3.192.168.88.0 = INTEGER: 0
iso.3.6.1.2.1.4.21.1.4.0.0.0.0 = INTEGER: -1
iso.3.6.1.2.1.4.21.1.4.10.149.255.252 = INTEGER: -1
iso.3.6.1.2.1.4.21.1.4.192.168.88.0 = INTEGER: -1
iso.3.6.1.2.1.4.21.1.5.0.0.0.0 = INTEGER: -1
iso.3.6.1.2.1.4.21.1.5.10.149.255.252 = INTEGER: -1
iso.3.6.1.2.1.4.21.1.5.192.168.88.0 = INTEGER: -1
iso.3.6.1.2.1.4.21.1.6.0.0.0.0 = INTEGER: -1
iso.3.6.1.2.1.4.21.1.6.10.149.255.252 = INTEGER: -1
iso.3.6.1.2.1.4.21.1.6.192.168.88.0 = INTEGER: -1
iso.3.6.1.2.1.4.21.1.7.0.0.0.0 = IpAddress: 10.149.255.253
iso.3.6.1.2.1.4.21.1.7.10.149.255.252 = IpAddress: 10.149.255.254
iso.3.6.1.2.1.4.21.1.7.192.168.88.0 = IpAddress: 192.168.88.1
iso.3.6.1.2.1.4.21.1.8.0.0.0.0 = INTEGER: 4
iso.3.6.1.2.1.4.21.1.8.10.149.255.252 = INTEGER: 3
iso.3.6.1.2.1.4.21.1.8.192.168.88.0 = INTEGER: 3
iso.3.6.1.2.1.4.21.1.9.0.0.0.0 = INTEGER: 2
iso.3.6.1.2.1.4.21.1.9.10.149.255.252 = INTEGER: 1
iso.3.6.1.2.1.4.21.1.9.192.168.88.0 = INTEGER: 1
iso.3.6.1.2.1.4.21.1.10.0.0.0.0 = INTEGER: 0
iso.3.6.1.2.1.4.21.1.10.10.149.255.252 = INTEGER: 0
iso.3.6.1.2.1.4.21.1.10.192.168.88.0 = INTEGER: 0
iso.3.6.1.2.1.4.21.1.11.0.0.0.0 = IpAddress: 0.0.0.0
iso.3.6.1.2.1.4.21.1.11.10.149.255.252 = IpAddress: 255.255.255.252
iso.3.6.1.2.1.4.21.1.11.192.168.88.0 = IpAddress: 255.255.255.0
iso.3.6.1.2.1.4.21.1.12.0.0.0.0 = INTEGER: -1
iso.3.6.1.2.1.4.21.1.12.10.149.255.252 = INTEGER: -1
iso.3.6.1.2.1.4.21.1.12.192.168.88.0 = INTEGER: -1
iso.3.6.1.2.1.4.21.1.13.0.0.0.0 = OID: ccitt.0
iso.3.6.1.2.1.4.21.1.13.10.149.255.252 = OID: ccitt.0
iso.3.6.1.2.1.4.21.1.13.192.168.88.0 = OID: ccitt.0
iso.3.6.1.2.1.4.22.1.1.3.192.168.88.191 = INTEGER: 3
iso.3.6.1.2.1.4.22.1.2.3.192.168.88.191 = Hex-STRING: 08 11 96 B4 D7 5C 
iso.3.6.1.2.1.4.22.1.3.3.192.168.88.191 = IpAddress: 192.168.88.191
iso.3.6.1.2.1.4.22.1.4.3.192.168.88.191 = INTEGER: 3
iso.3.6.1.2.1.4.24.3.0 = Gauge32: 3
iso.3.6.1.2.1.4.24.4.1.1.0.0.0.0.0.0.0.0.0.10.149.255.253 = IpAddress: 0.0.0.0
iso.3.6.1.2.1.4.24.4.1.1.10.149.255.252.255.255.255.252.0.10.149.255.254 = IpAddress: 10.149.255.252
iso.3.6.1.2.1.4.24.4.1.1.192.168.88.0.255.255.255.0.0.192.168.88.1 = IpAddress: 192.168.88.0
iso.3.6.1.2.1.4.24.4.1.2.0.0.0.0.0.0.0.0.0.10.149.255.253 = IpAddress: 0.0.0.0
iso.3.6.1.2.1.4.24.4.1.2.10.149.255.252.255.255.255.252.0.10.149.255.254 = IpAddress: 255.255.255.252
iso.3.6.1.2.1.4.24.4.1.2.192.168.88.0.255.255.255.0.0.192.168.88.1 = IpAddress: 255.255.255.0
iso.3.6.1.2.1.4.24.4.1.3.0.0.0.0.0.0.0.0.0.10.149.255.253 = INTEGER: 0
iso.3.6.1.2.1.4.24.4.1.3.10.149.255.252.255.255.255.252.0.10.149.255.254 = INTEGER: 0
iso.3.6.1.2.1.4.24.4.1.3.192.168.88.0.255.255.255.0.0.192.168.88.1 = INTEGER: 0
iso.3.6.1.2.1.4.24.4.1.4.0.0.0.0.0.0.0.0.0.10.149.255.253 = IpAddress: 10.149.255.253
iso.3.6.1.2.1.4.24.4.1.4.10.149.255.252.255.255.255.252.0.10.149.255.254 = IpAddress: 10.149.255.254
iso.3.6.1.2.1.4.24.4.1.4.192.168.88.0.255.255.255.0.0.192.168.88.1 = IpAddress: 192.168.88.1
iso.3.6.1.2.1.4.24.4.1.5.0.0.0.0.0.0.0.0.0.10.149.255.253 = INTEGER: 4
iso.3.6.1.2.1.4.24.4.1.5.10.149.255.252.255.255.255.252.0.10.149.255.254 = INTEGER: 4
iso.3.6.1.2.1.4.24.4.1.5.192.168.88.0.255.255.255.0.0.192.168.88.1 = INTEGER: 3
iso.3.6.1.2.1.4.24.4.1.6.0.0.0.0.0.0.0.0.0.10.149.255.253 = INTEGER: 4
iso.3.6.1.2.1.4.24.4.1.6.10.149.255.252.255.255.255.252.0.10.149.255.254 = INTEGER: 3
iso.3.6.1.2.1.4.24.4.1.6.192.168.88.0.255.255.255.0.0.192.168.88.1 = INTEGER: 3
iso.3.6.1.2.1.4.24.4.1.7.0.0.0.0.0.0.0.0.0.10.149.255.253 = INTEGER: 3
iso.3.6.1.2.1.4.24.4.1.7.10.149.255.252.255.255.255.252.0.10.149.255.254 = INTEGER: 2
iso.3.6.1.2.1.4.24.4.1.7.192.168.88.0.255.255.255.0.0.192.168.88.1 = INTEGER: 2
iso.3.6.1.2.1.4.24.4.1.8.0.0.0.0.0.0.0.0.0.10.149.255.253 = INTEGER: 0
iso.3.6.1.2.1.4.24.4.1.8.10.149.255.252.255.255.255.252.0.10.149.255.254 = INTEGER: 0
iso.3.6.1.2.1.4.24.4.1.8.192.168.88.0.255.255.255.0.0.192.168.88.1 = INTEGER: 0
iso.3.6.1.2.1.4.24.4.1.9.0.0.0.0.0.0.0.0.0.10.149.255.253 = OID: ccitt.0
iso.3.6.1.2.1.4.24.4.1.9.10.149.255.252.255.255.255.252.0.10.149.255.254 = OID: ccitt.0
iso.3.6.1.2.1.4.24.4.1.9.192.168.88.0.255.255.255.0.0.192.168.88.1 = OID: ccitt.0
iso.3.6.1.2.1.4.24.4.1.10.0.0.0.0.0.0.0.0.0.10.149.255.253 = INTEGER: 0
iso.3.6.1.2.1.4.24.4.1.10.10.149.255.252.255.255.255.252.0.10.149.255.254 = INTEGER: 0
iso.3.6.1.2.1.4.24.4.1.10.192.168.88.0.255.255.255.0.0.192.168.88.1 = INTEGER: 0
iso.3.6.1.2.1.4.24.4.1.11.0.0.0.0.0.0.0.0.0.10.149.255.253 = INTEGER: 0
iso.3.6.1.2.1.4.24.4.1.11.10.149.255.252.255.255.255.252.0.10.149.255.254 = INTEGER: 0
iso.3.6.1.2.1.4.24.4.1.11.192.168.88.0.255.255.255.0.0.192.168.88.1 = INTEGER: 0
iso.3.6.1.2.1.4.24.4.1.12.0.0.0.0.0.0.0.0.0.10.149.255.253 = INTEGER: -1
iso.3.6.1.2.1.4.24.4.1.12.10.149.255.252.255.255.255.252.0.10.149.255.254 = INTEGER: -1
iso.3.6.1.2.1.4.24.4.1.12.192.168.88.0.255.255.255.0.0.192.168.88.1 = INTEGER: -1
iso.3.6.1.2.1.4.24.4.1.13.0.0.0.0.0.0.0.0.0.10.149.255.253 = INTEGER: -1
iso.3.6.1.2.1.4.24.4.1.13.10.149.255.252.255.255.255.252.0.10.149.255.254 = INTEGER: -1
iso.3.6.1.2.1.4.24.4.1.13.192.168.88.0.255.255.255.0.0.192.168.88.1 = INTEGER: -1
iso.3.6.1.2.1.4.24.4.1.14.0.0.0.0.0.0.0.0.0.10.149.255.253 = INTEGER: -1
iso.3.6.1.2.1.4.24.4.1.14.10.149.255.252.255.255.255.252.0.10.149.255.254 = INTEGER: -1
iso.3.6.1.2.1.4.24.4.1.14.192.168.88.0.255.255.255.0.0.192.168.88.1 = INTEGER: -1
iso.3.6.1.2.1.4.24.4.1.15.0.0.0.0.0.0.0.0.0.10.149.255.253 = INTEGER: -1
iso.3.6.1.2.1.4.24.4.1.15.10.149.255.252.255.255.255.252.0.10.149.255.254 = INTEGER: -1
iso.3.6.1.2.1.4.24.4.1.15.192.168.88.0.255.255.255.0.0.192.168.88.1 = INTEGER: -1
iso.3.6.1.2.1.4.24.4.1.16.0.0.0.0.0.0.0.0.0.10.149.255.253 = INTEGER: 1
iso.3.6.1.2.1.4.24.4.1.16.10.149.255.252.255.255.255.252.0.10.149.255.254 = INTEGER: 1
iso.3.6.1.2.1.4.24.4.1.16.192.168.88.0.255.255.255.0.0.192.168.88.1 = INTEGER: 1
iso.3.6.1.2.1.17.1.1.0 = Hex-STRING: 4C 5E 0C 80 03 4C 
iso.3.6.1.2.1.17.2.1.0 = INTEGER: 3
iso.3.6.1.2.1.17.2.2.0 = INTEGER: 32768
iso.3.6.1.2.1.17.4.3.1.1.8.17.150.180.215.92 = Hex-STRING: 08 11 96 B4 D7 5C 
iso.3.6.1.2.1.17.4.3.1.1.76.94.12.128.3.77 = Hex-STRING: 4C 5E 0C 80 03 4D 
iso.3.6.1.2.1.17.4.3.1.2.8.17.150.180.215.92 = INTEGER: 2
iso.3.6.1.2.1.17.4.3.1.2.76.94.12.128.3.77 = INTEGER: 2
iso.3.6.1.2.1.17.4.3.1.3.8.17.150.180.215.92 = INTEGER: 3
iso.3.6.1.2.1.17.4.3.1.3.76.94.12.128.3.77 = INTEGER: 3
iso.3.6.1.2.1.25.1.1.0 = Timeticks: (12800) 0:02:08.00
iso.3.6.1.2.1.25.1.2.0 = Hex-STRING: 07 D2 01 01 01 05 04 00 2B 00 00 
iso.3.6.1.2.1.25.2.2.0 = INTEGER: 65536
iso.3.6.1.2.1.25.2.3.1.1.65536 = INTEGER: 65536
iso.3.6.1.2.1.25.2.3.1.1.131072 = INTEGER: 131072
iso.3.6.1.2.1.25.2.3.1.2.65536 = OID: iso.3.6.1.2.1.25.2.1.1
iso.3.6.1.2.1.25.2.3.1.2.131072 = OID: iso.3.6.1.2.1.25.2.1.4
iso.3.6.1.2.1.25.2.3.1.3.65536 = STRING: "main memory"
iso.3.6.1.2.1.25.2.3.1.3.131072 = STRING: "system disk"
iso.3.6.1.2.1.25.2.3.1.4.65536 = INTEGER: 1024
iso.3.6.1.2.1.25.2.3.1.4.131072 = INTEGER: 1024
iso.3.6.1.2.1.25.2.3.1.5.65536 = INTEGER: 65536
iso.3.6.1.2.1.25.2.3.1.5.131072 = INTEGER: 131072
iso.3.6.1.2.1.25.2.3.1.6.65536 = INTEGER: 23000
iso.3.6.1.2.1.25.2.3.1.6.131072 = INTEGER: 18152
iso.3.6.1.2.1.25.2.3.1.7.65536 = Counter32: 0
iso.3.6.1.2.1.25.2.3.1.7.131072 = Counter32: 0
iso.3.6.1.2.1.25.3.2.1.1.1 = INTEGER: 1
iso.3.6.1.2.1.25.3.2.1.2.1 = OID: iso.3.6.1.2.1.25.3.1.3
iso.3.6.1.2.1.25.3.3.1.1.1 = OID: ccitt.0
iso.3.6.1.2.1.25.3.3.1.2.1 = INTEGER: 0
iso.3.6.1.2.1.31.1.1.1.1.1 = STRING: "ether1"
iso.3.6.1.2.1.31.1.1.1.1.2 = STRING: "wlan1"
iso.3.6.1.2.1.31.1.1.1.1.3 = STRING: "bridge-local"
iso.3.6.1.2.1.31.1.1.1.1.4 = STRING: "lte1"
iso.3.6.1.2.1.31.1.1.1.2.1 = Counter32: 0
iso.3.6.1.2.1.31.1.1.1.2.2 = Counter32: 0
iso.3.6.1.2.1.31.1.1.1.2.3 = Counter32: 0
iso.3.6.1.2.1.31.1.1.1.2.4 = Counter32: 0
iso.3.6.1.2.1.31.1.1.1.3.1 = Counter32: 0
iso.3.6.1.2.1.31.1.1.1.3.2 = Counter32: 0
iso.3.6.1.2.1.31.1.1.1.3.3 = Counter32: 0
iso.3.6.1.2.1.31.1.1.1.3.4 = Counter32: 0
iso.3.6.1.2.1.31.1.1.1.4.1 = Counter32: 0
iso.3.6.1.2.1.31.1.1.1.4.2 = Counter32: 0
iso.3.6.1.2.1.31.1.1.1.4.3 = Counter32: 0
iso.3.6.1.2.1.31.1.1.1.4.4 = Counter32: 0
iso.3.6.1.2.1.31.1.1.1.5.1 = Counter32: 0
iso.3.6.1.2.1.31.1.1.1.5.2 = Counter32: 0
iso.3.6.1.2.1.31.1.1.1.5.3 = Counter32: 0
iso.3.6.1.2.1.31.1.1.1.5.4 = Counter32: 0
iso.3.6.1.2.1.31.1.1.1.6.1 = Counter64: 0
iso.3.6.1.2.1.31.1.1.1.6.2 = Counter64: 222900
iso.3.6.1.2.1.31.1.1.1.6.3 = Counter64: 203692
iso.3.6.1.2.1.31.1.1.1.6.4 = Counter64: 976
iso.3.6.1.2.1.31.1.1.1.7.1 = Counter64: 0
iso.3.6.1.2.1.31.1.1.1.7.2 = Counter64: 1153
iso.3.6.1.2.1.31.1.1.1.7.3 = Counter64: 1136
iso.3.6.1.2.1.31.1.1.1.7.4 = Counter64: 4
iso.3.6.1.2.1.31.1.1.1.8.1 = Counter64: 0
iso.3.6.1.2.1.31.1.1.1.8.2 = Counter64: 0
iso.3.6.1.2.1.31.1.1.1.8.3 = Counter64: 0
iso.3.6.1.2.1.31.1.1.1.8.4 = Counter64: 0
iso.3.6.1.2.1.31.1.1.1.9.1 = Counter64: 0
iso.3.6.1.2.1.31.1.1.1.9.2 = Counter64: 0
iso.3.6.1.2.1.31.1.1.1.9.3 = Counter64: 0
iso.3.6.1.2.1.31.1.1.1.9.4 = Counter64: 0
iso.3.6.1.2.1.31.1.1.1.10.1 = Counter64: 0
iso.3.6.1.2.1.31.1.1.1.10.2 = Counter64: 608263
iso.3.6.1.2.1.31.1.1.1.10.3 = Counter64: 606258
iso.3.6.1.2.1.31.1.1.1.10.4 = Counter64: 2468
iso.3.6.1.2.1.31.1.1.1.11.1 = Counter64: 0
iso.3.6.1.2.1.31.1.1.1.11.2 = Counter64: 1281
iso.3.6.1.2.1.31.1.1.1.11.3 = Counter64: 1238
iso.3.6.1.2.1.31.1.1.1.11.4 = Counter64: 15
iso.3.6.1.2.1.31.1.1.1.12.1 = Counter64: 0
iso.3.6.1.2.1.31.1.1.1.12.2 = Counter64: 0
iso.3.6.1.2.1.31.1.1.1.12.3 = Counter64: 0
iso.3.6.1.2.1.31.1.1.1.12.4 = Counter64: 0
iso.3.6.1.2.1.31.1.1.1.13.1 = Counter64: 0
iso.3.6.1.2.1.31.1.1.1.13.2 = Counter64: 0
iso.3.6.1.2.1.31.1.1.1.13.3 = Counter64: 0
iso.3.6.1.2.1.31.1.1.1.13.4 = Counter64: 0
iso.3.6.1.2.1.31.1.1.1.15.1 = Gauge32: 0
iso.3.6.1.2.1.31.1.1.1.15.2 = Gauge32: 0
iso.3.6.1.2.1.31.1.1.1.15.3 = Gauge32: 0
iso.3.6.1.2.1.31.1.1.1.15.4 = Gauge32: 0
iso.3.6.1.2.1.31.1.1.1.18.1 = ""
iso.3.6.1.2.1.31.1.1.1.18.2 = ""
iso.3.6.1.2.1.31.1.1.1.18.3 = ""
iso.3.6.1.2.1.31.1.1.1.18.4 = ""
iso.3.6.1.2.1.47.1.1.1.1.1.65536 = INTEGER: 65536
iso.3.6.1.2.1.47.1.1.1.1.1.262145 = INTEGER: 262145
iso.3.6.1.2.1.47.1.1.1.1.1.262146 = INTEGER: 262146
iso.3.6.1.2.1.47.1.1.1.1.2.65536 = STRING: "RouterOS 6.26 on RB912UAG-5HPnD"
iso.3.6.1.2.1.47.1.1.1.1.2.262145 = STRING: "Linux 3.3.5 ehci_hcd RB400 EHCI"
iso.3.6.1.2.1.47.1.1.1.1.2.262146 = STRING: "HUAWEI Technology HUAWEI Mobile"
iso.3.6.1.2.1.47.1.1.1.1.3.65536 = OID: ccitt.0
iso.3.6.1.2.1.47.1.1.1.1.3.262145 = OID: ccitt.0
iso.3.6.1.2.1.47.1.1.1.1.3.262146 = OID: ccitt.0
iso.3.6.1.2.1.47.1.1.1.1.4.65536 = INTEGER: 0
iso.3.6.1.2.1.47.1.1.1.1.4.262145 = INTEGER: 65536
iso.3.6.1.2.1.47.1.1.1.1.4.262146 = INTEGER: 65536
iso.3.6.1.2.1.47.1.1.1.1.5.65536 = INTEGER: 3
iso.3.6.1.2.1.47.1.1.1.1.5.262145 = INTEGER: 2
iso.3.6.1.2.1.47.1.1.1.1.5.262146 = INTEGER: 2
iso.3.6.1.2.1.47.1.1.1.1.6.65536 = INTEGER: -1
iso.3.6.1.2.1.47.1.1.1.1.6.262145 = INTEGER: -1
iso.3.6.1.2.1.47.1.1.1.1.6.262146 = INTEGER: -1
iso.3.6.1.2.1.47.1.1.1.1.7.65536 = STRING: "MIPS 74Kc V4.12"
iso.3.6.1.2.1.47.1.1.1.1.7.262145 = STRING: "1:1"
iso.3.6.1.2.1.47.1.1.1.1.7.262146 = STRING: "1:2"
iso.3.6.1.2.1.47.1.1.1.1.8.65536 = ""
iso.3.6.1.2.1.47.1.1.1.1.8.262145 = ""
iso.3.6.1.2.1.47.1.1.1.1.8.262146 = ""
iso.3.6.1.2.1.47.1.1.1.1.9.65536 = ""
iso.3.6.1.2.1.47.1.1.1.1.9.262145 = ""
iso.3.6.1.2.1.47.1.1.1.1.9.262146 = ""
iso.3.6.1.2.1.47.1.1.1.1.10.65536 = ""
iso.3.6.1.2.1.47.1.1.1.1.10.262145 = ""
iso.3.6.1.2.1.47.1.1.1.1.10.262146 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.65536 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.262145 = STRING: "rb400_usb"
iso.3.6.1.2.1.47.1.1.1.1.11.262146 = STRING: "0123456789ABCDEF"
iso.3.6.1.2.1.47.1.1.1.1.12.65536 = ""
iso.3.6.1.2.1.47.1.1.1.1.12.262145 = STRING: "0x1d6b"
iso.3.6.1.2.1.47.1.1.1.1.12.262146 = STRING: "0x12d1"
iso.3.6.1.2.1.47.1.1.1.1.13.65536 = ""
iso.3.6.1.2.1.47.1.1.1.1.13.262145 = STRING: "0x0002"
iso.3.6.1.2.1.47.1.1.1.1.13.262146 = STRING: "0x1573"
iso.3.6.1.2.1.47.1.1.1.1.14.65536 = ""
iso.3.6.1.2.1.47.1.1.1.1.14.262145 = ""
iso.3.6.1.2.1.47.1.1.1.1.14.262146 = ""
iso.3.6.1.2.1.47.1.1.1.1.15.65536 = ""
iso.3.6.1.2.1.47.1.1.1.1.15.262145 = ""
iso.3.6.1.2.1.47.1.1.1.1.15.262146 = ""
iso.3.6.1.2.1.47.1.1.1.1.16.65536 = INTEGER: 2
iso.3.6.1.2.1.47.1.1.1.1.16.262145 = INTEGER: 2
iso.3.6.1.2.1.47.1.1.1.1.16.262146 = INTEGER: 2
iso.3.6.1.2.1.55.1.3.0 = Gauge32: 4
iso.3.6.1.2.1.55.1.5.1.2.1 = STRING: "ether1"
iso.3.6.1.2.1.55.1.5.1.2.2 = STRING: "wlan1"
iso.3.6.1.2.1.55.1.5.1.2.3 = STRING: "bridge-local"
iso.3.6.1.2.1.55.1.5.1.2.4 = STRING: "lte1"
iso.3.6.1.2.1.55.1.5.1.3.1 = OID: ccitt.0
iso.3.6.1.2.1.55.1.5.1.3.2 = OID: ccitt.0
iso.3.6.1.2.1.55.1.5.1.3.3 = OID: ccitt.0
iso.3.6.1.2.1.55.1.5.1.3.4 = OID: ccitt.0
iso.3.6.1.2.1.55.1.5.1.4.1 = Gauge32: 1500
iso.3.6.1.2.1.55.1.5.1.4.2 = Gauge32: 1500
iso.3.6.1.2.1.55.1.5.1.4.3 = Gauge32: 1500
iso.3.6.1.2.1.55.1.5.1.4.4 = Gauge32: 1500
iso.3.6.1.2.1.55.1.5.1.5.1 = Gauge32: 65535
iso.3.6.1.2.1.55.1.5.1.5.2 = Gauge32: 65535
iso.3.6.1.2.1.55.1.5.1.5.3 = Gauge32: 65535
iso.3.6.1.2.1.55.1.5.1.5.4 = Gauge32: 65535
iso.3.6.1.2.1.55.1.5.1.6.1 = Hex-STRING: 00 00 00 01 
iso.3.6.1.2.1.55.1.5.1.6.2 = Hex-STRING: 00 00 00 02 
iso.3.6.1.2.1.55.1.5.1.6.3 = Hex-STRING: 00 00 00 03 
iso.3.6.1.2.1.55.1.5.1.6.4 = Hex-STRING: 00 00 00 04 
iso.3.6.1.2.1.55.1.5.1.7.1 = INTEGER: 32
iso.3.6.1.2.1.55.1.5.1.7.2 = INTEGER: 32
iso.3.6.1.2.1.55.1.5.1.7.3 = INTEGER: 32
iso.3.6.1.2.1.55.1.5.1.7.4 = INTEGER: 32
iso.3.6.1.2.1.55.1.5.1.8.1 = Hex-STRING: 4C 5E 0C 80 03 4C 
iso.3.6.1.2.1.55.1.5.1.8.2 = Hex-STRING: 4C 5E 0C 80 03 4D 
iso.3.6.1.2.1.55.1.5.1.8.3 = Hex-STRING: 4C 5E 0C 80 03 4C 
iso.3.6.1.2.1.55.1.5.1.8.4 = Hex-STRING: 00 1E 10 1F 00 00 
iso.3.6.1.2.1.55.1.5.1.9.1 = INTEGER: 1
iso.3.6.1.2.1.55.1.5.1.9.2 = INTEGER: 1
iso.3.6.1.2.1.55.1.5.1.9.3 = INTEGER: 1
iso.3.6.1.2.1.55.1.5.1.9.4 = INTEGER: 1
iso.3.6.1.2.1.55.1.5.1.10.1 = INTEGER: 2
iso.3.6.1.2.1.55.1.5.1.10.2 = INTEGER: 1
iso.3.6.1.2.1.55.1.5.1.10.3 = INTEGER: 1
iso.3.6.1.2.1.55.1.5.1.10.4 = INTEGER: 1
iso.3.6.1.2.1.55.1.5.1.11.1 = Timeticks: (0) 0:00:00.00
iso.3.6.1.2.1.55.1.5.1.11.2 = Timeticks: (0) 0:00:00.00
iso.3.6.1.2.1.55.1.5.1.11.3 = Timeticks: (0) 0:00:00.00
iso.3.6.1.2.1.55.1.5.1.11.4 = Timeticks: (0) 0:00:00.00
iso.3.6.1.2.1.55.1.8.1.1.3.254.128.0.0.0.0.0.0.78.94.12.255.254.128.3.76 = Hex-STRING: FE 80 00 00 00 00 00 00 4E 5E 0C FF FE 80 03 4C 
iso.3.6.1.2.1.55.1.8.1.1.4.254.128.0.0.0.0.0.0.2.30.16.255.254.31.0.0 = Hex-STRING: FE 80 00 00 00 00 00 00 02 1E 10 FF FE 1F 00 00 
iso.3.6.1.2.1.55.1.8.1.2.3.254.128.0.0.0.0.0.0.78.94.12.255.254.128.3.76 = INTEGER: 64
iso.3.6.1.2.1.55.1.8.1.2.4.254.128.0.0.0.0.0.0.2.30.16.255.254.31.0.0 = INTEGER: 64
iso.3.6.1.2.1.55.1.8.1.3.3.254.128.0.0.0.0.0.0.78.94.12.255.254.128.3.76 = INTEGER: 1
iso.3.6.1.2.1.55.1.8.1.3.4.254.128.0.0.0.0.0.0.2.30.16.255.254.31.0.0 = INTEGER: 1
iso.3.6.1.2.1.55.1.8.1.4.3.254.128.0.0.0.0.0.0.78.94.12.255.254.128.3.76 = INTEGER: 0
iso.3.6.1.2.1.55.1.8.1.4.4.254.128.0.0.0.0.0.0.2.30.16.255.254.31.0.0 = INTEGER: 0
iso.3.6.1.2.1.55.1.8.1.5.3.254.128.0.0.0.0.0.0.78.94.12.255.254.128.3.76 = INTEGER: 1
iso.3.6.1.2.1.55.1.8.1.5.4.254.128.0.0.0.0.0.0.2.30.16.255.254.31.0.0 = INTEGER: 1
iso.3.6.1.2.1.9999.1.1.1.1.0 = STRING: "MikroTik DHCP server"
iso.3.6.1.2.1.9999.1.1.1.2.0 = OID: iso.3.6.1.4.1.14988.1
iso.3.6.1.2.1.9999.1.1.6.4.1.4.192.168.88.191 = INTEGER: 2
iso.3.6.1.2.1.9999.1.1.6.4.1.4.192.168.88.192 = INTEGER: 2
iso.3.6.1.2.1.9999.1.1.6.4.1.5.192.168.88.191 = Gauge32: 501
iso.3.6.1.2.1.9999.1.1.6.4.1.5.192.168.88.192 = Gauge32: 444
iso.3.6.1.2.1.9999.1.1.6.4.1.7.192.168.88.191 = INTEGER: 3
iso.3.6.1.2.1.9999.1.1.6.4.1.7.192.168.88.192 = INTEGER: 3
iso.3.6.1.2.1.9999.1.1.6.4.1.8.192.168.88.191 = Hex-STRING: 08 11 96 B4 D7 5C 
iso.3.6.1.2.1.9999.1.1.6.4.1.8.192.168.88.192 = Hex-STRING: 10 1F 74 FD F1 97

I found in the notes for version 6.12, that the signal strength should be included in snmp..
*) l2tp - fixed ~no buffer space available~ problem;
*) ipsec - support IPv4 over IPv6 and vice versa;
*) pppoe - report correctly number of active links;
*) updated timezone information;
*) many fixes for CRS managed switch functionality -
particularly improved VLAN support, port isolation, defaults;
*) added trunk support for CRS switches;
*) added policing support for CRS switches;
*) www - added support for HTTP byte ranges;
*) lte - provide signal strength using snmp and make 'info once' work in console;


Do you know, where I can see the signal strength in the list above?
Or is there an other way to get the signal strength on the pc?


I'm really new to this Routerboard/Mikrotik stuff and hope you can help me.



Roger
Top
 
ronybeck
just joined
Posts: 2
Joined: Mon Dec 29, 2014 12:50 pm

Re: SNMP LTE signal strength

Thu Feb 12, 2015 4:52 pm

I am also interested in this. Did you find a solution?
Top
 
acidburn
just joined
Posts: 1
Joined: Thu Dec 17, 2015 10:33 am

Re: SNMP LTE signal strength

Thu Dec 17, 2015 10:37 am

I'm also interested. Did Anyone find the solution how to graph the LTE signal strenght?
Top
 
troffasky
Member
Member
Posts: 436
Joined: Wed Mar 26, 2014 4:37 pm

Re: SNMP LTE signal strength

Fri Dec 18, 2015 12:34 am

Tried "print oid" in the relevant section of the CLI? I don't have an LTE-equipped device to test with, but some examples:
Code: Select all
[admin@LivingRoom] > /interface wireless print oid
 0 tx-rate=.1.3.6.1.4.1.14988.1.1.1.3.1.2.6 rx-rate=.1.3.6.1.4.1.14988.1.1.1.3.1.3.6 
   ssid=.1.3.6.1.4.1.14988.1.1.1.3.1.4.6 bssid=.1.3.6.1.4.1.14988.1.1.1.3.1.5.6 
   client-count=.1.3.6.1.4.1.14988.1.1.1.3.1.6.6 frequency=.1.3.6.1.4.1.14988.1.1.1.3.1.7.6 
   band=.1.3.6.1.4.1.14988.1.1.1.3.1.8.6 noise-floor=.1.3.6.1.4.1.14988.1.1.1.3.1.9.6 
   overall-ccq=.1.3.6.1.4.1.14988.1.1.1.3.1.10.6
Code: Select all
[admin@LivingRoom] > /system resource print oid
         uptime: .1.3.6.1.2.1.1.3.0
   total-memory: .1.3.6.1.2.1.25.2.3.1.5.65536
    used-memory: .1.3.6.1.2.1.25.2.3.1.6.65536
  cpu-frequency: .1.3.6.1.4.1.14988.1.1.3.14.0
     build-time: .1.3.6.1.4.1.14988.1.1.7.6.0
Top
 
User avatar
travisms
newbie
Posts: 28
Joined: Mon Jul 13, 2015 8:47 pm
Location: Strand, South Africa

Re: SNMP LTE signal strength

Wed Feb 17, 2016 4:27 pm

Sorry to revive an old thread, but did you find a solution for this ? I would also like to be able to do it.
Top
 
tumik
just joined
Posts: 3
Joined: Tue Aug 16, 2016 12:47 am

Re: SNMP LTE signal strength

Tue Aug 16, 2016 1:10 am

Tried "print oid" in the relevant section of the CLI?
Print oid doesn't seem to work on LTE interfaces:
Code: Select all
> /interface lte print oid
expected end of command (line 1 column 22)
If anyone found a solution, I would also be interested.
I'm running SXT LTE with RouterOS 6.36 - no success getting LTE signal information via SNMP.
Top
 
User avatar
travisms
newbie
Posts: 28
Joined: Mon Jul 13, 2015 8:47 pm
Location: Strand, South Africa

Re: SNMP LTE signal strength

Tue Aug 16, 2016 2:40 pm

The oid for LTE signal strength is 1.3.6.1.4.1.14988.1.1.16.1.1.2
Top
 
tumik
just joined
Posts: 3
Joined: Tue Aug 16, 2016 12:47 am

Re: SNMP LTE signal strength

Tue Aug 16, 2016 3:30 pm

The oid for LTE signal strength is 1.3.6.1.4.1.14988.1.1.16.1.1.2
Hi,

Thanks for your reply. I suddenly got it working!

I also found the problem I was having.
Seems like it stops responding for SNMP LTE queries if I query some other (non-existent?) OID before it?
Code: Select all
# snmpwalk -v1 -cpublic -t 30 10.7.0.2 1.3.6.1.4.1.14988.1.1.16.1.1.2
MIKROTIK-MIB::mtxrLTEModemSignalRSSI.2 = INTEGER: -51
# snmpwalk -v1 -cpublic -t 30 10.7.0.2 MIKROTIK-MIB::mtxrLTEModemSignalRSSI
MIKROTIK-MIB::mtxrLTEModemSignalRSSI.2 = INTEGER: -51
# snmpwalk -v1 -cpublic -t 30 10.7.0.2 1.3.6.1.4.1.14988.1.1.16.1.1
# snmpwalk -v1 -cpublic -t 30 10.7.0.2 1.3.6.1.4.1.14988.1.1.16.1.1.2
# snmpwalk -v1 -cpublic -t 30 10.7.0.2 1.3.6.1.4.1.14988.1.1.16.1.1.2
# snmpwalk -v1 -cpublic -t 30 10.7.0.2 1.3.6.1.2.1.1.5
SNMPv2-MIB::sysName.0 = STRING: lte
# snmpwalk -v1 -cpublic -t 30 10.7.0.2 1.3.6.1.4.1.14988.1.1.16.1.1.2
#
So now it's broken again, and I don't know how to fix it.
Is this a RouterOS bug?

A snip from snmpwalk debug output, showing the SNMP server returning error status 2 (SNMP_ERRORSTATUS_NOSUCHNAME) and an empty value:
Code: Select all
trace: snmp_pdu_parse(): snmp_api.c, 4360:
dumpv_recv:     Command RESPONSE
trace: snmp_pdu_parse(): snmp_api.c, 4445:
dumph_recv:     request_id
dumpx_recv:      02 04 63 D4 49 54
dumpv_recv:        Integer:     1674856788 (0x63D44954)
trace: snmp_pdu_parse(): snmp_api.c, 4456:
dumph_recv:     error status
dumpx_recv:      02 01 02
dumpv_recv:        Integer:     2 (0x02)
trace: snmp_pdu_parse(): snmp_api.c, 4467:
dumph_recv:     error index
dumpx_recv:      02 01 01
dumpv_recv:        Integer:     1 (0x01)
trace: snmp_pdu_parse(): snmp_api.c, 4485:
dumph_recv:     VarBindList
trace: snmp_pdu_parse(): snmp_api.c, 4515:
dumph_recv:       VarBind
trace: snmp_parse_var_op(): snmp.c, 164:
dumph_recv:         Name
dumpx_recv:          06 0D 2B 06 01 04 01 F5 0C 01 01 10 01 01 02
dumpv_recv:            ObjID: MIKROTIK-MIB::mtxrLTEModemSignalRSSI
trace: snmp_pdu_parse(): snmp_api.c, 4524:
dumph_recv:         Value
trace: _sess_process_packet(): snmp_api.c, 5221:
sess_process_packet: received message id#0 reqid#1674856788 len 48
Top
 
User avatar
travisms
newbie
Posts: 28
Joined: Mon Jul 13, 2015 8:47 pm
Location: Strand, South Africa

Re: SNMP LTE signal strength

Tue Aug 16, 2016 3:45 pm

That would explain the same issue I was having when I was testing it - I thought it was just the SNMP walk application I was using that was doing weird stuff!

On another note - does anyone know if the access technology is available via SNMP ? Such as GSM, 3G, LTE etc...

I know that there is a number on 1.3.6.1.4.1.14988.1.1.16.1.1.1 but I do not know what this number represents - most of the time its a 2.
Top
 
tumik
just joined
Posts: 3
Joined: Tue Aug 16, 2016 12:47 am

Re: SNMP LTE signal strength

Tue Aug 16, 2016 4:38 pm

Definitely seems like a RouterOS bug.
I got it working again (for a while) by stopping snmp, waiting for a few minutes, and starting snmp again as mentioned in another thread: http://forum.mikrotik.com/viewtopic.php?t=87169
Code: Select all
# snmpwalk -v1 -cpublic -t 30 10.7.0.2 1.3.6.1.4.1.14988.1.1.16.1.1.2
# snmpwalk -v1 -cpublic -t 30 10.7.0.2 1.3.6.1.4.1.14988.1.1.16.1.1.2
# ssh 10.7.0.2

[sxt-lte] > /snmp set enabled=no
[sxt-lte] > /snmp set enabled=yes
[sxt-lte] > quit

# snmpwalk -v1 -cpublic -t 30 10.7.0.2 1.3.6.1.4.1.14988.1.1.16.1.1.2
MIKROTIK-MIB::mtxrLTEModemSignalRSSI.2 = INTEGER: -52
# snmpwalk -v1 -cpublic -t 30 10.7.0.2 1.3.6.1.4.1.14988.1.1.16.1.1.2
MIKROTIK-MIB::mtxrLTEModemSignalRSSI.2 = INTEGER: -51
#
On another note - does anyone know if the access technology is available via SNMP ? Such as GSM, 3G, LTE etc...
I know that there is a number on 1.3.6.1.4.1.14988.1.1.16.1.1.1 but I do not know what this number represents - most of the time its a 2.
I don't think it's available. 1.3.6.1.4.1.14988.1.1.16.1.1.1 is called mtxrLTEModemInterfaceIndex - so it should return the index number of LTE modem interface.
Top
 
mvalsasna
just joined
Posts: 18
Joined: Tue Sep 30, 2014 2:10 pm

Re: SNMP LTE signal strength

Wed Aug 17, 2016 6:05 pm

hi

I get the wrong result type from SNMP (STRING instead of INTEGER, and including the unit)

as a result, I'm forced to use a script in my monitoring software (zabbix) to clean it and store the result as a number that I can graph

# snmpget -v1 -c <COMMUNITY> <IP> .1.3.6.1.4.1.14988.1.1.16.1.1.2.3
MIKROTIK-MIB::mtxrLTEModemSignalRSSI.3 = Wrong Type (should be INTEGER): STRING: "-65 dBm"

/system resource print
version: 6.33 (stable)
build-time: Nov/06/2015 12:49:27
cpu: MIPS 74Kc V5.0
cpu-count: 1
cpu-frequency: 720MHz
architecture-name: mipsbe
board-name: RB953GS-5HnT
platform: MikroTik

/interface lte info lte1
status: call in progress
pin-status: no password required
functionality: full
manufacturer: Huawei Technologies Co., Ltd.
model: ME909u-521
revision: 12.636.11.01.00
current-operator: X
current-cellid: X
access-technology: 3G
signal-strength: -57 dBm
frame-error-rate: n/a
imei: X
imsi: X
Last edited by mvalsasna on Wed Aug 17, 2016 6:14 pm, edited 1 time in total.
Top
 
mvalsasna
just joined
Posts: 18
Joined: Tue Sep 30, 2014 2:10 pm

Re: SNMP LTE signal strength

Wed Aug 17, 2016 6:13 pm

The oid for LTE signal strength is 1.3.6.1.4.1.14988.1.1.16.1.1.2
the last digit of the OID is the interface ID, and on my unit (RB953GS-5HnT with one ME909u-521) it happens to be 3:

IF-MIB::ifDescr.3 = STRING: lte1

and at least the GETNEXT SNMP operation works fine, then snmpwalk is able to find the proper oids:

snmpwalk -v2c -c PE-SNMP 10.82.128.20 .1.3.6.1.4.1.14988.1.1.16.1.1 -On
.1.3.6.1.4.1.14988.1.1.16.1.1.1.3 = INTEGER: 3
.1.3.6.1.4.1.14988.1.1.16.1.1.2.3 = Wrong Type (should be INTEGER): STRING: "-59 dBm"
.1.3.6.1.4.1.14988.1.1.16.1.1.3.3 = INTEGER: 0

snmpwalk -v2c -c PE-SNMP 10.82.128.20 .1.3.6.1.4.1.14988.1.1.16.1.1
MIKROTIK-MIB::mtxrLTEModemInterfaceIndex.3 = INTEGER: 3
MIKROTIK-MIB::mtxrLTEModemSignalRSSI.3 = Wrong Type (should be INTEGER): STRING: "-59 dBm"
MIKROTIK-MIB::mtxrLTEModemSignalRSRQ.3 = INTEGER: 0


/system resource usb print
# DEVICE VENDOR NAME SPEED
0 2:1 Linux 3.3.5 ehci_hcd RB400 EHCI 480 Mbps
1 2:2 HUAWEI Technology HUAWEI Mobile 480 Mbps
2 1:1 Linux 3.3.5 ehci_hcd RB400 EHCI 480 Mbps
Top
 
pe1chl
Forum Guru
Forum Guru
Posts: 10529
Joined: Mon Jun 08, 2015 12:09 pm

Re: SNMP LTE signal strength

Wed Aug 17, 2016 7:33 pm

Changing OIDs after a reboot or interface down/up is not a RouterOS bug, it is a problem in understanding how SNMP works.
Sure it is an often-made mistake to hardwire OIDs that end in an interface number, assuming that this number is fixed.
This is not guaranteed. Other routers e.g. from Cisco have the same behaviour.
You really need to walk the proper sections of the OID tree to first find interface number from interface name, then
construct the proper OID to fetch.
In certain situations, it is possible to omit the .2 from the OID and then walk the tree from that point, and obtain the
value you are looking for. This can be done when the interface number is the last part of the OID (as it is here), and
there is only one interface in that part of the tree.

Returning a string instead of a number of course is a bug.
Top
 
troffasky
Member
Member
Posts: 436
Joined: Wed Mar 26, 2014 4:37 pm

Re: SNMP LTE signal strength

Sun Oct 23, 2016 1:16 am

Changing OIDs after a reboot or interface down/up is not a RouterOS bug, it is a problem in understanding how SNMP works.
Sure it is an often-made mistake to hardwire OIDs that end in an interface number, assuming that this number is fixed.
This is not guaranteed.
I think you're under the impression that people have observed the SNMP interface index changing unexpectedly, whilst I think what we see in this thread is that people with different routers observe that the index of the their LTE interface is different [because they're different routers].
Other routers e.g. from Cisco have the same behaviour.
Which is why IOS has "snmp-server ifindex persist" option, to get around this annoying behaviour.
Top
 
gdanov
Member Candidate
Member Candidate
Posts: 161
Joined: Thu Jan 17, 2019 1:10 pm

Re: SNMP LTE signal strength

Wed Dec 02, 2020 11:43 am

I know this is old thread, but posting for ppl that will google like me

the lte modem is described in the mikrotik's mib file (the wiki has link to it). you have to download it locally in the right folder. this page describes it pretty well http://net-snmp.sourceforge.net/wiki/in ... P_Protocol

it's important to load the mib. the laziest way is
add to snmp.conf:

mibs +ALL
then you can query the modem via it's oid name, not the id which may change like this:
snmpwalk -v2c -c public 192.168.1.2 mtxrLTEModemTable
Top
 
User avatar
SiB
Forum Guru
Forum Guru
Posts: 1888
Joined: Sun Jan 06, 2013 11:19 pm
Location: Poland

Re: SNMP LTE signal strength

Wed Dec 02, 2020 3:35 pm

You can too:
Code: Select all
[marcin.przysowa@SXTR_LTE6] > tool snmp-walk 127.0.0.1 oid=1.3.6.1.4.1.14988.1.1.16.1.1
OID                                                                                          TYPE             VALUE                                                                                        
1.3.6.1.4.1.14988.1.1.16.1.1.2.1                                                             integer          -57                                                                                          
1.3.6.1.4.1.14988.1.1.16.1.1.3.1                                                             integer          -12                                                                                          
1.3.6.1.4.1.14988.1.1.16.1.1.4.1                                                             integer          -91                                                                                          
1.3.6.1.4.1.14988.1.1.16.1.1.5.1                                                             integer          3623426                                                                                      
1.3.6.1.4.1.14988.1.1.16.1.1.6.1                                                             integer          7                                                                                            
1.3.6.1.4.1.14988.1.1.16.1.1.7.1                                                             integer          7                                                                                            
1.3.6.1.4.1.14988.1.1.16.1.1.8.1                                                             integer          14154                                                                                        
1.3.6.1.4.1.14988.1.1.16.1.1.9.1                                                             integer          2                                                                                            
1.3.6.1.4.1.14988.1.1.16.1.1.10.1                                                            integer          11009                                                                                        
1.3.6.1.4.1.14988.1.1.16.1.1.11.1                                                            octet-string     356662100047064                                                                              
1.3.6.1.4.1.14988.1.1.16.1.1.12.1                                                            octet-string     260121000490483                                                                              
1.3.6.1.4.1.14988.1.1.16.1.1.13.1                                                            octet-string     8948121010004904830                                                                          
1.3.6.1.4.1.14988.1.1.16.1.1.14.1                                                            octet-string     Evolved 3G (LTE)

I add some offtopic.

We can grab that Signals from RB and send them out to e.g. dweet.io by
Code: Select all
local lteinfo [interface lte info lte1 once as-value ]
local lteimei ($lteinfo->"imei")
local ltersrp ($lteinfo->"rsrp")
local ltesinr ($lteinfo->"sinr")
tool fetch url="https://dweet.io/dweet/for/$lteimei\?rsrp=$ltersrp&sinr=$ltesinr" keep-result=no
Watch internal at https://dweet.io/follow/356662100047064 or create a dashboards like https://freeboard.io/board/tJL5xo :
Image
Top
 
User avatar
Larsa
Forum Guru
Forum Guru
Posts: 1611
Joined: Sat Aug 29, 2015 7:40 pm
Location: The North Pole, Santa's Workshop

Re: SNMP LTE signal strength

Wed Dec 02, 2020 3:51 pm

That was really a nice and elegant solution with dweet.io, thanks for the suggestion!

Btw, net-snmp is now on github: https://github.com/net-snmp/net-snmp. Link to tutorials is http://net-snmp.sourceforge.net/wiki/index.php/Tutorials. Not sure what the github link is tho.
Top
Post Reply

Who is online

Users browsing this forum: No registered users and 23 guests
  4. RouterOS
  5. General