Wireless Access

Hi there.

I'm trying to update the arubaOS image on an ap204 over tftp (using solarwinds in windows) but each time it tries to get the image, it runs on this loop where instead of printing "###" it starts to print T and drops connection, which also is shown on the solarwinds console log. I have checked every possible scenario; At boot, both the PC and the AP are on connected to the same switch with each at 1gbps connection, turned off not only the firewall but all windows security measures, tried both PoE and DC input, but nothing seems to work. Something weird is that sometimes, it almost manages to get the image, but then it can't even load a part of it. Any idea why this happens? I even tried factory_reset and purgeenv on the console. Nothing.

T means timeout, so the AP is not receiving an expected block of data. I found TFTP having quite some issues, it doesn't handle fragmentation or NAT very well and is somewhat irreable across firewalls. Changing to another TFTP server sometimes helps, or removing devices in between (mainly firewalls/routing), but seems you did that last already.

Besides that, you should not need to manual upload an ArubaOS image to an AP204, as you would need a controller for that and the controller has a tftp server and automates/provides the firmware download.

Hi there.

I'm trying to update the arubaOS image on an ap204 over tftp (using solarwinds in windows) but each time it tries to get the image, it runs on this loop where instead of printing "###" it starts to print T and drops connection, which also is shown on the solarwinds console log. I have checked every possible scenario; At boot, both the PC and the AP are on connected to the same switch with each at 1gbps connection, turned off not only the firewall but all windows security measures, tried both PoE and DC input, but nothing seems to work. Something weird is that sometimes, it almost manages to get the image, but then it can't even load a part of it. Any idea why this happens? I even tried factory_reset and purgeenv on the console. Nothing.

What other options are there available besides uploading over TFTP? and which other recommendatios would you suggest for using another tftp server? Beforehand I had successfully uploaded the same image to another 3 ap204 on the same setup and right now they are working, so im not sure why with this one now it doesn't work.

The thing here is this AP doesn't have any image, the whole os 0 and os 1 memory locations are completely blank, so it does this each time it boots on it's own:

And doesn't connect to the controller. Right now I have a controller on the same network at 192.168.49.76:4343, which is where the other 3 are working from, so as you mention, how could I connect to the tftp server of that controller and maybe try to get it from there? I tried using the normal ip but each time the ap goes timeout. thanks

T means timeout, so the AP is not receiving an expected block of data. I found TFTP having quite some issues, it doesn't handle fragmentation or NAT very well and is somewhat irreable across firewalls. Changing to another TFTP server sometimes helps, or removing devices in between (mainly firewalls/routing), but seems you did that last already.

Besides that, you should not need to manual upload an ArubaOS image to an AP204, as you would need a controller for that and the controller has a tftp server and automates/provides the firmware download.

Hi there.

I'm trying to update the arubaOS image on an ap204 over tftp (using solarwinds in windows) but each time it tries to get the image, it runs on this loop where instead of printing "###" it starts to print T and drops connection, which also is shown on the solarwinds console log. I have checked every possible scenario; At boot, both the PC and the AP are on connected to the same switch with each at 1gbps connection, turned off not only the firewall but all windows security measures, tried both PoE and DC input, but nothing seems to work. Something weird is that sometimes, it almost manages to get the image, but then it can't even load a part of it. Any idea why this happens? I even tried factory_reset and purgeenv on the console. Nothing.

What other options are there available besides uploading over TFTP? and which other recommendatios would you suggest for using another tftp server? Beforehand I had successfully uploaded the same image to another 3 ap204 on the same setup and right now they are working, so im not sure why with this one now it doesn't work.

The thing here is this AP doesn't have any image, the whole os 0 and os 1 memory locations are completely blank, so it does this each time it boots on it's own:

And doesn't connect to the controller. Right now I have a controller on the same network at 192.168.49.76:4343, which is where the other 3 are working from, so as you mention, how could I connect to the tftp server of that controller and maybe try to get it from there? I tried using the normal ip but each time the ap goes timeout. thanks

T means timeout, so the AP is not receiving an expected block of data. I found TFTP having quite some issues, it doesn't handle fragmentation or NAT very well and is somewhat irreable across firewalls. Changing to another TFTP server sometimes helps, or removing devices in between (mainly firewalls/routing), but seems you did that last already.

Besides that, you should not need to manual upload an ArubaOS image to an AP204, as you would need a controller for that and the controller has a tftp server and automates/provides the firmware download.

Hi there.

I'm trying to update the arubaOS image on an ap204 over tftp (using solarwinds in windows) but each time it tries to get the image, it runs on this loop where instead of printing "###" it starts to print T and drops connection, which also is shown on the solarwinds console log. I have checked every possible scenario; At boot, both the PC and the AP are on connected to the same switch with each at 1gbps connection, turned off not only the firewall but all windows security measures, tried both PoE and DC input, but nothing seems to work. Something weird is that sometimes, it almost manages to get the image, but then it can't even load a part of it. Any idea why this happens? I even tried factory_reset and purgeenv on the console. Nothing.

Looks like your controller has ADP disabled. You can check on the controller CLI:

(md7005) #show adp configADP Configuration-----------------key           value---           -----discovery     enableigmp-join     enableigmp-vlan-id  0

It's by far easiest to get the image from the controller and it should go automatically if the AP discovers the controller.

As you did a factory_reset, that wiped all images on the AP, so that is the reason why there are no images (anymore). I would try to get ADP working first, otherwise DNS or DHCP discovery should work as well. Or could it be that there are access-lists, or other security enabled on your switch that may block traffic from/to the AP?

What other options are there available besides uploading over TFTP? and which other recommendatios would you suggest for using another tftp server? Beforehand I had successfully uploaded the same image to another 3 ap204 on the same setup and right now they are working, so im not sure why with this one now it doesn't work.

The thing here is this AP doesn't have any image, the whole os 0 and os 1 memory locations are completely blank, so it does this each time it boots on it's own:

And doesn't connect to the controller. Right now I have a controller on the same network at 192.168.49.76:4343, which is where the other 3 are working from, so as you mention, how could I connect to the tftp server of that controller and maybe try to get it from there? I tried using the normal ip but each time the ap goes timeout. thanks

T means timeout, so the AP is not receiving an expected block of data. I found TFTP having quite some issues, it doesn't handle fragmentation or NAT very well and is somewhat irreable across firewalls. Changing to another TFTP server sometimes helps, or removing devices in between (mainly firewalls/routing), but seems you did that last already.

Besides that, you should not need to manual upload an ArubaOS image to an AP204, as you would need a controller for that and the controller has a tftp server and automates/provides the firmware download.

Hi there.

I'm trying to update the arubaOS image on an ap204 over tftp (using solarwinds in windows) but each time it tries to get the image, it runs on this loop where instead of printing "###" it starts to print T and drops connection, which also is shown on the solarwinds console log. I have checked every possible scenario; At boot, both the PC and the AP are on connected to the same switch with each at 1gbps connection, turned off not only the firewall but all windows security measures, tried both PoE and DC input, but nothing seems to work. Something weird is that sometimes, it almost manages to get the image, but then it can't even load a part of it. Any idea why this happens? I even tried factory_reset and purgeenv on the console. Nothing.