09-14-2010 09:25 AM
No such instance currently exists at this OID.
All the aruba AP branch:
number of down APs
I'm doing it like it says on the Using MIBs chapter on the arubaOS 3.4.2MG
Number of Down APs per Controller
snmpwalk -v 2c -m ALL -c
With other OIDs it is working correctly
09-24-2010 06:14 AM
I am having the same issue, that nothing in the .188.8.131.52.4.1.14823.2.3 branch is returning any values, while everything in the .184.108.40.206.4.1.14823.2.2 branch is returning values. I have a 650 controller with 220.127.116.11.
I opened a case with tech support, who said they can replicate it. Their response exactly was:
"I was able to replicate the issue internally
• SNMP Server : Ireasoning
• Controller : 800
• OS: 18.104.22.168
I will do further testing and will report the issue to the Engineering. If you have further queries please feel free to get back to us."
I'll post their answer when I get it.
09-28-2010 07:10 AM
this OID is not implemented. You may have noticed there is less verbose description for this OID than for other OIDs.
Statement from support is:
'This particular OID is not there in the controller. We have also informed the development team regarding this.'
09-29-2010 04:45 AM
ArubaOS_3.4.2MG.pdf one can read
.22.214.171.124.4.1.148126.96.36.199.188.8.131.52.1 as wlsxvoicecdrentry and this is readable on the controller.
The bad information is on the page 386 that says all this voice data is on OID:
10-20-2010 09:18 AM
Aruba Engineering said that they are no longer present in firmware after 3.x, so of course they cannot be queried.
The reason given was that querying AP's/AM's directly caused them to crash sometimes, so Aruba decided to eliminate the ability to directly make SNMP queries to AP's/AM's, and to eliminate the entire .2.3 MIB. Instead, only controllers can be SNMP queried after 3.x firmware. So, we can now only query the controller for .2.2 OIDs.
Here is their exact answer, "I have received an update from Engineering that the OIDs containing (184.108.40.206.4.1.14823.2.3 ) are AP MIBs and will only work on AP/AM. These MIBs do not work on the controller. It was not supported after 3.x Aruba OS." I then clarified this answer on a phone call with the tech support person.