Wireless Access

 View Only

  • 1.  Cisco wireless bridge 1240 not connecting with Aruba after upgrading to 8.6.0.15 from 6.4.4.16

    Posted Feb 28, 2022 12:56 AM
    We have Cisco wireless bridge 1240 (client) which connects to Aruba AP on g radio. It was working fine with 6.4.4.16. However after we upgrade to 8.6.0.15 it's not working at all. We are seeing a deauth from AP (saying station roamed to another AP).But actually the client is stationery. Collected packet capture. After association response, immediate de-auth from AP with reason (previous auth is no longer valid).
    ​Client trail info output says as below:

    Reason                                                          Timestamp

    ------                                                          ---------

    Disassociated; Auth frame from STA that was already associated  Jan 31 17:35:52

    Disassociated; Auth frame from STA that was already associated  Jan 31 17:35:51

    Disassociated; Auth frame from STA that was already associated  Jan 31 17:35:50

    Disassociated; Auth frame from STA that was already associated  Jan 31 17:35:27

    STA has left and is disassociated                               Jan 31 17:35:26

    Disassociated; Auth frame from STA that was already associated  Jan 31 17:35:25

    Disassociated; Auth frame from STA that was already associated  Jan 31 17:35:25

    Disassociated; Auth frame from STA that was already associated  Jan 31 17:34:48

    Disassociated; Auth frame from STA that was already associated  Jan 31 17:34:47

    Disassociated; Auth frame from STA that was already associated  Jan 31 17:34:47

    Num Deauths:10

     

    Alerts

    ------

    Reason                        Timestamp

    ------                        ---------

    STA has roamed to another AP  Jan 31 17:35:54

    STA has roamed to another AP  Jan 31 17:35:53

    STA has roamed to another AP  Jan 31 17:35:53

    STA has roamed to another AP  Jan 31 17:35:52

    STA has roamed to another AP  Jan 31 17:35:52

    STA has roamed to another AP  Jan 31 17:35:52

    STA has roamed to another AP  Jan 31 17:35:52


    ​

    ------------------------------
    Vinod
    ------------------------------


  • 2.  RE: Cisco wireless bridge 1240 not connecting with Aruba after upgrading to 8.6.0.15 from 6.4.4.16

    Posted Feb 28, 2022 11:18 PM
    Experts,

    In what scenario I see this reason in client trail-info "Disassociated; Auth frame from STA that was already associated "

    Also this reason on air packet-capture de-auth frame "previous auth is no longer valid"

    I already opened a tac case , but no update yet. 

    ------------------------------
    Kumara Vinod Kakarlapudi
    ------------------------------

    Original Message


  • 3.  RE: Cisco wireless bridge 1240 not connecting with Aruba after upgrading to 8.6.0.15 from 6.4.4.16

    Posted Mar 01, 2022 05:25 AM
    What is the encryption type you configured on the SSID and Wireless bridge?
    What type of APs do you have?
    You can try to change the 802.11r/k/v settings to see if that changes the behavior. TAC would be my go-to for such an issue as well, and please inform them about the priority of your issue. If you have severe impacted connectivity, or if it is just nice if it will be solved but low prio, that should be reflected in the case priority.

    ------------------------------
    Herman Robers
    ------------------------
    If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
    ------------------------------

    Original Message


  • 4.  RE: Cisco wireless bridge 1240 not connecting with Aruba after upgrading to 8.6.0.15 from 6.4.4.16

    Posted Mar 01, 2022 05:35 AM
    Hi Herman,

    Thanks for the reply. We are using EAP-TLS (Wpa2-aes). AP-277. We have already requested for high priority. 
    I guess we are using default settings for dot11r/k/v profiles. I will check this again. 

    Just curious, in general what triggers those type of de-auth frames.

    ------------------------------
    Kumara Vinod Kakarlapudi
    ------------------------------

    Original Message


Related Content