(AF LTU) how to add multiplier to value from sensor?

Help
#1

so i’ve been trying to make wireless sensor for AF5XHD (AirosAfLtu.php)
using snmprec.py i found this OID

TX 1.3.6.1.4.1.41112.1.10.1.4.1.3.24.232.41.30.54.151
RX 1.3.6.1.4.1.41112.1.10.1.4.1.4.24.232.41.30.54.151

it’s working finally we have some rate to graph, but the problem value only detected as Kbps, it should be Mbps (already compared with live radio, the number is correct)
so question is how can we add multiplier ? i want to multiply it by 1000 so it will display correct number

indent preformatted text by 4 spaces

Discovered LibreNMS\Device\WirelessSensor Array
(
[sensor_class] => rate
[device_id] => 8
[sensor_oids] => Array
(
[0] => .1.3.6.1.4.1.41112.1.10.1.4.1.3.24.232.41.30.54.151
)

[sensor_index] => 1
[sensor_type] => airos-af-ltu-tx
[sensor_descr] => Tx Capacity
[sensor_divisor] => 1
[sensor_multiplier] => 1

)
..4.1.41...151 = No Such Instance currently exists at this OID

Discovered LibreNMS\Device\WirelessSensor Array
(
[sensor_class] => rate
[device_id] => 8
[sensor_oids] => Array
(
[0] => .1.3.6.1.4.1.41112.1.10.1.4.1.4.24.232.41.30.54.151
)

 [sensor_type] => airos-af-ltu-rx
[sensor_descr] => Rx Capacity
[sensor_divisor] => 1
[sensor_multiplier] => 1

indent preformatted text by 4 spaces
public function discoverWirelessRate()
            {
                            $tx_oid = '.1.3.6.1.4.1.41112.1.10.1.4.1.3.24.232.41.30.54.151'; // UBNT-AirFIBER-MIB::txCapacity.1
                            $rx_oid = '.1.3.6.1.4.1.41112.1.10.1.4.1.4.24.232.41.30.54.151'; // UBNT-AirFIBER-MIB::rxCapacity.1
                            return array(
                            new WirelessSensor('rate',$this->getDeviceId(), $tx_oid,'airos-af-ltu-tx',1,'Tx Capacity'),
                            new WirelessSensor('rate',$this->getDeviceId(), $rx_oid,'airos-af-ltu-rx',1,'Rx Capacity'),
                                    );
        }

rate
rate782×273 58.2 KB

firefox_81dvEAOqvE

#2

well… this ubnt AF LTU sure is broken…

i have 2 ptp link using AF5XHD see what happen when using snmprec.py

1st link

1.3.6.1.4.1.41112.1.10.1.4.1.3.24.232.41.30.54.151|2|142720
1.3.6.1.4.1.41112.1.10.1.4.1.4.24.232.41.30.54.151|2|214080

2nd link

1.3.6.1.4.1.41112.1.10.1.4.1.3.24.232.41.30.88.103|2|180224
1.3.6.1.4.1.41112.1.10.1.4.1.4.24.232.41.30.88.103|2|268800

no wonder my 2nd link are not detecting new wireless sensor

#3

In a sensor discovery, the multiplier does exactly what you want. But you need to apply it only for a device, and a sensor that requires it. Usually, the MIB says what kind of multiplier / divisor should be used.
Now if the device is broken, and replies the wrong value (and is the only one of its kind to do so) may be a firmware upgrade could help (or a ticket opened at the vendor to get the patch).

#4

yep, reading from
LibreNMS/Device/WirelessSensor.php, found where to put those multiplier, since all ptp device(connected) have different OID, so make it like this and it works

public function discoverWirelessRate()
            {
                            $tx_oid = '.1.3.6.1.4.1.41112.1.10.1.4.1.3.24.232.41.30.54.151'; // UBNT-AirFIBER-MIB::txCapacity.1
                            $rx_oid = '.1.3.6.1.4.1.41112.1.10.1.4.1.4.24.232.41.30.54.151'; // UBNT-AirFIBER-MIB::rxCapacity.1
                            $tx_oid1 = '.1.3.6.1.4.1.41112.1.10.1.4.1.3.24.232.41.30.88.103';  
                            $rx_oid1 = '.1.3.6.1.4.1.41112.1.10.1.4.1.4.24.232.41.30.88.103'; 
                            return array(
                            new WirelessSensor('rate',$this->getDeviceId(), $tx_oid,'airos-af-ltu-tx', 1,'Tx Capacity', null, 1000),
                            new WirelessSensor('rate',$this->getDeviceId(), $rx_oid,'airos-af-ltu-rx', 1,'Rx Capacity', null, 1000),
                            new WirelessSensor('rate',$this->getDeviceId(), $tx_oid1,'airos-af-ltu-tx',1,'Tx Capacity', null, 1000),
                            new WirelessSensor('rate',$this->getDeviceId(), $rx_oid1,'airos-af-ltu-rx',1,'Rx Capacity', null, 1000),
                                    );
        }

searching on vendor forum, well… they gonna fix mib/oid but still unknown ETA

#5