Wireless Access

Hi

We have VRRP switchover test on two 6000 controllers(primary/primary) with AP135 over 6.1.3.6.

Client has communication loss for 30 seconds in case for 802.11a & g dual which is acceptable for us.  

However, it takes 90 to 120 seconds to switchover in case 802.11 a only which is NOT acceptable for us.

During that time, VRRP is quickly switchover, but wireless is disconnected and GRE is re-negotiate and wireless reconnect.

The symptom is same in 5.0 too.

Do you have any idea why 11a is longer time to recover traffic and give me advice if there is any solution?

The customer want to use 11a only.

Regards

Simon

1. When this occurs, is the 90-120 seconds you indicate the time for the AP to create its tunnel or for the client to be back online?
2. Do you have CPSec enabled?
3. What type of security is on the network?
4. When you do your "a-only" test, are those AP-135s as well?

Hi Clembo

Thanks for your attention.

When this occurs, is the 90-120 seconds you indicate the time for the AP to create its tunnel or for the client to be back online?
  -> It is time for client to ba back online

Do you have CPSec enabled?

  -> no,  we don't.

What type of security is on the network?

  -> we use 802.1x with EAP-TLS. WPA2-PSK

When you do your "a-only" test, are those AP-135s as well?

  -> Yes, AP-135, also AP-105 are same symptom.

I attache tech for your reference.

Regards

Simon

tech-support

can't attach log.

• How many APs on the controller at the time?
• Do you have band-steering on?   If so, what happens if you turn it off when doing the "a-only" test?
• Does this happen for all client OS?
• Does it look like the client is attempting to connect during this 90-120 seconds or is just sititng idle disconnected?
• Have you tried to enable debugging for a specific client MAC during this to see if it is attempting any sort of association/authentication?

Hi Clembo

    How many APs on the controller at the time?
   -> Customer NW has about fifty AP. But it is occuring in just one in lab setup.
    Do you have band-steering on?  
   -> No
    Does this happen for all client OS?
   -> Not all. We  only use XP and didn't realize to use another OS. We will try tommorow.
    Does it look like the client is attempting to connect during this 90-120 seconds or is just sititng idle disconnected?
   -> It is idle because wireless is not up
    Have you tried to enable debugging for a specific client MAC during this to see if it is attempting any sort of association/authentication?
   -> No, we will try tommorow.

Regards
Simon

Hi Clembo

We trited xp, 7 and vista. All are same symptom, so OS may be not related.

Below is output of logging debug user-debug.

I am wondering if  "Fastroaming Disabled" message appreas on debugging level. We don't chage from default.

Regards

Simon

(OAW-4704) #show log user-debug all | begin " 13:"
Feb 13 13:11:12 :501065:  <DBUG> |stm|  send_ageout_sta_ack 8157: Send ageout sta 60:67:20:ab:34:94 ack back to AP (10.10.100.135)
Feb 13 13:11:12 :501105:  <NOTI> |stm|  Deauth from sta: 60:67:20:ab:34:94: AP 10.10.100.135-6c:f3:7f:b4:9f:10-AP135 Reason Unspecified Failure
Feb 13 13:11:12 :501065:  <DBUG> |stm|  Sending STA 60:67:20:ab:34:94 message to Auth and Mobility Unicast Encr WPA2 PSK AES Multicast Encr WPA2 PSK AES VLAN 0xa, wmm:1, rsn_cap:3c
Feb 13 13:11:12 :522036:  <INFO> |authmgr|  MAC=60:67:20:ab:34:94 Station DN: BSSID=6c:f3:7f:b4:9f:10 ESSID=TTEESSTT VLAN=10 AP-name=AP135
Feb 13 13:11:12 :500511:  <DBUG> |mobileip|  Station 60:67:20:ab:34:94, 0.0.0.0: Received disassociation on ESSID: TTEESSTT Mobility service ON, HA Discovery on Association Off, Fastroaming Disabled, AP: Name AP135 Group TEST BSSID 6c:f3:7f:b4:9f:10, phy a, VLAN 10
Feb 13 13:11:12 :500010:  <NOTI> |mobileip|  Station 60:67:20:ab:34:94, 255.255.255.255: Mobility trail, on switch 10.10.100.1, VLAN 10, AP AP135, TTEESSTT/6c:f3:7f:b4:9f:10/a
Feb 13 13:11:12 :501000:  <DBUG> |stm|  Station 60:67:20:ab:34:94: Clearing state
Feb 13 13:11:32 :501095:  <NOTI> |stm|  Assoc request @ 13:11:32.512533: 60:67:20:ab:34:94 (SN 1680): AP 10.10.100.135-6c:f3:7f:b4:9f:10-AP135
Feb 13 13:11:32 :501100:  <NOTI> |stm|  Assoc success @ 13:11:32.515911: 60:67:20:ab:34:94: AP 10.10.100.135-6c:f3:7f:b4:9f:10-AP135
Feb 13 13:11:32 :501065:  <DBUG> |stm|  Sending STA 60:67:20:ab:34:94 message to Auth and Mobility Unicast Encr WPA2 PSK AES Multicast Encr WPA2 PSK AES VLAN 0x64, wmm:1, rsn_cap:3c
Feb 13 13:11:32 :522035:  <INFO> |authmgr|  MAC=60:67:20:ab:34:94 Station UP: BSSID=6c:f3:7f:b4:9f:10 ESSID=TTEESSTT VLAN=100 AP-name=AP135
Feb 13 13:11:32 :500511:  <DBUG> |mobileip|  Station 60:67:20:ab:34:94, 0.0.0.0: Received association on ESSID: TTEESSTT Mobility service ON, HA Discovery on Association Off, Fastroaming Disabled, AP: Name AP135 Group TEST BSSID 6c:f3:7f:b4:9f:10, phy a, VLAN 100
Feb 13 13:11:32 :500010:  <NOTI> |mobileip|  Station 60:67:20:ab:34:94, 0.0.0.0: Mobility trail, on switch 10.10.100.1, VLAN 100, AP AP135, TTEESSTT/6c:f3:7f:b4:9f:10/a
Feb 13 13:11:32 :501065:  <DBUG> |stm|  send_ageout_sta_ack 8157: Send ageout sta 60:67:20:ab:34:94 ack back to AP (10.10.100.135)
Feb 13 13:11:32 :501105:  <NOTI> |stm|  Deauth from sta: 60:67:20:ab:34:94: AP 10.10.100.135-6c:f3:7f:b4:9f:10-AP135 Reason Unspecified Failure
Feb 13 13:11:32 :501065:  <DBUG> |stm|  Sending STA 60:67:20:ab:34:94 message to Auth and Mobility Unicast Encr WPA2 PSK AES Multicast Encr WPA2 PSK AES VLAN 0xa, wmm:1, rsn_cap:3c
Feb 13 13:11:32 :500511:  <DBUG> |mobileip|  Station 60:67:20:ab:34:94, 0.0.0.0: Received disassociation on ESSID: TTEESSTT Mobility service ON, HA Discovery on Association Off, Fastroaming Disabled, AP: Name AP135 Group TEST BSSID 6c:f3:7f:b4:9f:10, phy a, VLAN 10
Feb 13 13:11:32 :522036:  <INFO> |authmgr|  MAC=60:67:20:ab:34:94 Station DN: BSSID=6c:f3:7f:b4:9f:10 ESSID=TTEESSTT VLAN=10 AP-name=AP135
Feb 13 13:11:32 :500010:  <NOTI> |mobileip|  Station 60:67:20:ab:34:94, 255.255.255.255: Mobility trail, on switch 10.10.100.1, VLAN 10, AP AP135, TTEESSTT/6c:f3:7f:b4:9f:10/a
Feb 13 13:11:32 :501000:  <DBUG> |stm|  Station 60:67:20:ab:34:94: Clearing state
Feb 13 13:11:38 :501095:  <NOTI> |stm|  Assoc request @ 13:11:38.792906: 60:67:20:ab:34:94 (SN 1684): AP 10.10.100.135-6c:f3:7f:b4:9f:10-AP135
Feb 13 13:11:38 :501100:  <NOTI> |stm|  Assoc success @ 13:11:38.796260: 60:67:20:ab:34:94: AP 10.10.100.135-6c:f3:7f:b4:9f:10-AP135
Feb 13 13:11:38 :501065:  <DBUG> |stm|  Sending STA 60:67:20:ab:34:94 message to Auth and Mobility Unicast Encr WPA2 PSK AES Multicast Encr WPA2 PSK AES VLAN 0x64, wmm:1, rsn_cap:3c
Feb 13 13:11:38 :522035:  <INFO> |authmgr|  MAC=60:67:20:ab:34:94 Station UP: BSSID=6c:f3:7f:b4:9f:10 ESSID=TTEESSTT VLAN=100 AP-name=AP135
Feb 13 13:11:38 :500511:  <DBUG> |mobileip|  Station 60:67:20:ab:34:94, 0.0.0.0: Received association on ESSID: TTEESSTT Mobility service ON, HA Discovery on Association Off, Fastroaming Disabled, AP: Name AP135 Group TEST BSSID 6c:f3:7f:b4:9f:10, phy a, VLAN 100
Feb 13 13:11:38 :500010:  <NOTI> |mobileip|  Station 60:67:20:ab:34:94, 0.0.0.0: Mobility trail, on switch 10.10.100.1, VLAN 100, AP AP135, TTEESSTT/6c:f3:7f:b4:9f:10/a
Feb 13 13:12:01 :501065:  <DBUG> |stm|  Sending STA 60:67:20:ab:34:94 message to Auth and Mobility Unicast Encr WPA2 PSK AES Multicast Encr WPA2 PSK AES VLAN 0xa, wmm:1, rsn_cap:3c
Feb 13 13:12:01 :522036:  <INFO> |authmgr|  MAC=60:67:20:ab:34:94 Station DN: BSSID=6c:f3:7f:b4:9f:10 ESSID=TTEESSTT VLAN=10 AP-name=AP135
Feb 13 13:12:01 :501000:  <DBUG> |stm|  Station 60:67:20:ab:34:94: Clearing state
Feb 13 13:12:01 :500511:  <DBUG> |mobileip|  Station 60:67:20:ab:34:94, 0.0.0.0: Received disassociation on ESSID: TTEESSTT Mobility service ON, HA Discovery on Association Off, Fastroaming Disabled, AP: Name AP135 Group TEST BSSID 6c:f3:7f:b4:9f:10, phy a, VLAN 10
Feb 13 13:12:01 :500010:  <NOTI> |mobileip|  Station 60:67:20:ab:34:94, 255.255.255.255: Mobility trail, on switch 10.10.100.1, VLAN 10, AP AP135, TTEESSTT/6c:f3:7f:b4:9f:10/a
Feb 13 13:12:25 :522050:  <INFO> |authmgr|  MAC=60:67:20:ab:34:94,IP=192.168.10.111 User data downloaded to datapath, new Role=authenticated/50, bw Contract=0/0,reason=Download driven by user role setting

Please open a support case so they can look over your configuration.  It should not take that long.

Hi Cjoseph

ok, I will open a case for TAC about this issue to investigate further.

Regards

Simon