Controllerless Networks

last person joined: yesterday 

Instant Mode - the controllerless Wi-Fi solution that's easy to set up, is loaded with security and smarts, and won't break your budget
Expand all | Collapse all

Clients unable to associate after upgrade to 6.5.2.0

This thread has been viewed 3 times
  • 1.  Clients unable to associate after upgrade to 6.5.2.0

    Posted Jul 12, 2017 04:56 AM
      |   view attached

    After upgrading a site with a single IAP-315 to 6.5.2.0 clients are unable to associate with the SSIDs. There are two SSIDs:

     

    Corporate - Corporate network with 802.1x auth

    AL Surf - PSK Guest network, GRE tunnel to Aruba controller

     

    Straight after the upgrade, the Corporate network stopped working, but AL Surf still worked. The day after (yesterday), none of the networks work.

     

    Debugging the AP shows that the AP seems to be unable to respond to the AUTH requests. Any ideá why? Attaching a full show tech.

     

    Kista# show ap debug mgmt-frames

    Traced 802.11 Management Frames
    -------------------------------
    Timestamp stype SA DA BSS signal Misc
    --------- ----- -- -- --- ------ ----
    Jul 12 10:33:01 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)
    Jul 12 10:33:01 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)
    Jul 12 10:33:00 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)
    Jul 12 10:33:00 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)
    Jul 12 10:32:59 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)
    Jul 12 10:32:59 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)
    Jul 12 10:32:58 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)
    Jul 12 10:32:58 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)
    Jul 12 10:29:49 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)
    Jul 12 10:29:48 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)
    Jul 12 10:29:48 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)
    Jul 12 10:29:47 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)
    Jul 12 10:29:44 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)
    Jul 12 10:29:44 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)
    Jul 12 10:29:43 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)
    Jul 12 10:29:43 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)
    Jul 12 10:29:42 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)
    Jul 12 10:29:42 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)
    Jul 12 10:29:40 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)
    Jul 12 10:29:40 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)
    Jul 12 10:28:35 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)
    Jul 12 10:28:35 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)
    Jul 12 10:28:34 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)
    Jul 12 10:28:34 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)
    Jul 12 10:28:33 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)

    Traced 802.11 Management Frames
    -------------------------------
    Timestamp stype SA DA BSS signal Misc
    --------- ----- -- -- --- ------ ----
    Jul 12 10:28:33 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)
    Jul 12 10:28:33 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)
    Jul 12 10:28:32 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)
    Jul 12 10:26:35 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)
    Jul 12 10:26:20 auth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 Success (seq num 2056)
    Jul 12 10:26:20 auth f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 34:fc:b9:e6:a2:32 0 -
    Jul 12 10:26:20 auth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 Success (seq num 0)
    Jul 12 10:26:20 auth f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 34:fc:b9:e6:a2:32 0 -
    Jul 12 10:26:19 auth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 Success (seq num 2056)
    Jul 12 10:26:19 auth f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 34:fc:b9:e6:a2:32 0 -
    Jul 12 10:26:19 auth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 Success (seq num 4095)
    Jul 12 10:26:19 auth f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 34:fc:b9:e6:a2:32 0 -
    Jul 12 10:26:18 auth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 Success (seq num 2056)
    Jul 12 10:26:18 auth f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 34:fc:b9:e6:a2:32 0 -
    Jul 12 10:26:18 auth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 Success (seq num 0)
    Jul 12 10:26:18 auth f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 34:fc:b9:e6:a2:32 0 -
    Jul 12 10:26:17 auth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 Success (seq num 0)
    Jul 12 10:26:17 auth f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 34:fc:b9:e6:a2:32 0 -
    Jul 12 10:26:17 auth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 Success (seq num 0)
    Jul 12 10:26:17 auth f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 34:fc:b9:e6:a2:32 0 -
    Jul 12 10:25:27 deauth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 - (internal only)
    Jul 12 10:25:12 auth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 Success (seq num 0)
    Jul 12 10:25:12 auth f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 34:fc:b9:e6:a2:32 0 -
    Jul 12 10:25:12 auth 34:fc:b9:e6:a2:32 f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 15 Success (seq num 0)
    Jul 12 10:25:12 auth f0:d5:bf:c6:dd:79 34:fc:b9:e6:a2:32 34:fc:b9:e6:a2:32 0 -


    Kista# show log driver

    ] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [164790.676699] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [164791.193632] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [164791.692507] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [164792.222622] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [164792.724778] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [164793.240492] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [164793.740523] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [164860.281885] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [164860.779167] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [164861.295881] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [164861.794944] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [164862.327059] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [164862.840273] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [164863.358924] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [164863.857237] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [164867.590258] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [164868.077074] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [164868.593881] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [164869.092694] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [164916.997880] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:88:6b:6e:25:f1:2c
    [164917.333119] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:88:6b:6e:25:f1:2c
    [164917.668796] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:88:6b:6e:25:f1:2c
    [164918.005034] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:88:6b:6e:25:f1:2c
    [164918.340211] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:88:6b:6e:25:f1:2c
    [164918.850520] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:88:6b:6e:25:f1:2c
    [164919.186727] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:88:6b:6e:25:f1:2c
    [164919.521342] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:88:6b:6e:25:f1:2c
    [164919.855987] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:88:6b:6e:25:f1:2c
    [164920.191945] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:88:6b:6e:25:f1:2c
    [164920.705815] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:88:6b:6e:25:f1:2c
    [164921.040867] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:88:6b:6e:25:f1:2c
    [164921.375294] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:88:6b:6e:25:f1:2c
    [164921.709720] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:88:6b:6e:25:f1:2c
    [164922.044334] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:88:6b:6e:25:f1:2c
    [164931.754175] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [164932.243553] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [164932.760829] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [164933.259299] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [164933.776199] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [164934.275012] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [164934.793007] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [164935.305940] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [165000.077105] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [165000.579886] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [165001.096724] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [165001.609689] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [165002.128058] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [165002.627590] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [165003.144772] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [165003.643210] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [165068.405190] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [165068.901129] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [165069.418280] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [165069.916906] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [165070.433588] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [165070.947865] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [165071.479074] aruba_send_auth_resp: send auth-resp:0 failed ret:-1 STA:f0:d5:bf:c6:dd:79
    [165090.032619] [wifi0][22 37 255]:FWLOG: [34818196] WAL_DBGID_DEV_TX_TIMEOUT ( 0x4, 0x1 )
    [165090.032619] [wifi0][22 37 255]:FWLOG: [34818196] WAL_DBGID_DEV_TX_TIMEOUT ( 0x6a, 0x7, 0x1 )
    [165090.032651] [wifi0][22 37 255]:FWLOG: [34818196] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1e, 0xf, 0x2 )
    [165090.032682] [wifi0][22 37 255]:FWLOG: [34818196] WAL_DBGID_DEV_TX_TIMEOUT ( 0xc6, 0xc7, 0x3 )
    [165103.034869] [wifi0][22 37 255]:FWLOG: [34830945] WAL_DBGID_DEV_TX_TIMEOUT ( 0x4, 0x1 )
    [165103.034900] [wifi0][22 37 255]:FWLOG: [34830945] WAL_DBGID_DEV_TX_TIMEOUT ( 0x28, 0x45, 0x1 )
    [165103.034931] [wifi0][22 37 255]:FWLOG: [34830945] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1a, 0xb, 0x2 )
    [165103.034962] [wifi0][22 37 255]:FWLOG: [34830945] WAL_DBGID_DEV_TX_TIMEOUT ( 0x4, 0x5, 0x3 )
    [165151.044803] [wifi0][22 37 255]:FWLOG: [34880510] WAL_DBGID_DEV_TX_TIMEOUT ( 0x4, 0x1 )
    [165151.044834] [wifi0][22 37 255]:FWLOG: [34880510] WAL_DBGID_DEV_TX_TIMEOUT ( 0x79, 0x16, 0x1 )
    [165151.044866] [wifi0][22 37 255]:FWLOG: [34880510] WAL_DBGID_DEV_TX_TIMEOUT ( 0x19, 0xa, 0x2 )
    [165151.044866] [wifi0][22 37 255]:FWLOG: [34880510] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1ef, 0x1f0, 0x3 )
    [165193.052707] [wifi0][22 37 255]:FWLOG: [34923520] WAL_DBGID_DEV_TX_TIMEOUT ( 0x4, 0x1 )
    [165193.052707] [wifi0][22 37 255]:FWLOG: [34923520] WAL_DBGID_DEV_TX_TIMEOUT ( 0x34, 0x51, 0x1 )
    [165193.052738] [wifi0][22 37 255]:FWLOG: [34923520] WAL_DBGID_DEV_TX_TIMEOUT ( 0xe, 0x1f, 0x2 )
    [165193.052769] [wifi0][22 37 255]:FWLOG: [34923520] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1aa, 0x1ab, 0x3 )
    [165225.058861] [wifi0][22 37 255]:FWLOG: [34956495] WAL_DBGID_DEV_TX_TIMEOUT ( 0x4, 0x1 )
    [165225.058892] [wifi0][22 37 255]:FWLOG: [34956495] WAL_DBGID_DEV_TX_TIMEOUT ( 0x24, 0x41, 0x1 )
    [165225.058892] [wifi0][22 37 255]:FWLOG: [34956495] WAL_DBGID_DEV_TX_TIMEOUT ( 0x12, 0x3, 0x2 )
    [165225.058924] [wifi0][22 37 255]:FWLOG: [34956495] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1b8, 0x1b9, 0x3 )
    [165274.068202] [wifi0][22 37 255]:FWLOG: [35006469] WAL_DBGID_DEV_TX_TIMEOUT ( 0x4, 0x1 )
    [165274.068233] [wifi0][22 37 255]:FWLOG: [35006469] WAL_DBGID_DEV_TX_TIMEOUT ( 0xd, 0x2a, 0x1 )
    [165274.068264] [wifi0][22 37 255]:FWLOG: [35006469] WAL_DBGID_DEV_TX_TIMEOUT ( 0x12, 0x3, 0x2 )
    [165274.068296] [wifi0][22 37 255]:FWLOG: [35006469] WAL_DBGID_DEV_TX_TIMEOUT ( 0x121, 0x122, 0x3 )
    [165322.077637] [wifi0][22 37 255]:FWLOG: [35055167] WAL_DBGID_DEV_TX_TIMEOUT ( 0x4, 0x1 )
    [165322.077668] [wifi0][22 37 255]:FWLOG: [35055167] WAL_DBGID_DEV_TX_TIMEOUT ( 0x3c, 0x59, 0x1 )
    [165322.077699] [wifi0][22 37 255]:FWLOG: [35055167] WAL_DBGID_DEV_TX_TIMEOUT ( 0x3, 0x14, 0x2 )
    [165322.077699] [wifi0][22 37 255]:FWLOG: [35055167] WAL_DBGID_DEV_TX_TIMEOUT ( 0x160, 0x161, 0x3 )
    [165344.081823] [wifi0][22 37 255]:FWLOG: [35078153] WAL_DBGID_DEV_TX_TIMEOUT ( 0x4, 0x1 )
    [165344.081823] [wifi0][22 37 255]:FWLOG: [35078153] WAL_DBGID_DEV_TX_TIMEOUT ( 0x52, 0x6f, 0x1 )
    [165344.081854] [wifi0][22 37 255]:FWLOG: [35078153] WAL_DBGID_DEV_TX_TIMEOUT ( 0xb, 0x1c, 0x2 )
    [165344.081885] [wifi0][22 37 255]:FWLOG: [35078153] WAL_DBGID_DEV_TX_TIMEOUT ( 0x176, 0x177, 0x3 )
    [165365.085165] [wifi0][22 37 255]:FWLOG: [35099865] WAL_DBGID_DEV_TX_TIMEOUT ( 0x4, 0x1 )
    [165365.085197] [wifi0][22 37 255]:FWLOG: [35099865] WAL_DBGID_DEV_TX_TIMEOUT ( 0x69, 0x6, 0x1 )
    [165365.085228] [wifi0][22 37 255]:FWLOG: [35099865] WAL_DBGID_DEV_TX_TIMEOUT ( 0x0, 0x11, 0x2 )
    [165365.085228] [wifi0][22 37 255]:FWLOG: [35099865] WAL_DBGID_DEV_TX_TIMEOUT ( 0x8d, 0x8e, 0x3 )
    [165374.087446] [wifi0][22 37 255]:FWLOG: [35109031] WAL_DBGID_DEV_TX_TIMEOUT ( 0x4, 0x1 )
    [165374.087477] [wifi0][22 37 255]:FWLOG: [35109031] WAL_DBGID_DEV_TX_TIMEOUT ( 0x3b, 0x58, 0x1 )
    [165374.087508] [wifi0][22 37 255]:FWLOG: [35109031] WAL_DBGID_DEV_TX_TIMEOUT ( 0x10, 0x1, 0x2 )
    [165374.087540] [wifi0][22 37 255]:FWLOG: [35109031] WAL_DBGID_DEV_TX_TIMEOUT ( 0x5f, 0x60, 0x3 )
    [165407.103941] [wifi0][22 37 255]:FWLOG: [35142672] WAL_DBGID_DEV_TX_TIMEOUT ( 0x4, 0x1 )
    [165407.103972] [wifi0][22 37 255]:FWLOG: [35142672] WAL_DBGID_DEV_TX_TIMEOUT ( 0x3a, 0x57, 0x1 )
    [165407.104003] [wifi0][22 37 255]:FWLOG: [35142672] WAL_DBGID_DEV_TX_TIMEOUT ( 0x13, 0x4, 0x2 )
    [165407.104035] [wifi0][22 37 255]:FWLOG: [35142672] WAL_DBGID_DEV_TX_TIMEOUT ( 0x15e, 0x15f, 0x3 )
    [165495.135650] [wifi0][22 37 255]:FWLOG: [35233029] WAL_DBGID_DEV_TX_TIMEOUT ( 0x4, 0x1 )
    [165495.135650] [wifi0][22 37 255]:FWLOG: [35233029] WAL_DBGID_DEV_TX_TIMEOUT ( 0x55, 0x72, 0x1 )
    [165495.135681] [wifi0][22 37 255]:FWLOG: [35233029] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1e, 0xf, 0x2 )
    [165495.135712] [wifi0][22 37 255]:FWLOG: [35233029] WAL_DBGID_DEV_TX_TIMEOUT ( 0x115, 0x116, 0x3 )
    [165618.159923] [wifi0][22 37 255]:FWLOG: [35358738] WAL_DBGID_DEV_TX_TIMEOUT ( 0x4, 0x1 )
    [165618.159923] [wifi0][22 37 255]:FWLOG: [35358738] WAL_DBGID_DEV_TX_TIMEOUT ( 0x13, 0x30, 0x1 )
    [165618.159955] [wifi0][22 37 255]:FWLOG: [35358738] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1a, 0xb, 0x2 )
    [165618.159986] [wifi0][22 37 255]:FWLOG: [35358738] WAL_DBGID_DEV_TX_TIMEOUT ( 0x16f, 0x170, 0x3 )
    [165663.169483] [wifi0][22 37 255]:FWLOG: [35404382] WAL_DBGID_DEV_TX_TIMEOUT ( 0x4, 0x1 )
    [165663.169514] [wifi0][22 37 255]:FWLOG: [35404382] WAL_DBGID_DEV_TX_TIMEOUT ( 0x4b, 0x68, 0x1 )
    [165663.169545] [wifi0][22 37 255]:FWLOG: [35404382] WAL_DBGID_DEV_TX_TIMEOUT ( 0x0, 0x11, 0x2 )
    [165663.169577] [wifi0][22 37 255]:FWLOG: [35404382] WAL_DBGID_DEV_TX_TIMEOUT ( 0x127, 0x128, 0x3 )
    [165739.186665] [wifi0][22 37 255]:FWLOG: [35482893] WAL_DBGID_DEV_TX_TIMEOUT ( 0x4, 0x1 )
    [165739.186696] [wifi0][22 37 255]:FWLOG: [35482893] WAL_DBGID_DEV_TX_TIMEOUT ( 0x40, 0x5d, 0x1 )
    [165739.186727] [wifi0][22 37 255]:FWLOG: [35482893] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1d, 0xe, 0x2 )
    [165739.186759] [wifi0][22 37 255]:FWLOG: [35482893] WAL_DBGID_DEV_TX_TIMEOUT ( 0x50, 0x51, 0x3 )
    [165820.201598] [wifi0][22 37 255]:FWLOG: [35565614] WAL_DBGID_DEV_TX_TIMEOUT ( 0x4, 0x1 )
    [165820.201629] [wifi0][22 37 255]:FWLOG: [35565614] WAL_DBGID_DEV_TX_TIMEOUT ( 0x3c, 0x59, 0x1 )
    [165820.201660] [wifi0][22 37 255]:FWLOG: [35565614] WAL_DBGID_DEV_TX_TIMEOUT ( 0x19, 0xa, 0x2 )

    Attachment(s)

    txt
    Kista_showtech_20170712b.txt   330 KB 1 version


  • 2.  RE: Clients unable to associate after upgrade to 6.5.2.0

    EMPLOYEE
    Posted Jul 12, 2017 07:30 AM

    What version of instant code did you upgrade from?



  • 3.  RE: Clients unable to associate after upgrade to 6.5.2.0

    Posted Jul 12, 2017 07:38 AM

    Sorry, don't remember. Is there a way to tell after? Most likely it was the shipping version of IAP-315.

     

    Just did a remote session with the Aruba TAC who couldn't find the root cause, but a reboot solved the issue (as I suspected, but didn't want to do before finding the real root cause).

     

    Summary of the session:

     

    * When starting the session no client could connect to any of the SSIDs
    * We added Test SSID with PSK which worked.
    * Right after we had added “Test”, also the old AL-Surf PSK SSID started to work.
    * Corporate “Atrium Ljungberg” network still did work. No trace of auth attempts in “show ap debug auth”.
    * After reboot of the IAP all SSIDs worked again.
     
     


  • 4.  RE: Clients unable to associate after upgrade to 6.5.2.0

    EMPLOYEE
    Posted Jul 12, 2017 07:41 AM

    You were working with TAC, which is the right thing.  Please let us know if anything else happens.



  • 5.  RE: Clients unable to associate after upgrade to 6.5.2.0

    Posted Jul 20, 2017 04:08 AM

    This week the same problem hit my customer at another site, also upgraded to 6.5.2.0 with IAP-315s. Some of the APs in a VC consisting of 10 IAP-315 are affected, not all.

     

    The problem is now escalated to the engineering team at Aruba who as ackknowleded it's abnormal and working on finding the root cause.

     

    On the APs affected by this problem you can also see "Radio reset" counter keep increasing and the driver log keeps complaining about TX errors:

     

    SicklaHK-forv# show clock
    Current Time     :2017-07-19 00:17:28
    SicklaHK-forv# show ap debug system-status | inc wifi0
    wifi0      4143780  516430     366805    13276244  0          59213     14752
    wifi0         803161067   4143780     258215   366805   0        258215    0              0             1155427146  13276244    0        59213    0        0         0           0              14752
      68:  209186258          0       GIC  wifi0

    SicklaHK-forv# show clock
    Current Time     :2017-07-19 00:17:57
    SicklaHK-forv# show ap debug system-status | inc wifi0
    wifi0      4143793  516430     366815    13276798  0          59213     14754
    wifi0         803163073   4143793     258215   366815   0        258215    0              0             1155427146  13276798    0        59213    0        0         0           0              14754
      68:  209187359          0       GIC  wifi0

    SicklaHK-forv# show clock
    Current Time     :2017-07-19 00:18:19

    SicklaHK-forv# show ap debug system-status | inc wifi0
    wifi0      4143796  516430     366818    13277129  0          59213     14756
    wifi0         803163669   4143796     258215   366818   0        258215    0              0             1155427146  13277129    0        59213    0        0         0           0              14756
      68:  209188046          0       GIC  wifi0

    SicklaHK-forv# show log driver
    <cut>
    [479727.662245] [wifi0][22 37 255]:FWLOG: [88534551] WAL_DBGID_DEV_TX_TIMEOUT ( 0x0, 0x1 )
    [479727.662276] [wifi0][22 37 255]:FWLOG: [88534551] WAL_DBGID_DEV_TX_TIMEOUT ( 0x74, 0x11, 0x1 )
    [479727.662276] [wifi0][22 37 255]:FWLOG: [88534551] WAL_DBGID_DEV_TX_TIMEOUT ( 0xb, 0x1c, 0x2 )
    [479727.662307] [wifi0][22 37 255]:FWLOG: [88534551] WAL_DBGID_DEV_TX_TIMEOUT ( 0x6a, 0x6b, 0x3 )
     
    Anyone else seen this problem?


  • 6.  RE: Clients unable to associate after upgrade to 6.5.2.0

    Posted Sep 14, 2017 09:08 AM

    Have you found a solution to this with TAC? I've been working with them on what seems to be the same issue on ArubaOS 6.5.3.0.

    Many of our AP-315s stop authenticating users every day and have to be rebooted. The log is spammed with  "aruba send auth resp: send auth-resp:0 failed ret:-1" and the 5 GHz radios have unusually high number of radio resets.

     

    So far they only aknowledged that I am not the only one with this issue, but it looks like I will have to downgrade AOS to 6.5.1.x, where the issue did not ocur.



  • 7.  RE: Clients unable to associate after upgrade to 6.5.2.0

    Posted Sep 18, 2017 02:46 PM

    No, TAC has not been able find a solution based on the show tech etc that I provided while the problem was occuring. After a few days my customer decided to downgrade to 4.3.1.3 which has been running stable since.

     

    TAC is now requesting me to upgrade to 6.5.2.0 again to see if I can reproduce the issue again to run additional tests. I'm awaiting approval from my customer to do this.

     

    PS: I'm not sure if the Radio Reset increases were really related. There seems to be another problem associated with the "scanning" feature. When I disable scanning on the ARM profile, the radio resets stops increasing.



  • 8.  RE: Clients unable to associate after upgrade to 6.5.2.0

    Posted Oct 17, 2017 06:53 AM

    FYI

    After trying to resolve this with TAC for over a month we downgraded AOS to 6.5.1.8 and the issue is gone.

    So if you wanted to use software branch that is recent, still being maintained and does not have the issue, 6.5.1.x is the way to go.



  • 9.  RE: Clients unable to associate after upgrade to 6.5.2.0

    Posted Dec 21, 2017 04:16 AM

    Another FYI - it should be fixed in 6.5.3.4. Bug ID 168530.