There's a MIB for AirOS whith was the M gear 5.6+ There's a MIB for AF5x/af24/etc stuff that's like v3.x I think
There was a couple OIDs you could use on af5xHD in 1.1.1. They removed them in 1.1.2. There is no MIB. There's no standardized OIDs. SNMP is 99.99% useless with af5xHD. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Fri, Jan 18, 2019 at 11:34 AM Eric Kuhnke <eric.kuh...@gmail.com> wrote: > Did ubnt publish a new MIB for the af5xhd? As far as I know there is still > only one "AF" mib. For instance the specific OIDs for crucial rf data on an > af11fx are the same as on an af24. > > On Fri, Jan 18, 2019, 8:01 AM Josh Luthman <j...@imaginenetworksllc.com > wrote: > >> Eric that looks all af5x. Not af5xHD. >> >> Josh Luthman >> Office: 937-552-2340 >> Direct: 937-552-2343 >> 1100 Wayne St >> Suite 1337 >> Troy, OH 45373 >> >> >> On Fri, Jan 18, 2019 at 3:03 AM Eric Kuhnke <eric.kuh...@gmail.com> >> wrote: >> >>> From my AF5 and AF5/AF5HD snmpwalk notes. >>> >>> You should be able to build a cacti data acquisition and chart template >>> from this. >>> >>> ubnt af5 snmp mib notes, the most important items to poll >>> >>> based on snmpwalk of firmware v3.2.3 radio >>> >>> >>> radio board uptime in seconds >>> myworkstationhostname:~ erickuhnke$ snmpwalk -v1 -O n -c >>> mysnmpcommunitystring ip.of.my.af5.radio .1.3.6.1.4.1.41112.1.3.2.1.38.1 >>> .1.3.6.1.4.1.41112.1.3.2.1.38.1 = INTEGER: 4951 >>> >>> >>> radio is enabled yes or no, 1=enabled, 2=disabled >>> myworkstationhostname:~ erickuhnke$ snmpwalk -v1 -O n -c >>> mysnmpcommunitystring ip.of.my.af5.radio .1.3.6.1.4.1.41112.1.3.1.1.2.1 >>> .1.3.6.1.4.1.41112.1.3.1.1.2.1 = INTEGER: 1 >>> >>> >>> radio link state, 0=down, 1=up >>> myworkstationhostname:~ erickuhnke$ snmpwalk -v1 -O n -c >>> mysnmpcommunitystring ip.of.my.af5.radio .1.3.6.1.4.1.41112.1.3.2.1.26.1 >>> .1.3.6.1.4.1.41112.1.3.2.1.26.1 = INTEGER: 1 >>> >>> >>> radio link uptime in seconds >>> myworkstationhostname:~ erickuhnke$ snmpwalk -v1 -O n -c >>> mysnmpcommunitystring ip.of.my.af5.radio .1.3.6.1.4.1.41112.1.3.2.1.44.1 >>> .1.3.6.1.4.1.41112.1.3.2.1.44.1 = INTEGER: 2537 >>> >>> >>> radio mode master or slave, 1=master, 2=slave, 3=spectrum analysis >>> myworkstationhostname:~ erickuhnke$ snmpwalk -v1 -O n -c >>> mysnmpcommunitystring ip.of.my.af5.radio .1.3.6.1.4.1.41112.1.3.1.1.3.1 >>> .1.3.6.1.4.1.41112.1.3.1.1.3.1 = INTEGER: 1 >>> >>> >>> gps satellites visible >>> myworkstationhostname:~ erickuhnke$ snmpwalk -v1 -O n -c >>> mysnmpcommunitystring ip.of.my.af5.radio .1.3.6.1.4.1.41112.1.3.2.1.34.1 >>> .1.3.6.1.4.1.41112.1.3.2.1.34.1 = INTEGER: 6 >>> >>> >>> gps satellites being tracked >>> myworkstationhostname:~ erickuhnke$ snmpwalk -v1 -O n -c >>> mysnmpcommunitystring ip.of.my.af5.radio .1.3.6.1.4.1.41112.1.3.2.1.35.1 >>> .1.3.6.1.4.1.41112.1.3.2.1.35.1 = INTEGER: 8 >>> >>> >>> gps sync status, 1=off, 2=yes >>> myworkstationhostname:~ erickuhnke$ snmpwalk -v1 -O n -c >>> mysnmpcommunitystring ip.of.my.af5.radio .1.3.6.1.4.1.41112.1.3.1.1.8.1 >>> .1.3.6.1.4.1.41112.1.3.1.1.8.1 = INTEGER: 2 >>> >>> >>> >>> radio link distance in meters >>> myworkstationhostname:~ erickuhnke$ snmpwalk -v1 -O n -c >>> mysnmpcommunitystring ip.of.my.af5.radio .1.3.6.1.4.1.41112.1.3.2.1.4.1 >>> .1.3.6.1.4.1.41112.1.3.2.1.4.1 = INTEGER: 8159 >>> >>> >>> radio0 temperature in c >>> myworkstationhostname:~ erickuhnke$ snmpwalk -v1 -O n -c >>> mysnmpcommunitystring ip.of.my.af5.radio .1.3.6.1.4.1.41112.1.3.2.1.8.1 >>> .1.3.6.1.4.1.41112.1.3.2.1.8.1 = INTEGER: 32 >>> >>> >>> radio1 temperature in c >>> myworkstationhostname:~ erickuhnke$ snmpwalk -v1 -O n -c >>> mysnmpcommunitystring ip.of.my.af5.radio .1.3.6.1.4.1.41112.1.3.2.1.10.1 >>> .1.3.6.1.4.1.41112.1.3.2.1.10.1 = INTEGER: 46 >>> >>> >>> >>> radio duplex mode, 1=halfduplex, 2=fullduplex >>> myworkstationhostname:~ erickuhnke$ snmpwalk -v1 -O n -c >>> mysnmpcommunitystring ip.of.my.af5.radio .1.3.6.1.4.1.41112.1.3.1.1.4.1 >>> .1.3.6.1.4.1.41112.1.3.1.1.4.1 = INTEGER: 2 >>> >>> >>> radio tx frequency in MHz >>> myworkstationhostname:~ erickuhnke$ snmpwalk -v1 -O n -c >>> mysnmpcommunitystring ip.of.my.af5.radio .1.3.6.1.4.1.41112.1.3.1.1.5.1 >>> .1.3.6.1.4.1.41112.1.3.1.1.5.1 = INTEGER: 5666 >>> >>> >>> radio rx frequency in MHz >>> myworkstationhostname:~ erickuhnke$ snmpwalk -v1 -O n -c >>> mysnmpcommunitystring ip.of.my.af5.radio .1.3.6.1.4.1.41112.1.3.1.1.6.1 >>> .1.3.6.1.4.1.41112.1.3.1.1.6.1 = INTEGER: 5709 >>> >>> >>> radio tx power >>> myworkstationhostname:~ erickuhnke$ snmpwalk -v1 -O n -c >>> mysnmpcommunitystring ip.of.my.af5.radio .1.3.6.1.4.1.41112.1.3.1.1.9.1 >>> .1.3.6.1.4.1.41112.1.3.1.1.9.1 = INTEGER: 30 >>> >>> >>> >>> radio rx gain setting, 1=low, 2=high >>> myworkstationhostname:~ erickuhnke$ snmpwalk -v1 -O n -c >>> mysnmpcommunitystring ip.of.my.af5.radio .1.3.6.1.4.1.41112.1.3.1.1.10.1 >>> .1.3.6.1.4.1.41112.1.3.1.1.10.1 = INTEGER: 2 >>> >>> >>> >>> radio max modulation setting, 0=qpsk, 8=256qam >>> myworkstationhostname:~ erickuhnke$ snmpwalk -v1 -O n -c >>> mysnmpcommunitystring ip.of.my.af5.radio .1.3.6.1.4.1.41112.1.3.1.1.11.1.1 >>> .1.3.6.1.4.1.41112.1.3.1.1.11.1 = INTEGER: 8 >>> >>> >>> >>> radio current tx modulation rate >>> 0=qpsk siso >>> 2=qpsk mimo >>> 4=16qam mimo >>> 6=64qam mimo >>> 8=256qam mimo >>> myworkstationhostname:~ erickuhnke$ snmpwalk -v1 -O n -c >>> mysnmpcommunitystring ip.of.my.af5.radio .1.3.6.1.4.1.41112.1.3.2.1.2.1 >>> .1.3.6.1.4.1.41112.1.3.2.1.2.1 = INTEGER: 6 >>> >>> >>> radio current rx capacity in bits per second (divide by 1000000 to get >>> Mbps) >>> myworkstationhostname:~ erickuhnke$ snmpwalk -v1 -O n -c >>> mysnmpcommunitystring ip.of.my.af5.radio .1.3.6.1.4.1.41112.1.3.2.1.5.1 >>> .1.3.6.1.4.1.41112.1.3.2.1.5.1 = INTEGER: 148446720 >>> >>> >>> radio current tx capacity in bits per second (divide by 1000000 to get >>> Mbps) >>> myworkstationhostname:~ erickuhnke$ snmpwalk -v1 -O n -c >>> mysnmpcommunitystring ip.of.my.af5.radio .1.3.6.1.4.1.41112.1.3.2.1.6.1 >>> .1.3.6.1.4.1.41112.1.3.2.1.6.1 = INTEGER: 214749440 >>> >>> >>> radio rx power rsl chain 0 >>> myworkstationhostname:~ erickuhnke$ snmpwalk -v1 -O n -c >>> mysnmpcommunitystring ip.of.my.af5.radio .1.3.6.1.4.1.41112.1.3.2.1.11.1 >>> .1.3.6.1.4.1.41112.1.3.2.1.11.1 = INTEGER: -74 >>> >>> >>> radio rx power rsl chain 1 >>> myworkstationhostname:~ erickuhnke$ snmpwalk -v1 -O n -c >>> mysnmpcommunitystring ip.of.my.af5.radio .1.3.6.1.4.1.41112.1.3.2.1.14.1 >>> .1.3.6.1.4.1.41112.1.3.2.1.14.1 = INTEGER: -74 >>> >>> >>> >>> radio tx frames OK >>> myworkstationhostname:~ erickuhnke$ snmpwalk -v1 -O n -c >>> mysnmpcommunitystring ip.of.my.af5.radio .1.3.6.1.4.1.41112.1.3.3.1.2.1 >>> .1.3.6.1.4.1.41112.1.3.3.1.2.1 = Counter64: 144530 >>> >>> >>> radio rx frames OK >>> myworkstationhostname:~ erickuhnke$ snmpwalk -v1 -O n -c >>> mysnmpcommunitystring ip.of.my.af5.radio .1.3.6.1.4.1.41112.1.3.3.1.3.1 >>> .1.3.6.1.4.1.41112.1.3.3.1.3.1 = Counter64: 0 >>> >>> >>> radio tx errored frames >>> myworkstationhostname:~ erickuhnke$ snmpwalk -v1 -O n -c >>> mysnmpcommunitystring ip.of.my.af5.radio .1.3.6.1.4.1.41112.1.3.3.1.11.1 >>> .1.3.6.1.4.1.41112.1.3.3.1.11.1 = Counter64: 12 >>> >>> >>> >>> radio rx frames with crc error >>> myworkstationhostname:~ erickuhnke$ snmpwalk -v1 -O n -c >>> mysnmpcommunitystring ip.of.my.af5.radio .1.3.6.1.4.1.41112.1.3.3.1.4.1 >>> .1.3.6.1.4.1.41112.1.3.3.1.4.1 = Counter64: 0 >>> >>> >>> radio rx frames with alignment error >>> myworkstationhostname:~ erickuhnke$ snmpwalk -v1 -O n -c >>> mysnmpcommunitystring ip.of.my.af5.radio .1.3.6.1.4.1.41112.1.3.3.1.5.1 >>> .1.3.6.1.4.1.41112.1.3.3.1.5.1 = Counter64: 0 >>> >>> >>> radio rx errored frames >>> myworkstationhostname:~ erickuhnke$ snmpwalk -v1 -O n -c >>> mysnmpcommunitystring ip.of.my.af5.radio .1.3.6.1.4.1.41112.1.3.3.1.10.1 >>> .1.3.6.1.4.1.41112.1.3.3.1.10.1 = Counter64: 0 >>> >>> >>> >>> On Thu, Jan 17, 2019 at 2:29 PM dave <dmilho...@wletc.com> wrote: >>> >>>> something comes to mind... Oh yeah PTP550 :) >>>> >>>> >>>> On 1/17/19 1:48 PM, Josh Luthman wrote: >>>> >>>> 1.1.1 is one set of OIDs >>>> 1.1.2 is another set of OIDs (and it lost some capabilities from 1.1.1) >>>> >>>> There's a MIB on the website that sucks. >>>> >>>> I've been emailing them back/forth about this so we can get a useful >>>> MIB like we had/have with af5x for months. >>>> >>>> Josh Luthman >>>> Office: 937-552-2340 >>>> Direct: 937-552-2343 >>>> 1100 Wayne St >>>> Suite 1337 >>>> Troy, OH 45373 >>>> >>>> >>>> On Thu, Jan 17, 2019 at 10:30 AM Zack Deveaux <zack_deve...@hotmail.com> >>>> wrote: >>>> >>>>> Has anyone made Cacti templates/Data Queries for Airfiber 5XHD >>>>> radios? They use a different MIB than the other AirFiber radios and the >>>>> OIDs for the main radio values seem to be indexed, so differ based on >>>>> which >>>>> link I'm graphing. I'm not great with creating xml/Data Queries in Cacti, >>>>> hoping someone has already gone through the pain and is willing to share. >>>>> >>>>> -Zack D >>>>> -- >>>>> AF mailing list >>>>> AF@af.afmug.com >>>>> http://af.afmug.com/mailman/listinfo/af_af.afmug.com >>>>> >>>> >>>> -- >>>> -- >>>> AF mailing list >>>> AF@af.afmug.com >>>> http://af.afmug.com/mailman/listinfo/af_af.afmug.com >>>> >>> -- >>> AF mailing list >>> AF@af.afmug.com >>> http://af.afmug.com/mailman/listinfo/af_af.afmug.com >>> >> -- >> AF mailing list >> AF@af.afmug.com >> http://af.afmug.com/mailman/listinfo/af_af.afmug.com >> > -- > AF mailing list > AF@af.afmug.com > http://af.afmug.com/mailman/listinfo/af_af.afmug.com >
-- AF mailing list AF@af.afmug.com http://af.afmug.com/mailman/listinfo/af_af.afmug.com
