I thought I’d break out the bug reports from the v71beta4 release announcement [1] to a separate topic.
Please leave a comment if this topic is a duplicate and accept my apologies.
Several users have reported in [1] that export hangs or is slow. I can confirm this behaviour.
At the same time, I noticed that a verbose export does not suffer from this performance issue.
Since the default export is compact [2] I assume that the filtering for non-default configurations may be the culprit.
ROS v6 is like this as well and it’s easy to explain: backup file is a mere a collection of binary configuration, I guess a combination of memory dumps (or may be not) and pre-existing binary configuration files and backup process simply collects them and packs them into single file. Export OTOH has to covert it to ASCII format and reorder stanzas so that they can be imported line-by-line to a empty-config device.
What is new in v7 is that exporter seemingly chokes on comparison of running config versus default config (verbose and terse don’t do it) in certain sections. I’m pretty sure MT devs are aware of the problem given how simply it’s replicated but solving it is probably not at the top of To-Do list.
There is definitely a problem with “export” on 7.1beta4.
I see the following in the output of “export terse hide-sensitive”: “#error exporting /routing/filter/rule”
Sure enough, running “export” inside “/routing/filter/rule” hangs for a long time (multiple minutes). Adding “verbose” to that makes it return immediately, but I don’t really want a verbose export.
This is on a WAP ac with the default configuration. There is nothing (that I can see, at least) in /routing/filter/rule to export.
