If we could get a "cisco-like" restore-from-text-file system it would be perfect!
ryan Scott Reed wrote: > Backup does require nearly identical equipment. > I have some scripts that I use to export the parts that change, rather > than the entire configuration. > The problem with export is that it saves MAC addresses on interfaces. > If you just delete the mac=xxxxxxx part of the interfaces, you can > usually import the rest directly into a new board. > There is one more caveat. Some of the configuration words changed from > 2.9 to 3.x. If you are changing versions when changing boards, there > are some things that won't load. What I do is open the export in > notepad. I then copy the sections to the clipboard and then paste them > in the new machine. When there is an error, I determine what needs to > be changed, do a global search and replace in notepad and paste it > again. Even this can be much faster than rebuilding from scratch. > > David E. Smith wrote: > >> My network has a couple dozen RouterOS systems (mostly small >> RouterBoards) doing a number of jobs, from "simple routing and DHCP >> server" to "this is a vital backhaul link." I kinda know my way around >> networking concepts, so should a board fail, replacing it is easy >> enough. And none of our configurations are overly complex, so rebuilding >> one from scratch, as it were, rarely takes more than a half-hour. >> >> I'd like to make that process even more simple, though. >> >> I know RouterOS has two sorta-backup tools built-in. You can log into >> the terminal and run /export which will dump the whole configuration in >> a mostly-readable format. You can also run "/system export save" and get >> the same thing in a much bigger binary format. >> >> The problem I have is that these backups seem to be very >> hardware-dependent. Today, I was trying to reproduce the configuration >> of two radios I already had in the air; I thought it would be simple >> enough. Download the configuration from the existing ones, upload it to >> the new ones, change IP addresses and SSIDs, and call it a day. Turns >> out so much of the configuration is tied to things like "the MAC address >> of a given radio card or Ethernet interface," that after twenty minutes >> of trying to correct addresses to match the new hardware, it was easier >> just to start over. >> >> I can do this, but what if I get hit by a bus which subsequently careens >> into a tower, so someone else has to? >> >> Any suggestions on better ways to back up configurations from RouterOS >> devices, so I can subsequently restore them to identical (but different) >> hardware, would be appreciated. >> >> David Smith >> MVN.net >> >> >> >> -------------------------------------------------------------------------------- >> WISPA Wants You! Join today! >> http://signup.wispa.org/ >> -------------------------------------------------------------------------------- >> >> WISPA Wireless List: [email protected] >> >> Subscribe/Unsubscribe: >> http://lists.wispa.org/mailman/listinfo/wireless >> >> Archives: http://lists.wispa.org/pipermail/wireless/ >> ------------------------------------------------------------------------ >> >> >> No virus found in this incoming message. >> Checked by AVG - http://www.avg.com >> Version: 8.0.175 / Virus Database: 270.8.6/1769 - Release Date: 11/5/2008 >> 7:17 AM >> >> >> > > -------------------------------------------------------------------------------- WISPA Wants You! Join today! http://signup.wispa.org/ -------------------------------------------------------------------------------- WISPA Wireless List: [email protected] Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
