Cisco Configuring Autoconf: Руководство по настройке и конфигурации

Restrictions for Autoconf

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 16 Additional References for Autoconf, on page 18 Feature History for Autoconf, on page 18 Prerequisites for Autoconf • Before enabling Autoconf, disable the Auto SmartPort (ASP) macro, device classifier, and then access the session monitor. Restrictions for Autoconf • ASP macro and Autoconf are not supported on the same interface at the same time.

Either Autoconf or ASP 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 service policy is applied to all the interfaces. No other service policy can be applied globally using the service-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.

The global 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 service instances. • Only one service template can be nested inside an interface template. • Autoconf does not support the switchover feature. Configuring Autoconf 1

Page 1

Identity Session Management and Templates

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. Configuring Autoconf Information about Autoconf Configuring Autoconf 2

Page 2

Autoconf Operation

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 Configuring Autoconf Autoconf Operation Configuring Autoconf 3

Page 3

Autoconf Operation

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. Note 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" 20 interface-template DMP_INTERFACE_TEMPLATE Map: 40 map oui eq "00.0f.44" Action(s): Action(s): 20 interface-template DMP_INTERFACE_TEMPLATE Map: 50 map oui eq "00.23.ac" 20 interface-template DMP_INTERFACE_TEMPLATE Map: 60 map device-type regex "Cisco-AIR-AP" Action(s): Action(s): 20 interface-template AP_INTERFACE_TEMPLATE Map: 70 map device-type regex "Cisco-AIR-LAP" 20 interface-template LAP_INTERFACE_TEMPLATE Map: 80 map device-type regex "Cisco-TelePresence" Action(s): Action(s): 20 interface-template TP_INTERFACE_TEMPLATE Map:

90 map device-type regex "Surveillance-Camera" 10 interface-template MSP_CAMERA_INTERFACE_TEMPLATE Map: 100 map device-type regex "Video-Conference" Action(s): Action(s): 10 interface-template MSP_VC_INTERFACE_TEMPLATE Use the show parameter-map type subscriber attribute-to-service All command to view the configuration for the built-in parameter map. Note Configuring Autoconf Autoconf Operation Configuring Autoconf 4

Page 4