You are here

Mikrotik-952ui-5ac2nd won't TFTP

6 posts / 0 new
Last post
KN6RVU
Mikrotik-952ui-5ac2nd won't TFTP
Just bought two Mikrotik-952ui-5ac2nd routers from Amazon.  Neither responded to the Tiny PXE server.  The two units I purchase last year, program without a problem using the same equipment and process. Tried two different computers and switches without success.
K7EOK
It doesn't matter when you
It doesn't matter when you bought them, it matters when they were made.  Lately all the Mkrotik stuff I've flashed has had to have the new extra step described in the latest docs, where you go first to the factory firmware and change a boot setting to something like "try ethernet first then ... "

Tiny PXE returns errors unless you do that first.  Once you make the factory firmware settings change you can proceed.

Ed

PS ... or of course it could be something else smiley
K4APR
K4APR's picture
I am running into this exact
I am running into this exact issue now.  Got a brand new Lite from Amazon today.  Immediately ran into the TFTP issue, since it shipped with 7.x firmware.  However, I'm having no luck with guides to to a backend change on this ethernet-then-nand setting.  I have been reading docs on the AREDN site for two hours now.  I just can't seem to find the exact steps to do this.

Jason K4APR
w6bi
w6bi's picture
Ethernet-then-nand
I had the some problem making the change via the GUI.  But I found a command-ine process that worked.   Try this:

To set a MikroTik device to boot via Ethernet first (i.e., use Etherboot for Netinstall or PXE-type boot) using the command line, use the following RouterOS CLI command:

shell

/system routerboard settings set boot-device=try-ethernet-once-then-nand

    This will instruct the device to first attempt booting via Ethernet (Etherboot mode). If no Netinstall server is found, it will then boot from onboard storage (NAND).

    After issuing the command, reboot the device:

shell
/system reboot

    On the next boot, the router will first try to boot from Ethernet. This is commonly used for reinstallation or recovery scenarios with MikroTik Netinstall.

Good luck!

Orv W6BI
K4APR
K4APR's picture
I actually tried this exact
I actually tried this exact command in the CLI a little bit ago and got the same error.  "failure: not allowed by device-mode".

Also, the "shell" command returns "bad command".


 
Image Attachments: 
w6bi
w6bi's picture
Issues
I think you're already in the shall.  So it doesn't recognize the command.
Also, I think the command should be 

system routerboard settings set boot-device=try-ethernet-once-then-nand

Give that a shot.

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer