Wireless Access

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

AP-655 cannot DHCP

This thread has been viewed 56 times
  • 1.  AP-655 cannot DHCP

    Posted May 05, 2023 08:02 AM

    I have an AP-655 which is refusing to DHCP. 

    Console messages on repeat: 

    Apr 11 00:12:57 udhcpc[11416]: Sending discover...

    Apr 11 00:12:59 udhcpc[11416]: send_discover: pkt num 2, secs 47616

    Port configuration on the switch seems fine as others APs are able to DHCP and are coming up on the controller. 

    There is no activity in the DHCP logs at all - not even failed attempts.

    The subnet range has plenty of IP leases available. 

    How can I get around this issue? 



  • 2.  RE: AP-655 cannot DHCP

    EMPLOYEE
    Posted May 05, 2023 08:33 AM

    Find out, if when it is booting it is running AOS 8.10.0.0.  There was a fix in 8.10.0.1 that had an updated ethernet phy receiver that could keep an access point from obtaining an ip address:  https://www.arubanetworks.com/techdocs/ArubaOS/Consolidated_8.x_RN/Content/8.10/01/resolved_8.10.0.1.htm

    If you break into apboot>  and type dhcp and it works, that could be your issue.

    To fix:  you will need to setup a tftp server with a later version of 8.10.x.x and do this:

    apboot> dhcp

    This should get you an ip address

    Put the version of instant on a tftp server on the network and set the serverip variable to the tftp server:

    apboot>  setenv serverip <ip address of tftp server>
    apboot> save
    apboot>  upgrade os <filename of instant version you are upgrading to>

    You should reboot it after and see if that fixes it...



    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
    ------------------------------



  • 3.  RE: AP-655 cannot DHCP

    Posted May 05, 2023 09:58 AM

    Hi, 

    Thanks for the quick reply. 

    I followed your instructions but the 'dhcp' command did not seem to work and kept receiving this error: 

    Retry count exceeded; starting again
    eth0 up: 1 Gb/s full duplex
    eth1: link down
    DHCP broadcast 1
    DHCP broadcast 2
    DHCP broadcast 3
    DHCP broadcast 4
    DHCP broadcast 5

    I have since manually given it an IP and the AP appears to have used it - looking in the 'print' of the AP. 

    Then running the 'upgrade os' <filename> command produces this on repeat: 
    Load address: 0x50500000
    Loading: *.T T T T T T T T T T
    Retry count exceeded; starting again
    eth0 up: 1 Gb/s full duplex
    eth1: link down
    Using eth0 device
    TFTP from server 131.111.12.6; our IP address is 172.30.185.26
    Filename 'ArubaInstant_Norma_8.10.0.1_84079'.
    Load address: 0x50500000

    Also tried + various other combinations. 
    apboot>upgrade os 131.111.12.6:an481/home/ArubaInstant_Norma_8.10.0.1_84079
    apbootupgrade boot ArubaInstant_Norma_8.10.0.1_84079






  • 4.  RE: AP-655 cannot DHCP

    EMPLOYEE
    Posted May 05, 2023 10:25 AM

    You need to do:

    apboot>  setenv serverip 131.111.12.6
    apboot> upgrade os ArubaInstant_Norma_8.10.0.1_84079

    TTTT means no connectivity to the tftp server.  I would try to ping it at apboot> to be sure.



    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
    ------------------------------



  • 5.  RE: AP-655 cannot DHCP

    Posted May 05, 2023 11:59 AM

    So I've managed to get the image to upgrade successfully. I triggered a 'boot' on the command line and the AP is just going through the boot process and gets stuck like it was previously. Am I missing a step? Should the AP not become an instant at this point and start broadcasting the 'set me up SSID'? Upon boot cycle it appear to still be on 8.10.0.0.

    apboot> upgrade os ArubaInstant_Norma_8.10.0.1_84079
    eth0 up: 1 Gb/s full duplex
    eth1: link down
    Using eth0 device
    TFTP from server 131.111.12.6; our IP address is 172.30.185.231; sending through gateway 172.30.185.254
    Filename 'ArubaInstant_Norma_8.10.0.1_84079'.
    Load address: 0x50500000
    Loading: *.#################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #######################################################################################################################################################################
    . 526.4 KiB/s done
    Bytes transferred = 39766552 (25eca18 hex)
    Image is signed; verifying checksum... passed
    SHA2 Signature available
    Signer Cert OK
    Policy Cert OK
    RSA signature verified using SHA2.
    Writing kernel into mmc...
    Journal Scan Completed
    Recovery required
    Journal Recovery Completed
    update journal finished
    File System is consistent
    update journal finished
    Verifying mmc...
    Writing rootfs into mmc...
    Journal Scan Completed
    Recovery required
    Journal Recovery Completed
    update journal finished
    File System is consistent
    update journal finished
    Verifying mmc...
    Upgrade successful.




  • 6.  RE: AP-655 cannot DHCP

    Posted May 09, 2023 08:34 AM

    Hi Colin, 

    Sorry to chase. 

    Do you have any recommendations or insight into the device behaviour as described above? 

    Also, the bug which is now resolved - could this be an intermittent issue? A colleague has pointed out me that prior to coming across this issue they booted up an AP-655 without issue and the AP was able to obtain an IP through DHCP. 

    Thanks, Adam




  • 7.  RE: AP-655 cannot DHCP

    EMPLOYEE
    Posted May 09, 2023 09:43 AM

    It should only occur on 655s shipped with 8.10.0.0.

    Once you can get it upgraded and booted you should have no issue.

    Try this:

    apboot> upgrade prov <imagename>

    That should upgrade the provisioning image.  When it is done upgrading type osinfo at the apboot prompt to see the status of your partitions... 



    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
    ------------------------------



  • 8.  RE: AP-655 cannot DHCP

    Posted May 15, 2023 04:31 AM

    Thanks, Colin. 

    I managed to get this working - I was probably being impatient. Once the upgrade prov command was run the AP successfully upgraded and converted to an IAP after a short while. 

    I'm guessing the upgrade doesn't necessarily have to use an InstantOS image and could just use the regular ArubaOS image? We run our APs as CAPs so I had to then convert the IAP back to a CAP once it was upgraded. 

    Adam





  • 9.  RE: AP-655 cannot DHCP

    Posted Mar 15, 2024 03:57 PM

    We happened to have the same issue on a bunch of 655.

    apboot> osinfo
    Partition 0:
        image type: 0
      machine type: 71
              size: 4009832
           version: 8.10.0.1-8.10.0.1
      build string: ArubaOS version 8.10.0.1-8.10.0.1 for Norma (jenkins@pr-hpn-cd-build78) (gcc version 5.3.0) #84079 SMP Tue May 17 22:14:33 PDT 2022
             flags: Instant preserve 0120
               oem: aruba

    Image is signed; verifying checksum... passed
    SHA2 Signature available
    Signer Cert OK
    Policy Cert OK
    RSA signature verified using SHA2.

    Partition 1:
        image type: 0
      machine type: 71
              size: 4010016
           version: 8.10.0.0-8.10.0.0
      build string: ArubaOS version 8.10.0.0-8.10.0.0 for Norma (jenkins@pr-hpn-cd-build78) (gcc version 5.3.0) #83812 SMP Mon Apr 11 00:09:35 PDT 2022
             flags: Instant preserve 0120
               oem: aruba

    apboot> printenv
    autoload=n
    autostart=yes
    baudrate=9600
    boardname=Aultmore
    bootargs=console=ttyMSM0,9600n8
    bootcmd=boot ap
    bootdelay=2
    bootfile=arm64emmc.ari
    enet1_mode=uplink
    fileaddr=50500000
    filesize=3d3020
    machid=8010012
    num_reboot=48
    os_partition=1
    servername=aruba-conductor
    stderr=serial
    stdin=serial
    stdout=serial

    partition 0 was 8.10.0.1, partition 1 was 8.10.0.0 and a boot variable was present to force part 1.

    Following commands did the trick.

    setenv os_partition 0
    save
    boot

    Thanks for your post, it helped understanding the issue.