Is there is a change in SNMP traps for AP UP & Down status post 6.3.x code stream

Aruba Employee

A network admin would have configured AP UP/Down status in pre 6.3 code stream and it would not work after upgrading to 6.3. This article explains on what the change and what config should be done to get this working.

 

Here is the list of SNMP traps in pre-6.3 controller, in 6.3 we do not have wlsxAccessPointIsUp and wlsxAccessPointIsDown traps.
This would have worked fine in earlier versions.
 
#show snmp trap-list | include AccessPointIs
wlsxAccessPointIsDown                      Yes           Enabled
wlsxAccessPointIsUp                        Yes           Enabled
wlsxNAccessPointIsDown                     Yes           Disabled
wlsxNAccessPointIsUp                       Yes           Disabled
 
This is on controller running 6.3


#show snmp trap-list | include AccessPointIs
wlsxNAccessPointIsDown                     Yes           Disabled
wlsxNAccessPointIsUp                       Yes           Disabled
 
(Aruba) (config) #snmp-server trap enable wlsxNAccessPointIsDown
(Aruba) (config) #snmp-server trap enable wlsxNAccessPointIsUp

Enabling the above in 6.3 code would send a trigger when there is an event AP Status change.
 
As far as the AP Up/Down traps (wlsxAccessPointIsUp , wlsxAccessPointIsDown)are older traps and they are deprecated in 6.3 code. 
 
There are newer traps - wlsxNAccessPointIsUp and wlsxNAccessPointIsDown trap that is generated only when the AP goes up and down.  Hence we notice the change in syntax of the message.
 
Please look for wlsxNAccessPointIsUp and wlsxNAccessPointIsDown traps for AP Up/Down event.

Version history
Revision #:
1 of 1
Last update:
‎06-26-2014 01:22 PM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: