17-5
Software Configuration Guide—Release 15.0(2)SG
OL-23818-01
Chapter 17 Configuring Auto SmartPort Macros Configuring Auto SmartPorts
If the macro conflicts with the original configuration, some macro commands might not be applied,
or some antimacro commands might not be applied. (The antimacro is the portion of the applied
macro that removes it at link down.)
Note Failure of one command in the macro halts the application of the entire macro.
For example, if 802.1X authentication is enabled, you cannot remove switchport-mode access
configuration. You must remove the 802.1X authentication before removing the configuration.
A port should not be a member of an EtherChannel when applying Auto SmartPorts macros.
If Auto SmartPort is not yet enabled globally, disable Auto SmartPort on all the EtherChannel ports
before enabling it globally. If Auto SmartPort is already enabled, shut down the port and disable it
before adding the port to an EtherChannel.
Note If an Auto SmartPort macro is applied on an interface, EtherChannel configuration usually fails
because of conflict with the auto-QoS configuration applied by the macro.
The built-in macro default data VLAN is VLAN 1. The default voice VLAN is VLAN 2. You should
modify the built-in macro default values if your switch uses different VLANs. To view all built-in
macro default values, use the show shell functions privileged EXEC command.
To detect non-Cisco devices for 802.1X authentication or MAB, configure the RADIUS server to
support the Cisco AV pair auto-smart-port=event trigger. You must configure a user-defined
trigger with the value returned in the AV pair for auto-smart-port.
For stationary devices that do not support CDP, MAB, or 802.1X authentication, such as network
printers, we recommend that you disable Auto SmartPorts on the port.
If authentication is enabled on a port, the switch ignores CDP unless the fallback cdp keyword is
in the macro auto global processing global configuration command.
The order of CLI commands within the macro and the corresponding antimacro can differ.
Before converting a port into an Layer 3 interface, enter the no macro auto processing command.
This prevents Auto SmartPort from applying macros on the interface. If Layer 3 is already
configured, enter the no macro auto processing command on the Layer 3 interface enable Auto
SmartPort globally.
Auto SmartPort and SmartPorts cannot coexist on an interface.
A switch applies a macro in accordance with the LLDP advertisement from the attached device. If
the device does not identify itself properly, the wrong macro is applied. Consult the specific device
documentation to ensure the device's firmware is current.
The LWAP’s WLC software v ersion must be 6.0.188 ( => Cisco IOS 12.4(21a)JA2) or later to make
it detectable as LWAP by AutoSmartPort.
As of Cisco IOS Release 12.2(54)SG, Auto SmartPort does not support macros that apply
EtherChannel configurations. Interfaces that belong to EtherChannel groups are treated as standard
interfaces. You can apply macros on individual interfaces based on the device type but the CLIs in
the macro (for example, auto-QoS) might conflict with an EtherChannel configuration. We
recommend that you disable Auto SmartPort on interfaces belonging to EtherChannels before you
enable Auto SmartPort globally. If Auto SmartPort is already enabled, disable Auto SmartPort on
the interfaces before configuring EtherChannel.