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
mls qos trust dscp
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:
Command |
Description |
access-session
|
Configures access session specific interface commands.
|
authentication
|
Configures authentication manager Interface Configuration commands.
|
carrier-delay
|
Configures delay for interface transitions.
|
dampening
|
Enables event dampening.
|
default
|
Sets a command to its defaults.
|
description
|
Configures interface-specific description.
|
dot1x
|
Configures interface configuration commands for IEEE 802.1X.
|
hold-queue
|
Sets hold queue depth.
|
ip
|
Configures IP template.
|
keepalive
|
Enables keepalive.
|
load-interval
|
Specifies interval for load calculation for an interface.
|
mab
|
Configures MAC authentication bypass Interface.
|
mls
|
Enables multilayer switching configurations. This command is available on the following devices in template configuration
mode:
-
Cisco Catalyst 2960-S Series Switches
-
Cisco Catalyst 2960-X Series Switches
-
Cisco Industrial Ethernet 3000 Series Switches
|
peer
|
Configures peer parameters for point to point interfaces.
|
priority-queue
|
To set the priority-queue size for a template. This command is available on the following devices in template configuration
mode:
-
Cisco Catalyst 2960-S Series Switches
-
Cisco Catalyst 2960-X Series Switches
-
Cisco Industrial Ethernet 3000 Series Switches
|
queue-set
|
Configures the QoS queue set on a template. This command is available on the following devices in template configuration mode:
-
Cisco Catalyst 2960-S Series Switches
-
Cisco Catalyst 2960-X Series Switches
-
Cisco Industrial Ethernet 3000 Series Switches
|
radius-server
|
Enables RADIUS server configurations. This command is available on the following devices in template configuration mode:
-
Catalyst 4500E Supervisor Engine 7-E
-
Catalyst 4500E Supervisor Engine 7L-E
-
Catalyst 4500E Supervisor Engine 8-E
-
Catalyst 4500-X Series Switches
|
service-policy
|
Configures CPL service policy.
|
source
|
Gets configurations from another source.
|
spanning-tree
|
Configures spanning tree subsystem
|
storm-control
|
Configures storm control.
|
subscriber
|
Configures subscriber inactivity timeout value.
|
switchport
|
Sets switching mode configurations
|
trust
|
Sets trust value for the interface.
|
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.
|