Wireless Access

last person joined: 12 hours ago 

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

mobility service will be aborted

This thread has been viewed 0 times
  • 1.  mobility service will be aborted

    Posted Aug 24, 2012 02:02 PM

    We are tring to diagnose a client connectivity issue that is intermittant in nature. 

     

    It appears that clients can connect both open and 802.1x but they don't get a DHCP address. 

    We have verified that the DHCP messages are getting to the DHCP server and there are no ACL's that block this either on the user role or on the network behind. Also since this is intermittant it appears that normally this is working properly.

     

    In debugging this we see this message in the logs

     

    Aug 24 09:31:23  mobileip[1901]: <500022> <WARN> |mobileip|  Station 3c:d0:xx:ss:dd:ff, x.x.x.x: IP address change y.y.y.y detected, mobility service will be aborted

     

    What exactly does this Warning mean?

     

    We also occasionally see this message

     

    Aug 22 15:11:14  mobileip[1850]: <500347> <WARN> |mobileip|  Station 3c:d0:xx:ss:dd:ff0.0.0.0: Too many BOOTP messages (25) from/to client max allowed 25; Dropping


  • 2.  RE: mobility service will be aborted

    EMPLOYEE
    Posted Aug 24, 2012 07:51 PM

    I do not know about the second message, but in the release notes for 6.1.3.4:

     

    69155 An issue where an Apple iOS/MacOS device sometimes took longer than a minute to get an IP address from the DHCP server after resuming from sleep has been fixed. This was observed when IP mobility was enabled on controllers running ArubaOS 6.1.3.0.



  • 3.  RE: mobility service will be aborted

    Posted Aug 25, 2012 12:59 PM

    Thanks Collin. Missed that. 

     

     



  • 4.  RE: mobility service will be aborted

    EMPLOYEE
    Posted Aug 25, 2012 01:02 PM

    You didn't say what version of ArubaOS you are on, but 6.1.3.2 contains over 500 bug fixes and should be the starting point of any safe harbor deployment.