Wireless Access

Reply
Contributor I

AP's reporting down when they are not really down.

We recently upgraded our controllers to 6.1.3.5 and have been fairly happy with it. However, since upgrading I have random AP's that will be reported as Down when they are really not down at all. I run scripts against our controllers to poll for information, such as AP up/down status.

 

These AP's primarily live on one of our Local controllers. (Current setup is: A Master and 2 Locals).  They are set to failover to the Master if there is any issue with the local.

 

What I "think" is happening is the AP is associating with the Master for some short time, then going back to the Local. The problem is the Master is seeing the AP as down, once it goes back to the local.

 

I run several snmp scripts against the controllers. I first grab a list of all of the AP's:

 

snmpwalk -v2c Aruba-master -c some_snmp_password .1.3.6.1.4.1.14823.2.2.1.5.2.1.4.1.3

 

This returns a complete list of AP's:

 

SNMPv2-SMI::enterprises.14823.2.2.1.5.2.1.4.1.3.216.199.200.204.250.102 = STRING: "AP-one"
SNMPv2-SMI::enterprises.14823.2.2.1.5.2.1.4.1.3.216.199.200.204.250.120 = STRING: "AP-two"
                                                                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                                                                                        AP string

 

I then poll each one using the AP string from above:

 

snmpwalk -v2c Aruba-master -c some_snmp_password .1.3.6.1.4.1.14823.2.2.1.5.2.1.4.1.19."AP string"

i.e.

snmpwalk -v2c Aruba-master -c some_snmp_password .1.3.6.1.4.1.14823.2.2.1.5.2.1.4.1.19.216.199.200.204.250.120

 

This returns either a 1 for up, or a 2 for down:

 

SNMPv2-SMI::enterprises.14823.2.2.1.5.2.1.4.1.19.216.199.200.204.250.120 = INTEGER: 2

 

In this case, 2 means it's down.

 

If I run the same snmp script against the Local, it will come back with a INTEGER: 1  or UP.

 

 

Logging on to both controllers gives me similar results. Doing a:  show AP database | include Down    will show the AP as Down on the Master and "Up" on the Local. The AP is also working and passing data.

 

The Master controller will eventually update it' status to  show the correct AP state, but only after I've gotten a bunch of email messages that an AP is down. I've tried several things to get the Master to update itself, including doing a Write Mem command. Which does not update the AP's  to their correct state. If I show all of the Controller's status - show switches, they claim to be ins sync - Update Successful. (A reboot does get things back on track but for obvious reasons, I'd like to not do this.)

 

 

This brings up several questions....

 

1. What is the best way to poll four up/down status? (Since the above method no longer seems to be reliable).

 

2. Why are the controllers reporting different UP/Down status?

 

3. How do I modify the master's behavior to work as it should (i.e. show the correct up/down state of the AP)?

 

 Anyone have any insight into this?

Re: AP's reporting down when they are not really down.

This isn't particularly helpful I know, but I think you'd best log that with TAC. If there's delays between the master and local in terms of AP up/down status, there might be a timer in 6.1.3,.5 for data sync that wasn't there before that I'm not aware of (a guess).

 

Debugging this will be a nightmare I'd suspect, so TAC will likely be your way forward.

 

Kudos appreciated, but I'm not hunting! (ACMX 104)
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: