Whatever management IP you assigned to the management port in ftos, please try pinging it from the computer running tftp. If the ping works, then it's a high chance of being an issue with your tftp setup. If the simple ping fails, then ensure you actually assigned an IP to the management port in ftos as the guide instructs, and ensure the management port is linked up. There's a chance it could be a bug I ran into, where the offset between the u-boot mac address and the system burnt in mac address did not have the required offset and needed to be fixed. Please run the following and send me the output:
in the bootloader, run "printenv" and find the line ethaddr=, send me that. then netboot into ftos again, and once inside it, run the following and send the output:
enable
show system
For some reason (didn't have time to debug) management connections never worked correctly unless there was an offset of 2 between u-boot's environment mac and BSD's (FTOS) kernel mac (stack mac). My guess is the BSD kernel/FTOS when fully booted uses the stack mac as well as the MAC address one address higher for various unix interfaces underneath, so it will use 30 and 31 in this case, so if u-boot had either of those assigned, there will be overlap (even though u-boot is supposed to drop anything once the kernel boots, but who knows). For example the following works correctly:
Code:
#in FTOS uboot bootloader:
ethaddr=00:01:E8:D8:3A:32
in FTOS:
Dell(conf)#do show system
Stack MAC : 00:01:e8:d8:3a:30
Burned In MAC : 00:01:e8:d8:3a:30
If they're the same, or only 1 apart, it just doesn't work right. The uboot mac should always be two higher than the stack/chassis mac reported by FTOS. The fix is to get your stack mac with the command above in ftos, then in uboot, set the uboot mac to two higher like:
Code:
setenv ethaddr 00:01:E8:D8:3A:32
saveenv
reset
