Template is a Collection of one or more commands with zero or more variables to be executed on devices for Configuration commands for specific scenarios that are to be executed in specific device or device groups can be added in a template for ease in executing. Changes like “Provisioning”, “OS Upgrade”, “Service Creation”, “Service Deactivation” etc on Networking Devices can be performed using Configuration Templates.
Navigation: Configuration Template is grouped under the Configuration icon on the left panel.Template Execution Notes
- Template is a collection of one or more commands with zero or more variables to be executed on devices for specific operations like ACL Modification, Route ADD, Interface NAC configuration, Interface IP Change, Interface Enable Disable, SNMP/LLDP/CDP enable or Disabling, OS Upgrade). By substituting different values (to variables) for different Devices, user can reuse the same template for similar operations on multiple devices. Device Credentials, Device Interface Name/IP Address, command inputs will become a variable portion in command template.
- Templates are vendor and OS Type specific, which means individual templates are required to be built for the same operation on two different vendor devices or for two different OS Types of same vendor. This is due to a difference in the command syntax and command formats for the same operation on two vendor devices.
- Apart from command portion, Templates also contain information of Vendor, OS Type, Series and Model where templates can RUN, along with ACL configuration which defines who (roles) are allowed to manage the Templates.
- Configuration Template (Network Diagnosis type) can be used in Network Diagnosis functionality for checking the Device’s operational data and for performing simple configurations like Crypto cache clearing, daily diagnosis check etc., (Which does not affect and is not a part of the Device Configuration).
- Configuration Template command portion must be written in XML format only.
- Configuration Template inherits Jinja2 Templating standards where user is enabled with all the advantages of Jinja2 Template such as Data Types (Integer, Boolean, List), Control Statement (If – elif – else, For Loop, while Loop), Operator condition (=, != , >, <, >=, <= etc.).
Template framework and fundamental is also followed in:
- Configuration Profile - Used by Configuration upload Job to add/remove/modify the services on devices.
- CLI (Command Line Interface) Job - User will be given Direct CLI (SSH or Telnet) access to the Devices through Infraon SecuRA (like a Gateway process) for changing configurations.
- What are the different types of Configuration Templates supported by SecuRA?
- How to write the Command Portion of Template?
- How to add comments inside the command portion?
- How to use Variable Substitutions in SecuRA?
- How to use Conditioning in SecuRA?
- How to use Looping in SecuRA?
- View Sample Template Configurations.
More about Configuration Templates