Wireless Access

last person joined: 2 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

Unable to add new Aruba 135 AP to the existing RAP3 network

This thread has been viewed 0 times

  • 1.  Unable to add new Aruba 135 AP to the existing RAP3 network

    Posted Dec 31, 2013 02:29 AM

    Recently, we would like to added two Aruba 135 APs into our existing production network, which is shared with Aruba Instant AP RAP3 currently. The AP 135 is running fine when I configured it with closed network. However, it will keep rebooting when it connecting to the existing network. Please kindly see the console capture as attached.

     

    Do you guys have any idea?


    #AP135


  • 2.  RE: Unable to add new Aruba 135 AP to the existing RAP3 network

    EMPLOYEE
    Posted Dec 31, 2013 02:34 AM

    Are they both on the same version.  If they are different codes, then when you add the IAP135, it needs to get it's image from either Airwave or the cloud server.  Do the APs have access to the internet?



  • 3.  RE: Unable to add new Aruba 135 AP to the existing RAP3 network

    Posted Dec 31, 2013 02:39 AM

    Hi Michael,

     

    Yes, both are running same firmware version and seating in a closed network with Airware but no internet access.

    but when I add AP 135 in to the RAP-3 connecting network, the AP 135 will not populate SSID and keep rebooting. Have you encounter this case?