Wireless Access

 View Only
last person joined: 11 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

MSM720 unable to detect after reset via a hole on the bottom of the AP MSM430

This thread has been viewed 0 times

  • 1.  MSM720 unable to detect after reset via a hole on the bottom of the AP MSM430

    Posted Nov 13, 2019 09:53 PM

    Hi,

    MSM720 controller unable to detect AP MSM430 after reset via a hole on the bottom of the AP. I already follow the guideline from this url https://support.hpe.com/hpsc/doc/public/display?docId=c04915287 but still not detect.

    I also cannot access web browser https://192.168.1.1/.

    Appreciate someone to help me to solve this problem.

     

     


    #msm430


  • 2.  RE: MSM720 unable to detect after reset via a hole on the bottom of the AP MSM430

    EMPLOYEE
    Posted Nov 14, 2019 07:05 AM

    Hello, 

    Did you perform a reset or a reset to factory defaults?

    If not done please try to perform a reset to factory defaults - press the reset button and keep it pressed: All LEDs should go on and then start flashing slowly all together. After the 3rd slow flash you should release the reset button. If you release it later, when the LEDs start flashing faster, you have put the AP in TFTP mode.

    It would be important to know how exactly are blinking the LEDs of the AP after the reset when it is not able to discover the controller? The link you provided has a description of the different LED pattern for your reference (page 5 and 6). This can be helpful when you are troubleshooting.

    You are writing that you tried to access the AP via the default IP 192.168.1.1. After a factory reset the AP will respond to this IP only if it cannot obtain an IP via DHCP. Are you sure that no DHCP server provided an IP to this AP?

    If you are sure that no DHCP server provided IP and you cannot access the AP via 192.168.1.1 did you test if you can ping this IP address? To exclude network problems maybe you can connect directly a laptop to the Ethernet port of the AP.

    If you can ping the AP but you cannot access the GUI and it is not connecting to the controller, the AP probably has a corrupted startup image. How to fix this is explained in the following document

    https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c02684335

    https://support.hpe.com/hpsc/doc/public/display?docId=mmr_sf-EN_US000005379

    For this procedure you need a cim.startup file. This is not the normal AP firmware file that can be downloaded from the public download page. It is not publicly available and you need to contact your local support and request this file.