A new feature in v5.12 is the ability to export only that configuration which you have changed (if the device had default configuration, then also that). This gives you ability to debug configuration problems, compare routers more easily, and even simplify the process of migrating configuration to other devices.
to try:
/export compact
and this is all I get, instead of the usual 4 page blob:
[admin@Normis] > export compact
# jan/02/2012 01:57:23 by RouterOS 5.12
#
/ip pool
add name=dhcp_pool1 ranges=10.1.0.2-10.1.0.254
/ip dhcp-server
add address-pool=dhcp_pool1 disabled=no interface=ether3 name=dhcp1
/ip address
add address=10.1.0.1/24 interface=ether3
/ip dhcp-client
add disabled=no interface=ether1
/ip dhcp-server network
add address=10.1.0.0/24 gateway=10.1.0.1
/ip dns
set allow-remote-requests=yes max-udp-packet-size=512 servers=10.5.8.1
/ip firewall nat
add action=masquerade chain=srcnat out-interface=ether1
/ip smb shares
set [ find default=yes ] directory=/pub
/system identity
set name=Normis
/system ntp client
set primary-ntp=10.1.1.1 secondary-ntp=10.1.1.2
/system routerboard settings
set cpu-frequency=266MHz
/tool bandwidth-server
set authenticate=no
[admin@Normis] >
I’m still stunned by the simplicity of this. The amount of hours I must have wasted over the years having to remove all the default ‘rubbish’ from a config. Thank you Mikrotik!
Another great thing to implement would be candidate configurations, commits and rollbacks.
This means that any changes are made to a “candidate configuration” that is not active until the user “commits” the configuration. At the time they commit the config it saves a “rollback” point allowing the user to rollback previous commits, then commits their new config making it active.
This is kind of like the existing safe-mode but is a lot more flexible and logical. If you have ever used JunOS or Palo Alto Networks devices you will already be familiar with these concepts.
I have also recently encountered a system where administrators are able to “lock” parts of the configuration, e.g. 3 administrators are logged in to a core router, adding routes, adding queues, adding address lists, adding ip firewall policies. If an administrator wants to make a change without other administrators inadvertently making a conflicting change, they are able to “lock” the part of the configuration e.g. “firewall filters” they are working on. This give them the exclusive right to edit that part of the configuration. Other administrators who try to add/remove/disable/enable a locked section will be warned, and if they are in the correct user group are able to override the lock.
all of the described can be achieved with safe mode. you say that it’s not logical, but that’s only if you have used JunOS. if you get used to safe mode approach, it’s quite logical.
