The MNDP reply message doesn't appear to include the CPU type string in the form that MikroTik uses in naming firmware upgrade packages, but it does have a "Board" string you can map to the CPU type, which then tells you which file to send. Perhaps your existing Ansible setup will suffice for this.Īlternately, there are MNDP (MikroTik Neighbor Discovery Protocol) programs which give output you can use to drive the upgrade loop. The tricky bit is sending the right version of the firmware to each subset of boxes that has a different CPU, or needs a different version than the others, and so on. Putting this into a loop to iterate over all available routers is not difficult. That will reboot that one router, which will see an *.npk file on boot at the root of its file system, and so will automatically upgrade to that version. Create a user on each MT box that has a full-capability user with an authorized SSH key. I want to create a local firmware mirror that can be scripted.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |