As some of you know I have been working on a canopy data collection service, which is designed to pull information out of the modules (such as jitter, rssi, octets etc…) and write the data into a SQL database.
I started by pulling the data out of the subscriber modules, but then realized that there is no way of resetting the information back to zero when I am finished. So I embarked on another attempt to get this working straight, and started looking into how I could pull the data out of 10 ap’s, rather than 100 modules.
After looking at the mib for an AP, I found what looks to be like the data from modules connected to the ap: (OID .18.104.22.168.22.214.171.124.3.1.4) I programmed a little app to run down the list and collect all the data in the list.
The first thing is that LUID 1 is not valid. All APs start their LUID numbering at 2.
Also, I think you need to double check the OIDs that you are using.
For instance, the OID for the InOctets of LUID 2 is .126.96.36.199.188.8.131.52.184.108.40.206.7.2 the OID for the InOctets of LUID 3 is .220.127.116.11.18.104.22.168.22.214.171.124.7.3 the OID for the LastJitter of LUID 2 is .126.96.36.199.188.8.131.52.184.108.40.206.23.2 the OID for the LastJitter of LUID 3 is .220.127.116.11.18.104.22.168.22.214.171.124.23.3
A MIB Browser and the Canopy MIBs work great for this.
Ok, I was not aware that the LUID started at 2, so thank you. I have got the data working now with the OID + the luid number after like you suggested and that works great also
When looking through the canopy AP Mib, I found: .126.96.36.199.188.8.131.52.184.108.40.206.19 (Which is describes as: Current operational state of an interface. 0 = Idle 1 = In Session 2 = Clearing 3 = Re-registration downlink reset 4 = Authentication Challenge 5 = Registering 6 = Not in use)
Is there any way to write to the module to tell it to reset the linkOutOctets and the linkInOctets? Possibly by using the “2 = Clearing” on the oid: .220.127.116.11.18.104.22.168.22.214.171.124.19?
That way after data is written to the database everything can be reset.
The operational state is a read-only value and reflects the current status of the sm’s connection to the ap. Those listed values in your message above will be the ones that you can see on the sessions page on the same line as the LUID after “State:”. Mostly you will only see Idle or In Session, but if you catch the sessions page while a radio is registering, you will see the others depending on when in the cycle you catch it.