I never use the default configs. I wish Mikrotik devices came blank - the manual process of logging in via Winbox MAC, copying the lastest firmware over and import an .rsc file can be quicker than holding the reset button down while coordinating turning on the power and hoping netinstall finds the device - it's not always reliable. Don't get me started about having to log into the open wifi interface because the only ethernet port won't allow Winbox access. <shakes fist at clouds> On 5 March 2018 at 11:04, Thomas Jackson <thomas@thomax.com.au> wrote:
Hi Mike,
I may have done something wrong when I last tried this, but I couldn't seem to get netinstall to address more than one device at a time?
Thanks,
Thomas
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Monday, 5 March 2018 10:45 AM To: 'MikroTik Australia Public List' <public@talk.mikrotik.com.au> Subject: Re: [MT-AU Public] Bulk net-installing
Hi Thomas!
You are right about the factory default config - only netInstall can overwrite factory default! So if that is what you need, then netinstall is the only way.
You can speed up the process by using PoE switch and netinstall in batches ;)
Cheers, Mike.
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Monday, 5 March 2018 10:17 AM To: MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: [MT-AU Public] Bulk net-installing
As someone with a large pile of hAP devices that need to be netinstalled (both to run a config script, and to get them onto the right version of ROS), my options appear to be a) spend all day laboriously processing one device at a time, b) try and find someone else to push the job onto, or c) figure out a way that I can run the process in bulk.
Before I spend more time reverse engineering the netinstall process to try and replicate it en-masse, how do others typically approach this?
My other thought is to use flashfig with a line in the script to pull down the right ROS version as part of the process, the downside there is that (if my understanding is right) our config is not "burned into" the device so if they are reset in the field they'll go back to the factory-default Mikrotik configuration which isn't ideal in this environment.
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com. au
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au