Network Management Configuration Guide, Cisco IOS XE Gibraltar 16.12.x (Catalyst 9200 Switches) - Configuring Autoconf [Support] (2023)

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

Information about Autoconf

The following sections provide information about Autoconf.

Benefits of Autoconf

The Autoconf feature permits hardbinding between an end device and an interface. Autoconf falls under the umbrella of the Cisco Smart Operations solution. Smart Operations is a comprehensive set of capabilities that can simplify and improve LAN switch deployment, and help organizations deliver operational excellence and scale services on the network.

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

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

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

  • The Autoconf feature provides built-in and user-defined configurations using interface and service templates. 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 making them intuitive and autoconfigurable. This reduces operation expenses (OPEX) and lowers the total cost of ownership (TCO).

Identity Session Management and Templates

A key advantage of the Autoconf feature is that the core session management capability is decoupled from the application-specific logic, allowing the same framework to be used regardless of the criteria for policy determination or the nature of the policies applied.

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

Both service and interface templates are named as containers of configuration and policy. Service templates can be applied only to access sessions, while interface templates can be applied only to ports. When a service template is applied to an access session, the contained configuration and policy are applied only to the target session, and has no impact on other sessions that may be hosted on the same access port. Similarly, when an interface 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 designed based on best practices for interface configurations. Built-in templates can be modified by users to include customized 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 on a device and can be mapped to any built-in or user-defined trigger.

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

Autoconf Operation

Autoconf 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 the Device Classifier.

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

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

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

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

Network Management Configuration Guide, Cisco IOS XE Gibraltar 16.12.x (Catalyst 9200 Switches) - Configuring Autoconf [Support] (1)
Note

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

The template that is selected is based on parameter map information applied to an interface. This information can 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 the following configuration:

Parameter-map name: BUILTIN_DEVICE_TO_TEMPLATE Map: 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
Network Management Configuration Guide, Cisco IOS XE Gibraltar 16.12.x (Catalyst 9200 Switches) - Configuring Autoconf [Support] (2)
Note

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

The Autoconf feature provides one built-in policy map (BUILTIN_AUTOCONF_POLICY) with the following configuration:
BUILTIN_AUTOCONF_POLICY event identity-update match-all 10 class always do-until-failure 10 map attribute-to-service table BUILTIN_DEVICE_TO_TEMPLATE
Network Management Configuration Guide, Cisco IOS XE Gibraltar 16.12.x (Catalyst 9200 Switches) - Configuring Autoconf [Support] (3)
Note

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

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 Services Engine (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 access sessions, 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 template returned 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 defined or sourced from the AAA server, the interface template must be applied to the interface hosting an access-session on which the service template is applied. (Add a new command for interface template reference from within a locally defined service template.)
  • Subscriber control-policy action: A mapping action under the subscriber control policy activates service or interface template (as referenced in a parameter map) or both based on the type of filter, and removes templates, if any, associated with a previous policy.
  • Device-to-template parameter map: A subscriber parameter map that allows the filter type-to-service or interface template mappings or both to be specified in an efficient and readable manner.

Advantages of Using Templates

Using templates for auto configuration has the following benefits:

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

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

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

  • Service templates are applied to access sessions and hence only impact the traffic exchanged with a single endpoint 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 framework by using all the available techniques, including link-up or link-down.

  • Templates can be updated with a single operation. All the applied instances of templates are also updated during 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 actions when failures occur.

  • Data VLAN, quality of service (QoS) parameters, storm control, and MAC-based port security are configured 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 disconnected from a port.

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

Autoconf Functionality

The Autoconf feature is disabled by default in global configuration mode. When you enable the Autoconf feature in global configuration mode, it is enabled by default at the interface level. The built-in template configurations 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 interface level, 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
Global Interface Level AutoConf Status
Disable Disable No automatic configurations are applied when an end device is connected.
Enable Enable If Autoconf is enabled at the global level, it is also enabled at the interface level by default. Built-in template configurations are applied based on the end devices that are detected on all the interfaces.
Enable Disable Enabled at global level. Disabled at interface level. No automatic configurations are applied when an end device is connected to the interface on which Autoconf is disabled.

Autoconf allows you to retain the template even when the link to the end device is down or the end device is disconnected, by configuring the autoconf sticky feature access-session interface-template sticky command in global configuration mode. The Autoconf sticky feature avoids the need for detecting the end device and applying 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 contains access-session commands on an interface. Configure the access-session interface-template sticky command to apply interface template on a port using a service policy.

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

How to Configure Autoconf

The following sections provide information about how to configure Autoconf.

Applying a Built-In Template to an End Device

The 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

Command or Action Purpose
Step1

enable

Example:

Device> enable

Enables privileged EXEC mode. Enter your password if prompted.

Step2

configure terminal

Example:

Device(config)# configure terminal

Enters global configuration mode.

Step3

autoconf enable

Example:

Device(config)# autoconf enable

Enables the Autoconf feature.

Step4

end

Example:

Device(config)# end

Exits global configuration mode and enters privileged EXEC mode.

Step5

show device classifier attached interface interface-type interface-number

Example:

Device# show device classifier attached interface Gi3/0/26

(Optional) Displays whether the end device is classified by the device classifier with correct attributes.

Step6

show template binding target interface-type interface-number

Example:

Device# show template binding target gi3/0/26

Displays the configuration applied through the template on the interface.

Example

The following example shows that an IP phone is classified by the device classifier with correct attributes:

Device# show device classifier attached interface GigabitEthernet 3/0/26Summary: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/26Interface 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 template is 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!EndDevice# show derived-config interface GigabitEthernet 3/0/26Building configuration...Derived configuration : 649 bytes!interface GigabitEthernet3/0/26 switchport mode access switchport block unicast switchport port-security maximum 3 switchport port-security maximum 2 vlan access switchport port-security violation restrict switchport port-security aging time 2 switchport port-security aging type inactivity switchport port-security load-interval 30 storm-control broadcast level pps 1k storm-control multicast level pps 2k storm-control action trap spanning-tree portfast spanning-tree bpduguard enable service-policy input AutoConf-4.0-CiscoPhone-Input-Policy service-policy output AutoConf-4.0-Output-Policy ip dhcp snooping limit rate 15end

The following example shows how to verify the global configuration after configuring Autoconf:

Device# show running configclass-map match-any AutoConf-4.0-Scavenger-Queue match dscp cs1 match cos 1 match access-group name AutoConf-4.0-ACL-Scavengerclass-map match-any AutoConf-4.0-VoIP match dscp ef match cos 5class-map match-any AutoConf-4.0-Control-Mgmt-Queue match cos 3 match dscp cs7 match dscp cs6 match dscp cs3 match dscp cs2 match access-group name AutoConf-4.0-ACL-Signalingclass-map match-any AutoConf-4.0-Multimedia-Conf match dscp af41 match dscp af42 match dscp af43class-map match-all AutoConf-4.0-Broadcast-Vid match dscp cs5class-map match-any AutoConf-4.0-Bulk-Data match dscp af11 match dscp af12 match dscp af13class-map match-all AutoConf-4.0-Realtime-Interact match dscp cs4class-map match-any AutoConf-4.0-VoIP-Signal match dscp cs3 match cos 3class-map match-any AutoConf-4.0-Trans-Data-Queue match cos 2 match dscp af21 match dscp af22 match dscp af23 match access-group name AutoConf-4.0-ACL-Transactional-Dataclass-map match-any AutoConf-4.0-VoIP-Data match dscp ef match cos 5class-map match-any AutoConf-4.0-Multimedia-Stream match dscp af31 match dscp af32 match dscp af33class-map match-all AutoConf-4.0-Internetwork-Ctrl match dscp cs6class-map match-all AutoConf-4.0-VoIP-Signal-Cos match cos 3class-map match-any AutoConf-4.0-Multimedia-Stream-Queue match dscp af31 match dscp af32 match dscp af33class-map match-all AutoConf-4.0-Network-Mgmt match dscp cs2class-map match-all AutoConf-4.0-VoIP-Data-Cos match cos 5class-map match-any AutoConf-4.0-Priority-Queue match cos 5 match dscp ef match dscp cs5 match dscp cs4class-map match-any AutoConf-4.0-Bulk-Data-Queue match cos 1 match dscp af11 match dscp af12 match dscp af13 match access-group name AutoConf-4.0-ACL-Bulk-Dataclass-map match-any AutoConf-4.0-Transaction-Data match dscp af21 match dscp af22 match dscp af23class-map match-any AutoConf-4.0-Multimedia-Conf-Queue match cos 4 match dscp af41 match dscp af42 match dscp af43 match access-group name AutoConf-4.0-ACL-Multimedia-Confclass-map match-all AutoConf-4.0-Network-Ctrl match dscp cs7class-map match-all AutoConf-4.0-Scavenger match dscp cs1class-map match-any AutoConf-4.0-Signaling match dscp cs3 match cos 3!!policy-map AutoConf-4.0-Cisco-Phone-Input-Policy class AutoConf-4.0-VoIP-Data-Cos set dscp ef police cir 128000 bc 8000 exceed-action set-dscp-transmit cs1 exceed-action set-cos-transmit 1 class AutoConf-4.0-VoIP-Signal-Cos set dscp cs3 police cir 32000 bc 8000 exceed-action set-dscp-transmit cs1 exceed-action set-cos-transmit 1 class class-default set dscp default set cos 0policy-map AutoConf-4.0-Output-Policy class AutoConf-4.0-Scavenger-Queue bandwidth remaining percent 1 class AutoConf-4.0-Priority-Queue priority police cir percent 30 bc 33 ms class AutoConf-4.0-Control-Mgmt-Queue bandwidth remaining percent 10 class AutoConf-4.0-Multimedia-Conf-Queue bandwidth remaining percent 10 class AutoConf-4.0-Multimedia-Stream-Queue bandwidth remaining percent 10 class AutoConf-4.0-Trans-Data-Queue bandwidth remaining percent 10 dbl class AutoConf-4.0-Bulk-Data-Queue bandwidth remaining percent 4 dbl class class-default bandwidth remaining percent 25 dblpolicy-map AutoConf-DMP class class-default set dscp cs2policy-map AutoConf-IPVSC class class-default set cos dscp table AutoConf-DscpToCospolicy-map AutoConf-4.0-Input-Policy class AutoConf-4.0-VoIP class AutoConf-4.0-Broadcast-Vid class AutoConf-4.0-Realtime-Interact class AutoConf-4.0-Network-Ctrl class AutoConf-4.0-Internetwork-Ctrl class AutoConf-4.0-Signaling class AutoConf-4.0-Network-Mgmt class AutoConf-4.0-Multimedia-Conf class AutoConf-4.0-Multimedia-Stream class AutoConf-4.0-Transaction-Data class AutoConf-4.0-Bulk-Data class AutoConf-4.0-Scavenger

Applying a Modified Built-In Template to an End Device

The following task shows how to modify a built-in template when multiple wireless access points and IP cameras are connected to a switch.

Procedure

Command or Action Purpose
Step1

enable

Example:

Device> enable

Enables privileged EXEC mode. Enter your password if prompted.

Step2

configure terminal

Example:

Device(config)# configure terminal

Enters global configuration mode.

Step3

template template-name

Example:

Device(config)# template AP_INTERFACE_TEMPLATE

Enters template configuration mode for the built-in template.

Step4

switchport access vlan vlan-id

Example:

Device(config-template)# switchport access vlan 20

Sets the VLAN when the interface is in access mode.

Step5

description description

Example:

Device(config-template)# description modifiedAP

Modifies the description of the built-in template.

Step6

exit

Example:

Device(config-template)# exit

Exits template configuration mode and enters global configuration mode.

Step7

autoconf enable

Example:

Device(config)# autoconf enable

Enables the Autoconf feature.

Step8

end

Example:

Device(config)# end

Exits global configuration mode and enters privileged EXEC mode.

Step9

show template interface binding all

Example:

Device# show template interface binding all 

Displays whether the template is applied on the interface.

Example

The following example shows that an IP camera and access points are classified by the device classifier with correct attributes:

Device# show device classifier attached detailDC default profile file version supported = 1Detail:MAC_Address Port_Id Cert Parent Proto ProfileType Profile Name Device_Name===================================================================================================001d.a1ef.23a8 Gi1/0/7 30 3 C M Default Cisco-AIR-AP-1130 cisco AIR-AP1131AG-A-K9001e.7a26.eb05 Gi1/0/30 70 2 C M Default Cisco-IP-Camera Cisco IP 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 macro auto global command.

Procedure

Command or Action Purpose
Step1

enable

Example:

Device> enable

Enables privileged EXEC mode. Enter your password if prompted.

Step2

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

Step3

no macro auto global processing

Example:

Device(config)# no macro auto global processing 

Disables ASP on a global level.

Step4

exit

Example:

Device(config)# exit

Exits global configuration mode and returns to privileged EXEC mode.

Step5

clear macro auto configuration all

Example:

Device# clear macro auto configuration all 

Clears macro configurations for all interfaces.

Step6

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

Step7

autoconf enable

Example:

Device(config)# autoconf enable

Enables the Autoconf feature.

Step8

end

Example:

Device(config)# end

Exits global configuration mode and returns to privileged EXEC mode.

Configuring Platform Type Filter

The following tasks shows how to configure platform type filter for class maps and parameter maps.

Configuring a Platform Type Filter for a Class Map

A control class defines the conditions under which the actions of a control policy are executed. You should define whether all, any, or none of the conditions must be evaluated to execute the actions of the control policy. Platform types are evaluated based on the specified platform name in the control policy.

Procedure
Command or Action Purpose
Step1

enable

Example:
Device> enable

Enables privileged EXEC mode. Enter your password if prompted.

Step2

configure terminal

Example:
Device# configure terminal

Enters global configuration mode.

Step3

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

Example:
Device(config)# class-map type control subscriber match-all DOT1X_NO_AGENT

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

  • match-all : Must match all the conditions in the control class.

  • match-any : Must match at least one condition in the control class.

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

Step4

match platform-type platform-name

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

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

Step5

end

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

Exits control class-map filter mode and returns to privileged EXEC mode.

Step6

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

Example:
Device# show class-map type control subscriber all

(Optional) Displays information about control policies for all the class maps or a specific class map.

Configuring a Platform Type Filter for a Parameter Map

We recommend that you use the parameter map.

Procedure
Command or Action Purpose
Step1

enable

Example:
Device> enable

Enables privileged EXEC mode. Enter your password if prompted.

Step2

configure terminal

Example:
Device# configure terminal

Enters global configuration mode.

Step3

parameter-map type subscriber attribute-to-service parameter-map-name

Example:
Device(config)# parameter-map type subscriber attribute-to-service Aironet-Policy-para

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

Step4

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

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

Specifies the parameter map attribute filter criteria to the platform type.

Step5

end

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

Exits parameter-map filter mode and returns to privileged EXEC mode.

Step6

show parameter-map type subscriber attribute-to-service{all | name parameter-map-name}

Example:
Device# show parameter-map type subscriber attribute-to-service

(Optional) Displays the parameter map attributes.

Configuration Examples for Autoconf

The 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 an interface:

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

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

The following example shows how to apply a modified built-in template to an end device and verify the 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 Autoconf

The following example shows how to migrate from ASP to Autoconf:
Device> enableDevice# configure terminalDevice(config)# no macro auto global processing Device(config)# exitDevice# clear macro auto configuration all Device# configure terminalDevice(config)# autoconf enableDevice(config)# end

Example: Configuring a Platform Type Filter

The 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#

Additional References for Autoconf

Related Documents

Related Topic

Document Title

Cisco identity-based networking services commands

Cisco IOS Identity-Based Networking Services Command Reference

Interface Templates

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

Standards and RFCs

Standard/RFC

Title

IEEE 802.1X

Port Based Network Access Control

Technical Assistance

Description

Link

The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.

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

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

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

Feature Information for Autoconf

The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. 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.
Table 2. Feature Information for Autoconf

Feature Name

Releases

Feature Information

Autoconf

Cisco IOS XE Fuji 16.9.1

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 type subscriber attribute-to-service all , show template interface .

AutoConf Device Granularity to PID of Cisco Switch

Cisco IOS XE Gibraltar 16.12.1

The platform type filter option has been introduced for class map and parameter map configurations.

References

Top Articles
Latest Posts
Article information

Author: Horacio Brakus JD

Last Updated: 13/10/2023

Views: 5520

Rating: 4 / 5 (51 voted)

Reviews: 90% of readers found this page helpful

Author information

Name: Horacio Brakus JD

Birthday: 1999-08-21

Address: Apt. 524 43384 Minnie Prairie, South Edda, MA 62804

Phone: +5931039998219

Job: Sales Strategist

Hobby: Sculling, Kitesurfing, Orienteering, Painting, Computer programming, Creative writing, Scuba diving

Introduction: My name is Horacio Brakus JD, I am a lively, splendid, jolly, vivacious, vast, cheerful, agreeable person who loves writing and wants to share my knowledge and understanding with you.