An interface template is a container of configurations or policies that can be applied to specific ports. When an interface template is applied to an access port, it impacts all traffic that is exchanged on the port.

There are two types of interface templates; user and builtin templates. Builtin templates are created by the system.

You can modify builtin templates. If you delete a modified builtin template the system restores the original definition of the template.

The following are the available builtin templates:

• AP_INTERFACE_TEMPLATE (Access Point)

• DMP_INTERFACE_TEMPLATE (Digital Media Player)

• IP_CAMERA_INTERFACE_TEMPLATE

• IP_PHONE_INTERFACE_TEMPLATE

• LAP_INTERFACE_TEMPLATE (Lightweight Access Point)

• MSP_CAMERA_INTERFACE_TEMPLATE

• MSP_VC_INTERFACE_TEMPLATE (Video Conferencing)

• PRINTER_INTERFACE_TEMPLATE

• ROUTER_INTERFACE_TEMPLATE

• SWITCH_INTERFACE_TEMPLATE

• TP_INTERFACE_TEMPLATE (TelePresence)

Following is an example of a builtin interface template:

Template Name       : IP_CAMERA_INTERFACE_TEMPLATE
Modified            : No
Template Definition :
 spanning-tree portfast
 spanning-tree bpduguard enable
 switchport mode access
 switchport block unicast
 switchport port-security
 srr-queue bandwidth share 1 30 35 5
 priority-queue out 
!

You can also create specific user templates with the commands that you want to include.

Note	The template name must not contain spaces.

You can create an interface template using the template command in global configuration mode. In template configuration mode, enter the required commands. The following commands can be entered in template configuration mode:

Note

System builtin templates are not displayed in the running configuration. These templates show up in the running configuration only if you edit them. The stateful switchover fails if access-session and swithcport mode access are both configured in an interface template. To avoid the switchover failure, configure the switchport mode access command on the interface, instead of in an interface template. When you configure an interface template, it is recommended that you enter all the required dependent commands on the same template. It is not recommended to configure the dependent commands on two different templates.

Each template can be bound to a target. Template binding or sourcing can be either static or dynamic. Static binding of a template involves binding the template to a target, like an interface. Only one template can be bound at a time using static binding. Static binding of another template to the same target will unbind the previously bound template. To configure static binding, use the source template command in interface configuration mode.

Any number of templates can be bound dynamically to a target. To configure dynamic binding using builtin policy maps and parameter maps, enable the autoconf feature using the autoconf enable command.

Note	You can have statically and dynamically bind templates on the same interface at a time.

Configuration applied through dynamically-bound templates has the highest priority, followed by configuration applied directly on the interface, and then configuration applied through statically-bound templates. When similar commands are present at different priority levels, the one at the highest priority is applied. If a configuration at a higher priority level is not applied, then the configuration with the next highest priority is applied to the target.

Multiple templates can be dynamically bound to a target. When multiple templates are dynamically bound, the template that is applied last has the highest priority.

To delete a template, you must remove the binding to all targets. If you bind a template that does not exist, a new template is created with no configurations.