configuringautoconf - cisco - global home page · class-map match-any autoconf-4.0-multimedia-conf...

Configuring Autoconf

The following sections provide information about Autoconf and how to configure Autoconf:

• Prerequisites for Autoconf, on page 1• Restrictions for Autoconf, on page 1• Information about Autoconf , on page 2• How to Configure Autoconf, on page 7• Configuration Examples for Autoconf, on page 15• Additional References for Autoconf, on page 17• Feature Information for Autoconf, on page 17

Prerequisites for Autoconf• Before enabling Autoconf, disable the Auto SmartPort (ASP) macro, device classifier, and then accessthe session monitor.

Restrictions for Autoconf• ASP macro and Autoconf are not supported on the same interface at the same time. Either Autoconf orASP must be disabled on a per-interface level.

• Interface templates are not applicable for wireless sessions.

• When the Autoconf feature is enabled using the autoconf enable command, the default Autoconf servicepolicy is applied to all the interfaces. No other service policy can be applied globally using theservice-policy command. To apply a different service policy, you must disable Autoconf on that interface.When a service policy is applied globally, you must disable it before enabling the Autoconf feature.

• When both local (interface level) and global service policies exist, the local policy takes precedence. Theglobal service policy comes into effect only when the local policy is removed.

• Service templates cannot be applied to interfaces, and interface templates cannot be applied to serviceinstances.

• Only one service template can be nested inside an interface template.

Configuring Autoconf1

Information about AutoconfThe following sections provide information about Autoconf.

Benefits of AutoconfThe Autoconf feature permits hardbinding between an end device and an interface. Autoconf falls under theumbrella of the Cisco Smart Operations solution. Smart Operations is a comprehensive set of capabilities thatcan simplify and improve LAN switch deployment, and help organizations deliver operational excellence andscale services on the network.

The Autoconf feature automatically applies the necessary configurations on the device ports to enable theefficient performance of each directly connected end device using a set of interface configurations that areconfigured inside an interface template:

• Autoconf efficiently applies commands to an interface because the parser does not need to parse eachcommand each time.

• Configurations that are applied through the Autoconf feature can be reliably removed from a port withoutimpacting previous or subsequent configurations on the port.

• The Autoconf feature provides built-in and user-defined configurations using interface and servicetemplates. Configurations applied through templates can be centrally updated with a single operation.

• Using the Autoconf feature, a configuration can be applied to ports and access sessions.

• The Autoconf feature reduces ongoing maintenance for devices and attached end devices by makingthem intuitive and autoconfigurable. This reduces operation expenses (OPEX) and lowers the total costof ownership (TCO).

Identity Session Management and TemplatesA key advantage of the Autoconf feature is that the core session management capability is decoupled fromthe application-specific logic, allowing the same framework to be used regardless of the criteria for policydetermination or the nature of the policies applied.

The identity session management infrastructure allows configurations or policies or both to be applied astemplates.

Both service and interface templates are named as containers of configuration and policy. Service templatescan be applied only to access sessions, while interface templates can be applied only to ports. When a servicetemplate is applied to an access session, the contained configuration and policy are applied only to the targetsession, and has no impact on other sessions that may be hosted on the same access port. Similarly, when aninterface template is applied to an access port, it impacts all the traffic exchanged on the port.

The Autoconf feature uses a set of built-in maps and built-in templates. The built-in templates are designedbased on best practices for interface configurations. Built-in templates can be modified by users to includecustomized configurations, limiting the need to create a new template.

The templates created by users are referred to as user-defined templates. These templates can be defined ona device and can be mapped to any built-in or user-defined trigger.


Configuring AutoconfInformation about Autoconf

Use the show derived-config command, to view the overall applied configurations applied by Autoconftemplate andmanual configuration. The interface commands shown in the output of the show running-configinterface type number command are not necessarily the operational configuration. The Autoconf featuredynamically applies a template to the interface, and overrides any conflicting static configuration that is alreadyapplied.

Autoconf OperationAutoconf uses the Device Classifier to identify the end devices that are connected to a port.

The Autoconf feature uses the device classification information gleaned from Cisco Discovery Protocol,LLDP, DHCP, MAC addresses, and the Organizationally Unique Identifier (OUI) that is identified by theDevice Classifier.

The Device Classifier provides improved device classification capabilities and accuracy, and increased devicevisibility for enhanced configuration management.

Device classification is enabled when you enable the Autoconf feature using the autoconf enable commandin global configuration mode.

The device detection acts as an event trigger, which in turn applies the appropriate automatic template to theinterface.

The Autoconf feature is based on a three-tier hierarchy.

• A policy map identifies the trigger type for applying the Autoconf feature.

• A parameter map identifies the appropriate template that must be applied, based on the end device.

• The templates contain the configurations to be applied.

The Autoconf built-in templates and triggers perform the above tasks automatically.

The Autoconf feature provides the following built-in templates:

• AP_INTERFACE_TEMPLATE

• DMP_INTERFACE_TEMPLATE

• IP_CAMERA_INTERFACE_TEMPLATE

• IP_PHONE_INTERFACE_TEMPLATE

• LAP_INTERFACE_TEMPLATE

• MSP_CAMERA_INTERFACE_TEMPLATE

• MSP_VC_INTERFACE_TEMPLATE

• PRINTER_INTERFACE_TEMPLATE

• ROUTER_INTERFACE_TEMPLATE

• SWITCH_INTERFACE_TEMPLATE

• TP_INTERFACE_TEMPLATE


Configuring AutoconfAutoconf Operation

By default, built-in templates are not displayed under running configuration. The built-in templates aredisplayed in the running configuration only if you edit them.

Note

The template that is selected is based on parameter map information applied to an interface. This informationcan be based on the following criteria:

• End Device type

• MAC address

• OUI

• Platform type

• User role

• Username

The Autoconf feature provides one built-in parameter map (BUILTIN_DEVICE_TO_TEMPLATE) with thefollowing configuration:Parameter-map name: BUILTIN_DEVICE_TO_TEMPLATEMap: 10 map device-type regex "Cisco-IP-Phone"Action(s):20 interface-template IP_PHONE_INTERFACE_TEMPLATE

Map: 20 map device-type regex "Cisco-IP-Camera"Action(s):20 interface-template IP_CAMERA_INTERFACE_TEMPLATE

Map: 30 map device-type regex "Cisco-DMP"Action(s):20 interface-template DMP_INTERFACE_TEMPLATE

Map: 40 map oui eq "00.0f.44"Action(s):20 interface-template DMP_INTERFACE_TEMPLATE

Map: 50 map oui eq "00.23.ac"Action(s):20 interface-template DMP_INTERFACE_TEMPLATE

Map: 60 map device-type regex "Cisco-AIR-AP"Action(s):20 interface-template AP_INTERFACE_TEMPLATE

Map: 70 map device-type regex "Cisco-AIR-LAP"Action(s):20 interface-template LAP_INTERFACE_TEMPLATE

Map: 80 map device-type regex "Cisco-TelePresence"Action(s):20 interface-template TP_INTERFACE_TEMPLATE

Map: 90 map device-type regex "Surveillance-Camera"Action(s):10 interface-template MSP_CAMERA_INTERFACE_TEMPLATE

Map: 100 map device-type regex "Video-Conference"Action(s):10 interface-template MSP_VC_INTERFACE_TEMPLATE

Use the show parameter-map type subscriber attribute-to-service All command to view the configurationfor the built-in parameter map.

Note


Configuring AutoconfAutoconf Operation

TheAutoconf feature provides one built-in policymap (BUILTIN_AUTOCONF_POLICY)with the followingconfiguration:BUILTIN_AUTOCONF_POLICYevent identity-update match-all10 class always do-until-failure10 map attribute-to-service table BUILTIN_DEVICE_TO_TEMPLATE

Use the show policy-map type control subscriber BUILTIN_AUTOCONF_POLICY command to viewthe configuration for the built-in policy map.

Note

You can also manually create policy maps, parameter maps, and templates.

When a trigger is created that is based on specific user information, a local 802.1X Cisco Identity ServicesEngine (ISE) server authenticates it, ensuring the security of the operation.

An interface template can be dynamically activated (on an interface) using any of the following methods:

• RADIUS CoA: While Change of Authorization (CoA) commands are targeted at one or more accesssessions, any referenced template must be applied to the interface that is hosting the referenced session.

• RADIUS Access-Accept for client authentication or authorization: Any referenced interface templatereturned in an Access-Accept must be applied to the port that is hosting the authorized access session.

• Service template: If an interface template is referenced in a service template that is either locally definedor sourced from the AAA server, the interface template must be applied to the interface hosting anaccess-session on which the service template is applied. (Add a new command for interface templatereference from within a locally defined service template.)

• Subscriber control-policy action: A mapping action under the subscriber control policy activates serviceor interface template (as referenced in a parameter map) or both based on the type of filter, and removestemplates, if any, associated with a previous policy.

• Device-to-template parameter map: A subscriber parameter map that allows the filter type-to-service orinterface template mappings or both to be specified in an efficient and readable manner.

Advantages of Using TemplatesUsing templates for auto configuration has the following benefits:

• Templates are parsed once when they are being defined. This makes the dynamic application of thetemplates very efficient.

• Templates can be applied to an Ethernet interface that is connected to an end device, based on the typeof end device.

• Service templates allow the activation of session-oriented features, whereas interface templates applyconfigurations to the interface that is hosting a session.

• Service templates are applied to access sessions and hence only impact the traffic exchanged with a singleendpoint on a port.

• Startup and running configurations of a device are not modified by the dynamic application of a template.

• Policy application is synchronized with the access-session life cycle. This is tracked by the frameworkby using all the available techniques, including link-up or link-down.


Configuring AutoconfAdvantages of Using Templates

• Templates can be updated with a single operation. All the applied instances of templates are also updatedduring this operation.

• Constituent commands of templates do not appear in the running configuration.

• Templates can be removed with no impact on previous or subsequent configurations.

• Template application is acknowledged, allowing for synchronization and performance of remedial actionswhen failures occur.

• Data VLAN, quality of service (QoS) parameters, storm control, and MAC-based port security areconfigured automatically based on the end device that is connected to the switch.

• The switch port is cleaned up completely by removing configurations when the device is disconnectedfrom a port.

• Human error is reduced in the installation and configuration process.

Autoconf FunctionalityThe Autoconf feature is disabled by default in global configuration mode. When you enable the Autoconffeature in global configuration mode, it is enabled by default at the interface level. The built-in templateconfigurations are applied based on the end devices detected on all the interfaces.

Use the access-session inherit disable autoconf command to manually disable Autoconf at the interfacelevel, even when Autoconf is enabled at the global level.

If you disable Autoconf at the global level, all the interface-level configurations are disabled.

Table 1: Autoconf Functionality

AutoConf StatusInterface LevelGlobal

No automatic configurations are applied when an end device isconnected.

DisableDisable

If Autoconf is enabled at the global level, it is also enabled atthe interface level by default. Built-in template configurationsare applied based on the end devices that are detected on all theinterfaces.

EnableEnable

Enabled at global level. Disabled at interface level. No automaticconfigurations are applied when an end device is connected tothe interface on which Autoconf is disabled.

DisableEnable

Autoconf allows you to retain the template even when the link to the end device is down or the end device isdisconnected, by configuring the autoconf sticky feature access-session interface-template sticky commandin global configuration mode. The Autoconf sticky feature avoids the need for detecting the end device andapplying the template every time the link flaps or the device is removed and connected back.

The access-session interface-template sticky command is mandatory to apply an inbuilt template that containsaccess-session commands on an interface. Configure the access-session interface-template sticky commandto apply interface template on a port using a service policy.

To disable the Autoconf feature on a specific interface, use the access-session inherit disableinterface-template-sticky command in interface configuration mode.


Configuring AutoconfAutoconf Functionality

How to Configure AutoconfThe following sections provide information about how to configure Autoconf.

Applying a Built-In Template to an End DeviceThe following task shows how to apply a built-in template on an interface that is connected to an end device,for example, a Cisco IP phone.

Before you begin

Make sure that the end device, for example, a Cisco IP phone, is connected to a switch port.

Procedure

PurposeCommand or Action

Enables privileged EXEC mode. Enter yourpassword if prompted.

enable

Example:

Step 1

Device> enable

Enters global configuration mode.configure terminal

Example:

Step 2

Device(config)# configure terminal

Enables the Autoconf feature.autoconf enable

Example:

Step 3

Device(config)# autoconf enable

Exits global configuration mode and entersprivileged EXEC mode.

end

Example:

Step 4

Device(config)# end

(Optional) Displays whether the end device isclassified by the device classifier with correctattributes.

show device classifier attached interfaceinterface-type interface-number

Example:

Step 5

Device# show device classifier attachedinterface Gi3/0/26

Displays the configuration applied through thetemplate on the interface.

show template binding target interface-typeinterface-number

Example:

Step 6

Device# show template binding targetgi3/0/26


Configuring AutoconfHow to Configure Autoconf

Example

The following example shows that an IP phone is classified by the device classifier with correctattributes:Device# show device classifier attached interface GigabitEthernet 3/0/26

Summary:

MAC_Address Port_Id Profile Name Device Name============== ========== ================== ===================0026.0bd9.7bbb Gi3/0/26 Cisco-IP-Phone-7962 Cisco IP Phone 7962

The following example shows that a built-in interface template is applied on an interface:Device# show template binding target GigabitEthernet 3/0/26

Interface Templates===================Interface: Gi4/0/11Method Source Template-Name------ ------ -------------dynamic Built-in IP_PHONE_INTERFACE_TEMPLATE

The following example shows how to verify the interface configuration after the interface templateis applied to an IP phone connected to the GigabitEthernet interface 3/0/26:Device# show running-config interface GigabitEthernet 3/0/26Building configuration...

Current configuration : 624 bytes!interface GigabitEthernet3/0/26!End

Device# show derived-config interface GigabitEthernet 3/0/26

Building configuration...

Derived configuration : 649 bytes!interface GigabitEthernet3/0/26switchport mode accessswitchport block unicastswitchport port-security maximum 3switchport port-security maximum 2 vlan accessswitchport port-security violation restrictswitchport port-security aging time 2switchport port-security aging type inactivityswitchport port-securityload-interval 30storm-control broadcast level pps 1kstorm-control multicast level pps 2kstorm-control action trapspanning-tree portfastspanning-tree bpduguard enableservice-policy input AutoConf-4.0-CiscoPhone-Input-Policyservice-policy output AutoConf-4.0-Output-Policyip dhcp snooping limit rate 15


Configuring AutoconfApplying a Built-In Template to an End Device

end

The following example shows how to verify the global configuration after configuring Autoconf:Device# show running configclass-map match-any AutoConf-4.0-Scavenger-Queuematch dscp cs1match cos 1match access-group name AutoConf-4.0-ACL-Scavengerclass-map match-any AutoConf-4.0-VoIPmatch dscp efmatch cos 5class-map match-any AutoConf-4.0-Control-Mgmt-Queuematch cos 3match dscp cs7match dscp cs6match dscp cs3match dscp cs2match access-group name AutoConf-4.0-ACL-Signalingclass-map match-any AutoConf-4.0-Multimedia-Confmatch dscp af41match dscp af42match dscp af43class-map match-all AutoConf-4.0-Broadcast-Vidmatch dscp cs5class-map match-any AutoConf-4.0-Bulk-Datamatch dscp af11match dscp af12match dscp af13class-map match-all AutoConf-4.0-Realtime-Interactmatch dscp cs4class-map match-any AutoConf-4.0-VoIP-Signalmatch dscp cs3match cos 3class-map match-any AutoConf-4.0-Trans-Data-Queuematch cos 2match dscp af21match dscp af22match dscp af23match access-group name AutoConf-4.0-ACL-Transactional-Dataclass-map match-any AutoConf-4.0-VoIP-Datamatch dscp efmatch cos 5class-map match-any AutoConf-4.0-Multimedia-Streammatch dscp af31match dscp af32match dscp af33class-map match-all AutoConf-4.0-Internetwork-Ctrlmatch dscp cs6class-map match-all AutoConf-4.0-VoIP-Signal-Cosmatch cos 3class-map match-any AutoConf-4.0-Multimedia-Stream-Queuematch dscp af31match dscp af32match dscp af33class-map match-all AutoConf-4.0-Network-Mgmtmatch dscp cs2class-map match-all AutoConf-4.0-VoIP-Data-Cosmatch cos 5class-map match-any AutoConf-4.0-Priority-Queuematch cos 5match dscp efmatch dscp cs5match dscp cs4



class-map match-any AutoConf-4.0-Bulk-Data-Queuematch cos 1match dscp af11match dscp af12match dscp af13match access-group name AutoConf-4.0-ACL-Bulk-Dataclass-map match-any AutoConf-4.0-Transaction-Datamatch dscp af21match dscp af22match dscp af23class-map match-any AutoConf-4.0-Multimedia-Conf-Queuematch cos 4match dscp af41match dscp af42match dscp af43match access-group name AutoConf-4.0-ACL-Multimedia-Confclass-map match-all AutoConf-4.0-Network-Ctrlmatch dscp cs7class-map match-all AutoConf-4.0-Scavengermatch dscp cs1class-map match-any AutoConf-4.0-Signalingmatch dscp cs3match cos 3!!policy-map AutoConf-4.0-Cisco-Phone-Input-Policyclass AutoConf-4.0-VoIP-Data-Cosset dscp efpolice cir 128000 bc 8000exceed-action set-dscp-transmit cs1exceed-action set-cos-transmit 1

class AutoConf-4.0-VoIP-Signal-Cosset dscp cs3police cir 32000 bc 8000exceed-action set-dscp-transmit cs1exceed-action set-cos-transmit 1

class class-defaultset dscp defaultset cos 0

policy-map AutoConf-4.0-Output-Policyclass AutoConf-4.0-Scavenger-Queuebandwidth remaining percent 1class AutoConf-4.0-Priority-Queueprioritypolice cir percent 30 bc 33 msclass AutoConf-4.0-Control-Mgmt-Queuebandwidth remaining percent 10class AutoConf-4.0-Multimedia-Conf-Queuebandwidth remaining percent 10class AutoConf-4.0-Multimedia-Stream-Queuebandwidth remaining percent 10class AutoConf-4.0-Trans-Data-Queuebandwidth remaining percent 10dbl

class AutoConf-4.0-Bulk-Data-Queuebandwidth remaining percent 4dbl

class class-defaultbandwidth remaining percent 25dbl

policy-map AutoConf-DMPclass class-defaultset dscp cs2

policy-map AutoConf-IPVSC



class class-defaultset cos dscp table AutoConf-DscpToCos

policy-map AutoConf-4.0-Input-Policyclass AutoConf-4.0-VoIPclass AutoConf-4.0-Broadcast-Vidclass AutoConf-4.0-Realtime-Interactclass AutoConf-4.0-Network-Ctrlclass AutoConf-4.0-Internetwork-Ctrlclass AutoConf-4.0-Signalingclass AutoConf-4.0-Network-Mgmtclass AutoConf-4.0-Multimedia-Confclass AutoConf-4.0-Multimedia-Streamclass AutoConf-4.0-Transaction-Dataclass AutoConf-4.0-Bulk-Dataclass AutoConf-4.0-Scavenger

Applying a Modified Built-In Template to an End DeviceThe following task shows how to modify a built-in template when multiple wireless access points and IPcameras are connected to a switch.

Procedure



enable

Example:

Step 1

Device> enable


Example:

Step 2

Device(config)# configure terminal

Enters template configuration mode for thebuilt-in template.

template template-name

Example:

Step 3

Device(config)# templateAP_INTERFACE_TEMPLATE

Sets the VLAN when the interface is in accessmode.

switchport access vlan vlan-id

Example:

Step 4

Device(config-template)# switchportaccess vlan 20

Modifies the description of the built-in template.description description

Example:

Step 5

Device(config-template)# descriptionmodifiedAP

Exits template configuration mode and entersglobal configuration mode.

exit

Example:

Step 6


Configuring AutoconfApplying a Modified Built-In Template to an End Device

PurposeCommand or ActionDevice(config-template)# exit


Example:

Step 7


Exits global configuration mode and entersprivileged EXEC mode.

end

Example:

Step 8

Device(config)# end

Displays whether the template is applied on theinterface.

show template interface binding all

Example:

Step 9

Device# show template interface bindingall

Example

The following example shows that an IP camera and access points are classified by the device classifierwith correct attributes:Device# show device classifier attached detail

DC default profile file version supported = 1

Detail:MAC_Address Port_Id Cert Parent Proto ProfileType Profile NameDevice_Name===================================================================================================001d.a1ef.23a8 Gi1/0/7 30 3 C M Default Cisco-AIR-AP-1130 ciscoAIR-AP1131AG-A-K9001e.7a26.eb05 Gi1/0/30 70 2 C M Default Cisco-IP-Camera CiscoIP Camera

The following example shows that the built-in interface template is applied on an interface:Device# show template interface binding all

Template-Name Source Method Interface------------- ------ ------ ---------IP_CAMERA_INTERFACE_TEMPLATE Built-in dynamic Gi1/0/30AP_INTERFACE_TEMPLATE Modified-Built-in dynamic Gi1/0/7

Migrating from ASP to Autoconf

Before you begin

Verify that the AutoSmart Port (ASP) macro is running by using the show running-config | include macroauto global command.


Configuring AutoconfMigrating from ASP to Autoconf

Procedure



enable

Example:

Step 1

Device> enable


Example:

Step 2

Device# configure terminal

Disables ASP on a global level.no macro auto global processing

Example:

Step 3

Device(config)# no macro auto globalprocessing

Exits global configuration mode and returns toprivileged EXEC mode.

exit

Example:

Step 4

Device(config)# exit

Clears macro configurations for all interfaces.clear macro auto configuration all

Example:

Step 5

Device# clear macro auto configurationall


Example:

Step 6



Example:

Step 7


Exits global configuration mode and returns toprivileged EXEC mode.

end

Example:

Step 8

Device(config)# end

Configuring Platform Type FilterThe following tasks shows how to configure platform type filter for class maps and parameter maps.

Configuring a Platform Type Filter for a Class MapA control class defines the conditions under which the actions of a control policy are executed. You shoulddefine whether all, any, or none of the conditions must be evaluated to execute the actions of the controlpolicy. Platform types are evaluated based on the specified platform name in the control policy.


Configuring AutoconfConfiguring Platform Type Filter

Procedure



enable

Example:

Step 1

Device> enable


Example:

Step 2


Creates a control class and enters controlclass-map filter mode.

class-map type control subscriber {match-all| match-any | match-none} control-class-name

Step 3

Example: • match-all: Must match all the conditionsin the control class.Device(config)# class-map type control

subscriber match-all DOT1X_NO_AGENT• match-any: Must match at least onecondition in the control class.

• match-none: Must not match any of theconditions in the control class.

Creates a condition to evaluate control classesbased on the specified platform type.

match platform-type platform-name

Example:

Step 4

Device(config-filter-control-classmap)#match platform-type C3850

Exits control class-map filter mode and returnsto privileged EXEC mode.

end

Example:

Step 5

Device(config-filter-control-classmap)#end

(Optional) Displays information about controlpolicies for all the class maps or a specific classmap.

show class-map type control subscriber {all| name control-class-name}

Example:

Step 6

Device# show class-map type controlsubscriber all

Configuring a Platform Type Filter for a Parameter MapWe recommend that you use the parameter map.

Procedure



enable

Example:

Step 1


Configuring AutoconfConfiguring a Platform Type Filter for a Parameter Map

PurposeCommand or ActionDevice> enable


Example:

Step 2


Specifies the parameter map type and name,and enters parameter-map filter mode.

parameter-map type subscriberattribute-to-service parameter-map-name

Example:

Step 3

Device(config)# parameter-map typesubscriber attribute-to-serviceAironet-Policy-para

Specifies the parameter map attribute filtercriteria to the platform type.

map-index map platform-type {{eq | not-eq| regex} filter-name}

Example:

Step 4

Device(config-parameter-map-filter)# 10map platform-type eq C9xxx

Exits parameter-map filter mode and returns toprivileged EXEC mode.

end

Example:

Step 5

Device(config-parameter-map-filter-submode)#end

(Optional) Displays the parameter mapattributes.

show parameter-map type subscriberattribute-to-service{all | nameparameter-map-name}

Step 6

Example:Device# show parameter-map typesubscriber attribute-to-service

Configuration Examples for AutoconfThe following sections provide configuration examples for the Autoconf feature.

Example: Applying a Built-In Template to an End Device

The following example shows how to apply a built-in template to an end device connected to aninterface:Device> enableDevice(config)# configure terminalDevice(config)# autoconf enableDevice(config)# endDevice# show device classifier attached interface Gi3/0/26Device# show template binding target GigabitEthernet 3/0/26


Configuring AutoconfConfiguration Examples for Autoconf

Example: Applying a Modified Built-In Template to an End DeviceThe following example shows how to apply a modified built-in template to an end device and verifythe configuration:Device> enableDevice(config)# configure terminalDevice(config)# template AP_INTERFACE_TEMPLATEDevice(config-template)# switchport access vlan 20Device(config-template)# description modifiedAPDevice(config-template)# exitDevice(config)# autoconf enableDevice(config)# endDevice# show template interface binding all

Example: Migrating from ASP Macros to AutoconfThe following example shows how to migrate from ASP to Autoconf:Device> enableDevice# configure terminalDevice(config)# no macro auto global processingDevice(config)# exitDevice# clear macro auto configuration allDevice# configure terminalDevice(config)# autoconf enableDevice(config)# end

Example: Configuring a Platform Type FilterThe following example shows how to configure a platform type filter for a class map:Device> enableDevice# configure terminalDevice(config)# class-map type control subscriber match-all DOT1X_NO_AGENTDevice(config-filter-control-classmap)# match platform-type C9xxxDevice(config-filter-control-classmap)# endDevice#

The following example shows how to configure a platform type filter for a parameter map:Device> enableDevice# configure terminalDevice(config)# parameter-map type subscriber attribute-to-service Aironet-Policy-paraDevice(config-parameter-map-filter)# 10 map platform-type eq C9xxxDevice(config-parameter-map-filter-submode)# endDevice#


Configuring AutoconfExample: Applying a Modified Built-In Template to an End Device

Additional References for AutoconfRelated Documents

Document TitleRelated Topic

Cisco IOS Identity-Based Networking Services CommandReference

Cisco identity-based networking servicescommands

“Interface Templates” chapter in Identity-Based NetworkingServices Configuration Guide.

Interface Templates

Standards and RFCs

TitleStandard/RFC

Port Based Network Access ControlIEEE 802.1X

Technical Assistance

LinkDescription

http://www.cisco.com/cisco/web/support/index.htmlThe Cisco Support website provides extensive onlineresources, including documentation and tools fortroubleshooting and resolving technical issues withCisco products and technologies.

To receive security and technical information aboutyour products, you can subscribe to various services,such as the Product Alert Tool (accessed from FieldNotices), the Cisco Technical Services Newsletter, andReally Simple Syndication (RSS) Feeds.

Access to most tools on the Cisco Support websiterequires a Cisco.com user ID and password.

Feature Information for AutoconfThe following table provides release information about the feature or features described in this module. Thistable lists only the software release that introduced support for a given feature in a given software releasetrain. Unless noted otherwise, subsequent releases of that software release train also support that feature.

Use Cisco Feature Navigator to find information about platform support and Cisco software image support.To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.


Configuring AutoconfAdditional References for Autoconf

http://www.cisco.com/en/US/docs/ios-xml/ios/ibns/command/ibns-cr-book.html

http://www.cisco.com/en/US/docs/ios-xml/ios/ibns/command/ibns-cr-book.html

https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ibns/configuration/15-e/ibns-15-e-book.html

https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ibns/configuration/15-e/ibns-15-e-book.html

http://www.cisco.com/cisco/web/support/index.html

http://www.cisco.com/go/cfn

Table 2: Feature Information for Autoconf

Feature InformationReleasesFeature Name

This feature was introduced.

The following commands were added or modified:autoconf enable, map attribute-to-service(autoconf),map device-type (service-template),parameter-map type subscriber(service-template), show parameter-map typesubscriber attribute-to-service all, showtemplate interface.

Cisco IOS XE Everest16.6.1

Autoconf

The platform type filter option has beenintroduced for class map and parameter mapconfigurations.

Cisco IOS XE Gibraltar16.12.1

AutoConfDeviceGranularityto PID of Cisco Switch


Configuring AutoconfFeature Information for Autoconf