Try putting a .0 at the end of that OID and see if it then starts graphing. That's common with a lot of OIDs.

Also, how the hell would they not support the standard IF-MIB interface OID tree. I assume you've tried that anyway. I don't have any of that shit to test against. A walk of .1.3.6.1.2.1.2 would tell you if the standard stuff is there. That's dumb if it's not.
It's not.

Or the interfaces in the if-mib are virtual interfaces that are not showing actual traffic....or something. Hard to remember.



On 9/15/2015 10:36 PM, That One Guy /sarcasm wrote:
half those would never graph: for example

danEthRxTotalBytes <http://support.cambiumnetworks.com/framed/onlinetools/content.DAN-BASIC-MIB-ADMIN.html#danEthRxTotalBytes> Object ID: 1.3.1.4.1.32584.1.8.13.5
Total number of bytes received.


On Tue, Sep 15, 2015 at 10:31 PM, Colin Stanners <cstann...@gmail.com <mailto:cstann...@gmail.com>> wrote:

    Do you want it from the AP
    
http://support.cambiumnetworks.com/framed/onlinetools/content.DAN-BASIC-MIB-ADMIN.html
    Or the CPEs?
    
http://support.cambiumnetworks.com/framed/onlinetools/content.Motorola-CPE-PRIVATE-MIB.html

    On Tue, Sep 15, 2015 at 10:16 PM, That One Guy /sarcasm
    <thatoneguyst...@gmail.com> wrote:

        I need to know OIDS (numeric) that can be monitored
        successfully on these pieces of shit. Im stuck with it. We
        have the basics rssi, cinr 1 cinr 2 etc. Any ethernet stats
        would be nice.

        RIght know we have random loss to the subs, im guessing its
        something to do with some interference, But it could boil
        down to a saturated AP, and so far as I have been able to
        tell you cant monitor throughput on these trash cans other
        than monitoring the ethernet of the connected device

-- If you only see yourself as part of the team but
        you don't see your team as part of yourself you have already
        failed as part of the team.





--
If you only see yourself as part of the team but you don't see your team as part of yourself you have already failed as part of the team.


Reply via email to