General information on “SDW Configuration templates”:
- vManage configuration templates are the preferred way to configure devices
- Templates can be created using the wizard or by entering a CLI text-style configuration
- vManage wizard and the CLI text-style configuration have feature parity
- In the backend, both template types will generate the final configuration to be pushed via NETCONF
- It’s possible to configure an automatic rollback feature (to the previous) config which gets triggered if a config is pushed out to a vDevice (vEdge/vSmart/vManage/vBond) and the device loses the connection to the overlay network
- When a device template is pushed out to multiple vDevices, it will be pushed sequentially and not parallel
- Once a device is in vManage mode (template attached), it can no longer be configured via CLI
- Device configuration modes:
- CLI mode: Device is currently in an “unmanaged” state and manually configured via CLI
- vManage mode: Device is configured via vManage using templates
- Two types of templates:
- Device templates: Contains a sub-set of feature templates and “glues” them together to an overall config file which will be then pushed out to the specified devices.
- Feature templates: For each feature (eg. system config, VPNs, interfaces, …) an own template can be configured containing the final parameters.
- Feature templates variables types:
- Global: The parameter is valid for ALL devices.
- Specific: The parameter must be set for each device individually when the configuration is pushed.
- Default: The system default parameter will be used.
- Before creating a template, the device type to which the configuration will be pushed needs to be selected