The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
You use templates to define device parameters and settings, which you can later deploy to a specified number of devices based on device type. Templates enhance productivity when you are implementing new services or a new site. Altering configurations across a large number of devices can be tedious and time-consuming, and templates save you time by applying the necessary configurations and by ensuring consistency across devices.
Table 4-1 describes the process for creating and deploying templates.
This chapter contains the following sections:
•About Templates for Branch Design and Deployment
•Creating Configuration Templates for Branch Deployment
•Creating and Deploying Composite Templates for Branch Deployment
•Creating Configuration Templates
•Creating Feature and Technology Templates
•Creating Security Configuration Templates
•Creating Security Configuration Templates
•Importing and Deploying a Configuration Template
•Troubleshooting Template Deployment
When you have a site, office, or branch that uses a similar set of devices and configurations, you can use configuration templates to build a generic configuration that you can apply to one more or more devices in the branch. You can also use configuration templates when you have a new branch and want to quickly and accurately set up common configurations on the devices in the branch.
Deploying a branch is creating the minimum configurations for the branch router. Prime NCS (WAN) allows you to create a set of required features that include:
•Feature templates for the Ethernet interface
•Feature templates for the routing configuration
•CLI template for additional features you require
All of the templates you create can then be added to a single composite template, which aggregates all the individual feature templates you need for the branch router. You can then use this composite template when you perform branch deployment operations and to replicate the configurations at other branches.
When you have a set of similar devices across a branch, you can deploy a composite template that includes "golden" configurations to simplify deployment and ensure consistency across your device configurations. You can also use the composite template to compare against an existing device configuration to determine if there are mismatches.
Related Topics
•Creating Configuration Templates for Branch Deployment
•Creating and Deploying Composite Templates for Branch Deployment
The following sections explain how to create and deploy configuration templates that are commonly used in branch deployments:
•Creating an Ethernet Interface Configuration Template
•Creating an EIGRP Routing Configuration Template
•Creating a RIP Routing Configuration Template
•Creating a CLI Configuration Template
Many branch deployments require an Ethernet interface configuration template, which you then include in the composite template for branch deployments.
To create an Ethernet interface configuration template:
Step 1 Choose Design > Configuration Templates.
Step 2 Under the Features and Technologies folder, expand Interfaces, then click Ethernet Interfaces.
Step 3 Enter the basic template information.
Step 4 From the Device Type drop-down list, choose Routers.
Step 5 Under Template Detail, click Add Row in the Ethernet Interfaces table.
Step 6 Complete the fields for an Ethernet interface that is configured on the device. (If, for example, you enter "GigabitEthernet0/1" in the Interface field, the GigabitEthernet0/1 interface must be physically present on the device.)
Step 7 In the IP Address field, enter a valid IP and mask configuration; for example, 192.168.1.1 255.255.255.0.
Step 8 Click Save.
Step 9 Click Save as New Template.
Many branch deployments require an EIGRP routing configuration template, which you then include in the composite template for branch deployments.
To create an EIGRP routing configuration template:
Step 1 Choose Design > Templates > Configuration.
Step 2 Under the Features and Technologies folder, expand Routing, then click EIGRP.
Step 3 Enter the basic template information.
Step 4 From the Device Type drop-down list, choose Routers.
Step 5 Under Template Detail, click Add Row in the EIGRP Routes table.
Step 6 Enter an Autonomous System (AS) Number and a passive interface such as FastEthernet0/0, and choose a value for Auto Summary.
Step 7 Click Save.
Step 8 Click Save as New Template.
Many branch deployments require a RIP routing configuration template, which you then include in the composite template for branch deployments.
To create a RIP routing configuration template:
Step 1 Choose Design > Templates > Configuration.
Step 2 Under the Features and Technologies folder, expand Routing, then click RIP.
Step 3 Enter the basic template information.
Step 4 From the Device Type drop-down list, choose Routers.
Step 5 Under Template Detail, click Enable RIP.
Step 6 Choose a RIP version.
Step 7 Under Advanced Configuration, choose:
•IP Network List—Enter network IP addresses, such as 10.10.10.10.
•Passive Interfaces—Enter a passive interface, such as FastEthernet0/0.
Step 8 Click Save.
Step 9 Click Save as New Template.
Many branch deployments require a CLI configuration template, which you then include in the composite template for branch deployments.
To create a CLI configuration template:
Step 1 Choose Design > Templates > Configuration.
Step 2 Under the Features and Technologies folder, expand CLI Templates, then click CLI.
Step 3 Enter the basic template information.
Step 4 From the Device Type drop-down list, choose Routers.
Step 5 Under Template Detail, click the CLI Content tab, and then enter the following text:
banner motd #Welcome to Prime NCS#
Step 6 Click Save.
Step 7 Click Save as New Template.
You create a composite template if you have a collection of existing feature or CLI templates that you want to apply collectively to devices. You specify the order in which the templates contained in the composite template are applied to devices.
If you have multiple similar devices replicated across a branch, you can create and deploy a "master" composite template to all the devices in the branch. This master composite template can also be used later when you create new branches.
Step 1 Choose Design > Templates > Configuration, then click Composite Template.
Step 2 Enter parameters for the composite template.
Step 3 From the Validation Criteria drop-down list, choose the devices to which all of the templates contained in the composite template apply. For example, if in your composite template you have a template that applies to Cisco 7200 Series routers and another that applies to all routers, choose the Cisco 7200 Series routers in the Device Type drop-down menu.
Note If a device type is grayed out, the template cannot be applied on that device type.
Step 4 Under Template Details, choose the templates to include in the composite template.
Step 5 Using the arrows, put the templates in the composite into the order in which they should be deployed to the devices. For example, to create an ACL and associate it with an interface, put the ACL template first, followed by the interface template.
Step 6 Click Save as New Template.
Step 7 Navigate to the My Templates folder and choose the template you just saved.
Step 8 Click the Publish icon to publish the template so it can be deployed.
Step 9 Click the Go to Deployment icon and go to the Deploy > Configuration Tasks page.
Step 10 Click Deploy on the template you published.
Step 11 Specify the deployment options as explained in Specifying Template Deployment Options.
Step 12 Click OK.
Step 13 Choose Tools > Task Manager > Jobs Dashboard to verify the status of a template deployment.
Prime NCS (WAN) provides the following types of configuration templates:
•CLI templates—User-defined templates that are created based on your own parameters. CLI templates allow you to choose the elements in the configurations. Prime NCS (WAN) provides variables that you replace with actual values and logic statements. You can also import templates from Cisco Prime LAN Management System. See Creating and Deploying CLI Templates.
•Feature and technology templates—Configurations that are specific to a feature or technology in a device's configuration. See Creating and Deploying Feature and Technology Templates.
•Composite templates—Two or more feature or CLI templates grouped together into one template. You specify the order in which the templates contained in the composite template are deployed to devices. See Creating and Deploying Composite Templates for Branch Deployment.
Note All templates must be published before they can be deployed to devices.
You use templates to define device parameters and settings, which you can later deploy to a specified number of devices based on device type. Altering configurations across a large number of devices can be tedious and time-consuming, and templates save you time by applying the necessary configurations and ensuring consistency across devices.
Prime NCS (WAN) ships with default configuration templates that you can find under Design > Configuration Templates > My Templates > OOTB. These templates are described in Table 4-2.
|
|
---|---|
Medianet - PerfMon |
Configure performance monitoring for Medianet. |
PA with WAAS |
Configure Cisco Performance Agent1 and Wide Area Application Services (WAAS). |
PA without WAAS |
Configure Cisco Performance Agent without WAAS. |
Collecting Traffic Statistics |
Collect network traffic statistics. |
1 Cisco Performance Agent is a licensed feature of Cisco IOS Software. It offers comprehensive application performance and network usage data to help network administrators accurately assess user experience and optimize the use of network resources. |
Creating CLI templates is an advanced function that should be done by expert users. Before you create a CLI template, you should:
•Have expert knowledge and understanding of the CLI and be able to write the CLI in Apache VTL. For more information about Apache Velocity Template Language, see http://velocity.apache.org.
•Understand to what devices the CLI you create can be applied.
•Understand the data types supported by Prime NCS (WAN).
•Understand and be able to manually label configurations in the template.
Before creating a CLI template, make sure you have satisfied the prerequisites as described in Prerequisites for Creating CLI Templates.
Step 1 Choose Design > Configuration Templates.
Step 2 Expand the CLI Template folder, then click CLI.
Step 3 Enter the basic template information.
Step 4 From the Validation Criteria drop-down list, choose the device types to which this CLI template can be applied.
The Device Type field lists product types, product families, and model numbers.
Step 5 Under Template Detail, click Manage Variables.
This allows you to specify a variable for which you will define a value when you deploy the template.
Step 6 Click Add Row and enter the parameters for a new variable, then click Save.
Step 7 Enter the CLI information.
Note In the CLI field, you must enter code using Apache VTL.
Step 8 To view a list of all variables used in the template, click Form View (this is a read-only view), then click Manage Variables to change the variables.
Step 9 Click Save As New Template.
Step 10 Navigate to the My Templates folder and choose the template you just saved.
Step 11 Click the Publish icon at the top-right corner, then click OK.
Step 12 Click the Go to Deployment icon and go to the Deploy > Configuration tasks page.
Step 13 Click Deploy on the template you published.
Step 14 Specify the deployment options as explained in Specifying Template Deployment Options.
Step 15 Click OK.
When a device is discovered and added to Prime NCS (WAN), you can use the database values that were gathered during the inventory collection to create CLI templates. For example, if you want to create and deploy a CLI template to shut down all interfaces in a branch, you can create a CLI template that contains the following commands:
#foreach ($interfaceName in $interfaceNameList)
interface $interfaceName \n
shutdown
#end
where $interfaceNameList is the database variable type whose value will be retrieved from the database. $interfaceNameList has a default value of Inventory::EthernetProtocolEndpoint.IntfName.
To populate interfaceNameList with the value from the database, you must create a properties file to capture the query string as described below and save it in the /opt/CSCOlumos/conf/ifm/template/InventoryTagsInTemplate folder.
Sample Property File
Filename: interface.properties
# for interface name tag->Name
EthernetProtocolEndpoint.IntfName=select u.name from EthernetProtocolEndpoint u where u.owningEntityId =
# say for other attributes of EthernetProtocolEndpoint Model, should we define tags
# any good generic way of accepting tags -attr+its mapped query ?
After you create the CLI template and the property file and deploy the CLI template, the following CLI is configured on the devices. This output assumes the device has two interfaces (Gigabitethernet0/1 and Gigabitethernet0/0):
interface GigabitEthernet0/0
shutdown
interface GigabitEthernet0/1
shutdown
Note InterfaceNameList is a Prime NCS (WAN) default database variable.
Verify that the Enterprise JavaBeans Query Language (EJB QL) specified in the properties file returns a list of strings; or, if a single element is specified, the EJB QL should return a list containing one element.
After you publish a template and want to deploy it to one or many devices, you can specify devices, values, and scheduling information to tailor your deployment. Table 4-3 explains the deployment options.
Feature and technology templates are templates that are based on device configuration. Feature and technology templates focus on specific features or technologies in a device's configuration. When you add a device to Prime NCS (WAN), Prime NCS (WAN) gathers the device configuration for the model you added.
Note Prime NCS (WAN) does not support every configurable option for all device types. If Prime NCS (WAN) does not have a feature and technology template for the specific feature or parameter you want configure, create a CLI template as described in Creating and Deploying CLI Templates.
You create feature and technology templates to simplify the deployment of configuration changes. For example, you can create an SNMP feature and technology template and then quickly deploy it to the devices you specify. You can also add one or more feature and technology templates to a composite template. If you do, when you update the SNMP template, the composite template in which the SNMP template is contained automatically has your latest changes.
Step 1 Choose Design > Configuration Templates.
Step 2 Expand the Features and Technologies folder, choose an appropriate subfolder, then choose a template type to create.
Step 3 Enter the basic template information.
Step 4 From the Validation Criteria drop-down list, choose the device types to which this feature template can be applied. The Device Type field lists product types, product families, and model numbers.
Note If you are creating a feature template that applies only to a particular device type, the Device Type field lists only the applicable device type, and you cannot change the selection.
Step 5 Under Template Detail, enter the CLI information.
Step 6 Click Save As New Template.
Step 7 Navigate to the My Templates folder and choose the template you just saved.
Step 8 Click the Publish icon to publish the template so it can be deployed.
Step 9 Click the Go to Deployment icon and go to the Deploy > Configuration Tasks page.
Step 10 Click Deploy on the template you published.
Step 11 Specify the deployment options as explained in Specifying Template Deployment Options.
Step 12 Click OK.
You can use a template to configure a static route. Static routes can be overwhelming in a large or complicated network. By creating a static routing template, you can avoid making manual changes each time there is a change in the network.
To create and deploy a static routing template:
Step 1 Choose Design > Configuration Templates.
Step 2 Expand the Features and Technologies folder, expand the Routing subfolder, then click Static.
Step 3 Enter the basic template information.
Step 4 Under Template Detail, click Add Row, then complete the fields.
Note For Permanent Route, choose
•True to specify that the route will not be removed from the routing table, even if the next-hop interface shuts down or next-hop IP address is not reachable.
•False to specify that the route will be removed from the routing table, even if the next-hop interface shuts down or next-hop IP address is not reachable.
Step 5 Click Save As New Template.
Step 6 Navigate to the My Templates folder and choose the template you just saved.
Step 7 Click the Publish icon to publish the template so it can be deployed.
Step 8 Click the Go to Deployment icon and go to the Deploy > Configuration Tasks page.
Step 9 Click Deploy on the template you published.
Step 10 Specify the deployment options as explained in Specifying Template Deployment Options.
Step 11 Click OK.
To create and deploy a template to configure access lists:
Step 1 Choose Design > Configuration Templates.
Step 2 Expand the Features and Technologies folder, expand the Security subfolder, then click ACL.
Step 3 Enter the basic template information.
Step 4 Under Template Detail, click Add Row, then complete the fields described in Table 4-4.
Step 5 Click Save As New Template.
Step 6 Navigate to the My Templates folder and choose the template you just saved.
Step 7 Click the Publish icon to publish the template so it can be deployed.
Step 8 Click the Go to Deployment icon and go to the Deploy > Configuration Tasks page.
Step 9 Click Deploy on the template you published.
Step 10 Specify the deployment options as explained in Specifying Template Deployment Options.
Step 11 Click OK.
You can create security configuration templates for the following features:
•Dynamic Multipoint VPN (DMVPN)
•Group Encrypted Transport VPN (GETVPN)
To create a DMVPN template, follow these steps:
Step 1 Choose Design > Configuration > Features and Technologies > Security > DMVPN.
The Dynamic Multipoint VPN Configuration Template page opens.
Step 2 In the Template Basic section, enter a name and a description in the appropriate fields.
Step 3 From the Validation Criteria drop-down list, choose a device type from the drop-down list and enter the OS version.
Step 4 In the Template Detail section, enter the IKE Authentication and Encryption policy.
Step 5 In the IKE Authentication Type field, click the anchored plus button (+), and choose the IKE authentication type.
If you choose the default Pre-Shared key, you must provide the secret key and reconfirm it. If you choose the Digital Certificate as the authentication type, the router must have a digital certificate issued by a Certificate Authority to authenticate itself.
Step 6 In the IKE Authentication Policy section, click the Add Row button to add the IKE policies
Step 7 Enter the priority, and choose Authentication, Diffie-Hellman (D-H) Group, Encryption, Hash, and Lifetime from the drop-down list.
To delete the IKE policies, choose the policy and click Delete.
To edit the parameters of the IKE policy, click a row or field and edit its parameters.
Step 8 Click Save to save the configuration.
Step 9 In the Encryption policy field, click the anchored plus button (+) to add the Transform Set Profile.
Step 10 In the Transform Set Profile dialog box, enter a name and choose the acceptable combination of security protocols and algorithm from the drop-down list to configure the transform set.
Step 11 Enable IP compression and choose a mode for the transform set.
Step 12 To delete the transfer set, choose the transfer set and click Delete. To edit the parameters of the transfer set, click a row or field and edit its parameters.
Step 13 Click Save to save the configuration.
Step 14 In the Topology and Routing Information section, choose the topology and the device role. For the Routing Protocol, choose the Extended Interior Gateway Routing Protocol (EIGRP) or Routing Information Protocol Version 2 (RIPv2). Use the Other option to configure other protocols.
Note The routing information are disabled when you select Hub as the device role.
Step 15 Enter the required information in the NHRP and Tunnel Parameters section.
Step 16 In the NHS Server Information section, add the Next Hub server information, including the IP Address of Hub's physical interface and the IP address of Hub's tunnel interface.
Note If you check the Cluster Support check box, add the information, such as Cluster ID, Max Connection, and Next Hub Server. The template with the NHS cluster configuration will be applied only to the device running Cisco IOS Software version 15.1(2)T or later.
Step 17 Click Save As New Template.
The new template appears in the My Templates folder.
Step 18 Click the Publish icon to publish the template so it can be deployed.
Note After you create the template, publish it to make it available for deployment.
For a list and descriptions of elements on the Dynamic Multipoint VPN Template page, see Table 4-5.
To deploy the DMVPN template, follow these steps.
Note You must publish the specified template before it can be deployed to devices.
Step 1 Choose Deploy > Configuration Tasks > My Templates.
Step 2 On the My Templates page, select the DMVPN template, and click the Tasked View button.
Step 3 From the Deploy Task pad, click Deploy.
The Template Deployment page opens.
Step 4 From the device selection section, select the list of devices on which to deploy the template.
Step 5 In the Value Assignment section, click the radio button to select the device.
Step 6 For DMVPN, you can change the values for GRE IP Address, Subnet Mask, and Tunnel Throughput Delay.
Step 7 If you have changed the values, click Apply. For elements on the page, see Table 4-5.
Note The spoke option for Cisco IOS Software version 15.1(2)T or later should display the NHS cluster configuration section.
Step 8 In the Schedule section, enter the Job Name, then click one of the following radio buttons:
•Run—To run the job immediately.
•Run at Schedule Time—To specify a time to run the job.
Step 9 Under Summary, verify your entries, then click OK.
To create a GETVPN group member template:
Step 1 Choose Design > Configuration > Features and Technology > Security > GETVPN-GroupMember.
The GETVPN-GroupMember Configuration Template page appears.
Step 2 In the Template Basic section, enter a name, description, and author name in the appropriate fields.
Step 3 From the Validation Criteria drop-down list, choose a device type from the drop-down list and enter the OS version.
Step 4 In the Group Information section, enter the group name and the group ID.
Step 5 Click the IKE Authentication Policy + button to add the IKE authentication information.
Step 6 In the IKE Authentication Policy dialog box, click the Pre-Shared key or Digital Certificate radio button.
The key server authenticates by using the digital certificate. The router must have a digital certificate issued by a Certificate Authority to authenticate itself.
Step 7 In the IKE Policy section, click Add Row and add the IKE policies, then click Save. Click on the Row or Field to edit the parameters. Select the IKE policies from the list and click Delete to delete the IKE policies.
Step 8 Enter the registration interface for the group member.
Step 9 In the Traffic Detail section, enter the Local Exception ACL and the Fail Close ACL.
Step 10 In the Key Servers section, enter the Primary Key Servers and Secondary Key Servers IP addresses/Hostname.
Step 11 Click Add Row or Delete to add or delete the secondary key server. If you want to edit the secondary key server, click on the Row or Field and edit the IP address of the key server.
Step 12 In the Migration section, check the Enable Passive SA check box to enable passive SA. Use this option to turn on the Passive SA mode on this group member.
For a list and description of elements on the GETVPN Group Member template page, see Table 4-6.
Note After you create the template, publish it to make it available for deployment.
Step 13 Click Save As New Template.
The template you created appears under My Templates.
Step 14 Click the Publish icon to publish the template so it can be deployed.
Use the GETVPN Key Server template to create the template.
To create a GETVPN Key Server template:
Step 1 Choose Design > Configuration > Features Technologies > Security > GETVPN-KeyServer.
The GETVPN-KeyServer Configuration Template page opens.
Step 2 In the Template Basic section, enter a name, description, and author in the appropriate fields.
Step 3 From the Validation Criteria drop-down list, choose a device type from the drop-down list and enter the OS version.
Step 4 In the Group Information section, enter the group name and group ID.
Step 5 Click the IKE Authentication Policy + button to add the IKE authentication information. The IKE Authentication Policy dialog box opens.
Step 6 Click the Pre-Shared key radio button or the Digital Certificate radio button.
Step 7 In the IKE Authentication Policy section, click Add Row to add the IKE policies.
Step 8 In the IKE Policy section, click Add Row and add the IKE policies. Click on the Row or Field to edit the parameters. Select the IKE policies from the list and click Delete to delete the IKE policies.
Step 9 Enter the WAN IP address of the device and check the Dead Peer Detection (DPD) check box to enable DPD on all key servers, to effectively keep track of the states of other key servers.
Step 10 In the Key Server Profile section, select the Rekey tab, and choose the Distribution method from the drop-down list. Enter the required information in the Rekey section.
Step 11 To encrypt rekey messages, use the RSA key. You can either select the existing RSA key from the drop-down list or click the + button to create a new RSA key.
Step 12 To generate an RSA key, provide the key label and modulus. Check the Exportable key check box, if you want to export the certificate.
Step 13 In the Add KeyServer dialog box, select the GETVPN Traffic tab, and enter the traffic to be encrypted, the encryption policy, and anti-replay.
Step 14 Choose the Rekey Encryption algorithm from the drop-down list to encrypt the rekey.
Step 15 In the Key Server Profile page, click the GETVPN Traffic tab.
Step 16 In the GETVPN Traffic dialog box, enter the Traffic to be encrypted, the encryption policy, and anti-replay.
Step 17 Click the Encryption Policy + button to add the transform sets that are to be part of this encryption policy.
Step 18 In the Migration section, check the Enable Receive Only SA Feature to send traffic in clear text to all group members. This feature can decrypt any arriving encrypted traffic.
Note After you create the template, publish it to make it available for deployment.
Step 19 Click Save As New Template.
The template you created appears under My Templates.
Step 20 Click the Publish icon to publish the template so it can be deployed.
For a list and descriptions of elements on the GETVPN Key Server template page, see Table 4-7.
This task enables you to deploy the GETVPN group member and key server template.
Note Before you can deploy your template to devices, you must publish the template.
To deploy the GETVPN template:
Step 1 Choose Deploy > Configuration Tasks > My Templates.
Step 2 On the My Templates page, select the GETVPN-GroupMember or KeyServer template, and click the Tasked View button.
Step 3 From the Deploy Task Pad, click Deploy.
The Template Deployment page opens.
Step 4 From the Device Selection section, select the device and the location.
Step 5 In the Value Assignment section, click the radio button to select the device.
Step 6 For GETVPN-GroupMember, you can change the values for Registration Interface, Enable Passive SA, Local Exception Policy ACL, and Fail Close ACL.
Step 7 For GETVPN Key Server, you can change the values for Keyserver, WAN IP Address, ACL, Priority, and Cooperative servers.
Step 8 If you changed the values, click Apply. For elements on the page, refer to Table 4-6 and Table 4-7.
Step 9 Click the Schedule section, enter the Job Name, then click one of the following radio buttons:
•Run—To run the job immediately.
•Run at Schedule Time—To specify a time to run the job.
Step 10 Under Summary, verify your entries, then click OK.
In addition to creating new configuration templates, you can import configurations from Cisco Prime LAN Management Solution (LMS). If you have "golden" templates in Cisco Prime LMS, you can import those configurations into Prime NCS (WAN) and save them as configuration templates that you can deploy to the devices in your network.
Before you import a configuration, you must first export and save the configuration from Cisco Prime LMS.
Step 1 Choose Design > Configuration Templates.
Step 2 Expand the CLI Template folder, then choose the CLI template.
Step 3 Click the Import icon at the top right of the CLI template page.
Step 4 Browse to the configuration .xml file that you previously exported from Cisco Prime LMS, then click OK.
Step 5 Navigation to the My Templates folder and choose the configuration you imported.
Step 6 To view the contents of the configuration, click the CLI Content tab.
To view the parameters defined in the configuration, click the Form View tab. These values are read-only.
To change any of the variables defined in the configuration, click Manage Variables.
Step 7 Click the Publish icon to publish the template so it can be deployed.
Step 8 Click the Go to Deployment icon and go to the Deploy > Configuration Tasks page.
Step 9 Click Deploy on the template you published.
Step 10 Specify the deployment options as explained in Specifying Template Deployment Options.
Step 11 Click OK.
The most common reasons that a template might not be deployed are:
•One or more devices are unreachable—Verify that the device credentials are correct; ping the device to verify that it is reachable. (See Using 360° View for more information.)
•A device CLI returned an error because the CLI was incorrect—Verify that the CLI commands contained in the template are correct by running the commands on a test device.