Wireless Access

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? 

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...

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? 

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

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...

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? 

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.

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

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...

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? 

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.

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

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...

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? 

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

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.

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

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...

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? 

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... 

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

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.

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

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...

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?