Wireless Access

last person joined: 17 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

No response from AP for REG_DOM_INFO request for 3614 sec; deleting AP.

This thread has been viewed 8 times

  • 1.  No response from AP for REG_DOM_INFO request for 3614 sec; deleting AP.

    Posted May 17, 2016 03:08 AM

    Hi Everyone,

    I have a 7210 controller holding 62 number ap225 in my network . I can see all 62 aps details in show ap database and they are up  but i cannot see all the aps details in show ap active i,e hardly 10 are available.

    I cannot see any profile-errors but in show log system 50 i can see below mentioned logs for many APs.

    AP INDC-5F46-5147 No response from AP for REG_DOM_INFO request for 3614 sec; deleting AP.

     OS details: Controller 7210 - 6.4.3.5

    can somebidy Please suggest how to reslove this.



  • 2.  RE: No response from AP for REG_DOM_INFO request for 3614 sec; deleting AP.

    EMPLOYEE
    Posted May 17, 2016 03:11 AM

    Are these access points connected over a MPLS link or a private WAN?

     



  • 3.  RE: No response from AP for REG_DOM_INFO request for 3614 sec; deleting AP.

    Posted May 17, 2016 03:20 AM

    Hi Joseph,

     

    Its over Private WAN.



  • 4.  RE: No response from AP for REG_DOM_INFO request for 3614 sec; deleting AP.

    EMPLOYEE
    Posted May 17, 2016 03:26 AM

    I am assuming that this worked at some point and then stopped working.

     

    When did it stop working?

     



  • 5.  RE: No response from AP for REG_DOM_INFO request for 3614 sec; deleting AP.

    Posted May 17, 2016 03:36 AM

    Yes, it was working since past 2 weeks.

    just 30 min back i found this issue not sure why



  • 6.  RE: No response from AP for REG_DOM_INFO request for 3614 sec; deleting AP.

    EMPLOYEE
    Posted May 17, 2016 03:40 AM

    Sending the Reg_Domain_Info is probably the first fragmented packet when the AP boots up.  See if anything like MTU in your network has changed in the past few weeks.  Without knowing that, it would be hard to suggest a workaround.