Hmmm... are you able to run the other commands properly? 'setenv uboot ICX64xx/kxz10105.bin' works without error? After I updated the Primary in the webui and rebooted, I was able to run those commands. I didn't see a way to update uboot through the webui but since the console commands worked I didn't need to worry about it. If you updated Primary through your TFTP then I assume it's not a firewall issue. You've run 'reset' to reboot the switch after updating the Primary?
That was it. The Windows firewall seems to be blocking pings on 'private' networks. I'll have to dig into that.
The 'setenv' commands have always worked on mine, even before flashing the new primary image. It just was never able to connect to/ping the TFTP server which I assumed was an issue with the TFTP server/Windows Firewall but that doesn't seem to be the case since no issues flashing via the GUI. So far, I've flashed new primary/secondary and ran 'reload' to reboot the switch.
ICX6450-48P Router>show flash
Stack unit 1:
Compressed Pri Code size = 9871112, Version:08.0.30uT313 (ICX64R08030u.bin)
Compressed Sec Code size = 8563580, Version:08.0.30uT311 (ICX64S08030u.bin)
Compressed Boot-Monitor Image size = 512, Version:07.4.00T310
Code Flash Free Space = 33636352ICX6450-48P Router>ping 192.168.1.123
Sending 1, 16-byte ICMP Echo to 192.168.1.123, timeout 5000 msec, TTL 64
Type Control-c to abort
Reply from 192.168.1.123 : bytes=16 time=1ms TTL=128
Success rate is 100 percent (1/1), round-trip min/avg/max=1/1/1 ms.Pinging 192.168.1.150 with 32 bytes of data:
Reply from 192.168.1.150: bytes=32 time<1ms TTL=64
Reply from 192.168.1.150: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.1.150:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0msHmmm. Well that's about the limits of what I know about the switch lol. You'll have to wait until one of the more knowledgeable members chimes in. I wish I could be better help!
I'm going to ask a question you may have already answered and I just missed it, but is your ethernet cable plugged into the actual management port, or one of the switch ports?
Yup, console cable plugged into console port and ethernet cable plugged into management port below.
OK. From the CLI, usually if the switch can ping the TFTP host, but TFTP isn't working (and Windows Firewall is completely off) then it's possibly a misconfiguration of the TFTP server itself. For example, mine likes to forget the root folder I have the firmware files in, so I have to remember to updated it; on occasion it's bound itself to the wrong interface (when my workstation used to have Hyper-V enabled, it would for some reason prefer the HV NIC that was not configured to an interface rather than the PHY). I've also had problems with TFTPd64 when files I want are not in the root folder, so I would move them up one level and the issue would go away.
honestly at this point I'd say 8090+ isn't even to beta yet, boot is still full of python packaging errors and some of the recent bugs they've patched are along the lines of "device eats its own flash alive with spurious writes"
Current project for work has me out of town and only home every other weekend but I'll post results next time I'm back. Thanks @fohdeesha
Well damn. That was easy as heck. Thanks for posting (and also to the others who worked this out). Anybody want an unused Brocade mini-usb to serial cable?
you have something strange going on on your network if something is replying for 10.10.10.15 with ICMP redirects, something on your network is answering for .15 and trying to advertise a better path. maybe reboot your router and windows 11 machine. you should absolutely be able to ping the icx from w11 and vice versa