Open as PDF
Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0
Appendix B Working with Templates and Data Files
Using Templates with Service Requests
• If you change the template associated with a service request, the negate template automatically
changes to the negate template of the newly selected template. In this case, ISC executes the negate
template of the previously associated template, as well as the newly associated template.
• When a template or negate template is modified, the service request does not roll back the
configuration changes made earlier through the template.
• When a service request is modified, the template command is always deployed. (See the remaining
bullet items for some additional clarifications.)
• When a service request is modified without changing template/data file information, the template
commands are not redeployed. The only a modification that triggers a change in template/data file
results is the negation of the old template and the addition of new template commands in the device
• When the ForceTemplateDeploy DCPL property is turned ON then, irrespective of templates being
modified, if a service request is modified, templates are re-deployed. However, negate templates are
not necessarily re-deployed. Negate templates are deployed only when a link/attachment circuit in
the service request is deleted, which implicitly means removing templates associated with the link
being deleted as well. When the ForceTemplateDeploy DCPL property is turned OFF, negate
templates are instantiated under the following conditions:
Deleting or decommissioning a link/attachment circuit in a service request.
Modifying templates (for example, delete existing templates and adding new ones to a link, or
deleting only existing ones).
Rehoming links/devices in a service request that has associated templates.
• When a device is changed in a service request, the negate template is deployed for the old device,
and the template is deployed for the new device.
• When a link in a service request is removed and a new link is added, a negate template is deployed
for the deleted link and a template is deployed for the added link.
Using Templates and Data Files with Service Requests
This section describes tasks related to templates, data files, and negate templates that can be performed
in the service request workflow. The following tasks are covered:
• Choosing a Template in the Service Request Workflow, page B-14
• Creating a Data File in the Service Request Workflow, page B-16
• Decommissioning Service Requests with Added Templates, page B-18
• Viewing Templates from the Service Requests Window, page B-18
Choosing a Template in the Service Request Workflow
When creating a service request, the workflow involves selecting a policy on which to base the service
request, setting interface and other attributes, and so on. The specific windows and attributes presented
in the workflow depend on the type of service request, such as L2VPN, VPLS, MPLS, or FlexUNI/EVC.
To associate templates and data files in a service request, you must select a link in the appropriate
window of the Service Request Editor window, usually by clicking the Add link for the device.