Backup and restore work well, at least I have never had an issue. There
are some things to be aware of, but they work as designed.
Export and import also work well. Again, you have to know what they do,
but they work consistently for us.
I am looking forward to the compact option as it will make configuring
replacement boards much easier.
On 4/30/2012 8:03 PM, Josh Luthman wrote:
I wouldn't depend on that. I know I won't. You can't reliably do their
own backup and restore...
Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373
On Apr 30, 2012 8:01 PM, "Justin Miller"<mikro...@dynstatic.net> wrote:
I think once "compact" export in 5.x gets nice and stable a lot of those
rancid issues can be lessened by updating the rancid script to use it.
I use rancid but it's most difficult to teach people how to maintain the
router files.
Justin
On Apr 23, 2012, at 4:09 PM, Simon Westlake wrote:
I was previously backing up all our Mikrotik routers in RANCID but it
was difficult for some techs to work with - the files wouldn't always paste
back in correctly and randomly had capitalization errors, etc, that would
cause issues. So I decided to build an FTP system to back up the binary
configuration files instead.
I have something in the scheduler that backs up the current config to
'today.backup'. I then have a script on a remote server that FTPs in, pulls
the file and exits. It works fine.. other than the fact that ~50% of the
Mikrotiks do not work. What specifically does not work is any kind of data
transfer - I *can* connect and authenticate.
220 BRLLWIKSSW-RTR1 FTP server (MikroTik 4.12) ready
Name (x.x.x.x:simon): admin
331 Password required for admin
Password:
230 User admin logged in
Remote system type is UNIX.
ftp> ls
200 PORT command successful
425 Can't build data connection
ftp> ls
200 PORT command successful
425 Can't build data connection
ftp> Terminated
I am not firewalling the port at all, tried disabling every firewall
rule just in case to no avail. Neither box is behind a NAT of any kind (the
backup system or the Mikrotik.) There seems to be no reason why the ones
that work DO work.. and the ones that don't work DON'T.. they both have
identical configs from a firewall/FTP perspective. Google didn't lead me
anywhere helpful. Any ideas?
--
Simon Westlake
Powercode.com
(920) 351-1010
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
http://www.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
RouterOS
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
http://www.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
RouterOS
-------------- next part --------------
An HTML attachment was scrubbed...
URL:<http://www.butchevans.com/pipermail/mikrotik/attachments/20120430/d4283717/attachment.html>
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
http://www.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.1913 / Virus Database: 2411/4969 - Release Date: 04/30/12
--
Scott Reed
Owner
NewWays Networking, LLC
Wireless Networking
Network Design, Installation and Administration
Mikrotik Advanced Certified
www.nwwnet.net
(765) 855-1060
(765) 439-4253
(855) 231-6239
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
http://www.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
