Controllerless Networks

I am having an issue upgrading the OS on a Aruba 7005 controller using cpboot.

I used the following variables: 

cpboot> setenv ipaddr 192.168.1.199  <<< Controller IP address
cpboot> setenv netmask 255.255.255.0 <<< Controller subnet mask
cpboot> setenv gatewayip 192.168.1.1 <<< Controller gateway IP
cpboot> setenv serverip 192.168.1.200<<< tftp server IP address(laptop)
cpboot> setenv ethact xlr_gmac0  

cpboot> save 

I have a laptop connected to the controller on interface ge0.

I installed Solarwinds tftp and server bindings to 192.168.1.200.

From the controller cpboot prompt, I can IP 192.168.1.200.

However, I am unable to ping the default-gateway 192.168.1.1.

From the laptop, I am able to ping the controller's IP address.

Here are the env variables: 

cpboot> printenv
bootargs=quiet
bootcmd=bootf
bootdelay=2
baudrate=9600
netretry=no
stdin=serial
stdout=serial
stderr=serial
wdtftp=1
ethaddr=00:0b:86:be:95:46
eth1addr=00:0b:86:be:95:47
ipaddr=192.168.1.199
netmask=255.255.255.0
gatewayip=192.168.1.1
serverip=192.168.1.200
ethact=xlr_gmac0

Here are the print results:

cpboot> ping 192.168.1.1
Using ge-0 device
ping failed; host 192.168.1.1 is not alive
cpboot> ping 192.168.1.200
Using ge-0 device
host 192.168.1.200 is alive
cpboot>

Here is error message that appears during upgrade:

cpboot> upgrade 0 ArubaOS_70xx_6.4.4.6_54633

AOS Upgrades with Ancillary Files images from cpboot will cause
partition 0 and 1 to both contain the new AOS version.
Do you wish to continue? (y or n): y
Starting TFTP Download ...
Using ge-0 device
TFTP from server 192.168.1.200; our IP address is 192.168.1.199
Filename 'ArubaOS_70xx_6.4.4.6_54633'.
Load address: 0xa800000030000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
cpboot>

Anyone have any suggestions on how to fix issue?

what are the logs on the server? does it say, controller IP reached out to it?

T T T T T means TFTP timeouts, so your TFTP server is not responding. That is likely either a firewall issue on your laptop, or a configuration on the TFTP server software. Please try to disable your firewall (temporarily) and check the TFTP server log files.

Thanks for the tip about the TFTP server applications.

Once I shutdown the firewall and reconfigured the binding settings, the tftp file transfer started working.

I successfully loaded the 6.5.0.0 OS on both partitions and restarted the controller. 

For anyone that has arrived here via google (like myself), If the 7005 is powered via POE, I noticed that the interface I was trying to ping from wasn't the one that was plugged into the switch. I promptly plugged another cable into eth3 and sure enough everything worked flawlessly.