I'm not seeing the snapshots you're referring to. Also, there's no ArubaOS firmware 7.4, so I'm suspecting you're referring to some HPE switch documentation. It's possible that ENTITY-MIB was supported by HPE switches, but not the Aruba controllers since the merger was fairly recent. You might try using a MIB crawling tool on the Aruba 6000 (since I don't have that model in my home lab) to see which of the MIB tables maps out better. I was trying to reverse engineer it from the AirWave code, but I was guestimating at the MIBs based on their filenames. I actually did try walking the MIBs I suggested, but the WSLX-SWITCH-MIB ironically is about the APs/BSSIDs/ESSIDs/usage counters - yay to whoever named that MIB. The WLSX-SYSTEMEXT-MIB showed a bit more.
.1.3.6.1.4.1.14823.2.2.1.2.1.1.0 = IpAddress: 100.100.130.30
.1.3.6.1.4.1.14823.2.2.1.2.1.2.0 = STRING: Aruba7210test
.1.3.6.1.4.1.14823.2.2.1.2.1.3.0 = STRING: A7210-US
.1.3.6.1.4.1.14823.2.2.1.2.1.4.0 = INTEGER: master(1)
.1.3.6.1.4.1.14823.2.2.1.2.1.5.0 = IpAddress: 0.0.0.0
.1.3.6.1.4.1.14823.2.2.1.2.1.6.0 = STRING: 2018-04-19 15:30:07
.1.3.6.1.4.1.14823.2.2.1.2.1.7.0 = STRING: 0:1:1c:1:1b:32
.1.3.6.1.4.1.14823.2.2.1.2.1.8.0 = STRING:
.1.3.6.1.4.1.14823.2.2.1.2.1.9.0 = STRING:
.1.3.6.1.4.1.14823.2.2.1.2.1.10.0 = STRING: 27.00 degrees Celsius (NORMAL)
.1.3.6.1.4.1.14823.2.2.1.2.1.11.0 = STRING:
.1.3.6.1.4.1.14823.2.2.1.2.1.12.0 = INTEGER: 2
.1.3.6.1.4.1.14823.2.2.1.2.1.13.1.2.1 = STRING: Supervisor Card CPU
.1.3.6.1.4.1.14823.2.2.1.2.1.13.1.2.8 = STRING: Network Processor CPU8
.1.3.6.1.4.1.14823.2.2.1.2.1.13.1.2.9 = STRING: Network Processor CPU9
.1.3.6.1.4.1.14823.2.2.1.2.1.13.1.2.10 = STRING: Network Processor CPU10
.1.3.6.1.4.1.14823.2.2.1.2.1.13.1.2.11 = STRING: Network Processor CPU11
.1.3.6.1.4.1.14823.2.2.1.2.1.13.1.2.12 = STRING: Network Processor CPU12
.1.3.6.1.4.1.14823.2.2.1.2.1.13.1.2.13 = STRING: Network Processor CPU13
.1.3.6.1.4.1.14823.2.2.1.2.1.13.1.2.14 = STRING: Network Processor CPU14
.1.3.6.1.4.1.14823.2.2.1.2.1.13.1.2.15 = STRING: Network Processor CPU15
.1.3.6.1.4.1.14823.2.2.1.2.1.13.1.3.1 = INTEGER: 3
.1.3.6.1.4.1.14823.2.2.1.2.1.13.1.3.8 = INTEGER: 0
.1.3.6.1.4.1.14823.2.2.1.2.1.13.1.3.9 = INTEGER: 0
.1.3.6.1.4.1.14823.2.2.1.2.1.13.1.3.10 = INTEGER: 0
.1.3.6.1.4.1.14823.2.2.1.2.1.13.1.3.11 = INTEGER: 0
.1.3.6.1.4.1.14823.2.2.1.2.1.13.1.3.12 = INTEGER: 0
.1.3.6.1.4.1.14823.2.2.1.2.1.13.1.3.13 = INTEGER: 0
.1.3.6.1.4.1.14823.2.2.1.2.1.13.1.3.14 = INTEGER: 0
.1.3.6.1.4.1.14823.2.2.1.2.1.13.1.3.15 = INTEGER: 0
.1.3.6.1.4.1.14823.2.2.1.2.1.14.1.2.1 = INTEGER: ram(1)
.1.3.6.1.4.1.14823.2.2.1.2.1.14.1.2.2 = INTEGER: flashMemory(2)
.1.3.6.1.4.1.14823.2.2.1.2.1.14.1.2.3 = INTEGER: flashMemory(2)
.1.3.6.1.4.1.14823.2.2.1.2.1.14.1.3.1 = INTEGER: 2048
.1.3.6.1.4.1.14823.2.2.1.2.1.14.1.3.2 = INTEGER: 1535
.1.3.6.1.4.1.14823.2.2.1.2.1.14.1.3.3 = INTEGER: 5713
.1.3.6.1.4.1.14823.2.2.1.2.1.14.1.4.1 = INTEGER: 22
.1.3.6.1.4.1.14823.2.2.1.2.1.14.1.4.2 = INTEGER: 153
.1.3.6.1.4.1.14823.2.2.1.2.1.14.1.4.3 = INTEGER: 139
.1.3.6.1.4.1.14823.2.2.1.2.1.14.1.5.1 = STRING: /tmp
.1.3.6.1.4.1.14823.2.2.1.2.1.14.1.5.2 = STRING: /flash
.1.3.6.1.4.1.14823.2.2.1.2.1.14.1.5.3 = STRING: /flash1
.1.3.6.1.4.1.14823.2.2.1.2.1.15.1.2.1 = INTEGER: 5170880
.1.3.6.1.4.1.14823.2.2.1.2.1.15.1.3.1 = INTEGER: 1849408
.1.3.6.1.4.1.14823.2.2.1.2.1.15.1.4.1 = INTEGER: 3321472
.1.3.6.1.4.1.14823.2.2.1.2.1.16.1.2.1 = INTEGER: sw7210(17)
.1.3.6.1.4.1.14823.2.2.1.2.1.16.1.3.1 = INTEGER: 6
.1.3.6.1.4.1.14823.2.2.1.2.1.16.1.4.1 = INTEGER: 0
.1.3.6.1.4.1.14823.2.2.1.2.1.16.1.5.1 = INTEGER: 6
.1.3.6.1.4.1.14823.2.2.1.2.1.16.1.6.1 = STRING:
.1.3.6.1.4.1.14823.2.2.1.2.1.16.1.7.1 = STRING:
.1.3.6.1.4.1.14823.2.2.1.2.1.16.1.8.1 = STRING: Date:05/22/15
.1.3.6.1.4.1.14823.2.2.1.2.1.16.1.9.1 = STRING: Rev:06.00
.1.3.6.1.4.1.14823.2.2.1.2.1.16.1.10.1 = STRING: (Rev: 1.4)
.1.3.6.1.4.1.14823.2.2.1.2.1.16.1.11.1 = STRING:
.1.3.6.1.4.1.14823.2.2.1.2.1.16.1.12.1 = INTEGER: active(1)
.1.3.6.1.4.1.14823.2.2.1.2.1.16.1.13.1 = INTEGER: 0
.1.3.6.1.4.1.14823.2.2.1.2.1.16.1.14.1 = STRING:
.1.3.6.1.4.1.14823.2.2.1.2.1.17.1.2.0 = INTEGER: active(1)
.1.3.6.1.4.1.14823.2.2.1.2.1.17.1.2.1 = INTEGER: active(1)
.1.3.6.1.4.1.14823.2.2.1.2.1.17.1.2.2 = INTEGER: active(1)
.1.3.6.1.4.1.14823.2.2.1.2.1.17.1.2.3 = INTEGER: active(1)
.1.3.6.1.4.1.14823.2.2.1.2.1.18.1.2.0 = INTEGER: inactive(2)
.1.3.6.1.4.1.14823.2.2.1.2.1.18.1.2.1 = INTEGER: active(1)
.1.3.6.1.4.1.14823.2.2.1.2.1.19.1.2.10.51.3.190 = INTEGER: master(1)
.1.3.6.1.4.1.14823.2.2.1.2.1.19.1.3.10.51.3.190 = STRING: Building1.floor1
.1.3.6.1.4.1.14823.2.2.1.2.1.19.1.4.10.51.3.190 = STRING: 6.5.1.1_56903
.1.3.6.1.4.1.14823.2.2.1.2.1.19.1.5.10.51.3.190 = INTEGER: active(1)
.1.3.6.1.4.1.14823.2.2.1.2.1.19.1.6.10.51.3.190 = STRING: Aruba7210test
.1.3.6.1.4.1.14823.2.2.1.2.1.19.1.7.10.51.3.190 = STRING:
.1.3.6.1.4.1.14823.2.2.1.2.1.20.1.2.1 = STRING:
.1.3.6.1.4.1.14823.2.2.1.2.1.20.1.2.2 = STRING:
.1.3.6.1.4.1.14823.2.2.1.2.1.20.1.3.1 = STRING: 2016-05-05 23:26:24
.1.3.6.1.4.1.14823.2.2.1.2.1.20.1.3.2 = STRING: 2016-05-05 23:26:42
.1.3.6.1.4.1.14823.2.2.1.2.1.20.1.4.1 = STRING:
.1.3.6.1.4.1.14823.2.2.1.2.1.20.1.4.2 = STRING:
.1.3.6.1.4.1.14823.2.2.1.2.1.20.1.5.1 = STRING: E
.1.3.6.1.4.1.14823.2.2.1.2.1.20.1.5.2 = STRING: E
.1.3.6.1.4.1.14823.2.2.1.2.1.20.1.6.1 = STRING:
.1.3.6.1.4.1.14823.2.2.1.2.1.20.1.6.2 = STRING:
.1.3.6.1.4.1.14823.2.2.1.2.1.21.0 = INTEGER: 4
.1.3.6.1.4.1.14823.2.2.1.2.1.22.0 = INTEGER: 0
.1.3.6.1.4.1.14823.2.2.1.2.1.23.0 = INTEGER: 50
.1.3.6.1.4.1.14823.2.2.1.2.1.24.0 = INTEGER: false(2)
.1.3.6.1.4.1.14823.2.2.1.2.1.25.0 = STRING: User reboot
.1.3.6.1.4.1.14823.2.2.1.2.1.26.0 = Timeticks: (0) 0:00:00.00
.1.3.6.1.4.1.14823.2.2.1.2.1.27.0 = STRING: A1.0
.1.3.6.1.4.1.14823.2.2.1.2.1.28.0 = STRING: 6.5.1.1
.1.3.6.1.4.1.14823.2.2.1.2.1.29.0 = STRING:
.1.3.6.1.4.1.14823.2.2.1.2.1.30.0 = Gauge32: 4
.1.3.6.1.4.1.14823.2.2.1.2.1.31.0 = Gauge32: 35
.1.3.6.1.4.1.14823.2.2.1.2.1.32.0 = INTEGER: 0
.1.3.6.1.4.1.14823.2.2.1.2.1.33.0 = INTEGER: 0
.1.3.6.1.4.1.14823.2.2.1.2.2.1.0 = INTEGER: 0
.1.3.6.1.4.1.14823.2.2.1.2.2.2.0 = INTEGER: 158
.1.3.6.1.4.1.14823.2.2.1.2.2.3.0 = INTEGER: 7012
.1.3.6.1.4.1.14823.2.2.1.2.2.4.0 = INTEGER: 12
.1.3.6.1.4.1.14823.2.2.1.2.2.5.0 = INTEGER: 0
.1.3.6.1.4.1.14823.2.2.1.2.2.6.0 = INTEGER: 0
.1.3.6.1.4.1.14823.2.2.1.2.2.7.0 = INTEGER: 2
.1.3.6.1.4.1.14823.2.2.1.2.2.8.0 = INTEGER: 9
.1.3.6.1.4.1.14823.2.2.1.2.2.9.0 = INTEGER: 0
.1.3.6.1.4.1.14823.2.2.1.2.2.10.0 = INTEGER: 0
.1.3.6.1.4.1.14823.2.2.1.2.2.11.0 = INTEGER: 0
Keep in mind, my output is from a 7210 controller which isn't a chassis, so it might work for your needs, but if this isn't what you're looking for, it may be worth it to open a TAC case to inquire. And like Praveen said - it'd be a feature request to get ArubaOS to adopt the ENTITY-MIB model which you could file at the same time if you contact TAC.
@csudaya wrote:
>From 7.4 user guide , I see reference to ENTITY-MIB in the user guide ( refer snapshot )
However , I run 6.4.4.6 on my device ( However , 6.4 user guide does not have reference ).