Как сохранить настройки роутера mikrotik

Manual:Configuration Management

This manual introduces you with commands which are used to perform the following functions:

• system backup;
• system restore from a backup;
• configuration export;
• configuration import;
• system configuration reset.

Description

The configuration backup can be used for backing up MikroTik RouterOS configuration to a binary file, which can be stored on the router or downloaded from it using FTP for future use. The configuration restore can be used for restoring the router’s configuration, exactly as it was at the backup creation moment, from a backup file. The restoration procedure assumes the configuration is restored on the same router, where the backup file was originally created, so it will create partially broken configuration if the hardware has been changed.

The configuration export can be used for dumping out complete or partial MikroTik RouterOS configuration to the console screen or to a text (script) file, which can be downloaded from the router using FTP protocol. The configuration dumped is actually a batch of commands that add (without removing the existing configuration) the selected configuration to a router. The configuration import facility executes a batch of console commands from a script file.

System reset command is used to erase all configuration on the router. Before doing that, it might be useful to backup the router’s configuration.

System Backup

The system backup feature allows you to effortlessly save and load device’s configuration. Read more about the backup feature in the System/Backup section.

Exporting Configuration

Command name: /export

The export command prints a script that can be used to restore configuration. The command can be invoked at any menu level, and it acts for that menu level and all menu levels below it. The output can be saved into a file, available for download using FTP.

Command Description

Example

[admin@MikroTik] > ip address print Flags: X - disabled, I - invalid, D - dynamic # ADDRESS NETWORK BROADCAST INTERFACE 0 10.1.0.172/24 10.1.0.0 10.1.0.255 bridge1 1 10.5.1.1/24 10.5.1.0 10.5.1.255 ether1 [admin@MikroTik] >

[admin@MikroTik] ip address> export file=address [admin@MikroTik] ip address>

To see the files stored on the router:

[admin@MikroTik] > file print # NAME TYPE SIZE CREATION-TIME 0 address.rsc script 315 dec/23/2003 13:21:48 [admin@MikroTik] >

Compact Export

Starting from v5.12 compact export was added. It allows to export only part of configuration that is not default RouterOS config.

Note: Starting from v6rc1 «export compact» is default behavior. To do old style export use export verbose

For example compact OSPF export:

[admin@SXT-ST] /routing ospf> export compact # jan/02/1970 20:16:32 by RouterOS 5.12 # software ospf instance set [ find default=yes ] redistribute-connected=as-type-1 /routing ospf interface add disabled=yes interface=wlan1 network-type=point-to-point /routing ospf network add area=backbone network=10.255.255.36/32 add area=backbone disabled=yes network=10.5.101.0/24 add area=backbone network=10.10.10.0/24 [admin@SXT-ST] /routing ospf>

Compact export introduces another feature that indicates which part of config is default on RouterOS and cannot be deleted. As in example below ‘*’ indicates that this OSPF instance is part of default configuration.

[admin@SXT-ST] /routing ospf instance> print Flags: X - disabled, * - default 0 * name="default" router-id=0.0.0.0 distribute-default=never redistribute-connected=as-type-1 redistribute-static=no redistribute-rip=no redistribute-bgp=no redistribute-other-ospf=no metric-default=1 metric-connected=20 metric-static=20 metric-rip=20 metric-bgp=auto metric-other-ospf=auto in-filter=ospf-in out-filter=ospf-out

List of default config by menus that cannot be removed:

Menu	Entries
/interface wireless security-profiles	default
/ppp profile	«default», «default-encryption»
/ip hotspot profile	«default»
/ip hotspot user profile	«default»
/ip ipsec proposal	«default»
/ip smb shares	«pub»
/ip smb users	«guest»
/ipv6 nd	«all»
/mpls interface	«all»
/routing bfd interface	«all»
/routing bgp instance	«default»
/routing ospf instance	«default»
/routing ospf area	«backbone»
/routing ospf-v3 instance	«default»
/routing ospf-v3 area	«backbone»
/snmp community	«public»
/tool mac-server mac-winbox	«all»
/tool mac-server	«all»
/system logging	«info», «error», «warning», «critical»
/system logging action	«memory», «disk», «echo», «remote»
/queue type	«default», «ethernet-default», «wireless-default», «synchronous-default», «hotspot-default», «only-hardware-queue», «multi-queue-ethernet-default», «default-small»

Importing Configuration

Command name: /import

The root level command /import [file_name] executes a script stored in the specified file. It will add the configuration from the specified file to an existing configuration. This file may contain any console commands, including scripts. Can be used to restore configuration or parts of it after configuration loss.

Command Description

Automatic Import

In RouterOS it is possible to automatically execute scripts — your script file has to be named anything.auto.rsc — once this file is uploaded using FTP to the router, it will automatically be executed, just like with the ‘/import’ command. This method only works with FTP.

Once the file is uploaded, it is automatically executed. Information about the success of the commands that were executed is written to anything.auto.log

Example

To load the saved export file use the following command:

[admin@MikroTik] > import address.rsc Opening script file address.rsc Script file loaded and executed successfully [admin@MikroTik] >

Configuration Reset

Command name: /system reset-configuration

Description

The command clears all configuration of the router and sets it to the default including the login name and password (‘admin’ and no password), IP addresses and other configuration is erased, interfaces will become disabled. After the reset command router will reboot. The default is either the factory default, that you can see in the article Default configurations, or it can be a custom default, that can be loaded by including an RSC file when doing Netinstall or if specified with a branding package.

Command Description

• keep-users: keeps router users, passwords and ssh host keys(since v6.45.1)
• no-defaults: doesn’t load any default cofigurations, just clears everything
• skip-backup: automatic backup is not created before reset, when yes is specified
• run-after-reset: specify export file name to run after reset

Note: If run-after-reset is set then no-defaults parameter will be ignored and only the specified script will be loaded!

Warning: Warning: If the device has a folder named «flash», then the confscript.rsc file must be stored in that folder to work with «run-after-reset» command. Everything outside this folder is stored on the RAM drive which contents are deleted on reboot or power cycle.

Warning: If the router has been installed using netinstall and had a script specified as the initial configuration, the reset command executes this script after purging the configuration. To stop it doing so, you will have to reinstall the router.

Example

[admin@MikroTik] > system reset-configuration Dangerous! Reset anyway? [y/N]: n action cancelled [admin@MikroTik] >

Import troubleshooting

Configuration parts to watch out for in exported .rsc files

Things that should be removed from export files that were created with: «/export», before attempting import on new device.

/interface ethernet set [ find default-name=ether5 ] auto-negotiation=no name=ether1-gateway set [ find default-name=ether6 ] name=ether2 set [ find default-name=ether7 ] name=ether3 set [ find default-name=ether8 ] name=ether4 set [ find default-name=ether1 ] name=ether5 set [ find default-name=ether2 ] name=ether6 set [ find default-name=ether3 ] name=ether7 set [ find default-name=ether4 ] name=ether8

• In older version exports default entries might show with «add» instead of «set» command. That should be edited before import to avoid errors.
• Check if interface/module: ether/wlan/modem/com/etc count match on new and old device. If there will some missing that will end up in error during .rsc import.

In case of problematic import, attempt the following:

• Reset the configuration on that device.
• Run import command again with «verbose=yes» argument. It will stop also stop import process on problem which you already encountered, but will also show place where export failed. That way showing you place where things need to be edited in .rsc import file

Startup delay

If your configuration relies on interfaces that might not yet have started up upon command execution, it is suggested to introduce delays, or to monitor until all needed interfaces are available. This example script allows you to set how many interfaces you are expecting, and how long to wait until they become available:

The above script will wait until there are 10 interfaces visible, or 30 seconds. If there are no 10 interfaces in this time, it will put a message in the log. Modify the variables according to your needs.

Источник

Summary

RouterOS backup feature allows you to save your current device’s configuration, which then can be re-applied on the same device. The system’s backup file also contains the device’s MAC addresses, which are restored when the backup file is loaded.

If The Dude and user-manager are installed on the router, then the system backup will not contain configuration from these services, therefore additional care should be taken to save configuration from these services. Use provided tool mechanisms to save/export configuration if you want to save it.

Certificates can not be restored from a backup file, they should be re-imported after a backup restore.

System backups contain sensitive information about your device and its configuration, always consider encrypting the backup file and keeping the backup file in a safe place.

Saving a backup

Sub-menu: /system backup save

Property	Description
dont-encrypt (yes | no; Default: no)	Disable backup file encryption. Note that since RouterOS v6.43 without a provided password the backup file is unencrypted.
encryption (aes-sha256 | rc4; Default: aes-sha256)	The encryption algorithm to use for encrypting the backup file. Note that is not considered a secure encryption method and is only available for compatibility reasons with older RouterOS versions.
name (string; Default: [identity]-[date]-[time].backup)	The filename for the backup file.
password (string; Default: )	Password for the encrypted backup file. Note that since RouterOS v6.43 without a provided password the backup file is unencrypted.

If a password is not provided in RouterOS versions older than v6.43, then the backup file will be encrypted with the current user’s password, except if the dont-encrypted property is used or the current user’s password is empty.

The backup file will be available under /file menu, which can be downloaded using FTP or using Winbox.

Loading a backup

Load units backup without password:

[admin@MikroTik] > system/backup/load name=auto-before-reset.backup password=""

Property	Description
name (string; Default: )	File name for the backup file.
password (string; Default: )	Password for the encrypted backup file.

Example

To save the router’s configuration to file test and a password:

[admin@MikroTik] > /system backup save name=test password= Configuration backup saved [admin@MikroTik] > /system backup

To see the files stored on the router:

[admin@MikroTik] > /file print # NAME TYPE SIZE CREATION-TIME 0 test.backup backup 12567 sep/08/2018 21:07:50 [admin@MikroTik] >

To load the saved backup file test:

[admin@MikroTik] > /system backup load name=test password: Restore and reboot? [y/N]: y Restoring system configuration System configuration restored, rebooting now

Cloud backup

Since RouterOS v6.44 it is possible to securely store your device’s backup file on MikroTik’s Cloud servers, read more about this feature on the IP/Cloud page.

Источник