11-26-2010 01:07 PM
Does anyone have better luck with this. We have tried some things but to no real avail so far....i can go so far as seeing the APs connecting but you can tell that it is still just tftp'ing the initial load still...
11-28-2010 02:34 AM
If your process is to first stage the APs by connecting to a controller, getting the up-to-date code, naming them and sending them out, it will save alot of time and effort. It will ensure that the AP functions properly, you can name it and optionally give it a static IP address before sending it out. It sure beats troubleshooting an upgrade/wan issue, if you can make it happen.
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base
11-29-2010 06:30 AM
- First, TFTP taking a long time should not prompt the AP to reboot unless the TFTP retry count is reach for a specific packet, which indicates loss on the link instead of latency. I have seen some of these APs take upwards of 10~15 minutes for a TFTP upload...their was some loss and a lot of latency, but not a long string of lost packets.
- Second, you can setup the AP to boot via TFTP to a TFTP server locally. To do so, you must set some environmental settings via the AP console. Specifically, if you set "setenv serverip
That said, because you MUST touch the AP to set these commands, and get the code off the controller and host on a TFTP server locally, it is generally easier to just plug the AP in and gets its code before deployment to the VSAT site. Once that is done, the AP will only download code when the controller code is upgraded and it will upgrade via FTP.