After experimenting with the Dude and Net-SNMP I've come to the conclusion that RouterOS on my RB411 does not support the "IEEE802dot11-MIB". Is that right?
Some of the information that can be polled for with IEEE MIB must be available to the existing agent. Is there anything I can do to make the existing agent respond to at least some of the IEEE OIDs?
Thanx, Vic.
Re: IEEE 802.11 MIB
What exactly do you want to monitor ?
RouterOS provides the following values over wireless,
To monitor clients values on the Access Point,
To monitor values on the stations,
interface wireless print oid
RouterOS provides the following values over wireless,
To monitor clients values on the Access Point,
Code: Select all
/interface wireless registration-table print oid
0 strength=.1.3.6.1.4.1.14988.1.1.1.2.1.3.0.11.107.77.4.42.7
tx-bytes=.1.3.6.1.4.1.14988.1.1.1.2.1.4.0.11.107.77.4.42.7
rx-bytes=.1.3.6.1.4.1.14988.1.1.1.2.1.5.0.11.107.77.4.42.7
tx-packets=.1.3.6.1.4.1.14988.1.1.1.2.1.6.0.11.107.77.4.42.7
rx-packets=.1.3.6.1.4.1.14988.1.1.1.2.1.7.0.11.107.77.4.42.7
tx-rate=.1.3.6.1.4.1.14988.1.1.1.2.1.8.0.11.107.77.4.42.7
rx-rate=.1.3.6.1.4.1.14988.1.1.1.2.1.9.0.11.107.77.4.42.7interface wireless print oid
Code: Select all
0 tx-rate=.1.3.6.1.4.1.14988.1.1.1.1.1.2.4
rx-rate=.1.3.6.1.4.1.14988.1.1.1.1.1.3.4
strength=.1.3.6.1.4.1.14988.1.1.1.1.1.4.4
ssid=.1.3.6.1.4.1.14988.1.1.1.1.1.5.4
bssid=.1.3.6.1.4.1.14988.1.1.1.1.1.6.4
frequency=.1.3.6.1.4.1.14988.1.1.1.1.1.7.4Re: IEEE 802.11 MIB
Thank-you for responding.
As this project proceeds I'll let you know of any specific MIB variables that our prospect feels he can't do without. At this time, the issue isn't missing variables.
Our prospect already has thousands of access points installed. He has set up his SNMP software to take advantage of IEEE 802dot11 MIB. Now we must convince him that the cost savings of our MikroTik based solution is worth the effort of creating a monitoring solution for a "new" device class.
It would be nice if all deployments were green field, and compatibility meant only getting along with other MikroTik devices.
As this project proceeds I'll let you know of any specific MIB variables that our prospect feels he can't do without. At this time, the issue isn't missing variables.
Our prospect already has thousands of access points installed. He has set up his SNMP software to take advantage of IEEE 802dot11 MIB. Now we must convince him that the cost savings of our MikroTik based solution is worth the effort of creating a monitoring solution for a "new" device class.
It would be nice if all deployments were green field, and compatibility meant only getting along with other MikroTik devices.