The tool lets you copy objects and their properties from a template to another file. By copying a template, you can augment newly
discovered plans with non-discoverable information, such as sites, layouts, shared-risk link groups (SRLGs), external endpoints,
and L1 objects.
-
One common use is to use the CLI copy_from_template tool to automate the process of applying a template to newly discovered network plan files before saving them in an archive
or WAE Automation Server. When you open the new plan file, you need not complete its layout or insert non-discovered objects.
Note that this CLI copy_from_template tool has more functionality than in the GUI. For information, see the copy_from_template -help output.
The copy_from_template tool is in $CARIDEN_HOME/bin, where $CARIDEN_HOME is the directory in which the Cisco WAE executables and binaries are installed.
On Linux, the default $CARIDEN_HOME is /opt/cariden/software/mate/current.
-
Another use is to create one or more visual layouts in one plan file and copy the layouts into other plan files, thus avoiding
repetitive efforts of recreating layouts. This practice is useful even for plans created outside of network discovery.
The selected properties or objects are copied from the template to the open plan file, and a report is displayed. If there
are nodes or interfaces in the plan file that are not in the template, this might indicate that the discovered network has
been changed, and the template is out of date. In this case, the report states that the template should be updated.
Note that you can individually import SRLGs, a Layer 1 model, a QoS model, demand groupings, external endpoints, and tags
from one plan file to another, all from the menu. For information, see the Cisco WAE Design Integration and Development Guide.